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.

How to Fix “This Site Can’t Provide a Secure Connection”: Certificate sheet with a split embossed seal, with the doxxnet wordmark.
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 network. If the problem is local, check your device’s clock, 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 networks, contact the site owner instead of bypassing the warning. The headline message alone doesn’t tell you the cause.

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.

  1. Verify the address. Make sure you typed the right hostname and HTTPS address, especially if you got here from a link.
  2. Reload once. If the error stays, stop refreshing and read the warning.
  3. Record the exact error code. Use the next section to interpret it. Different secure-connection warnings have different causes.
  4. Try another browser. If only your usual browser fails, follow the browser and device steps below.
  5. Try another device or a trusted network. 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.

CodeWhat failedNext check
ERR_SSL_PROTOCOL_ERRORA general SSL/TLS protocol failure, not necessarily limited to the handshakeCompare browsers, devices and networks to narrow it down
ERR_SSL_VERSION_OR_CIPHER_MISMATCHThe two sides couldn't agree on a protocol or cipherUpdate your browser; the site owner should check supported TLS settings
ERR_CERT_DATE_INVALIDThe certificate's validity dates failed the checkCheck your device clock and the certificate's dates
ERR_CERT_COMMON_NAME_INVALIDThe certificate doesn't cover the hostname you asked forVerify the address; the owner should check hostname coverage
ERR_CERT_AUTHORITY_INVALIDThe certificate's issuer isn't trustedLook at the certificate chain and your device's trust settings
ERR_CONNECTION_CLOSEDThe connection closed. The code doesn't say who closed it or whenCompare environments before blaming anything

A date error usually means the certificate's validity dates need checking, but an inaccurate device clock can also stop validation. 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.

ResultLikely causeNext step
One browser fails; another worksBrowser profile or version differencesUpdate the failing browser, then try a private window
Several browsers on one device failThe device's clock, software, trust or connection settingsFollow the device repair steps and try another device
Several devices on one network failThe network path or a shared configurationTry a trusted separate network and check managed-network settings
One site fails on independent devices and networksThe site's own HTTPS configurationContact 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 suspects). 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 side. 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.

  1. Turn on accurate automatic date and time. Then check the displayed date and time, because a wrong clock prevents reliable certificate validation.
  2. Install browser and operating-system updates. Old browsers and TLS libraries can fail against modern HTTPS servers. Restart the browser afterward.
  3. 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.
  4. Delete only the affected site's stored data, if it seems warranted. This can sign you out. Try again before clearing anything broader.
  5. Disable extensions one at a time. Start with recently added ones, and turn each one back on if it wasn't the culprit before you test the next.
  6. Optionally, clear SSL state on Windows. Open Internet Options, go to Content, choose Clear SSL state, 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.

  1. Compare a trusted, independent connection. Keep the URL the same and note the result.
  2. Complete the network's captive-portal login if there is one. Finish the network login before retrying secure sites. Don't switch the site to plain HTTP to get around it.
  3. Ask the administrator on managed devices. Get authorization before changing proxy or HTTPS-inspection settings.
  4. 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.
  5. Test only the relevant inspection feature. If the problem began after turning on HTTPS scanning, change only that feature for a short time, 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 security 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.

  1. Check validity dates and hostname coverage. Renew or reissue the certificate if needed. A certificate for example.com may not cover www.example.com.
  2. Check the intermediate certificate chain. Set the server to send the full chain, not just the site's own certificate.
  3. 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 suites.
  4. 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 failure. 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.

Ask an AI assistant

Share this article

Private Everywhere

Stop giving the internet everything

Keep your browsing, messages, files, and agents private.