ERR_SSL_OBSOLETE_VERSION
The site uses an outdated TLS version
Seen in Chrome, Edge
The server negotiated TLS 1.0 or 1.1, which browsers have retired as insecure.
Common causes
- The server or appliance only supports TLS 1.0 or 1.1.
- An old load balancer or proxy in front of the site caps the TLS version.
- TLS 1.2 is disabled in the server configuration.
How to fix it
- Enable TLS 1.2 and 1.3 (e.g. nginx "ssl_protocols TLSv1.2 TLSv1.3;").
- Upgrade the server software or OS so it supports TLS 1.2 or later.
- Put legacy devices behind a modern reverse proxy that terminates TLS.
Got a different message? Paste it into the error explainer.
Related errors
- NET::ERR_CERT_DATE_INVALID · The certificate has expired or is not yet valid
- NET::ERR_CERT_AUTHORITY_INVALID · The certificate isn't issued by a trusted authority
- SEC_ERROR_UNKNOWN_ISSUER · Firefox doesn't recognise the certificate's issuer
- NET::ERR_CERT_COMMON_NAME_INVALID · The certificate doesn't cover this name
- ERR_SSL_PROTOCOL_ERROR · The secure connection failed during the handshake
- ERR_SSL_VERSION_OR_CIPHER_MISMATCH · No TLS version or cipher in common
- You cannot visit this site right now because the website uses HSTS · HSTS blocks the bypass of a certificate error
- NET::ERR_CERT_REVOKED · The certificate has been revoked by its issuer
- NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM · The certificate is signed with an insecure algorithm
- NET::ERR_CERT_INVALID · The certificate is malformed or breaks platform rules
- NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED · The certificate is not logged in Certificate Transparency
- ERR_SSL_UNRECOGNIZED_NAME_ALERT · The server has no site configured for this hostname