Is this your problem?
- Chrome and Edge: "This site can't provide a secure connection" with ERR_SSL_PROTOCOL_ERROR
- Firefox: "Secure Connection Failed", or SSL_ERROR_NO_CYPHER_OVERLAP
- The site may load on an old device or browser but not a current one
- Plain http sometimes works while https fails
- A security scanner reports the server only supports old TLS 1.0 or 1.1
What usually causes it
How to tell: Modern browsers refuse TLS 1.0 and 1.1. If the server does not offer TLS 1.2 or 1.3, there is nothing safe to agree on and the handshake fails.
How to tell: The server answers on port 443 but has no valid certificate for this domain, so the secure channel cannot be set up.
How to tell: A rule sends every request to https, but https was never set up on the server, so every visit dead-ends.
How to tell: An intermediate certificate is missing, which some browsers tolerate and others reject.
How to tell: On one computer only, local security software or a work proxy can break the handshake. Test another network first.
Before you touch anything
- Check whether it fails for everyone or only you: open the site on your phone over mobile data. If it works there, the problem is your local network or antivirus, not the site.
- Run a free SSL test (such as an SSL Labs report) on your domain. It lists the protocols offered, the certificate, and any chain problems in plain terms.
How to fix it, step by step
-
1
Rule out your own machine first
Open the site on another device and network. If it loads, pause any local antivirus HTTPS scanning, clear the browser SSL state, and try again. Nothing on the server needs touching.
-
2
Read the SSL test report
The report shows the protocols the server offers. If it lists only TLS 1.0 or 1.1, the server must be set to offer TLS 1.2 and 1.3. On managed hosting this is a support request; on your own server it is a line in the web-server configuration.
-
3
Reissue or install a valid certificate
If the report says there is no certificate, or the wrong name, issue a free Let's Encrypt or AutoSSL certificate in the host panel for this exact domain, covering both www and non-www.
-
4
Fix a forced-https redirect with no https behind it
If a redirect pushes everything to https but https is not set up, either set up the certificate first, or remove the forced redirect until it is. Forcing https before the certificate exists locks the whole site out.
-
5
Add the missing certificate chain
If the test reports an incomplete chain, reinstall the certificate including the intermediate (chain or bundle) file your provider supplies. Most one-click installers do this for you.
-
6
If it is behind Cloudflare
Set the SSL/TLS mode to Full (strict) only when your server has a valid certificate. Flexible mode is a common cause of loops and errors. Do not turn on Always Use HTTPS while the origin server has no certificate.
Stop and get help if
- The SSL report shows only old TLS and you are on managed hosting, where only the host can change it. Open a ticket and quote the report.
- The site is a shop or booking system losing sales while it is unreachable.
- You do not have access to the server or DNS and cannot tell what changed.
Stop it happening again
- Keep the server offering current protocols only, TLS 1.2 and 1.3, and let the host manage it.
- Use auto-renewing certificates so a lapse never breaks the handshake.
- Test the site on a current browser after any host move or SSL change, not only your own cached one.
- Monitor SSL so a configuration slip emails you before customers find it.
Questions people ask
It works for me but customers say it fails. Why?
Your browser may have cached a working connection, or your device still allows an old protocol theirs refuses. Trust the SSL report, not one browser.
Is ERR_SSL_PROTOCOL_ERROR a hack?
Almost never. It is a configuration problem on the server or the local machine, not a break-in.
Can I just turn https off?
No. Browsers flag http sites as not secure and Google ranks them lower. The fix is a working certificate, not dropping https.