HostingTekniset asiat5 min lukuaikaLanetti

How to fix ERR_QUIC_PROTOCOL_ERROR in Google Chrome: 3 methods

Chrome sometimes fails on QUIC even when your site is healthy. Try these three fixes before you assume the server is down.

What is ERR_QUIC_PROTOCOL_ERROR?

ERR_QUIC_PROTOCOL_ERROR means the browser could not reach the server over QUIC (Quick UDP Internet Connections). Unlike a normal HTTP status code, this is a transport-layer failure. Visitors may see Chrome's "This site can't be reached" message even when the site is up on classic HTTPS.

Error typeNetwork protocol error
Common causesQUIC enabled in the browser, conflicting extensions, proxy or VPN misconfiguration, firewall blocking UDP 443

What causes ERR_QUIC_PROTOCOL_ERROR

Chrome can prefer QUIC for faster, encrypted UDP transport. Not every host or path supports it end to end. When QUIC negotiation fails, Chrome may refuse the page even though the site works over standard HTTPS.

QUIC enabled in Google Chrome

QUIC sits on UDP rather than TCP. It can reduce latency for some workloads, but compatibility varies. A host that serves HTTPS correctly may still fail when the browser insists on QUIC.

QUIC also expects a valid TLS setup. Sites without proper HTTPS may fail QUIC negotiation first. Lanetti hosting plans include free SSL; install it before you debug protocol errors.

Browser extensions

Privacy, VPN and ad-blocking extensions can intercept or rewrite connections. A broken or outdated extension is a frequent cause of QUIC errors on otherwise healthy sites.

Proxy settings

System or browser proxy settings that do not forward UDP correctly can block QUIC while leaving ordinary HTTPS untouched.

Quick checks before deeper fixes

  • Open the URL in Firefox, Safari or Edge. If it loads elsewhere, the server is likely fine and the issue is local to Chrome or QUIC.
  • Clear cache and cookies for the site.
  • Confirm UDP port 443 is allowed on your network firewall.
  • Test HTTP/3 support with an external checker if you manage the server.

3 ways to fix ERR_QUIC_PROTOCOL_ERROR

1. Disable QUIC in Chrome

  1. Open chrome://flags.
  2. Search for Experimental QUIC protocol.
  3. Set it to Disabled.
  4. Restart Chrome.

2. Disable Chrome extensions

  1. Open chrome://extensions or choose More tools → Extensions.
  2. Turn off extensions one by one, or disable all and re-enable as needed.
  3. Restart Chrome and reload the page.

3. Check proxy settings on Windows

  1. Open Control Panel → Network and Internet → Internet Options.
  2. On the Connections tab, click LAN settings.
  3. Uncheck Use a proxy server for your LAN unless your network requires a proxy.
  4. Save and retry the site.

Conclusion

ERR_QUIC_PROTOCOL_ERROR usually points to QUIC, an extension or proxy settings rather than a broken website. Disable QUIC, test without extensions and verify proxy configuration. If the error only affects your own site on Lanetti, open a support ticket with the URL and browser version so we can review HTTP/3 and TLS settings on the server.

Usein kysytyt kysymykset

You may see connection reset, stream reset or invalid flow control window messages. They all indicate QUIC failed before a normal HTTP response was returned.

Oppaat tarkistetaan säännöllisesti. Vaiheet voivat vaihdella selainversion mukaan.

Liittyvät oppaat

Eikö onnistu?

Avaa tukipyyntö ja liitä mukaan URL, selain ja mahdollinen virhekoodi.

Ota yhteyttä tukeen