ERR_QUIC_PROTOCOL_ERROR points to Chrome having trouble with QUIC, the fast connection protocol behind some HTTP/3 traffic. Most networks handle it correctly, but certain routers, firewalls, VPNs, public Wi-Fi networks, and workplace networks block or mishandle QUIC.
Does this affect you?
Use this for Chrome, Edge, and other Chromium browsers on Windows, Mac, or Chromebook when a page fails with ERR_QUIC_PROTOCOL_ERROR. The site may work on a different network because the issue is often network handling rather than the website itself.
Get around the failing QUIC connection
Recent Chrome versions removed the old easy QUIC flag, so the practical fix is testing the network or disabling QUIC at shortcut or policy level.
- Do not rely on chrome://flags/#enable-quic in current Chrome. The older experimental toggle is no longer available in many builds.
- Try a different network, such as mobile data instead of the problem Wi-Fi.
- If the site works elsewhere, the original network is likely blocking or breaking QUIC.
- On Windows, advanced users can right-click a Chrome shortcut, open Properties, and add –disable-quic after the closing quote in the Target field. Launch Chrome from that shortcut.
- On managed computers, an administrator can disable QUIC with the QuicAllowed policy.
- Reload the site and test again.
Clear cached data and test your network
A stale cached connection can contribute to the error, and network comparison tells you where to focus.
- Open Settings > Privacy and security > Delete browsing data.
- Set the range to All time.
- Select Cookies and other site data plus Cached images and files.
- Clear the data and restart Chrome.
- Disconnect VPNs and try again.
- If you are on public or work Wi-Fi, test from home or mobile data.
More control
Why some networks break QUIC
QUIC uses UDP, commonly over port 443, while older HTTPS mostly uses TCP. Some firewalls, routers, and security appliances block or throttle UDP traffic. If you manage the network, allowing outbound UDP 443 may fix the issue without disabling QUIC in Chrome.
QUIC is normally useful
QUIC can make supported browsing faster and more resilient. If you disabled it only as a workaround, try a normal Chrome shortcut again after changing networks, routers, or internet providers.
Other apps may show related issues
If video calls, games, or other real-time apps also struggle on the same network, the problem is probably network-level UDP handling rather than Chrome alone.
Sources
- Google Chrome Help – Fix connection errors (2025)
- Chromium Project – Net error list documentation (2025)
- Chromium Project – QUIC, a multiplexed transport protocol (2025)