Insights
How to Fix “This Site Can’t Provide a Secure Connection”
Check the error code, compare browsers and networks, and troubleshoot clock, browser, or HTTPS settings without bypassing certificate warnings.

On this page
To fix “This site can’t provide a secure connection,” reload once, note the exact error code, and test the same URL in another browser and on another device or trusted networkOpens in a new tab. If the problem is local, check your device’s clockOpens in a new tab, update your browser, and look at site data, extensions and connection settings one change at a time. If the same website fails across browsers, devices and networksOpens in a new tab, contact the site owner instead of bypassing the warning. The headline message alone doesn’t tell you the causeOpens in a new tab.
In short:
- Don't click through the warning. Find out why it's there.
- Compare: another browser, another device, another network.
- If every setup fails on one site, it's the site's problem. Report it.
Start with these checks before changing settings
Keep the URL identical for every comparison. These checks narrow down the cause. They won't repair every possible problem.
- Verify the address. Make sure you typed the right hostname and HTTPS address, especially if you got here from a link.
- Reload onceOpens in a new tab. If the error stays, stop refreshing and read the warning.
- Record the exact error code. Use the next section to interpret it. Different secure-connection warnings have different causes.
- Try another browserOpens in a new tab. If only your usual browser fails, follow the browser and device steps below.
- Try another device or a trusted networkOpens in a new tab. If the problem follows the network, use the network checks. If one site fails everywhere, go to the owner or reporting section.
Also check whether other HTTPS sites load. A failure on one domain points somewhere different from a failure on many.
Read the code beneath the warning
The code names what failed, but it often leaves several causes open. Match it to the next check instead of trying every fix you find.
| Code | What failed | Next check |
|---|---|---|
ERR_SSL_PROTOCOL_ERROR | A general SSL/TLS protocol failureOpens in a new tab, not necessarily limited to the handshake | Compare browsers, devices and networks to narrow it down |
ERR_SSL_VERSION_OR_CIPHER_MISMATCH | The two sides couldn't agree on a protocol or cipherOpens in a new tab | Update your browser; the site owner should check supported TLS settings |
ERR_CERT_DATE_INVALID | The certificate's validity dates failed the checkOpens in a new tab | Check your device clock and the certificate's dates |
ERR_CERT_COMMON_NAME_INVALID | The certificate doesn't cover the hostname you asked forOpens in a new tab | Verify the address; the owner should check hostname coverage |
ERR_CERT_AUTHORITY_INVALID | The certificate's issuer isn't trustedOpens in a new tab | Look at the certificate chain and your device's trust settings |
ERR_CONNECTION_CLOSED | The connection closed. The code doesn't say who closed it or when | Compare environments before blaming anything |
A date error usually means the certificate's validity dates need checking, but an inaccurate device clock can also stop validationOpens in a new tab. If your date or time is wrong, fix the clock first.
Find out whether the failure follows the site or your setup
Change one thing at a time where you can. Testing another browser on the same device, for example, holds more conditions steady than changing both the device and the network.
| Result | Likely cause | Next step |
|---|---|---|
| One browser fails; another works | Browser profile or version differences | Update the failing browser, then try a private window |
| Several browsers on one device fail | The device's clock, software, trust or connection settings | Follow the device repair steps and try another device |
| Several devices on one network fail | The network path or a shared configuration | Try a trusted separate network and check managed-network settings |
| One site fails on independent devices and networks | The site's own HTTPS configuration | Contact the operator, or inspect the configuration if you run the site |
If it works in a private window, that usually points to something in your browser profile (the usual suspectsOpens in a new tab). Extensions, stored site data and local certificate overrides are all possible, and success doesn't tell you which one it was.
When one website fails on independent setups, the problem is usually on the site's sideOpens in a new tab. If the failure only follows your environment, troubleshoot your browser, device or network first.
Repair browser and device problems one change at a time
Start small and avoid broad resets. After each step, reload the same URL. If nothing changes, undo any temporary setting before you move on.
- Turn on accurate automatic date and time. Then check the displayed date and time, because a wrong clock prevents reliable certificate validationOpens in a new tab.
- Install browser and operating-system updates. Old browsers and TLS libraries can fail against modern HTTPS serversOpens in a new tab. Restart the browser afterward.
- Try a private window. If it works, look at what's specific to your profile instead of assuming the cache or an extension is the cause.
- Delete only the affected site's stored data, if it seems warranted. This can sign you out. Try again before clearing anything broader.
- Disable extensions one at a time. Start with recently added onesOpens in a new tab, and turn each one back on if it wasn't the culprit before you test the next.
- Optionally, clear SSL state on Windows. Open Internet Options, go to Content, choose Clear SSL stateOpens in a new tab, then close and reopen the browser.
Clearing Windows SSL state is a different action from deleting cookies or clearing DNS data. If these checks change nothing, move on to the network or site-side steps instead of repeating them.
Test the network without bypassing HTTPS protection
Try a trusted network first before you disconnect a privacy tunnel or proxy. If the result changes, the connection path or its configuration is worth a closer look. But if you changed several things at once, you won't know which one made the difference.
- Compare a trusted, independent connection. Keep the URL the same and note the result.
- Complete the network's captive-portal login if there is one. Finish the network login before retrying secure sitesOpens in a new tab. Don't switch the site to plain HTTP to get around it.
- Ask the administrator on managed devices. Get authorization before changing proxy or HTTPS-inspection settings.
- If needed and authorized, briefly test a direct connection. Disconnect the tunnel or proxy for a moment, avoid sensitive browsing, and reconnect right away. A success doesn't prove your provider's infrastructure is at fault.
- Test only the relevant inspection feature. If the problem began after turning on HTTPS scanning, change only that feature for a short timeOpens in a new tab, then restore it even if the test fails.
Don't click through certificate warnings, and don't switch off all your security protection. Enabling obsolete SSL or TLS protocols weakens your securityOpens in a new tab and isn't a real fix.
If you own the site, check the HTTPS configuration
This section is for the site's owner or an authorized administrator. Visitors can't fix a website's certificate or server configuration.
- Check validity dates and hostname coverage. Renew or reissue the certificate if needed. A certificate for
example.comOpens in a new tab may not cover Opens in a new tabwww.example.comOpens in a new tab. - Check the intermediate certificate chain. Set the server to send the full chainOpens in a new tab, not just the site's own certificate.
- Check the HTTPS listener and TLS settings. Make sure the service accepts HTTPS connections. Typical fixes include supporting TLS 1.2 and TLS 1.3 and removing obsolete cipher suitesOpens in a new tab.
- Validate, then reload in a controlled way. Check the configuration, keep a rollback path, reload using your server's usual procedure, and retest the hostname.
Use a public TLS checker only for a public hostname you're authorized to test. For private-only services, test from an authorized client inside their network. Reaching a private service and trusting its certificate are two separate requirements.
Know when to stop and report the error
Visitors usually can't repair a site-side HTTPS failureOpens in a new tab. If one site fails on independent setups, contact its operator. If many sites fail on a managed network, contact the network administrator.
Include the hostname, the exact error code, the time of the failure, your browser version and what you compared. Remove tokens, private URL paths and personal information from any screenshots or reports before you send them.
Stop if the next suggested step means bypassing the warning. And don't enter credentials or payment details on a connection whose security warning is still unresolved.