Browser & network errors

    ERR_QUIC_PROTOCOL_ERROR: The QUIC / HTTP3 connection failed

    Also searched as: net::ERR_QUIC_PROTOCOL_ERROR · QUIC error · HTTP/3 error

    Is ERR_QUIC_PROTOCOL_ERROR happening on your domain?

    An external probe confirms the site responds normally over TCP, isolating the fault to the QUIC path.

    Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.

    Short answer

    The browser tried HTTP/3 over QUIC and the connection failed. Often a network path that mishandles UDP, or a CDN advertising HTTP/3 support it cannot deliver on that route.

    What ERR_QUIC_PROTOCOL_ERROR means

    QUIC runs over UDP rather than TCP. Networks that filter or rate-limit UDP break it, and because browsers advertise HTTP/3 via Alt-Svc, the failure can appear only after the first successful visit.

    Causes and fixes, most likely first

    most common

    A firewall or network filters UDP port 443.

    Allow UDP 443, or disable HTTP/3 advertising at the CDN so clients stay on TCP.

    common

    The CDN advertises HTTP/3 but a middlebox breaks the QUIC handshake.

    Turn off HTTP/3 at the CDN while investigating. The site will fall back to HTTP/2 with no visible difference to users.

    How to stop it happening again

    • •Verify HTTP/3 works from multiple networks before leaving it enabled — its failures are network-specific and invisible from a single vantage point.

    Frequently asked questions

    Why does the error only appear on repeat visits?

    Because the browser learns about HTTP/3 from the Alt-Svc header on the first response, then tries QUIC on the next visit.

    Related errors

    Monitor this continuously with LemWatch

    A one-off err_quic_protocol_error monitoring shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.

    Last verified: by the Lemwatch research team.