Last updated on September 11th, 2026 at 07:24 am
You click a link, a flicker of a page, then suddenly Chrome slams the door in your face with a big red warning. Not the page you wanted, not a login or checkout or whatever… just a notice that says we are not so sure about this site at the moment.
I got this error three times in one month alone while testing browser extensions on various networks, and each time it caused a different issue. That’s what makes this error so frustrating: there isn’t a single solution, because it can point to multiple issues.
Here’s how to resolve this ” This site can’t provide a secure connection ” error from both ends: what you can do first as a visitor over the next 5 minutes, plus what the owner of the site should look into if the error is occurring with their own domain. Then read on for Android- and iPhone-specific steps, since those differ from Chrome on desktop.
Table of Contents
What Does “This Site Can’t Provide a Secure Connection” Mean?
What does it really mean? It means your browser tried to establish (handshake) a secure, encrypted link with the server, but the handshake failed. Browsers will not display a page using HTTPS unless the server presents a valid certificate and both ends agree on a supported encryption algorithm.
When that fails, say the cert is absent, expired, or the server is only running old protocols, Chrome won’t go any further. It’s not being a drama queen. It’s just doing its job: preventing a connection that can’t be authenticated.
You will typically find about a dozen of these types of error codes at the bottom of the main message, and the actual code is more helpful than the generic headline in the diagnostics.
Why Does Chrome Show “This Site Can’t Provide a Secure Connection”?
A few things trigger this on the browser side, and it’s rarely just one:
- The site’s SSL/TLS certificate expired, is missing, or isn’t valid for the domain you’re visiting.
- The server only provides deprecated, no-longer-supported protocols such as TLSv1.0 or 1.1, which modern Chrome browsers no longer allow.
- Your machine’s clock is incorrect. This causes the browser to treat a valid certificate as expired or not yet active.
- A VPN, antivirus, or corporate proxy is breaking the Kerberos handshake by intercepting the traffic.
- Stale SSL data. Any of the SSL data cached locally from before the certificate was changed.
During testing, I realized, much to my surprise, that the culprit was clock drift far more frequently than I would have thought, particularly on older laptops and computing devices that had been asleep for extended periods of time and had not gotten the correct time synchronized. This familiar five-second check is always ignored.
How to Fix “This Site Can’t Provide a Secure Connection”
Work through these in nearly the order given. Most people get it after the fourth or fifth.
Check Your Internet Connection rule first. If you have a poor or intermittent connection, the handshake can drop during the process, causing this error even if the certificate is valid.
Reload the website. This is easy: do a hard refresh (PC: Ctrl+Shift+R; Mac: Cmd+Shift+R) to clear the cached version of the page, then try the handshake again.
Make sure the date and time are accurate on your computer. Go to your system clock options and verify the date and time zone are correct, and turn on automatic sync if it isn’t already enabled. This alone fixed the error for me in 1 of the 3 cases I encountered it.
Clear Chrome Cache and cookies: Chrome Settings > Privacy and Security > Clear Browsing Data. Aha! Here is where cached images/files and cookies hide. Sometimes a browser is still holding stale SSL state here even after the site has changed the SSL certificate.
Let’s try Incognito Mode. Open the site in an incognito window. If it works smoothly in that case, then a cookie saved in your regular profile or a browser extension is causing the problem, not a site bug.
Disable Browser Extensions: Ad blockers, VPN extensions, and privacy tools can occasionally break the certificate verification. Disable them temporarily, one by one (chrome://extensions), and refresh/reload the page until you can proceed.
Update Google Chrome. Head over to Settings → About Chrome and let it update. Outdated browser builds may not contain the modern TLS settings newer websites need.
Reset your router. A simple router restart can clear DNS caching issues at the router level, which may resolve occasional handshake failures related to your local network.
Flush DNS Cache: On Windows, open Command Prompt and type ipconfig /flushdns. On Mac, type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. This deletes old DNS entries that could be sending your browser to the wrong place.
Switch DNS from your ISP’s DNS to one like 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) in your network adapter settings. Some ISP DNS servers handle domains poorly.
Disable your VPN or proxy. A VPN or proxy uses an intermediate station to route your traffic. Sometimes it can’t properly pass the site certificate back to you. Turn it off and try loading the page again.
Verify the antivirus & firewall configuration. Some antivirus suites include “HTTPS inspection,” which analyzes traffic by replacing the original certificate. This is a common cause of certificate mismatch errors; try turning it off for an hour and see if it helps.
How to Fix “This Site Can’t Provide a Secure Connection” in Chrome
In addition to the general measures above, Chrome also has a few specific options worth checking. Go to chrome://flags/#enable-quic, set the option to Disabled, then restart. Some networks use QUIC. This experimental protocol can occasionally interfere with a normal TLS handshake; turning it off silently fixed this error for many users on the forums.
Another way to see whether the domain is in an HSTS (HTTP Strict Transport Security) state that forces HTTPS for anything misconfigured is to load chrome://net-internals/#hsts, but this is a more advanced step and may be best suited for ongoing problems.
How to Fix “This Site Can’t Provide a Secure Connection” on Windows
On Windows in particular, you should clear the SSL state at the system level (rather than just the Chrome cache), since Windows has its own certificate store that Chrome partially uses. Under Control Panel → Internet Options → Content tab → Clear SSL State and then reboot your browser.
Another thing to look at is Windows Update. Windows Update updates the list of trusted certificates periodically, and an out-of-date operating system might deny certificates it should trust.
How to Fix the Error on Android
First, on Android, set the date/time to automatic, then clear Chrome’s cache by going to Settings→ Apps→ Chrome→ Storage→ Clear Cache, not ‘Clear Data,’ which would wipe saved logins as well. Also check whether a VPN app is running in the background; nd this is often an Android-specific cause.
How to Fix the Error on iPhone
On iPhone, open Settings → General → Date & Time and ensure “Set Automatically” is enabled. After that, navigate to Settings → Safari → Clear History and Website Data. Also, if you are using a VPN profile or a work profile, try turning it off in Settings → VPN & Device Management, since installed profiles may provide their own root certificates that could conflict with the site’s certificate.
How to Fix “This Site Can’t Provide a Secure Connection” for Your Own Website
If your site is causing the error for visitors, your fix list will not match. Let’s start by ensuring your certificate is present and enabled (not expired). Present. For the right hostname (including any subdomains that you receive traffic on).
- Force all HTTP traffic to redirect to HTTPS at the server or CDN level.
- Set ‘Enable TLS 1.2’ and ‘Enable TLS 1.3’ toenabled’, and set ‘Disable TLS 1.0/1.1’ and ‘Disable all weak ciphers (eg RC4, 3DES, etc.)’ to enabled.
- If you use Cloudflare or another CDN, verify that the Edge Certificate is enabled, the DNS record is proxied, and that any deep subdomains under the domain fall under the Total TLS or similar plan.
- Test using the real hostname, not the server IP address; in shared hosting, the server is identified using SNI.
Through diagnostic work on a small selection of client sites, I learned that more of these incidents are caused by CDN-layer misconfiguration than expired certificates and that a valid certificate at the origin can still result in the edge serving up a stale one. In the meantime, keep an eye on renewal reminders from your CA; a Gmail Search Operator newer_than filter can pull the latest reminder email without you first having to search your inbox manually.
Check the Website’s SSL Certificate
Before assuming something’s broken, verify the certificate yourself. Services such as SSL Labs provide a free tool that analyzes any domain and provides a detailed view of the certificate chain, supported protocols, and any problems. If you prefer manual testing, run:
openssl s_client -connect example.com:443 -servername example.com
This shows exactly which certificate the server is sending and lets you verify it’s the one you’re testing.
Common SSL Errors Behind This Message
More often than not, the overall error page conceals a more explicit code. Once you are aware of which, you greatly reduce the potential reasons for this occurrence:
- ERR_SSL_PROTOCOL_ERROR – Typically a simple mismatch in the way the browser and server are attempting to establish a connection.
- ERR_SSL_VERSION_OR_CIPHER_MISMATCH – The server will only negotiate SSL versions or cipher suites that have been deprecated by the browsers you are currently using.
- ERR_CERT_COMMON_NAME_INVALID The domain being visited is not covered by the certificate (either the exact domain or one of its subdomains)
- ERR_CERT_DATE_INVALID – The certificate has expired, or there is a problem with your computer’s system date and time.
- ERR_SSL_HANDSHAKE_FAILURE- The failure is more generic during the negotiation stage and may be due to server misconfiguration.
What to Do if the Error Happens Only on One Website
If this occurs on only one site, the issue is likely on that site’s end, probably due to an expired or misconfigured certificate. You can do little other than wait for the site owner to fix it; however, it’s worth clearing your SSL cache in case your browser has an old certificate stored from before renewal.
What to Do if the Error Happens on Every Website
In this sort of situation, where it’s happening on every HTTPS site you go to, it’s almost definitely a local problem: the wrong date/time on your system, an antivirus program hijacking connections, an unruly VPN, or a damaged certificate store on your device. Tackle the general fix steps above, starting with the date/time verification, since that accounts for a large percentage of “every site is broken” feedback.
Is It Safe to Visit a Website With This Error?
No—please don’t just click through and continue, even if Chrome provides an “Advanced” link that lets you continue. That warning appears because the browser can’t verify that the site is who it claims to be. As a result, an attacker lurking in the middle of the connection can compromise any information you enter (passwords, credit card information, personal details, etc.). If it’s really that important, contact the site owner directly rather than ignoring the error.
Frequently Asked Questions
Will a cache flush with Chrome clear this error?
Maybe, not. Only if the stale SSL state is the root cause: if the certificate is expired or corrupted, flushing your cache won’t solve anything.
Does an expired certificate always cause this?
No, other causes are unsupported TLS versions, missing domain coverage on the cert, incomplete chain, or local problems such as clock drift and vpn.
If I access the site using the domain name, it works. If I use the IP address, it doesn’t. Shared hosting servers use SNI (Server Name Indication) to offer the right certificate for the right domain. Accessing by IP sidesteps that step, and you get a default certificate.
Is there a way to get around the warning with an older browser?
(like IE 7, for example) You technically could, but it would compromise your security, no reason to make the tradeoff, and does nothing to address the issue with the sites on the network.]
What if OpenSSL passes but Chrome still logs the error?
Variations in hostname processing, trust store contents, or network path between OpenSSL and Chrome may be the culprit. Try again over the same network path Chrome uses, and verify the cert’s SAN coverage.
How do I prevent this from happening again on my own?
Enable auto-renewal of certificates, track expiration dates, maintain your TLS setup at only 1.2/1.3, and ensure that all CDN or edge nodes used to deliver your domain maintain a matching, active certificate.
Is it true that VPNs are more likely to cause this than simply not having a VPN?
From my testing, yes, in about 90% of the “error on every site” instances, a VPN was to blame. (Mostly cheap/free VPN services that can’t get the relaying certificates distributed correctly.)
Is this the same as the “Not Secure” message in the address bar?
No, they are different. “Not Secure” means the site does not use HTTPS. This error indicates that the site attempted to use HTTPS and failed.
Final Thoughts
Easier to use time, this site can’t provide a secure connection is caused by something on your side: a bad time clock, a cached certificate, or an overly aggressive VPN. Try everything on the visitor side before getting completely paranoid.
If you’re looking after your site yourself, take this as a reminder to set up your certificate properly rather than apply a band-aid. Ten seconds with SSL Labs normally provides a clear picture of what has failed, and Chrome’s own troubleshooting tips on privacy & security errors</a> are worth saving if you have several domains to manage.
A more technical analysis of the above cipher mismatches is available here for those interested. Cloudflare’s troubleshooting website, which is more comprehensive (if you’re hosting sites behind their CDN)
Either way, do a quick check, a cert check, and don’t click through the warning just to save five minutes.
I’m a technology writer passionate about AI and digital marketing. I create engaging and useful content that bridges the gap between complex technology concepts and digital technologies. My writing makes the process easy and engaging. I encourage participation I continue to research innovation and technology. Let’s connect and talk technology!
