What Is ERR_QUIC_PROTOCOL_ERROR and How Do You Fix It in Chrome?

ERR_QUIC_PROTOCOL_ERROR is a connection error showing that Chrome ran into a problem while connecting to a site using the QUIC protocol. Chrome then shows the “This site can’t be reached” page with the code ERR_QUIC_PROTOCOL_ERROR. The error often appears only on certain sites (especially Google services and sites that support HTTP/3) and only on certain networks. In this guide we explain what QUIC is, why the error happens and how to fix it.

What Is QUIC and What Does the Error Mean?

QUIC is a transport protocol developed by Google and later standardized; HTTP/3 runs on top of it. While classic HTTPS connections use TCP, QUIC runs over UDP port 443 and aims to set up connections faster. When the browser learns that a site supports QUIC, it tries to use that protocol. If a device or piece of software in between blocks or damages UDP traffic, the QUIC connection fails and ERR_QUIC_PROTOCOL_ERROR appears.

Causes of the ERR_QUIC_PROTOCOL_ERROR Error

• A firewall or antivirus blocks UDP: Some security software and corporate firewalls cut UDP 443 traffic, or block it because they cannot inspect it.
• VPN or proxy: VPNs and proxies that do not carry UDP traffic properly break QUIC connections.
• Router or network device: Some routers and network filters drop UDP packets.
• Browser extensions: Extensions that modify requests can be incompatible with QUIC.
• Configuration on the server or CDN side: If a site advertises HTTP/3 but UDP port 443 is closed on the server, or the HTTP/3 configuration is wrong, the connection fails.

How to Fix ERR_QUIC_PROTOCOL_ERROR

1. Reload the Page and Try a Different Network

When QUIC fails, Chrome usually falls back to TCP on the next attempt; reloading the page a few times is sometimes enough. Try opening the site on mobile data: if it opens, something on your network is blocking QUIC.

2. Turn Off the QUIC Protocol in Chrome

The quickest fix is to stop Chrome from using QUIC. Type chrome://flags/#enable-quic in the address bar, set Experimental QUIC protocol to Disabled and restart the browser with Relaunch (experimental flags can change between Chrome versions; if it is not listed, move on to the other steps). After this, Chrome opens sites over classic HTTPS (TCP), and sites keep working normally. On centrally managed computers this setting may be controlled by an administrator policy.

3. Check Security Software, VPN and Proxy

Briefly turn off your antivirus web protection or firewall and try again; if you use a VPN or proxy, disconnect it. If that solves the problem, allow Chrome or UDP 443 traffic in the software’s settings.

4. Turn Off Extensions

Open the site in an incognito window. If it opens, turn extensions off one by one on the chrome://extensions page to find the problem one.

5. Reset Network Settings

On Windows, open Command Prompt as administrator, run netsh winsock reset and ipconfig /flushdns, then restart the computer and the router.

For Site Owners: HTTP/3 and QUIC Configuration

If your visitors get this error on your site from different networks, check your HTTP/3 configuration:

1. Make sure UDP 443 is open: If the server supports HTTP/3, the firewall must allow UDP 443 in addition to TCP 443 (for example ufw allow 443/udp).
2. Check the Alt-Svc header: The browser learns that a site supports HTTP/3 from the Alt-Svc response header. If HTTP/3 is not working properly, no longer sending this header stops browsers from trying QUIC.
3. Review the CDN setting: On CDNs such as Cloudflare, the HTTP/3 (QUIC) feature can be turned on and off from the dashboard. You can turn it off temporarily to isolate the cause.
4. Keep the web server up to date: HTTP/3 support in LiteSpeed, Nginx and other servers improves with each version; outdated versions can cause compatibility problems.

For similar cases where the connection cannot be established or is cut midway, see our guides on ERR_CONNECTION_TIMED_OUT and ERR_CONNECTION_RESET.

Conclusion

ERR_QUIC_PROTOCOL_ERROR shows that Chrome’s QUIC connection, which runs over UDP, failed. As a visitor, the quickest fix is to turn off QUIC in chrome://flags and check security software, the VPN and extensions. If you own the site, review UDP port 443, the Alt-Svc header and the HTTP/3 setting on your CDN.