ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • Web browsers

ERR_QUIC_PROTOCOL_ERROR

ERR_QUIC_PROTOCOL_ERROR in Google Chrome: QUIC protocol failure

Verified with sources4 sourcesReviewed Oct 3, 2026
Technician coming? See the 2 steps they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

Chrome detected an error in the QUIC protocol while talking to the site. Reload, update Chrome and test in Incognito and from another network; if it only fails on one network, check that network's firewall.

Safety first

Stop and check this first

  • Do not change Chrome's experimental settings to get around the error: they are not part of the steps in Chrome's official help for connection errors.

Safe checks you can perform

  • Reload and Chrome version
  • Incognito mode and extensions
  • The site from another network
  • QUIC on the server and on the network

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Review HTTP/3 on the server
  • Do not attempt this professional task: Review UDP handling on the network

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Review HTTP/3 on the server

    What they doThe operator reviews the QUIC and HTTP/3 configuration of the server or its delivery network, and its logs.

    They must show youthe protocol error logged at the server.

    In writingthe setting changed and the follow-up test.

  2. Review UDP handling on the network

    What they doThe network administrator checks whether the firewall blocks or modifies UDP traffic to the site.

    They must show youthe rule or log entry involved.

    In writingthe change applied and for which destinations.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Reload and Chrome version

    No special tools

    Who:
    you.
    How:
    reload the page, update Chrome and restart it.
    Result that matters:
    whether the error repeats with Chrome up to date.
    If it goes away:
    it was transient or tied to the old version.
    If it persists with Chrome updated:
    continue with Incognito and another network.
    Evidence to keep:
    Chrome version and time of the failure.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

  2. Incognito mode and extensions

    No special tools

    Who:
    you.
    How:
    open the address in an Incognito window; if it works, disable extensions and re-enable them one at a time.
    Result that matters:
    whether a specific extension triggers the failure.
    If it fails only with one extension on:
    that extension is the cause.
    If it also fails in Incognito:
    rule out extensions.
    Evidence to keep:
    name of the extension involved, if any.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

  3. The site from another network

    No special tools

    Who:
    you.
    How:
    test the same site on mobile data or from another Wi-Fi network.
    Result that matters:
    whether the failure depends on the network.
    If it works on another network:
    it points to your network's firewall or filter; tell its administrator.
    If it fails everywhere:
    it points to the site; tell its operator, with the time.
    Evidence to keep:
    networks tried and result.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome · RFC 9000 - QUIC: A UDP-Based Multiplexed and Secure Transport

  4. QUIC on the server and on the network

    Tools required

    Who:
    the site operator or the administrator of the affected network.
    How:
    review the HTTP/3 configuration of the server or delivery network, and whether the firewall allows UDP traffic to that destination without modifying it.
    Result that matters:
    whether the QUIC connection completes without errors.
    If it fails at the server:
    the HTTP/3 configuration is the cause to fix.
    If it only fails through a firewall:
    it indicates that filter alters UDP traffic.
    Evidence to keep:
    server and firewall logs with the time.

    Only the site operator or the network administrator. If you do not manage those systems, do not do it yourself.

    Evidence: RFC 9000 - QUIC: A UDP-Based Multiplexed and Secure Transport · RFC 9114 - HTTP/3

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Google Chrome
Product type
Web browsers

Known code variants

  • ERR_QUIC_PROTOCOL_ERROR
  • ERR_QUIC_PROTOCOL_ERROR (-356)
  • ERR_QUIC_PROTOCOL_ERROR Chrome
  • net::ERR_QUIC_PROTOCOL_ERROR

What it means

Chromium defines ERR_QUIC_PROTOCOL_ERROR (-356) as a QUIC protocol error and places it among its HTTP errors. QUIC is the transport defined in RFC 9000, which runs over UDP, and HTTP/3 (RFC 9114) is the mapping of HTTP over QUIC. The code does not say whether the problem is at the server, at a device in the network path or on your device: you separate them by comparing networks and reviewing the site's QUIC configuration.

Warnings and stop conditions

  • Loweditorial warning

    Do not change Chrome's experimental settings to get around the error: they are not part of the steps in Chrome's official help for connection errors.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

Symptoms and causes

Probable causes · in order

  • The site's QUIC or HTTP/3 configurationPossible

    If the error appears from several networks and devices, the problem is at the server or its delivery network.

    Evidence: Chromium source - net/base/net_error_list.h (network error list) · RFC 9114 - HTTP/3

  • A network that alters or blocks UDP trafficPossible

    QUIC uses UDP. If the site only fails on one particular network, a firewall on that network may be interfering.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome · RFC 9000 - QUIC: A UDP-Based Multiplexed and Secure Transport

  • Extension or software on the devicePossible

    If it works in Incognito, an extension or browser data is involved.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

Virtual technician

Does ERR_QUIC_PROTOCOL_ERROR still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    Chromium source - net/base/net_error_list.h (network error list)

    The Chromium Authors · 2026 · official_doc

  2. 2

    Google Chrome Help - Fix connection and loading errors in Chrome

    Google · 2026 · official_doc

  3. 3

    RFC 9000 - QUIC: A UDP-Based Multiplexed and Secure Transport

    IETF / RFC Editor · 2021 · standard

  4. 4

    RFC 9114 - HTTP/3

    IETF / RFC Editor · 2022 · standard

Sources: Chromium source - net/base/net_error_list.h (network error list) · Google Chrome Help - Fix connection and loading errors in Chrome · RFC 9000 - QUIC: A UDP-Based Multiplexed and Secure Transport · RFC 9114 - HTTP/3reviewed 2026-10-03 · verified

Was this entry useful?