Load the site on mobile data first. If it fails everywhere, the website's HTTPS setup is broken and only its owner can fix it. If only your device fails, try an Incognito window (extensions off), pause antivirus HTTPS scanning, turn off any VPN or proxy, and disable QUIC.

ERR_SSL_PROTOCOL_ERROR, explained

Before any secure page loads, the browser and the server run a TLS handshake: they agree on a protocol version and cipher and check the site’s certificate. ERR_SSL_PROTOCOL_ERROR means that conversation failed in a way Chrome couldn’t classify more precisely.

When only your device is affected, the cause is typically something between Chrome and the site: antivirus that intercepts HTTPS, a VPN or corporate proxy, or a browser extension. When every device fails, the server is sending something that isn’t a valid TLS response, often because port 443 is answering with plain HTTP or a CDN’s SSL mode doesn’t match the server. (Outdated TLS versions and wrong-hostname certificates show their own errors: ERR_SSL_VERSION_OR_CIPHER_MISMATCH and NET::ERR_CERT_COMMON_NAME_INVALID.)

How it shows up

  • “This site can’t provide a secure connection. Example.com sent an invalid response. ERR_SSL_PROTOCOL_ERROR”.
  • The error appears on one site, or on many HTTPS sites at once.
  • The same page may open in another browser or on a phone.

Common causes

  • A VPN, proxy or network filter interfering with the TLS handshake.
  • Antivirus or a proxy that decrypts and re-encrypts HTTPS traffic.
  • A browser extension or a corrupted cache interfering with the connection.
  • Server-side misconfiguration: port 443 serving plain HTTP, a broken TLS setup, or a CDN SSL mode that doesn't match the server.

How to fix it, step by step

  1. Check whether it's just youOpen the site on mobile data or another device. If it fails everywhere, skip to the last step: the website needs fixing. If it works elsewhere, continue below.
  2. Try IncognitoPress Ctrl+Shift+N and load the site. If it works, disable extensions one by one at chrome://extensions to find the culprit.
  3. Clear Chrome's cacheGo to chrome://settings/clearBrowserData and clear cached images and files, then reload.
  4. Turn off VPN and proxyDisconnect VPN apps and switch off any manual proxy in Windows Settings → Network & internet → Proxy.
  5. Pause HTTPS scanningTemporarily turn off the HTTPS / encrypted-connection scanning feature in third-party antivirus, then reload. If it fixes it, add an exception for the site.
  6. Disable QUICOpen chrome://flags/#enable-quic, set Experimental QUIC protocol to Disabled, and relaunch. Some networks break QUIC traffic.
  7. Check from another networkLoad the site on mobile data. If it fails everywhere, the website is at fault. Site owners can run their domain through an SSL test (for example SSL Labs) to see the exact handshake failure.
How to confirm the fix: The site loads with the padlock icon in the address bar and no warning, in a normal (not Incognito) window.

Keeping it from coming back

Keep Chrome and your antivirus up to date, avoid stacking several security extensions or VPNs, and (site owners) test HTTPS after every server or CDN change.