Chrome ERR_HTTP2_PROTOCOL_ERROR: Meaning & Fixes

If you see ERR_HTTP2_PROTOCOL_ERROR in Chrome, it means the browser and the website failed to communicate using the HTTP/2 protocol, and Chrome aborted the connection. This is usually a temporary glitch, a faulty browser extension, or a server-side misconfiguration; clearing the site’s data, disabling extensions, or switching to a different network fixes it in most cases.

What Is HTTP/2 and Why Does This Error Happen?

HTTP/2 is the second major version of the Hypertext Transfer Protocol, introduced in 2015 to make web pages load faster. Instead of opening a new connection for every file (images, scripts, stylesheets), HTTP/2 multiplexes many requests over a single connection, compresses headers, and lets servers push resources before they are requested.

Chrome displays ERR_HTTP2_PROTOCOL_ERROR when it detects something invalid in that HTTP/2 communication. The error is not a security warning; it simply means the data stream was malformed, interrupted, or violated the protocol’s rules. Chrome then kills the connection and shows the error page instead of the website.

Common Causes of ERR_HTTP2_PROTOCOL_ERROR

The error can originate from your computer, your network, or the website’s server. Here are the most frequent culprits:

Corrupted cache or cookies – Stored data for the site may be outdated or broken, causing a conflict with the new HTTP/2 session.
Browser extensions – Ad blockers, privacy tools, or VPN extensions can interfere with HTTP/2 headers or redirect requests.
Antivirus or firewall software – Some security programs intercept HTTPS traffic and may corrupt the HTTP/2 stream.
Network issues – A flaky Wi-Fi connection, a misbehaving router, or a proxy server can drop or reorder HTTP/2 frames.
Server misconfiguration – The website’s hosting provider may have an incorrect HTTP/2 setting, an outdated SSL certificate, or a buggy CDN (Content Delivery Network) that sends invalid frames.
Chrome flags or experimental features – If you’ve enabled experimental network flags in chrome://flags, they can break HTTP/2.

How to Fix ERR_HTTP2_PROTOCOL_ERROR in Chrome

Try these fixes in order, from simplest to most involved. After each step, reload the page to see if the error is gone.

Reload the page and try incognito mode. Press Ctrl+Shift+R (or Cmd+Shift+R on Mac) to do a hard reload that bypasses the cache. If that fails, open an incognito window (Ctrl+Shift+N) and visit the site. If it loads there, the problem is likely cache- or extension-related.
Clear the site’s cache and cookies. Go to Chrome’s menu (three dots) → Settings → Privacy and security → Third-party cookies → See all site data and permissions. Search for the domain, click the trash icon, and reload. This removes any corrupted HTTP/2 state stored for that site.
Disable browser extensions. Type chrome://extensions in the address bar, toggle off all extensions, and reload the page. If the error disappears, re-enable extensions one by one to find the offender. Pay special attention to ad blockers and privacy extensions.
Turn off your VPN or proxy. If you’re using a VPN or a proxy extension, temporarily disable it. Some VPNs use HTTP/2 themselves and can cause conflicts. Also check your system’s proxy settings: on Windows, go to Settings → Network & Internet → Proxy; on Mac, System Settings → Network → Proxies.
Flush the DNS cache and reset network settings. Open a command prompt (Windows) or terminal (Mac/Linux) and run ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (Mac). Then restart your router by unplugging it for 30 seconds. This clears any stale DNS entries that might be directing you to a broken server.
Disable experimental Chrome flags. Type chrome://flags, look for any flag related to HTTP/2 or network (like “HTTP/2” or “Parallel downloading”), and set them back to “Default” or “Disabled”. Then click “Relaunch”.
Reset Chrome settings to default. Go to Settings → Reset settings → Restore settings to their original defaults. This disables extensions, clears temporary data, and resets flags without deleting your bookmarks or passwords.
Try another browser or device. If the error persists in Chrome but the site works in Firefox or Edge, the issue is Chrome-specific. If it fails everywhere, the problem is on the website’s side.

