First refresh the page and check other websites to confirm whether it is a temporary or single site problem; 2. Clear browser cache and cookies to avoid corrupt data interference with HTTP/2 connections; 3. Temporarily disable all extensions to troubleshoot communication interruptions (such as ad blocking or security tools); 4. Disable "Experimental QUIC protocol" in chrome://flags, force HTTP/1.1 or standard HTTP/2 to eliminate protocol conflicts; 5. Check antivirus software, firewall or proxy settings, temporarily turn off HTTPS scanning function, and eliminate middleware interference to SSL/TLS; 6. Perform DNS refresh and network reset, and run ipconfig /flushdns, /release, /renew and netsh winsock on Windows reset, use dscacheutil and killall commands on Mac, or switch to Google DNS; 7. Update Chrome browser and operating system to ensure there are no known HTTP/2 compatibility issues; 8. Use Ctrl Shift N to turn on traceless mode tests to verify whether errors have been caused by extension or local data; 9. If you are a website administrator, you need to check the validity of SSL certificates, server configuration and HTTP/2 enabled status, and downgrade to HTTP/1.1 if necessary for fault isolation; if the above steps are invalid, you can try to replace the device or network to determine the source of the problem. In most cases, you can solve it by cleaning the cache, disabling QUIC or turning off the interference software.

The ERR_HTTP2_PROTOCOL_ERROR in Google Chrome usually happens when there's a problem with how the browser communicates with a website using the HTTP/2 protocol. It can be caused by network issues, browser settings, extensions, or server-side problems. Here's how to fix it step by step:

1. Refresh the Page and Check Other Sites

Before troubleshooting, confirm it's not a temporary or site-specific issue:

• Press F5 or Ctrl R to reload the page.
• Try opening other websites. If only one site fails, the issue might be on their server.

Some sites misconfigure HTTP/2, causing protocol errors. If only one site is affected, it might resolve on its own.

2. Clear Browser Cache and Cookies

Corrupted cache or cookies can interfere with HTTP/2 connections.

Steps:

• Press Ctrl Shift Delete to open Clear Browsing Data.
• Select "All time" as the time range.
• Check "Cookies and other site data" and "Cached images and files" .
• Click "Clear data" .
• Restart Chrome and try the site again.

3. Disable Extensions Temporarily

Some extensions (especially ad blockers, privacy tools, or security plugins) can disrupt HTTP/2 communication.

How to test:

• Type chrome://extensions in the address bar.
• Toggle off all extensions.
• Reload the problem page.
• If it works, re-enable extensions one by one to find the culprit.

4. Disable QUIC and Force HTTP/1.1

Chrome uses a protocol called QUIC (based on HTTP/3) which can sometimes conflict with HTTP/2.

Disable QUIC:

• Go to: chrome://flags
• Search for "Experimental QUIC protocol"
• Set it to Disabled
• Restart Chrome

This forces Chrome to use HTTP/1.1 or standard HTTP/2, which may resolve the error.

5. Check Antivirus, Firewall, or Proxy Settings

Security software or corporate networks often intercept HTTPS traffic (via SSL/TLS decryption), which can break HTTP/2.

What to do:

• Temporarily disable antivirus/firewall (especially if it has "web protection" or "HTTPS scanning").
• If you're on a company or school network, contact the admin—proxy servers may be interfering.
• Avoid using public Wi-Fi with captive portals or deep packet inspection.

6. Flush DNS and Reset Network

Stale DNS or network settings can cause connection issues.

On Windows:

• Open Command Prompt as admin.
• Run these commands one by one:

   ipconfig /flushdns
  ipconfig /release
  ipconfig /renew
  netsh winsock reset

• Restart your computer.

On Mac:

• Open Terminal and run:

   sudo dscacheutil -flushcache
  sudo killall -HUP mDNSResponder

You can also try switching to Google DNS (8.8.8.8 and 8.8.4.4) in your network settings.

7. Update Chrome and Your System

An outdated browser or OS might have bugs affecting HTTP/2.

• Go to chrome://settings/help to check for Chrome updates.
• Make sure your OS is up to date.

8. Try Incognito Mode

Incognito mode disables most extensions and uses clean session data.

• Press Ctrl Shift N to open an incognito window.
• Visit the site. If it works, the issue is likely with an extension or stored data.

9. Check Server-Side Issues (For Website Owners)

If you're managing the site:

• Ensure your SSL certificate is valid and properly configured.
• Avoid mixing HTTP/1.1 and HTTP/2 resources incorrectly.
• Update your web server (Apache, Nginx, etc.) and reverse proxies.
• Disable HTTP/2 temporarily to test: sometimes falling back to HTTP/1.1 helps isolate the issue.

Most cases are client-side and can be fixed with cache clearing, disabling QUIC, or turning off interfering software. If none work, try accessing the site from another device or network to confirm the root cause.

Basically, start simple—refresh, clear cache, disable extensions—then move to network and protocol settings.

The above is the detailed content of How to fix ERR_HTTP2_PROTOCOL_ERROR in Google Chrome?. For more information, please follow other related articles on the PHP Chinese website!