How to fix the “This site can’t provide a secure connection” error (6 methods)

The “This site can’t provide a secure connection” error appears when your browser can’t establish a secure HTTPS connection with a website. It usually points to an SSL/TLS certificate issue, incorrect system date and time, cached browser data, or a server configuration problem.

You can fix the error as a visitor or a site owner, depending on the cause. Visitors clear the browser and SSL cache, correct the device’s date and time, or disable browser features like QUIC. Site owners install or reinstall the SSL certificate and force HTTP traffic to HTTPS. The sections below walk through each method step by step, then explain what causes the error and how different browsers display it.

If you prefer a visual guide to fixing this error, watch the video tutorial below.

1. Install an SSL certificate

Installing an SSL certificate is one of the most effective website troubleshooting methods to fix “This site can’t provide a secure connection” error if you’re the site owner. The exact steps vary by web hosting provider.

At Hostinger, you can install an SSL certificate on hPanel:

1. Go to the SSL section and click the Install free SSL button.

2. Choose a domain and select Install SSL.

3. Once the website address shows a green check mark and Active status, the SSL is successfully installed. If not, make sure the domain is pointing to Hostinger nameservers.

This method should solve the Can’t Provide a Secure Connection issue on your website.

2. Force an HTTPS connection

By forcing HTTPS, visitors will automatically get redirected to the secure URL once they load your website.

If you’re a Hostinger user, follow these instructions to force an HTTPS connection on your site:

1. Head to Security → SSL from the hPanel dashboard.
2. Click the three-dot button next to the problematic domain and select Force HTTPS.

This should allow you to open the website. If the issue persists, try the next method.

3. Reinstall the SSL certificate

An invalid or broken SSL installation can cause your website to show “This site can’t provide a secure connection” error. The best way to solve it is by reinstalling the SSL certificate.

Here’s how to do it on hPanel:

1. Head to Security → SSL from the hPanel dashboard.
2. Click the three-dot button next to the problematic domain and choose Reinstall.

4. Reset the SSL cache and clear browser cache

If the solutions above don’t work, try resetting the SSL cache on the computer and clearing the browser history. This will allow you to start a new connection.

Follow these instructions to reset the SSL cache on Windows:

1. Type Control Panel on the Windows search tab.
2. On the Network and Internet panel, select View network status and tasks, and click Internet Options.

3. Once the Internet Properties box opens, choose the Content tab and click Clear SSL state.

To clear data on the Google Chrome browser, click the three dots on the upper right-hand corner of the display → More tools → Clear browsing data.

5. Turn off the QUIC protocol support

Another common solution is to disable the QUIC protocol support on the Google Chrome browser.

Follow these steps to do it:

1. Type chrome://flags/#enable-quic on the address bar.
2. Find the Experimental QUIC protocol option, usually placed at the top of the page.
3. Click the drop-down box and choose Disabled.

4. Relaunch the browser for the changes to take effect.

If turning off the protocol didn’t solve the problem, proceed to the next method.

6. Check the date and time settings

Certificate validity is a crucial element in the authentication process. Before accessing a website, the browser will check the SSL certificate’s signed and expiry dates using the system’s date and time settings.

If they are wrong, it may appear the certificate is no longer valid. Thus, adjusting the settings is one of the most effective ways for site visitors to fix the Can’t Provide a Secure Connection error message.

Follow these instructions to set the correct date and time zone on different operating systems, such as Windows and macOS.

Windows

1. Click the Windows Start button and select Settings.
2. Choose Time & Language.

3. Turn on the Set time automatically button. Do the same thing for the Set time zone automatically option.
4. Verify the changes and ensure the settings are correct.

macOS

1. Choose the Apple menu button and click System Settings.
2. Select General in the sidebar and scroll down to find Date & Time.

3. To set the date and time automatically, turn on the Set time and date automatically option. To set it manually, turn off the option and insert the current date and time.
4. To set the time zone automatically, turn on Set time zone automatically using your current location. To set it manually, turn the option off, enter the closest city, and select its full name from the list.

What causes “This site can’t provide a secure connection” error

There are six common reasons a browser displays this error.

No SSL certificate installed

The error message may appear because the website doesn’t have an SSL certificate installed. This means you’re accessing it via an HTTP connection, and the target host sends all requests and responses in plain text.

The data is not encrypted and may be intercepted by third parties to gather information passed between the website server and a browser. This may expose the site to potential cyber attacks such as malware and man-in-the-middle attacks.

HTTPS is not forced on the website

The issue may occur when you’ve installed the SSL certificate but didn’t enable the force HTTPS option. This way, visitors will access the website’s HTTP version instead of the secure URL.

Invalid or expired SSL certificate

You may encounter this error when the website uses an invalid or expired SSL certificate. This means the site currently runs on an HTTP connection.

Outdated SSL cache in the browser

Outdated or corrupt SSL cache in the browser may contribute to the website error. Usually, this can occur when you’re developing web pages or after installing a new SSL certificate.

QUIC protocol is enabled

The Quick UDP Internet Connections (QUIC) protocol is enabled by default on the Google Chrome browser. It is used for reducing connection time, improving congestion control, transporting extensibility, and multiplexing without head-of-line blocking.

However, in some cases, it can cause SSL problems, such as the Site Can’t Provide a Secure Connection issue.

Incorrect time and date settings

Time and date misconfiguration on your computer may lead the Google Chrome browser to block the website. Incorrect information can cause problems during the website certificate authentication process.

As a result, the error occurs.

How different browsers display this error

Browsers may display different error messages. Here’s how it looks on Chrome and Mozilla Firefox.

Google Chrome

If the website you’re trying to visit on Chrome doesn’t support the TLS/SSL protocols required, the browser will show “This Site Can’t Provide a Secure Connection”. It also tells users that the target host sent an invalid response.

Chrome suggests three methods to fix the issue – checking the connection, examining the proxy configuration, and running Windows Network Diagnostics.

Mozilla Firefox

On Firefox, an invalid SSL certificate may take you to the Secure Connection Failed page. The description tells users that the connection to the server was reset while the web page was loading.

Firefox also provides further explanations, saying the browser couldn’t authenticate the received data and asking users to inform the website owner about the error.

How to prevent secure connection errors

Fixing the error is one thing – keeping it from coming back is another. If you own the website, enable SSL certificate auto-renewal, monitor the certificate’s expiry date, and keep your server’s TLS configuration up to date. Using TLS 1.3, or a secure TLS 1.2 and 1.3 setup, helps reduce handshake issues and keeps HTTPS connections reliable.

If you’re a visitor, keep your browser updated and make sure your device’s date and time are correct. This helps prevent browser-side SSL warnings, especially those caused by outdated cache, browser settings, or incorrect system time.

If the page still won’t load and Chrome shows ERR_SSL_PROTOCOL_ERROR, the browser is likely failing to complete the SSL/TLS connection. Work through our guide to fixing the ERR_SSL_PROTOCOL_ERROR next for more targeted troubleshooting.

All of the tutorial content on this website is subject to Hostinger's rigorous editorial standards and values.

The author

Noviantika G.

Noviantika is a web development enthusiast with customer obsession at heart. Linux commands and web hosting are like music to her ears. When she's not writing, Noviantika likes to snuggle with her cats and brew some coffee.

More from Noviantika G.