Fixing ERR_SSL_PROTOCOL_ERROR and SSL handshake errors

“This site can’t provide a secure connection” (ERR_SSL_PROTOCOL_ERROR), SSL_ERROR_RX_RECORD_TOO_LONG and “SSL handshake failed” mean the browser and server couldn’t agree on a secure connection at all. It usually means HTTPS isn’t set up for that address yet, or something on the visitor’s side is interfering.

If you own the website

1. Is there a certificate for this exact address? In cPanel, open SSL/TLS Status and check the domain and www have a green padlock. If not, click Run AutoSSL. See Why AutoSSL didn’t issue a certificate.

2. Does the domain point to Ruachost? If DNS still points to an old host, visitors reach a server with no certificate for your site. Check your nameservers and A record. See My DNS changes aren’t working.

3. Using Cloudflare? A brand-new domain on Cloudflare can take up to 24 hours to get its edge certificate. Check SSL/TLS → Edge Certificates in Cloudflare.

4. Recently installed a paid certificate? Make sure the certificate, private key and CA bundle all match. Reinstall in SSL/TLS → Manage SSL sites using Autofill by Certificate.

If only some visitors see it

The problem is usually on their device or network:

• Check the device’s date and time are correct.
• Clear the browser cache and SSL state, or try another browser.
• Turn off antivirus “HTTPS scanning” or a VPN temporarily.
• Try a different network, such as mobile data. Some public or office networks interfere with HTTPS.
• Update the browser and operating system. Very old devices may not support the modern TLS versions our servers use. See TLS and cipher suites update.

Still not working? Open a support ticket with your domain, the exact error and which browser shows it.