Google Chrome ERR_QUIC_HANDSHAKE_FAILED: How to Fix It

Easy 10-25 minutes Medium Severity Verified June 2026
Summarize with ChatGPTSummarize with ClaudeSummarize with Perplexity Add as Preferred Source on Google
Error Code
ERR_QUIC_HANDSHAKE_FAILED
Brand
Google Chrome
Product Type
browser
Severity
Medium
DIY Difficulty
Easy
Estimated Fix Time
10-25 minutes
The ERR_QUIC_HANDSHAKE_FAILED error in Google Chrome occurs when the browser's QUIC protocol — a fast, modern transport layer used to connect to Google and other servers — fails to complete its security handshake. This typically happens due to network restrictions, firewall rules, outdated browser settings, or conflicts with your internet connection that block the UDP ports QUIC relies on. The good news is this error is almost always fixable through browser settings or network configuration changes without any technical expertise.
Ad

Tools You'll Need

How to Fix Error Code ERR_QUIC_HANDSHAKE_FAILED

  1. Disable QUIC Protocol in Chrome Flags

  2. Clear Chrome Browser Cache and Cookies

  3. Check and Temporarily Disable Your Firewall or Antivirus

    Never leave your firewall or antivirus disabled for longer than necessary. Re-enable it as soon as your test is complete to keep your system protected.

  4. Flush DNS Cache and Reset Network Settings

  5. Change Your DNS Server to a Public DNS

  6. Update Google Chrome to the Latest Version

  7. Disable VPN or Proxy and Check Router Settings

  8. Reset Chrome Settings to Default

    Resetting Chrome will disable all your extensions and revert custom settings. Make a note of any important extensions or settings before proceeding.
Ad

When to Call a Professional

If you have tried all the steps above and the error persists across multiple websites and multiple devices on the same network, the issue likely lies with your ISP or corporate network infrastructure blocking QUIC traffic at a higher level. Contact your Internet Service Provider and report that UDP traffic on port 443 may be blocked. If you are on a corporate or school network, contact your IT department — they may have intentionally restricted QUIC for security policy reasons and can either whitelist it or advise on approved alternatives. Additionally, if you are uncomfortable editing network adapter settings or running command-line tools, a local computer technician can perform these steps safely for you.

Frequently Asked Questions

What causes ERR_QUIC_HANDSHAKE_FAILED in Chrome?
This error is caused when Chrome's QUIC protocol cannot complete its security handshake with a server. Common causes include firewalls or antivirus software blocking UDP traffic on port 443, VPNs that don't support QUIC, network routers or ISPs that restrict UDP packets, outdated Chrome versions with QUIC bugs, or corrupted local browser cache and DNS data.
Will disabling QUIC in Chrome slow down my browsing?
Disabling QUIC may result in a very slight reduction in connection speed for Google services and other sites that use QUIC, since Chrome will fall back to standard TCP/TLS connections. In practice, the difference is barely noticeable for most users and browsing will still feel fast and secure. It is a safe and widely recommended fix for this error.
Does ERR_QUIC_HANDSHAKE_FAILED only happen on Google sites?
QUIC was originally developed by Google, so the error most commonly appears on Google services like Gmail, YouTube, and Google Search. However, it can also occur on any website that has adopted the QUIC or HTTP/3 protocol, so you may see it on other modern websites as well.
Is ERR_QUIC_HANDSHAKE_FAILED a security threat?
No, this error is not a sign of a security breach or malware. It simply means Chrome could not establish a QUIC connection, which is a performance-oriented transport protocol. The error prevents the page from loading but does not indicate your data has been compromised. However, if you also see certificate warnings alongside this error, you should investigate further.
Can a VPN cause ERR_QUIC_HANDSHAKE_FAILED?
Yes, VPNs are a very common cause of this error. Many VPN services route only TCP traffic and block or drop UDP packets, which QUIC requires. If you experience this error while connected to a VPN, try disconnecting from the VPN first. If the error goes away, either switch to a VPN that supports UDP and QUIC, or disable QUIC in Chrome flags (chrome://flags) so Chrome falls back to TCP, which works normally through most VPNs.

Related Error Codes