The ERR_QUIC_PROTOCOL_ERROR message is an error that shows up in the Google Chrome browser when you try to visit a site.

Typically, the full error reads something like:

This site can’t be reached, The webpage at might be temporarily down or it may have moved permanently to a new web address,


In this article, we’ll cover two things to help get your browser working again:



As the name suggests, this error indicates some problem with Chrome’s use of its Quick UDP Internet Connections (QUIC protocol) feature.

The QUIC protocol was developed by Google and helps improve the performance of connection-oriented web applications.

According to W3Techs, only about 3.2% of websites on the Internet are using the QUIC protocol, which means most of the websites you use will not use this protocol.

However, because Google developed the protocol for its own products, most of Google’s sites do use QUIC (including YouTube). So while the protocol’s overall usage rate is not high, the fact that Google uses QUIC means you’ll interact with sites using QUIC pretty much every day.

Sometimes, the ERR_QUIC_PROTOCOL_ERROR message could be directly caused by the protocol, but it can also be caused by a problem with your Internet connection (or VPN/proxy) or an issue with a browser extension.

Additionally, this error has nothing to do with your WordPress site. However, it can prevent you from accessing your WordPress site sometimes, which is why we’re helping you fix the issue.

How to Fix the ERR_QUIC_PROTOCOL_ERROR in Chrome

There are a few different methods to fix the ERR_QUIC_PROTOCOL_ERROR, which we’ll demonstrate below:

Solution 1: Disable the QUIC Protocol in Chrome

Because the error indicates a problem with the QUIC protocol, one solution is to simply disable the QUIC protocol in Chrome.

To do so, type chrome://flags/ into your Chrome browser address bar. Then, use the search box to search for “quic” to locate the protocol.

From there, use the drop-down to change from Default to Disabled:

How to disable QUIC protocol in Chrome
How to disable QUIC protocol in Chrome

Once you’ve disabled the Experimental QUIC protocol, restart the Chrome browser to make the changes take effect.

Solution 2: Disable Chrome Extensions

Sometimes, it could be an issue with one of your Chrome extensions that’s causing the error.

Unfortunately, there’s no way to diagnose the exact extension so the best approach is to disable all of your extensions and then re-enable them one-by-one to find the culprit.

If you only started seeing the ERR_QUIC_PROTOCOL_ERROR message after installing a new extension, you can try disabling that extension first.

To disable your Chrome extensions, you can enter chrome://extensions/ in your browser address bar:

How to disable Chrome browser extensions
How to disable Chrome browser extensions

Then, use the toggle to enable and disable extensions as needed.

Solution 3: Check Proxy Settings (Windows)

If you’re using Windows, you might have an issue with your proxy settings that’s causing the ERR_QUIC_PROTOCOL_ERROR message.

To get started, open your Settings area in Windows (hit the Windows key and then select the Settings gear).

Then, search for Internet Options and select the result:

How to access Internet Options in Windows
How to access Internet Options in Windows

In the Internet Properties popup, go to the Connections tab. Then, select LAN settings:

How to access LAN settings
How to access LAN settings

Make sure that the Use a proxy server for your LAN… setting is unchecked. Then, click OK and then Apply. You might also need to restart your computer:

Check the proxy settings
Check the proxy settings


The ERR_QUIC_PROTOCOL_ERROR message is an error that’s specific to the Chrome Browser and its use of the Quick UDP Internet Connections (QUIC protocol).

It has nothing to do with your WordPress site itself, but it might prevent you from accessing your WordPress site.

To fix the issue, you can try:

  • Disabling the Experimental QUIC protocol in Chrome’s settings
  • Disabling your Chrome browser extensions
  • Changing your Windows proxy settings