ERR_QUIC_PROTOCOL_ERROR, what it means and how to fix it

QUIC is the UDP-based transport under HTTP/3. Instead of TCP, it runs over UDP port 443, encrypts by default, and sets up connections faster. This error means the QUIC connection itself failed: most often a firewall, router, or provider that blocks or mangles UDP, or a server whose QUIC implementation is broken. Chrome normally falls back to TCP quietly; the error surfaces when the fallback also fails or the failure happens mid-session.

The fix, in order

  1. Reload. QUIC failures are frequently transient, and the retry usually lands on a working TCP connection.
  2. Test on another network. UDP handling varies wildly by network: some corporate and hotel networks block UDP outright, and some home routers mishandle it. If QUIC errors vanish on mobile data, the first network's UDP treatment is the cause.
  3. Restart the router. Consumer routers with stateful UDP handling are a recurring source; a power cycle clears the bad state.
  4. Disable QUIC as a test (and, on hostile networks, as a fix). At chrome://flags, set QUIC to Disabled and restart Chrome. If everything then works, leave it off on that network; you lose a small speed edge on good networks and gain working pages on bad ones.
  5. Check the firewall's UDP rules if you manage the network. QUIC needs outbound UDP 443. A firewall that only permits TCP 443 silently kills QUIC; that is a policy decision some networks make deliberately, in which case Chrome should fall back, and persistent errors mean the fallback path has its own problem.

If it still happens

If a site's QUIC is broken for everyone (a bad HTTP/3 deployment), visitors cannot repair it; the operator must fix or withdraw the QUIC advertisement. Disabling QUIC in your browser is the complete visitor-side workaround in that case.

Common questions

Is QUIC the same as HTTP/3? Nearly: HTTP/3 is the application protocol, QUIC is its transport underneath. Errors named QUIC come from the transport layer (connection setup, UDP delivery), while HTTP/3 errors resemble HTTP/2's framing problems.

Does disabling QUIC make browsing less secure? No. QUIC's encryption is replaced by ordinary TLS over TCP, the same protection the web used for decades. You give up connection speed features (faster setup, better loss recovery), not security.

Related errors

ERR_HTTP2_PROTOCOL_ERROR · ERR_SSL_PROTOCOL_ERROR · ERR_NETWORK_CHANGED