How to Fix ERR_SSL_PROTOCOL_ERROR in Chrome

By ErrorFix · Updated October 20, 2026 · 8 min read

What ERR_SSL_PROTOCOL_ERROR means

When you visit an HTTPS website, Chrome and the server hold a short encrypted conversation called the TLS handshake: they agree on the encryption rules, the server shows its certificate, and only then does the page load. ERR_SSL_PROTOCOL_ERROR is Chrome's way of saying that conversation collapsed — the site sent data Chrome could not make sense of, or the two sides could not agree on a way to talk securely. Instead of risking your data, Chrome stops and shows this error page with the message that the site cannot provide a secure connection.

The good news is that this error is almost never a virus or a broken computer. It usually comes down to one of three things: something on your device getting in the way (a wrong clock, a traffic-filtering extension, antivirus HTTPS scanning, or corrupted cached SSL data), something on the network getting in the way (a VPN, proxy, firewall, or a public Wi-Fi sign-in page intercepting the connection), or something on the website itself (an expired or misconfigured certificate, or a server speaking an encryption dialect Chrome no longer accepts). The trick is finding out which of the three you are dealing with, so you fix the right thing instead of changing settings at random.

Common causes

• Wrong date or time on your device: certificates are only valid inside a time window, so a clock that is days or months off makes every secure connection fail — the most common cause of this error.
• Extensions that filter traffic: ad blockers, privacy tools, and VPN or proxy extensions can corrupt the encrypted conversation between Chrome and the site.
• Antivirus HTTPS scanning: web shields that intercept encrypted traffic to scan it can break the handshake Chrome expects — products from Avast, AVG, Kaspersky, and others do this by default.
• Corrupted SSL state or cached data: a broken stored certificate or TLS session makes the site look misconfigured even when it is fine.
• Network interference: VPNs, proxies, corporate firewalls, and public Wi-Fi captive portals can all sit between you and the site and mangle the secure connection.

How to fix ERR_SSL_PROTOCOL_ERROR — step by step

Work through these fixes in order. Steps 1 and 2 alone resolve most cases.

1. Sync your device's date and time. An incorrect clock is the single most common trigger for this error, because certificates are only valid inside a time window and a skewed clock makes the whole handshake fail. On Windows, open Settings, go to Time & language, then Date & time, 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. On iPhone, open Settings, go to General, then Date & Time, and turn on Set Automatically. Reload the site after syncing — this one fix clears a surprising share of SSL protocol errors.
2. Figure out whether the problem is the site or your device. Before changing settings, diagnose. Try the site in an incognito window — if it loads there, your extensions or cached data are the cause. Try the site on another device on the same network, then on your phone with Wi-Fi off (mobile data). If every device fails on every network, the problem is the website's server or certificate, not you — stop troubleshooting your own machine and read the owner checklist below. If only your device fails, keep going with the steps here.
3. Disable extensions and test in incognito. Extensions that filter traffic — ad blockers, privacy tools, VPN or proxy extensions — can corrupt the encrypted conversation between Chrome and the site. Type chrome://extensions in the address bar and toggle every extension off, then reload the page. If it loads, re-enable extensions one at a time until the error returns; that one is the culprit. As a quick alternative, open an incognito window (Ctrl + Shift + N on Windows, Cmd + Shift + N on a Mac) and load the site there — incognito disables most extensions by default, so a working page there points at an extension immediately.
4. Clear the SSL state and browsing data. A corrupted cached certificate or a broken stored TLS session can make one site — or every site — refuse to connect. On Windows, search the Start menu for Internet Options, open 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 Cookies and other site data and Cached images and files, then click Clear data. Close Chrome completely and reopen it so the next connection performs a completely fresh handshake instead of reusing the broken session.
5. Disable QUIC and pause antivirus SSL scanning. Two separate pieces of software commonly poison the handshake. First, Chrome's experimental QUIC protocol: type chrome://flags in the address bar, search for Experimental QUIC protocol, set it to Disabled, and click Relaunch at the bottom. Try the site again. Second, antivirus HTTPS scanning: products like Avast, AVG, Kaspersky, Bitdefender, and ESET include a web shield that intercepts encrypted traffic to scan it, and that interception itself breaks the protocol. Open your antivirus settings and turn off HTTPS or encrypted-connection scanning as a temporary test. If the site loads, add an exception for the site or leave that feature off, then restore your antivirus protection.
6. If you own the site: check the certificate and server config. When visitors report this error everywhere, the server side is broken. Run your domain through an SSL test tool such as the Qualys SSL Labs server test. The usual culprits: an expired or mis-issued certificate; a certificate whose common name does not cover the domain (www versus non-www mismatch); an incomplete chain with missing intermediate certificates; the server still negotiating ancient protocols like SSL 3.0 or TLS 1.0; or a recent server or CDN change that broke the handshake. Re-issue the certificate if needed, install the full chain, and enable TLS 1.2 and 1.3. If you use Cloudflare or another CDN, check its SSL mode and minimum TLS version settings too.

Did this fix it? Quick checklist

• Your device clock is synced automatically and shows the correct date
• The site loads in an incognito window with all extensions off
• VPN, proxy, and firewall interference have been tested (temporarily off)
• SSL state is cleared, QUIC is disabled, and antivirus HTTPS scanning is paused

If the error appears on only your device while the site loads fine elsewhere, something on your device or network is mangling the connection — run a malware scan if nothing else helped, because adware and rootkits have been known to tamper with certificate validation and produce exactly these errors. If the error appears on every device and every network for the same site, the site's certificate or server configuration is broken — stop changing your own settings and contact the site owner, because only they can fix it. And one rule for every SSL error: never enter passwords, card numbers, or other sensitive details on a page that cannot establish a secure connection.