When the Problem Is on the Website’s Side

Sometimes you can’t fix it from your end. If the error happens on multiple devices and browsers, the website’s server is likely misconfigured. Common server-side causes include:

An outdated or invalid SSL/TLS certificate that doesn’t support HTTP/2’s ALPN (Application-Layer Protocol Negotiation).
A CDN or load balancer that is not properly configured for HTTP/2, sending frames that violate the spec.
Server software (like nginx or Apache) with a buggy HTTP/2 module or incorrect settings.
Aggressive firewall rules that drop HTTP/2 frames, especially if the site uses a Web Application Firewall.

In that case, you can try accessing the site over HTTP (if the site allows it) by replacing https:// with http:// in the URL, though this may not work if the site redirects. You can also use a public DNS service like Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) to rule out DNS issues. If the site is critical and you need it immediately, try a different browser or a mobile device on a different network (like cellular data) to confirm the server is the problem.

Does This Error Mean My Computer Is Infected?

No. ERR_HTTP2_PROTOCOL_ERROR is not a sign of malware, a virus, or a hacking attempt. It’s a technical communication failure between your browser and the server. However, if you see this error repeatedly on many different websites, it could indicate that your network is tampering with HTTPS traffic—for example, a corporate proxy or a malicious router. In that case, run a malware scan and check your router’s DNS settings for anything unusual.

Is It Safe to Ignore the Error?

If you see the error once and the page loads after a refresh, you can safely ignore it. It’s often a transient network hiccup. But if the error appears frequently on the same site, it may be a sign of an unstable connection or a server problem. There’s no security risk in seeing the error itself; the danger would be if you try to bypass it by disabling security features. Don’t disable Chrome’s safe browsing or SSL checks to fix this—that would expose you to real threats.

Frequently Asked Questions

Why does ERR_HTTP2_PROTOCOL_ERROR happen only on some websites?
Because each website has its own server configuration. Some servers have HTTP/2 set up correctly, others don’t. If a specific site is misconfigured, you’ll see the error only there. Your local cache or extensions can also be site-specific if they interact with that site’s resources.

Can I force Chrome to use HTTP/1.1 instead of HTTP/2?
Yes, but it’s not a permanent fix. You can disable HTTP/2 in Chrome by launching it with the command-line flag --disable-http2. On Windows, right-click the Chrome shortcut, go to Properties, and add that flag to the Target field. On Mac, you’d need to run Chrome from the terminal with that flag. This forces HTTP/1.1 for all sites, which may fix the error but slows down modern websites. It’s better to find the root cause.

Does clearing the cache delete my passwords?
No. Clearing the cache and cookies for a specific site removes temporary files and cookies, but not saved passwords. If you use Chrome’s “Clear browsing data” and check “Passwords and other sign-in data”, then yes, it will delete passwords. But the steps above only clear site data, not passwords.

Why does the error appear in Chrome but not in Firefox?
Different browsers implement HTTP/2 slightly differently. Chrome may be stricter about protocol violations, while Firefox might tolerate a malformed frame. Also, Chrome and Firefox store separate caches and extensions, so a corrupted cache in Chrome won’t affect Firefox. This is why trying another browser is a useful diagnostic step.

Is ERR_HTTP2_PROTOCOL_ERROR related to ERR_CONNECTION_RESET?
They are different errors. ERR_CONNECTION_RESET means the TCP connection was abruptly closed by the server or a network device, while ERR_HTTP2_PROTOCOL_ERROR means the connection was established but the HTTP/2 data exchange failed. Both can be caused by network interference, but the fixes overlap: clear cache, disable extensions, and check your network.

Will this error go away on its own?
Often yes, if it’s a temporary server glitch or a brief network issue. If it’s due to a corrupted cache or a problematic extension, it will persist until you take action. If it’s a server misconfiguration, it will persist until the site owner fixes it, which could take hours or days.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →