ERR_SSL_VERSION_OR_CIPHER_MISMATCH, what it means and how to fix it

Encryption requires overlap: the browser and server must both support at least one TLS version and one cipher suite. This error means the overlap is empty. In practice the server is still offering only long-obsolete security (TLS 1.0 or 1.1, or ancient ciphers) that modern browsers removed on purpose, because those protocols are breakable.

The fix, in order

  1. Confirm it is the site by trying another device and network. If a current phone fails too, the server only speaks obsolete TLS. There is no visitor-side setting that adds the old protocols back, by design.
  2. Update your own browser and OS if they are old. The reverse case exists: a very old browser may lack TLS 1.2 or 1.3 that a modern server requires. Updating is the whole fix in that direction.
  3. Try the other address variant. Occasionally the www and bare-domain names sit on different servers with different TLS setups; one may be modern while the other is stranded on an old host.
  4. If a work network is involved, tell IT. Some corporate TLS-inspection proxies downgrade connections; if sites fail only through the office network, the proxy's TLS support is the limit.
Do not install an old browser or disable TLS protections to reach the site. A server that only offers obsolete TLS cannot protect anything you send it, including passwords. If the site matters, contact its operator and tell them their TLS configuration is unreachable from modern browsers; that is the real fix.

If it still happens

For site operators: enable TLS 1.2 and 1.3 with a current cipher list on the server or CDN, and disable SSLv3, TLS 1.0, and TLS 1.1. That single configuration change removes this error for every modern visitor at once.

Common questions

Can I enable old TLS versions in Chrome to get past this? No. Chrome removed support for TLS 1.0 and 1.1 entirely; there is no flag or setting that restores them, deliberately, because they are not safe to use. The server must modernize.

Why does the site work in one old app but not in Chrome? Some older apps and embedded browsers still carry the obsolete protocols. That they connect does not make the connection safe; it means the app kept support Chrome dropped for security reasons.

Related errors

ERR_SSL_PROTOCOL_ERROR · ERR_CERT_AUTHORITY_INVALID · ERR_CERT_COMMON_NAME_INVALID