Firefox: Secure Connection Failed — SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
Firefox sent a TLS handshake but received plain HTTP back — you used https:// on a port that serves HTTP.
SSL received a record that exceeded the maximum permissible lengthSecure Connection Failed SSL_ERROR_RX_RECORD_TOO_LONGError code: SSL_ERROR_RX_RECORD_TOO_LONG Meaning
Most often the site is not configured for TLS on that port: Apache/Nginx listening on 443 without ssl, a development server on 8080 with HTTP only, or an https:// link to a non-TLS service. Use http:// or enable TLS on that port.
Common causes
- https:// used against an HTTP-only port
- Nginx
listen 443;withoutssl - Apache vhost on 443 without
SSLEngine on - Proxy forwarding HTTPS to an HTTP backend port
- Dev server (Node/Python) started without TLS
⚡ Quick fix
- Use
http://or the correct port - Add
sslto the listen directive and load certificates - Check:
curl -v http://host:portvshttps://host:port
Detailed fix by platform
Linux
curl -v https://host:8080 2>&1 | headshowswrong version numberwhen the port speaks plain HTTP
How to diagnose
- Port — TLS enabled?
- Scheme — http vs https?
- Config — ssl on?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- ERR_SSL_PROTOCOL_ERROR ERR_SSL_PROTOCOL_ERROR (This site can't provide a secure connection)
- no "ssl_certificate" is defined for the "listen ... ssl" directive Nginx: [emerg] no "ssl_certificate" is defined for the "listen ... ssl" directive in /etc/nginx/sites-enabled/default:3
- SEC_ERROR_EXPIRED_CERTIFICATE Firefox: Peer's Certificate has expired. Error code: SEC_ERROR_EXPIRED_CERTIFICATE
Most viewed in SSL / TLS
- NET::ERR_CERT_COMMON_NAME_INVALID NET::ERR_CERT_COMMON_NAME_INVALID: Your connection is not private (certificate is for a different domain)
- Challenge failed for domain Let’s Encrypt / Certbot: Challenge failed for domain example.com — Invalid response from http://example.com/.well-known/acme-challenge/x: 404
- no start line OpenSSL: unable to load certificate / PEM routines:get_name:no start line (key values mismatch)
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026