Opens in a new tab

ERR_SSL_VERSION_OR_CIPHER_MISMATCH: no TLS version or cipher in common

The browser and the server could not agree on a TLS version or cipher. Almost always the server only offers TLS 1.0 or 1.1, or ciphers browsers dropped years ago; Chrome, Edge and Firefox stopped accepting TLS 1.0 and 1.1 in 2020.

This site can’t provide a secure connection
example.com uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
How 5 other clients word the same error

Firefox

Error code: SSL_ERROR_NO_CYPHER_OVERLAP — “Cannot communicate securely with peer: no common encryption algorithm(s).”
or SSL_ERROR_UNSUPPORTED_VERSION — “This website might not support the TLS 1.2 protocol, which is the minimum version supported by Firefox.”

OpenSSL / curl / Python

tlsv1 alert protocol version · unsupported protocol · sslv3 alert handshake failure (ssl/tls alert handshake failure in OpenSSL 3.2+)

curl on Windows (Schannel)

SEC_E_ALGORITHM_MISMATCH (0x80090331) - The client and server cannot communicate, because they do not possess a common algorithm.

Java

Received fatal alert: handshake_failure · Received fatal alert: protocol_version

Go

remote error: tls: protocol version not supported · remote error: tls: handshake failure
ErrorERR_SSL_VERSION_OR_CIPHER_MISMATCH
Usually fixed byThe website
TLS 1.0 and 1.1Removed from Chrome 84 and Firefox 78 (2020); off by default in Edge 84
Chrome’s advice to site ownersEnable TLS 1.3; keep TLS 1.2 for older clients
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 the browser listing the versions and ciphers it accepts and the server picking one. If the server offers nothing on that list, the handshake fails. Chrome reports it as ERR_SSL_VERSION_OR_CIPHER_MISMATCH — including for servers still on TLS 1.0 or 1.1, which it no longer accepts at all.

Why it happens

  • The server offers only TLS 1.0 or 1.1 — old hardware, an old operating system, or a configuration never updated.
  • Only obsolete ciphers enabled (RC4, 3DES, export ciphers).
  • No certificate configured for the requested name on a server that picks certificates by name, so it aborts the handshake.
  • A CDN or load balancer in front of the site with an outdated TLS policy.

How to fix it

  1. Run the check above to see which TLS versions the server offers.
  2. Enable TLS 1.3 and TLS 1.2, and disable 1.0 and 1.1: nginx ssl_protocols TLSv1.2 TLSv1.3; Apache SSLProtocol -all +TLSv1.2 +TLSv1.3.
  3. Use a current cipher list — Mozilla’s SSL Configuration Generator gives one for each server — and update OpenSSL on old systems.
  4. On a CDN or load balancer, pick a TLS policy with a minimum of TLS 1.2.

See it for yourself

openssl s_client -connect example.com:443 -servername example.com -tls1_2 </dev/null
openssl s_client -connect example.com:443 -servername example.com -tls1_3 </dev/null

A server that fails both only speaks versions current browsers refuse.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

Hear about it before your visitors do

Add your domain and we check its certificate on every scan and email you before it expires, and when it changes or stops being valid — along with DNS, email and security headers. Free for your first domain.

Create a free account