ERR_QUIC_PROTOCOL_ERROR in Chrome on Mac
ERR_QUIC_PROTOCOL_ERROR is a Chrome network error. The Chromium source describes it as: “There is a QUIC protocol error.”
My Mac has this problem: ERR_QUIC_PROTOCOL_ERROR in Chrome on Mac. Read https://kilobat.app/guides/err-quic-protocol-error.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.
Symptoms
- Chrome shows “This site can’t be reached” and ERR_QUIC_PROTOCOL_ERROR.
- Reload sometimes works, because Chrome falls back to TCP.
- It affects sites that use HTTP/3.
Likely causes
- A network that blocks UDP. QUIC runs over UDP. Some firewalls and VPNs drop it.
- A VPN or filter. A VPN or security app can break QUIC packets.
- A server fault. The server HTTP/3 setup can fail.
- An unstable link. Packet loss disturbs QUIC.
How to check
Reload the page once. Chrome may then use TCP.
Test the site over HTTP/2 with curl.
curl -v --http2 https://example.comTry another network.
Turn off the VPN for a short test.
How to fix it
Turn off the VPN or security app for a short test. Turn it on again after.
Ask the network administrator to allow UDP port 443.
If the failure stays, compare the site over HTTP/2 with curl and report the result to the site.
Update Chrome.
With Kilobat
Kilobat's connection doctor tests the address layer by layer: network, proxy, DNS, rules, IPv4, IPv6, TLS and the server. It names the layer that failed.
kilobat why https://example.comThese Kilobat checks are free. AI agents run them through MCP with
diagnose_connectionanddiagnose_network. See Find why one site or API won't connect.
Questions
What is QUIC?
QUIC is the transport that HTTP/3 uses. It runs over UDP.
Does Chrome fall back to another transport?
Often yes. A reload can load the page over TCP, but the cause stays in the path.
Sources
Checked on 29 October 2026.