home / browser errors / err-ssl-version-or-cipher-mismatch

[ REPAIR GUIDE ] BROWSER ERRORS

How to fix ERR_SSL_VERSION_OR_CIPHER_MISMATCH

ERROR DETECTED >This site can't provide a secure connection. example.com uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH

UPDATED NOVEMBER 20262 MIN READ6 FIXES

QUICK FIX

This is almost always the website's problem: its server needs modern TLS settings or a valid certificate. As a visitor, update your browser and try another network; if it still fails, contact the site owner.

What it means

Your browser and the website could not agree on a secure way to talk. Usually the website only offers old, weak encryption that modern browsers refuse, or its certificate is missing for that address. Less often, something on your device is interfering.

Common causes

  • The site only supports old protocols such as TLS 1.0 or 1.1, or weak ciphers
  • The site's certificate does not cover the exact address (for example a deeper subdomain)
  • A new certificate on a CDN like Cloudflare has not finished activating
  • An outdated browser or operating system
  • Antivirus or a network device intercepting HTTPS

How to fix it

Work down the list. Each fix is safe to try before moving on to the next.

FIX 01Check whether it fails for everyoneEASY

  1. Open other secure sites to confirm they work.
  2. Try the problem site on another device using mobile data.
  3. If it fails everywhere, only the site owner can fix it; contact them.

Why it helps: Saves you from changing settings that will not help.

FIX 02Update the browser and operating systemEASY

  1. Chrome: More (three dots) > Help > About Google Chrome, then Relaunch.
  2. Edge: Settings and more (three dots) > Help and feedback > About Microsoft Edge.
  3. Windows 11: Settings > Windows Update > Check for updates. Mac: Apple menu > System Settings > General > Software Update.

Why it helps: Older software may not support the protocol the site needs.

FIX 03Clear cache and test in IncognitoEASY

  1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac), choose All time, tick cached files and cookies, and delete.
  2. Open the site in an Incognito window with Ctrl + Shift + N (Windows) or Cmd + Shift + N (Mac).
  3. If it works there, turn off extensions at chrome://extensions.

Why it helps: Rules out stale data and extensions.

FIX 04Try another network and pause HTTPS scanningMEDIUM

  1. Disconnect any VPN and try a different network.
  2. If you use antivirus with HTTPS scanning, turn it off briefly, reload, then turn it back on right away.

Why it helps: Some security tools and networks rewrite secure connections with older settings.

// RUN THIS SITE? FIXES FOR SITE OWNERS

FIX 05Enable modern TLS on the serverADVANCEDSITE OWNERS

  1. Turn on TLS 1.3 and keep TLS 1.2 for older clients; turn off SSL 3.0, TLS 1.0 and TLS 1.1.
  2. Make sure the cipher list includes modern AEAD suites. Chrome recommends TLS 1.3 with TLS_AES_128_GCM_SHA256.
  3. Restart the web server and test with an SSL checker or openssl s_client -connect example.com:443 -servername example.com.

Why it helps: Chrome blocks sites that only offer outdated security.

FIX 06Make sure the certificate covers the hostnameADVANCEDSITE OWNERS

  1. Check the certificate includes the exact hostname, including www and any subdomains.
  2. On Cloudflare, Universal SSL covers the root domain and one subdomain level only; for names like a.b.example.com use Total TLS, an Advanced Certificate or a custom certificate.
  3. On Cloudflare, confirm the certificate status is Active under SSL/TLS > Edge Certificates and the DNS record is Proxied.
  4. Replace any expired custom certificate.

Why it helps: A missing or inactive certificate for the hostname triggers this exact error on Cloudflare.

Check it's fixed

  • The site loads with no security warning.
  • An online SSL test shows TLS 1.2 or 1.3 enabled.
  • The site loads on several browsers and devices.

When to get help

Visitors should contact the site owner if the error appears everywhere. Site owners who do not manage their own server should ask their host to update the TLS settings or certificate.

Questions

Can I turn off the check in Chrome?

No, and you should not try. Chrome blocks these sites on purpose because their encryption is too weak to protect you.

Why did a site that used to work start showing this?

Browsers have dropped support for old protocols like TLS 1.0 and 1.1. Sites that never upgraded now fail.

Why does it happen right after adding a site to Cloudflare?

The new certificate can take up to 24 hours to become active, and records must be proxied to use it.

Related fixes

How to fix "This site can't provide a secure connection"Set your device's date and time automatically, clear cached files and reload. If other secure sites work and this one fails on every deHow to fix ERR_SSL_PROTOCOL_ERRORMake sure your device's date and time are set automatically, then clear the browser's cached images and files and reload. If it onHow to fix "Your connection is not private"Check the code under the warning. If it says your clock is ahead or behind, or NET::ERR_CERT_DATE_INVALID, set your date and time automaticaHow to fix NET::ERR_CERT_AUTHORITY_INVALIDSign in to the Wi-Fi network if you are on public Wi-Fi, update your device, and check whether antivirus HTTPS scanning is causing it. If th

Still stuck?

Paste the exact message and the repair bot will find the closest fix, or search it on Google, Microsoft, Apple, Reddit and YouTube.

Sources