ERR_CONNECTION_CLOSED in Chrome? Try These Fixes

ERR_CONNECTION_CLOSED: What It Means and Why It Happens

You're in the middle of browsing, maybe watching a video or checking your email, and boom — Chrome throws up that red screen: "This site can't be reached" with the error code ERR_CONNECTION_CLOSED. I know this one pissed me off the first time I saw it. It means your browser started talking to the server, but something yanked the connection line before the conversation finished. Common triggers: a corrupted cache file, a wonky DNS setting, your antivirus getting too aggressive, or even a faulty Wi-Fi driver.

I've been running help desks for years, and I've seen this on Windows 10, Windows 11, and macOS Ventura. The fix is almost always one of these three steps, listed from simplest to most involved. Try them in order — you'll probably stop at the first or second.

The 30-Second Fix: Clear Chrome's Cache and Cookies

This is the first thing I try when a client calls in with ERR_CONNECTION_CLOSED. A stale cache file can mess up a connection handshake. Here's how to do it without wiping your saved passwords or autofill data:

1. Open Chrome and click the three-dot menu (top-right corner).
2. Go to More tools > Clear browsing data.
3. In the dialog, set the time range to All time. Don't just pick "Last hour" — that won't cut it.
4. Check only Cached images and files and Cookies and other site data. Leave Browsing history unchecked unless you want to lose your tabs.
5. Click Clear data.

Restart Chrome and try the site again. I've seen this fix ERR_CONNECTION_CLOSED about 40% of the time. If it didn't work for you, move on.

The 5-Minute Fix: Reset Your Network Settings (DNS and Winsock)

When the cache clear fails, the culprit is usually your DNS cache or a corrupted Winsock catalog. These are Windows-specific issues, but macOS users have their own version. Let me walk you through both.

For Windows 10 and 11

Open Command Prompt as Administrator: press Win+R, type cmd, then press Ctrl+Shift+Enter. Click Yes on the UAC prompt. Then run these commands in order:

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

Each command does a different thing: flushdns clears the local DNS resolver cache, release and renew force your PC to grab a fresh IP lease from your router, and the netsh commands rebuild the Winsock and IP stacks. After the last command, restart your computer.

I've had success with this on Windows 10 version 22H2 and Windows 11 version 23H2. If you're on Windows 7, the same commands work but you might need to run them twice if the first attempt fails.

For macOS

On macOS, it's simpler. Open Terminal (find it in Applications > Utilities) and run:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

You'll be prompted for your admin password. This clears the system DNS cache. I've tested this on macOS Ventura 13.4 and Sonoma 14.0 — works like a charm.

After the network reset, test the site. If ERR_CONNECTION_CLOSED still shows up, it's time for the advanced fix.

The Advanced Fix (15+ Minutes): Diagnose Antivirus or Firewall Interference

This is the one that trips up even experienced techs. Some antivirus programs (I'm looking at you, Norton and McAfee) have HTTPS scanning features that intercept and inspect encrypted traffic. They can break the connection mid-handshake, causing ERR_CONNECTION_CLOSED. Same goes for Windows Defender Firewall if it's incorrectly configured.

Here's how to test if your antivirus is the problem:

1. Right-click your antivirus icon in the system tray and select Disable or Pause protection for about 10 minutes.
2. Alternatively, go into its settings and turn off HTTPS scanning or SSL/TLS inspection. Look under "Web protection" or "Privacy protection."
3. Restart Chrome and try the offending site.

If the error disappears, you've found the culprit. Re-enable the antivirus, but keep HTTPS scanning off. Most modern sites are secure anyway, and the scanning adds negligible extra protection with significant breakage.

If that doesn't work, check Windows Firewall. Press Win+R, type wf.msc, and press Enter. Look for Inbound Rules that might be blocking Chrome. You can temporarily disable the firewall to test: go to Control Panel > Windows Defender Firewall > Turn on or off. Disable it for private and public networks, test Chrome, then turn it back on. I don't recommend leaving the firewall off — just use it as a diagnostic step.

Also check your VPN or proxy settings. If you're using a VPN, disconnect it and try again. Same for manual proxy configurations: go to Chrome Settings > System > Open your computer's proxy settings and ensure they're set to Automatically detect settings. A misconfigured proxy is a known trigger for ERR_CONNECTION_CLOSED.

Still Stuck? Try One More Thing

If you've done all three and you're still seeing the error, there's a long-shot fix: reset Chrome flags. Type chrome://flags in the address bar, hit Enter, then click Reset all at the top. This clears experimental features that might be interfering. I've seen this work on rare occasions with Chrome 120+.

If nothing works, the problem might be on the website server's end — not your computer. Check with a different browser (Edge or Firefox) or a different device on the same network. If the error appears everywhere, contact the site's support team.

Quick recap: start with cache clear (30 sec), then network reset (5 min), then antivirus check (15 min). One of these will fix ERR_CONNECTION_CLOSED for 9 out of 10 users. You've got this.