home / browser errors / err-http2-protocol-error

[ REPAIR GUIDE ] BROWSER ERRORS

How to fix ERR_HTTP2_PROTOCOL_ERROR

ERROR DETECTED >This site can't be reached. The webpage at https://example.com/ might be temporarily down or it may have moved permanently to a new web address. ERR_HTTP2_PROTOCOL_ERROR

UPDATED NOVEMBER 20262 MIN READ7 FIXES

QUICK FIX

Reload, clear cached files and try an Incognito window. If the error happens on one site for everyone, the site's server or CDN is sending a bad HTTP/2 response and the owner must fix it.

What it means

Your browser and the website were using HTTP/2, a common way of sending web pages, and the site's reply broke the HTTP/2 rules, so the browser stopped. It is usually a server or proxy problem, but security software, extensions or stale cache on your side can trigger it too.

Common causes

  • The server or a proxy sends invalid HTTP/2 headers or responses
  • A server or proxy cuts off large responses or times out mid-transfer
  • Antivirus or a network device inspecting HTTPS traffic
  • A browser extension changing requests or headers
  • Stale cached data
  • An outdated browser

How to fix it

Work down the list. Each fix is safe to try before moving on to the next.

FIX 01Reload and test other sitesEASY

  1. Press F5 (Windows) or Cmd + R (Mac).
  2. Try a few other sites.
  3. Try the problem site on another device. If it fails everywhere, the site is the cause.

Why it helps: Separates a site problem from a device problem.

FIX 02Clear cache and cookiesEASY

  1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac).
  2. Choose All time, tick Cookies and other site data and Cached images and files, and delete.
  3. Reload the page.

Why it helps: Removes stale data that can produce a bad request.

FIX 03Try Incognito and turn off extensionsEASY

  1. Press Ctrl + Shift + N (Windows) or Cmd + Shift + N (Mac) and open the site.
  2. If it works there, turn off extensions at chrome://extensions (or edge://extensions) one at a time.

Why it helps: Extensions that change headers can break HTTP/2 responses.

FIX 04Update the browserEASY

  1. Chrome: More (three dots) > Help > About Google Chrome, then Relaunch.
  2. Edge: Settings and more (three dots) > Help and feedback > About Microsoft Edge.

Why it helps: Fixes browser-side bugs.

FIX 05Turn off VPN and pause HTTPS scanningMEDIUM

  1. Disconnect any VPN and try another network.
  2. If your antivirus has HTTPS scanning, turn it off briefly, reload, then turn it back on right away.

Why it helps: Tools that inspect secure traffic can corrupt HTTP/2 responses.

// RUN THIS SITE? FIXES FOR SITE OWNERS

FIX 06Check response headers and server logsADVANCEDSITE OWNERS

  1. Open your browser's developer tools, go to the Network tab and find the request that fails.
  2. Check your application and web server error logs at that time.
  3. Make sure the app does not send connection-specific headers such as Connection, Keep-Alive, Transfer-Encoding or Upgrade, and that header names are valid; HTTP/2 treats these as malformed.
  4. Check for proxy or server limits on response size, header size or timeouts that may cut responses short.

Why it helps: Invalid headers and truncated responses are common server-side triggers.

FIX 07Test with HTTP/2 turned offADVANCEDSITE OWNERS

  1. Temporarily disable HTTP/2 on your server or CDN to confirm whether it is the trigger.
  2. On Cloudflare (Pro plan and above), use Speed > Settings > Protocol Optimization and switch HTTP/2 off; it cannot be turned off on the Free plan.
  3. Fix the underlying header or proxy issue, then turn HTTP/2 back on.

Why it helps: Confirms the cause without leaving the site on an older protocol.

Check it's fixed

  • The page loads fully without the error.
  • The Network tab in developer tools shows the request completing.
  • The site loads on another browser and device.

When to get help

Visitors should report the error to the site owner if it fails everywhere. Site owners should ask their host or CDN support if logs show nothing.

Questions

What is HTTP/2?

It is a newer version of the protocol browsers use to fetch web pages. Most secure sites use it today.

Why does the console show ERR_HTTP2_PROTOCOL_ERROR 200?

The server started a successful response but the connection broke the protocol before it finished, often because of a proxy, timeout or invalid header.

Can I fix it if it is the website's fault?

Not really. You can only report it to the site owner, though clearing cache and trying another browser are worth a quick test.

Related fixes

How to fix ERR_QUIC_PROTOCOL_ERRORReload the page, then turn off any VPN or proxy and test another network. If the error keeps coming back, temporarily set Chrome's ExpeHow to fix ERR_SSL_PROTOCOL_ERRORMake sure your device's date and time are set automatically, then clear the browser's cached images and files and reload. If it onHow to fix ERR_CONNECTION_RESETRestart your router and the browser, then turn off any VPN or proxy and reload. If the page works on another network, your network or a filtHow to fix HTTP error 500 (500 Internal Server Error)If you are visiting the site, refresh after a minute or two and try again later; the fault is on the server. If you own the site, check the How to fix 504 Gateway TimeoutAs a visitor, wait a minute and reload, then try another network if it keeps happening. As a site owner, find what is making the origin serv

Still stuck?

Paste the exact message and the repair bot will find the closest fix, or search it on Google, Microsoft, Apple, Reddit and YouTube.

Sources