HTTP/2 is a faster version of HTTP that multiplexes requests over a single connection. Most modern websites use it.

Will disabling HTTP/2 fix it permanently?

It is a workaround, not a fix. Disabling HTTP/2 forces HTTP/1.1 which is slower. Better to report the issue to the website.

Chrome ERR_HTTP2_PROTOCOL_ERROR — HTTP/2 Protocol Failure

Errorchrome errors

Overview

Chrome ERR_HTTP2_PROTOCOL_ERROR indicates an HTTP/2 framing error between the browser and server, often caused by server misconfiguration or proxy interference.

Key Details

HTTP/2 is a binary protocol with strict framing requirements
Servers, proxies, or CDNs can send malformed HTTP/2 frames
More common with reverse proxies like nginx misconfigured for HTTP/2
Can be intermittent if the issue is related to specific request types
Chrome is stricter about HTTP/2 compliance than some other browsers

Common Causes

Server or reverse proxy sending malformed HTTP/2 frames
Content-Length header mismatch with actual response body size
Proxy or CDN incorrectly handling HTTP/2 stream multiplexing
Server closing HTTP/2 streams unexpectedly (GOAWAY or RST_STREAM)
Response body truncated due to upstream timeout

Steps

1Test in Firefox — if it works there, the server may have a Chrome-specific HTTP/2 issue
2Try disabling HTTP/2: type chrome://flags, search 'HTTP/2', disable and restart Chrome (temporary test)
3Open Chrome DevTools > Network > check the failing request for response headers
4If you own the server, check nginx/Apache HTTP/2 configuration and update to latest version
5Report the issue to the website — it is likely a server-side configuration problem