ERR_CONNECTION_RESET fix: Stop Chrome from killing your session

You're halfway through loading a page — a bank login, a Slack workspace, a critical Google Doc — and Chrome drops it with ERR_CONNECTION_RESET. The refresh does nothing. Sometimes it's one site, sometimes it's every site. You try rebooting your router (again), and nothing changes. I know this error is infuriating because it looks like your internet is dead, but your other apps are totally fine.

What's actually happening

This error means the TCP handshake started but never finished. The server sent a RST (reset) packet to Chrome, or Chrome sent one to the server. On Windows, you'll often see this with HTTPS sites because SSL/TLS negotiation fails. The root cause is almost never your ISP's fault — it's something on your machine that's corrupting the connection.

The real fix

Skip the usual “clear your cache” advice — that won't help here. The fix is almost always one of these three things, in this order:

1. Turn off Chrome's experimental QUIC protocol

Chrome has a hidden flag for QUIC (a Google-built protocol that bypasses TCP). It's buggy on Windows 11 and macOS Ventura+. Disabling it fixes the reset error for about 70% of people.

1. Type chrome://flags in the address bar and press Enter.
2. Search for experimental QUIC or scroll to #enable-quic.
3. Set the flag to Disabled.
4. Click Relaunch at the bottom.

Test the site that was failing. If it loads, you're done. If not, move on.

2. Reset your network stack (Windows)

Windows caches DNS and TCP settings aggressively. A single corrupt entry can kill connections to entire domains. This command flushes everything.

netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew

Run these in an admin Command Prompt, then restart your PC. On Windows 11 23H2, I've seen this fix the reset error instantly after a reboot.

3. Kill any VPN or proxy override

Even if your VPN is off, leftover proxy settings from a corporate VPN or a privacy add-on can trigger ERR_CONNECTION_RESET. Go to Windows Settings > Network & Internet > Proxy, and make sure Use a proxy server is off. On Mac, check System Settings > Network > Proxies — everything should be unchecked unless you know you need it. On Linux, look at /etc/environment or your desktop environment's proxy settings.

What to check if it still fails

If none of the above worked, you've got a more specific issue. Here's what to try next:

• Disable every extension in Chrome. Go to chrome://extensions and toggle them all off. Then turn them on one by one until the error comes back. I've seen ad blockers and privacy extensions cause this on sites with aggressive SSL certificate checks.
• Test in Incognito mode — if it works there, an extension or cookie corruption is the culprit.
• Switch to a different DNS server. Your ISP's DNS might be dropping connections under load. Set your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8) temporarily. On Windows, go to Network Settings > DNS server assignment and set it manually.
• Update or roll back your network driver. I once spent two hours on a Dell XPS 15 where the Killer Wi-Fi driver was killing connections every 30 seconds. Rolling back to the previous version fixed it.

If you're still getting the error on a specific site that works on your phone or another computer, the problem is that site's server. They might have a misconfigured SSL certificate or a firewall that's blocking your IP temporarily. Try using a web proxy like hide.me to check — if it loads through that, you know it's not your machine.

That's the whole process. Start with the QUIC flag, then the network reset, then check your proxy. I'd bet money one of those three gets you back online.