---
title: "ERR_QUIC_PROTOCOL_ERROR in Chrome on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/err-quic-protocol-error"
description: "Chrome on your Mac shows ERR_QUIC_PROTOCOL_ERROR. The HTTP/3 transport failed. Check UDP filtering, VPNs and the network."
---

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

**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_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.

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

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

1. Reload the page once. Chrome may then use TCP.
2. Test the site over HTTP/2 with curl.

   ```
   curl -v --http2 https://example.com
   ```
3. Try another network.
4. Turn off the VPN for a short test.

## How to fix it

1. Turn off the VPN or security app for a short test. Turn it on again after.
2. Ask the network administrator to allow UDP port 443.
3. If the failure stays, compare the site over HTTP/2 with curl and report the result to the site.
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

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

- [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_HTTP2_PROTOCOL_ERROR in Chrome on Mac](https://kilobat.app/guides/err-http2-protocol-error): ERR_HTTP2_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.
- [VPN connected but no internet on a Mac](https://kilobat.app/guides/vpn-connected-no-internet): A VPN sends traffic through a tunnel.
- [Test for packet loss on a Mac with ping](https://kilobat.app/guides/packet-loss-mac): Packet loss makes calls break up and pages stall.
