ERR_SSL_VERSION_OR_CIPHER_MISMATCH in Chrome on Mac
ERR_SSL_VERSION_OR_CIPHER_MISMATCH is a Chrome network error. The Chromium source describes it as: “The client and server don't support a common SSL protocol version or cipher suite.”
My Mac has this problem: ERR_SSL_VERSION_OR_CIPHER_MISMATCH in Chrome on Mac. Read https://kilobat.app/guides/err-ssl-version-or-cipher-mismatch.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.
Symptoms
- Chrome shows “This site can’t provide a secure connection”.
- The error is ERR_SSL_VERSION_OR_CIPHER_MISMATCH.
- The site is old or uses an unusual setup.
Likely causes
- An outdated server. The server supports only old TLS versions or ciphers that Chrome does not accept.
- A device with old firmware. A router or printer page can use outdated TLS.
- A filter in between. Security software can change the handshake.
- A wrong port. The port may not serve TLS.
How to check
Show the TLS handshake and the version chosen.
curl -v https://example.comTest the port with OpenSSL.
openssl s_client -connect example.com:443 -servername example.comTry another browser or network.
Check that the address uses the right port.
How to fix it
If the site is yours, enable TLS 1.2 or later on the server.
For a device, update its firmware or use its vendor’s guidance.
Turn off TLS scanning in security software for a short test. Turn it on again after.
Update Chrome and macOS.
With Kilobat
Kilobat's connection doctor tests the address layer by layer: network, proxy, DNS, rules, IPv4, IPv6, TLS and the server. It names the layer that failed.
kilobat why https://example.comThese Kilobat checks are free. AI agents run them through MCP with
diagnose_connectionanddiagnose_network. See Find why one site or API won't connect.
Questions
Can I allow old TLS in Chrome?
Do not weaken the browser. Update the server or device instead.
Is this the same as a certificate error?
No. The two sides could not agree on a protocol version or cipher suite.
Sources
Checked on 29 October 2026.