ERR_HTTP2_PROTOCOL_ERROR in Chrome on Mac
ERR_HTTP2_PROTOCOL_ERROR is a Chrome network error. The Chromium source describes it as: “There is an HTTP/2 protocol error.”
My Mac has this problem: ERR_HTTP2_PROTOCOL_ERROR in Chrome on Mac. Read https://kilobat.app/guides/err-http2-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 page isn’t working” and ERR_HTTP2_PROTOCOL_ERROR.
- One site fails. Others work.
- Reload may or may not fix it.
Likely causes
- A server fault. The server or a proxy in front of it sends invalid HTTP/2 frames.
- A proxy or filter. A device in the path can break HTTP/2.
- A bad cache or cookie state. A stale state in the browser can trigger it.
- A large header. Oversized cookies can break a request.
How to check
Open the page in a Private window.
Compare HTTP/2 and HTTP/1.1 with curl.
curl -v --http1.1 -I https://example.comTry another network and browser.
Read the curl output for errors on the HTTP/2 stream.
curl -v --http2 https://example.com
How to fix it
Delete the cookies for the site, then reload.
Turn off the VPN, proxy or security app for a short test. Turn it on again after.
If you run the site, check the proxy and server HTTP/2 setup.
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
Does the error mean my Mac is faulty?
Rarely. If curl and another network fail the same way, the site has the fault.
Is the error the same as QUIC?
No. QUIC is HTTP/3 over UDP. This is HTTP/2 over TCP.
Sources
Checked on 29 October 2026.