Chrome dropped TLS 1.0 and 1.1 and refuses RC4 and 3DES, so a server that still works in curl or an internal tool fails only in the browser.
Chrome dropped TLS 1.0 and 1.1 and refuses RC4 and 3DES, so a server that still works in curl or an internal tool fails only in the browser.
Run the SSL check below to see the highest protocol the server actually offers. If the answer is TLS 1.1 or lower, no browser fix exists — the server must enable TLS 1.2.
Chrome has its own failure mode, but ERR_SSL_VERSION_OR_CIPHER_MISMATCH has a wider set of causes. The most common one overall is: The server only supports TLS 1.0 or 1.1.
Enable TLS 1.2 and 1.3. On nginx: `ssl_protocols TLSv1.2 TLSv1.3;` then reload.
The SSL check enumerates exactly which protocol versions and suites the server accepts, turning guesswork into a list.
Chrome dropped TLS 1.0 and 1.1 and refuses RC4 and 3DES, so a server that still works in curl or an internal tool fails only in the browser.
Run the SSL check below to see the highest protocol the server actually offers. If the answer is TLS 1.1 or lower, no browser fix exists — the server must enable TLS 1.2.
The browser and server have no protocol version or cipher suite in common, so the handshake ends before it starts. Almost always an origin still pinned to TLS 1.0/1.1 or an ancient cipher list.