ERR_SSL_PROTOCOL_ERROR shows up when Chrome and a server can't agree on how to set up a secure connection. Most guides tell you to "clear your cache" first, which fixes almost nothing, because the cache isn't usually the problem. The actual cause is almost always one of four things: your system clock, a browser extension, security software intercepting traffic, or the site's own certificate. Working through them in this order takes a few minutes and tells you exactly which one it is, instead of randomly trying fixes.
01Check whether it's just one site or every site
Open two or three unrelated HTTPS sites you know work, like a bank site and a news site. If they load fine and only one site throws the error, skip to Step 4 — the problem is on that server's end, not your machine. If every HTTPS site fails, keep going.
02Fix your system clock
SSL certificates are only valid within a date range. If your clock is off by more than a few minutes, Chrome will refuse the handshake and often reports it as a protocol error instead of a clearer "certificate not yet valid" message.
- Windows: Settings → Time & Language → Date & time → turn on "Set time automatically," then click Sync now.
- macOS: System Settings → General → Date & Time → enable "Set time and date automatically."
Restart Chrome completely (not just the window — quit it from the taskbar/dock) and retest.
03Disable extensions one at a time
Ad blockers, "privacy" extensions, and VPN extensions are the most common software cause, because several of them intercept and rewrite HTTPS traffic.
- Go to
chrome://extensions. - Toggle every extension off.
- Reload the page that was failing. If it now loads, turn extensions back on one at a time, reloading after each, until you find the culprit.
04Check antivirus or "HTTPS scanning" software
Security suites like older versions of Avast, AVG, Kaspersky, and some corporate endpoint tools work by decrypting and re-encrypting HTTPS traffic to scan it — effectively a sanctioned man-in-the-middle. If their own certificate isn't installed correctly, Chrome rejects the connection.
Temporarily disable "HTTPS/SSL scanning" (not the whole antivirus) in your security software's settings, then retest. If that fixes it, update the software or reinstall its root certificate rather than leaving scanning off permanently.
05If it's only one specific site
Try the site in an incognito window with extensions disabled. If it still fails there and on another device on a different network, the problem is on the server: an expired certificate, a misconfigured intermediate certificate chain, or the server only supporting an outdated TLS version. There's nothing to fix on your end — you can report it to the site, or wait, since this generally gets resolved by the site owner.
| Symptom | Likely cause | Fix |
|---|---|---|
| Every HTTPS site fails | Clock or antivirus | Steps 2 and 4 |
| Fails after installing an extension | Extension conflict | Step 3 |
| Only one site fails, on all devices | Server certificate issue | Step 5 — not fixable client-side |
| Fails only on office/school Wi-Fi | Network-level filtering | Contact network admin |