The browser started a secure connection and got back something that is not TLS. On the site’s side, the usual reason is a server answering plain HTTP on the HTTPS port — port 443 open, but no certificate configured on it. Firefox names it SSL_ERROR_RX_RECORD_TOO_LONG.
This site can’t provide a secure connection example.com sent an invalid response. ERR_SSL_PROTOCOL_ERROR
How 5 other clients word the same error
Firefox
Secure Connection Failed An error occurred during a connection to example.com. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
OpenSSL, curl, Python
wrong version number — or, in OpenSSL 3.2 to 3.5, packet length too long / record layer failure
curl on Windows (Schannel)
curl: (35) schannel: next InitializeSecurityContext failed: SEC_E_INVALID_TOKEN (0x80090308) - The token supplied to the function is invalid
Java
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
Go
tls: first record does not look like a TLS handshake
| Error | ERR_SSL_PROTOCOL_ERROR |
| Usually fixed by | Either side |
| Shown by | Chrome and Edge; Firefox as SSL_ERROR_RX_RECORD_TOO_LONG |
| Can visitors click through? | No |
Check the certificate a site serves
Enter the site’s domain: we connect the way a browser does and show the certificate, its chain and the TLS versions it offers.
What it means
A TLS connection starts with records of a fixed shape. When a plain-HTTP server answers on port 443, its reply (“HTTP/1.1 400 …”) is read as a TLS record: Firefox sees an impossible record length and says so; Chrome sees an impossible version and reports a protocol error.
Chrome uses ERR_SSL_PROTOCOL_ERROR for any TLS failure it has no more specific code for, so on the visitor’s side it can also come from something interfering with the connection.
Why it happens
- Port 443 is served by a virtual host without SSL: Apache without SSLEngine on, nginx listening on 443 without the ssl parameter.
- A Listen 443 or port mapping that sends HTTPS traffic to a plain-HTTP service.
- On the visitor’s side: a VPN, antivirus that scans encrypted traffic, a proxy or a firewall interfering.
How to fix it
- Check what port 443 answers with the check above or openssl s_client — if it is not a certificate, TLS is not configured there.
- Apache: a <VirtualHost *:443> with SSLEngine on, SSLCertificateFile and SSLCertificateKeyFile, and Listen 443.
- nginx: listen 443 ssl; with ssl_certificate and ssl_certificate_key in the server block.
- Behind a CDN or load balancer, make sure the port it forwards HTTPS to actually speaks TLS.
If you are visiting the site
- Try another network, or turn off a VPN or antivirus HTTPS scanning briefly; if the error follows every site, it is on your side.
See it for yourself
openssl s_client -connect example.com:443 -servername example.com
A working server prints its certificate chain. “wrong version number” — or “packet length too long” in OpenSSL 3.2 to 3.5 — means plain HTTP answered on the port. The reverse mistake, plain HTTP sent to an HTTPS port, gets nginx’s “400 The plain HTTP request was sent to HTTPS port”.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- Net error list.h — raw.githubusercontent.com
- Secure connection failed and Firefox did not connect — support.mozilla.org
- SSL/TLS Strong Encryption: How-To — httpd.apache.org
- Configuring HTTPS servers — nginx.org