Google Chrome Error Code ERR_QUIC_SERVER_GOAWAY: How to Fix It

Easy 5-20 minutes Medium Severity Verified June 2026
Summarize with ChatGPTSummarize with ClaudeSummarize with Perplexity Add as Preferred Source on Google
Error Code
ERR_QUIC_SERVER_GOAWAY
Brand
Google Chrome
Product Type
browser
Severity
Medium
DIY Difficulty
Easy
Estimated Fix Time
5-20 minutes
The ERR_QUIC_SERVER_GOAWAY error appears in Google Chrome when the server you are trying to reach sends a signal that it is shutting down its QUIC connection, forcing Chrome to abandon the request before the page fully loads. QUIC is a fast, modern transport protocol built into Chrome that replaces older TCP connections for supported websites, but when a server gracefully closes that channel, Chrome can struggle to switch over to a standard connection cleanly. This error is usually temporary and can almost always be resolved by adjusting Chrome settings, clearing cached data, or disabling the QUIC protocol entirely.
Ad

Tools You'll Need

How to Fix Error Code ERR_QUIC_SERVER_GOAWAY

  1. Reload the Page or Wait Briefly

  2. Clear Chrome's Browser Cache and Cookies

    Clearing cookies will sign you out of most websites. Make sure you know your login credentials before proceeding.

  3. Disable the QUIC Protocol in Chrome Flags

    Disabling QUIC may slightly reduce page load speed on sites optimized for it, but this is an acceptable trade-off for reliability. You can re-enable it at any time by returning to the same flag.

  4. Flush the DNS Cache and Reset Network Settings

  5. Disable Browser Extensions Temporarily

  6. Check and Temporarily Disable Your VPN or Proxy

  7. Update Google Chrome to the Latest Version

  8. Reset Chrome Settings to Default

    Resetting Chrome will disable all extensions and reset all customized settings. Note down any important settings before proceeding.
Ad

When to Call a Professional

This error is almost always solvable without professional help. However, if ERR_QUIC_SERVER_GOAWAY appears consistently across multiple browsers and multiple websites on your network, the issue may be with your router firmware, ISP-level packet filtering, or a corporate firewall that is blocking UDP traffic on port 443 (used by QUIC). In that case, contact your network administrator or IT department. If you are a website owner or developer seeing this error server-side, consult your hosting provider or a network engineer to review your server's QUIC/HTTP3 configuration and graceful connection handling.

Frequently Asked Questions

What does ERR_QUIC_SERVER_GOAWAY mean in Chrome?
It means the server you were connecting to sent a GOAWAY frame over Chrome's QUIC protocol, signaling that it is closing the connection. This typically happens during server restarts, load balancer handoffs, or when a server is briefly overwhelmed. Chrome fails to seamlessly retry with a standard connection, so you see the error instead of the page loading normally.
Is ERR_QUIC_SERVER_GOAWAY a problem with my internet or the website?
It can be either, but it is most commonly triggered by a temporary server-side event on the website you are visiting. Your internet connection itself is usually fine. If you see the error only on one website, the server is the likely cause. If it appears on many websites simultaneously, check your VPN, proxy settings, or router configuration.
Will disabling QUIC in Chrome fix ERR_QUIC_SERVER_GOAWAY permanently?
Yes, disabling the Experimental QUIC protocol flag in chrome://flags will prevent Chrome from using QUIC entirely, which eliminates this specific error permanently. Chrome will fall back to HTTPS over TCP/TLS for all connections. The trade-off is a minor reduction in page load speed on sites that are optimized for QUIC or HTTP/3, though most users will not notice a meaningful difference.
Does ERR_QUIC_SERVER_GOAWAY only happen in Chrome?
Yes, this specific error code is unique to Google Chrome and Chromium-based browsers such as Microsoft Edge and Brave, because QUIC is a protocol developed and implemented by Google. Other browsers like Firefox use HTTP/3 with different underlying implementations and will show different error messages if similar connection issues occur.
Can a VPN cause ERR_QUIC_SERVER_GOAWAY?
Yes, VPNs are a common cause of this error. Many VPN services block or interfere with UDP traffic, and QUIC runs over UDP port 443. When the VPN drops UDP packets, Chrome's QUIC connection fails. Try disconnecting your VPN and reloading the page. If the error disappears, switch to a VPN provider that supports UDP pass-through or configure your current VPN to allow UDP traffic.

Related Error Codes