How to Fix the ERR_SSL_PROTOCOL_ERROR Error

ERR_SSL_PROTOCOL_ERROR is a generic error the browser shows when it cannot establish a secure TLS connection with the server. The cause is most often the server configuration or a simple client-side setting. In this guide we'll resolve it by eliminating the possible causes one by one, from the quickest to the deepest.

1 — Check the device date and time

Certificate validity depends on the date. If the clock on your computer or phone is wrong, the TLS handshake fails. Set the device date/time to automatic (from the network) and refresh the page.

2 — Clear the browser cache and SSL state

An old session record can cause problems. Clear the browser cache, try an incognito window, or open it in a different browser. If the problem occurs in only one browser, the cause is client-side.

3 — Update the server's TLS version

Modern browsers now reject the old and insecure TLS 1.0/1.1 versions. If your server offers only these old versions, the error occurs. Enable the current versions in Nginx:

ssl_protocols TLSv1.2 TLSv1.3;

The Apache equivalent: SSLProtocol -all +TLSv1.2 +TLSv1.3.

4 — Verify port 443 and the certificate configuration

Make sure HTTPS requests land in the correct server/VirtualHost block and that the ssl_certificate and ssl_certificate_key paths point to the right files. If you changed the configuration, reload the server (nginx -t && nginx -s reload).

5 — Check the certificate chain

A missing intermediate chain (CA Bundle) can turn into a protocol error on some clients. For Nginx, define the certificate and chain together as fullchain.pem. If you need to regenerate your certificate, our free SSL wizard gives you all files including fullchain.pem in a single ZIP.

6 — Rule out interfering software

Some antivirus and corporate network filters intercept HTTPS traffic and cause a protocol error. Temporarily disable the "HTTPS scanning" feature and try again; if the problem goes away, that software is the cause.

Summary

ERR_SSL_PROTOCOL_ERROR usually stems from a wrong clock, an old TLS version, or a faulty server configuration. Apply the steps above in order. If the problem is with the certificate, create a new one with our free wizard and reinstall it.