SSL certificates

How to fix ERR_SSL_PROTOCOL_ERROR

ERR_SSL_PROTOCOL_ERROR means the browser and server could not set up a secure connection. Learn the causes, from missing certificates to old TLS versions, and how to fix it.

BeginnercPanel hosting2 min read

ERR_SSL_PROTOCOL_ERROR is a Chrome error shown when the browser cannot complete the SSL/TLS handshake with a website. Firefox shows a similar SSL_ERROR_RX_RECORD_TOO_LONG or PR_END_OF_FILE_ERROR. It can come from your computer (clock, antivirus, cached state) or from the server (no certificate on port 443, broken configuration, outdated TLS).

Before you start

  • Test the site on another device or network to see if the error is local.
  • Run the domain through an SSL checker if you own the site.

Common causes of ERR_SSL_PROTOCOL_ERROR

  • No HTTPS on the server – port 443 serves plain HTTP or nothing for that domain.
  • Wrong DNS – the domain points to a server without the site or certificate.
  • An incorrect system date on your device.
  • Antivirus HTTPS scanning or a proxy breaking the handshake.
  • Outdated TLS – the server only offers TLS 1.0/1.1, which browsers reject.
  • QUIC/HTTP3 problems on certain networks.

How to fix it on your device

  1. Check the date and time and set them to update automatically.
  2. Open a private window to rule out extensions and cache.
  3. Clear the SSL state on Windows: Internet Options → Content → Clear SSL state.
  4. Disable antivirus HTTPS scanning or VPN temporarily.
  5. Try disabling QUIC in chrome://flags if only Chrome fails.

How to fix it on the server

  1. Make sure a certificate is installed. In cPanel → Security → SSL/TLS Status check the domain is covered, and run AutoSSL. If it fails, see AutoSSL not working.
  2. Check DNS points to the right server with nslookup example.com.
  3. Test the handshake with openssl s_client -connect example.com:443 -servername example.com. "wrong version number" means port 443 is serving plain HTTP.
  4. On a VPS, configure the HTTPS virtual host and enable TLS 1.2 and 1.3 only. See Let's Encrypt with Certbot.

Tip: If the error appears right after you added a domain, wait for DNS to point to the server and AutoSSL to run. Until then the domain has no certificate.

What to check afterwards

Open https:// in a private window on two devices and confirm the padlock.

FAQ

Is ERR_SSL_PROTOCOL_ERROR dangerous?

No. The browser simply refused to connect, so no data was sent.

Why does the site work on http but not https?

The server has no working HTTPS setup for the domain. Install a certificate.

Can a firewall cause it?

Yes, network filters that intercept HTTPS can break the handshake.

Next steps

Was this guide helpful?

Still stuck?

Ask MdmHost AI for a quick answer, or open a ticket and our team will take a look. We are here 24/7.

Ask MdmHost AIOpen a ticket

Related guides

SSL certificates

SNI explained: many SSL certificates on one IP address

How Server Name Indication lets a web server pick the right certificate for each domain on a shared IP, how Nginx, Apache and LiteSpeed use it, the default certificate problem and how to test SNI.

3 min read
SSL certificates

How to fix NET::ERR_CERT_AUTHORITY_INVALID

NET::ERR_CERT_AUTHORITY_INVALID means the browser does not trust whoever issued the certificate. Learn how self-signed certificates, missing chains and antivirus cause it.

2 min read
SSL certificates

How to fix NET::ERR_CERT_COMMON_NAME_INVALID

NET::ERR_CERT_COMMON_NAME_INVALID means the SSL certificate does not cover the domain you visited. Learn why it happens with www, subdomains and shared IPs, and how to fix it.

2 min read