---
title: "ERR_HTTP2_PROTOCOL_ERROR in Chrome on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/err-http2-protocol-error"
description: "Chrome on your Mac shows ERR_HTTP2_PROTOCOL_ERROR. The HTTP/2 layer failed. Test with a Private window, curl and another network."
---

# 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.”

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

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.

Applies to: Google Chrome and other Chromium browsers (Edge, Brave, Arc) on all current macOS versions. · Checked: 29 October 2026

## 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

1. Open the page in a Private window.
2. Compare HTTP/2 and HTTP/1.1 with curl.

   ```
   curl -v --http1.1 -I https://example.com
   ```
3. Try another network and browser.
4. Read the curl output for errors on the HTTP/2 stream.

   ```
   curl -v --http2 https://example.com
   ```

## How to fix it

1. Delete the cookies for the site, then reload.
2. Turn off the VPN, proxy or security app for a short test. Turn it on again after.
3. If you run the site, check the proxy and server HTTP/2 setup.
4. Update Chrome.

## With Kilobat

1. 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.com
   ```
2. These Kilobat checks are free. AI agents run them through MCP with `diagnose_connection` and `diagnose_network`. See [Find why one site or API won't connect](https://kilobat.app/guides/recipes/why-cant-it-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

- [Chromium source: net_error_list.h](https://chromium.googlesource.com/chromium/src/+/main/net/base/net_error_list.h)
- [Chrome Help: Fix connection errors](https://support.google.com/chrome/answer/95669)

Checked on 29 October 2026.

## Related guides

- [ERR_QUIC_PROTOCOL_ERROR in Chrome on Mac](https://kilobat.app/guides/err-quic-protocol-error): ERR_QUIC_PROTOCOL_ERROR is a Chrome network error.
- [ERR_CONNECTION_RESET in Chrome on Mac](https://kilobat.app/guides/err-connection-reset): ERR_CONNECTION_RESET is a Chrome network error.
- [ERR_TOO_MANY_REDIRECTS in Chrome on Mac](https://kilobat.app/guides/err-too-many-redirects): ERR_TOO_MANY_REDIRECTS is a Chrome network error.
- [“curl: (56) Failure when receiving data” on Mac](https://kilobat.app/guides/curl-56-failure-receiving-data): curl exit code 56 reports a failed step.
