How to Fix ERR_SSL_VERSION_OR_CIPHER_MISMATCH in Chrome
What ERR_SSL_VERSION_OR_CIPHER_MISMATCH means
Every time you open an HTTPS website, your browser and the server perform a TLS handshake: they agree on which encryption version (like TLS 1.2 or 1.3) and which cipher suite to use for everything that follows. ERR_SSL_VERSION_OR_CIPHER_MISMATCH appears when that negotiation fails — the two sides have no encryption settings in common, so no secure connection can exist and Chrome stops instead of loading the page.
This mismatch usually has one of two causes. On your end, an outdated browser or operating system may only speak retired protocols like TLS 1.0, which modern websites no longer accept — this is why the error shows up so often on old phones and aging Windows machines. On the website's end, the server may be misconfigured: still offering ancient SSL 3.0, using the banned RC4 cipher, or serving an incomplete certificate chain. Your job is to eliminate your side of the problem first (updates, clock, cached SSL state, QUIC, extensions, antivirus) and, if you run the site, fix the server configuration last.
Common causes
- Outdated browser or operating system: old browsers only understand TLS 1.0/1.1 and weak ciphers, which modern websites reject — the most common cause by far.
- Wrong date or time on your device: certificates are only valid inside a time window, so a skewed clock silently breaks the handshake.
- Corrupted SSL state or cached data: a broken stored certificate or TLS session can make every site look misconfigured.
- Chrome's experimental QUIC protocol: QUIC occasionally disagrees with a server's setup and produces exactly this error.
- Extensions or antivirus SSL scanning: anything that intercepts HTTPS traffic can break the handshake — privacy extensions and antivirus web shields are the usual suspects.
How to fix ERR_SSL_VERSION_OR_CIPHER_MISMATCH — step by step
Work through these fixes in order. Most cases are fixed by step 1 or 3.
- Update Chrome and your operating system. The most common cause of this error is an outdated browser or operating system that only supports old, retired encryption. On desktop, open Chrome, click the three-dot menu, go to Help, then About Google Chrome, and let it update — version 120 or newer is ideal. Also install your operating system updates: on Windows, open Settings, go to Windows Update, and click Check for updates. Phones and tablets that stopped receiving updates years ago (old Android versions, very old iPhones) may simply be unable to open modern HTTPS sites, and no browser tweak will change that — updating is the only real fix.
- Fix your device's date and time. A wrong clock silently breaks secure connections because certificates are only valid inside a time window. On Windows, open Settings, go to Time & language, then Date & time, and turn on Set time automatically and Set time zone automatically, then click Sync now. On a Mac, open System Settings, go to General, then Date & Time, and turn on Set time and date automatically. On Android, open Settings, go to System, then Date & time, and enable Automatic date & time. Reload the site after syncing — this alone fixes a surprising number of SSL errors.
- Clear the SSL state and browsing data. Corrupted cached certificates or a bad stored TLS session can make every site look broken. In Windows, open Internet Options (search for it in the Start menu), go to the Content tab, and click Clear SSL state. In Chrome, press Ctrl + Shift + Delete (Cmd + Shift + Delete on a Mac), set the time range to All time, check Cached images and files and Cookies and other site data, and click Clear data. Then close Chrome completely and reopen it — a full restart forces a fresh TLS handshake instead of reusing the broken session.
- Disable the QUIC protocol as a test. Chrome's experimental QUIC protocol occasionally triggers this exact error when it disagrees with a server's configuration. Type chrome://flags in the address bar, search for Experimental QUIC protocol, change it to Disabled, and click Relaunch at the bottom. Try the site again. If it loads, QUIC was the problem — leave it disabled. If nothing changes, go back to chrome://flags and reset the flag to Default so you are not left with a non-standard setting for no reason.
- Disable extensions and pause antivirus SSL scanning. Some extensions and antivirus programs intercept HTTPS traffic and break the handshake. Type chrome://extensions and toggle off every extension, then reload the page; re-enable them one by one to find the culprit. Next, check your antivirus: products like Avast, AVG, Kaspersky, and ESET include an HTTPS or web-shield feature that scans encrypted traffic. Open your antivirus settings and turn off HTTPS scanning temporarily as a test — if the site loads, add an exclusion or keep that feature off for this site, then re-enable your protection.
- If you own the site: fix the server's TLS configuration. When visitors report this error, the server itself is misconfigured. Run your domain through an SSL test tool like the Qualys SSL Labs test to see exactly what is failing. The usual fixes: enable TLS 1.2 and TLS 1.3 and disable SSL 2.0, SSL 3.0, and TLS 1.0/1.1 on the server; remove the RC4 cipher, which Chrome no longer accepts; install a valid certificate chain including the intermediate certificates; and if you use Cloudflare or another CDN, check that its minimum TLS version setting is not higher than what your visitors' devices support. Re-test after every change until the error is gone.
Did this fix it? Quick checklist
- Chrome and your operating system are fully updated
- Your device clock is set to sync automatically
- The site loads in an incognito window with extensions off
- QUIC is disabled (or reverted to Default after testing)
If the error appears on only one device but the site loads everywhere else, that device is the problem — usually it is too old to be updated, and there is no settings trick that adds modern TLS support. If the error appears on every device and every network for the same site, the problem is the server: stop troubleshooting your own setup and contact the site owner, because only they can fix a broken TLS configuration. And if nothing here helps, a full malware scan is worth running — rootkits and adware have been known to tamper with certificate validation and produce misleading SSL errors.
Frequently asked questions
What does ERR_SSL_VERSION_OR_CIPHER_MISMATCH mean?
It means Chrome and the website failed to agree on the encryption rules for a secure connection. When you visit an HTTPS site, both sides negotiate a TLS version and cipher suite; if they share none in common — because one side is too old or the server is misconfigured — the handshake fails and Chrome shows this error instead of loading the page.
Why does this error only appear on my old phone or computer?
Older devices only understand retired versions of TLS (1.0 and 1.1) and weak ciphers, while modern websites require TLS 1.2 or 1.3. As servers drop support for the old protocols, aging devices can no longer complete the handshake. Updating the browser helps on devices that still get updates; on devices that stopped receiving updates years ago, this error may be permanent.
Is it safe to bypass or click through this error?
Not really. This error means no safe encryption could be established, so bypassing it could send your data unprotected or let an attacker sit between you and the site. Only proceed if you trust the site completely and understand the risk — never enter passwords, card details, or other sensitive information on a page with SSL problems.
How do I disable QUIC in Chrome?
Type chrome://flags in the address bar, search for Experimental QUIC protocol, set it to Disabled, and click Relaunch. This turns off the QUIC protocol, which can conflict with some server configurations and trigger this error. If disabling it does not help, set the flag back to Default.
I own the website — what should I fix on the server?
Run your domain through the Qualys SSL Labs server test to see exactly what fails. Typically you need to enable TLS 1.2 and TLS 1.3, disable SSL 3.0 and TLS 1.0/1.1, remove the RC4 cipher suite, and install the full certificate chain including intermediate certificates. If you use a CDN like Cloudflare, also check its minimum TLS version setting.