ERR_SSL_OBSOLETE_VERSION Browser Origin: On your device Last updated 15 Oct 2026

Chrome: Connection not secure — ERR_SSL_OBSOLETE_VERSION (old TLS 1.0/1.1)

The server only supports an outdated TLS version that current browsers no longer allow.

Exact message you may see Connection not secureobsolete TLS
Explore the map of this error Full error map →
Seen on: Chrome Edge

Meaning

Chrome and Edge removed TLS 1.0 and 1.1. Old intranet servers, printers, routers and embedded devices are the main victims. The proper fix is to enable TLS 1.2 or higher on the device; as a last resort use an older browser inside a controlled network or put a modern reverse proxy in front.

Common causes

  • Server, appliance or load balancer limited to TLS 1.0/1.1
  • Old firmware on routers, printers, NAS, IPMI/iLO consoles
  • Legacy .NET/Java stack with TLS 1.2 disabled
  • Hardened OS policy disabling modern protocols for the server

⚡ Quick fix

  1. Update the device/server firmware or software and enable TLS 1.2+
  2. Put an nginx/Apache reverse proxy with modern TLS in front of a legacy device
  3. Do not re-enable obsolete TLS in the browser for the open internet

Detailed fix by platform

Nginx

  1. Front the legacy host: server { listen 443 ssl; ssl_protocols TLSv1.2 TLSv1.3; location / { proxy_pass http://192.168.1.10:80; } }

Windows

  1. For old IIS: enable TLS 1.2 via registry/IIS Crypto and update to a supported .NET version

How to diagnose

  1. Version — Which TLS versions does the host offer?
  2. Device — Firmware update available?
  3. Exposure — Internal-only or internet-facing?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

525 — Cloudflare Error 525: SSL Handshake Failed (Cloudflare)525A TLS error caused the secure connection to fail — Safari: Safari Can’t Open the Page — A TLS error caused the secure connection to fail (Browser)A TLS error caused th…ERR_CONNECTION_CLOSED — Chrome: This site can’t be reached — example.com unexpectedly closed the connection. ERR_CONNECTION_CLOSED (Browser)ERR_CONNECTION_CLOSEDERR_SSL_PROTOCOL_ERROR — ERR_SSL_PROTOCOL_ERROR (This site can't provide a secure connection) (JavaScript)ERR_SSL_PROTOCOL_ERRORERR_SSL_VERSION_OR_CIPHER_MISMATCH — Chrome: This site can’t provide a secure connection — uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH (Browser)ERR_SSL_VERSION_OR_CI…HSTS — Chrome: You cannot visit example.com right now because the website uses HSTS (NET::ERR_CERT_… no bypass) (Browser)HSTSNET::ERR_CERT_REVOKED — Chrome: Your connection is not private — NET::ERR_CERT_REVOKED (the certificate was revoked) (Browser)NET::ERR_CERT_REVOKEDSSL_ERROR_NO_CYPHER_OVERLAP — Firefox: Secure Connection Failed — SSL_ERROR_NO_CYPHER_OVERLAP (no common cipher) (Browser)SSL_ERROR_NO_CYPHER_O…ERR_SSL_O…

Explore the map of this error Full error map →

🧠 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.