How to Fix ERR_CONNECTION_CLOSED in Chrome

By ErrorFix · Updated October 24, 2026 · 7 min read

What ERR_CONNECTION_CLOSED means

ERR_CONNECTION_CLOSED means Chrome started loading a page, but the connection was shut down before the page finished arriving. Think of it like a phone call that connects and then goes dead halfway through the first sentence: the line was open, something answered, and then the connection ended without delivering the message. That something is usually sitting in the middle of the route between you and the website — your router, your VPN or proxy, your firewall or antivirus, or the website's own server giving up on the request.

The practical difference from its close cousins is small but useful. A timeout means no answer ever came back; a reset means a connection was forcibly cut; a closed connection means the connection ended early, often because the server stopped responding or a middle layer dropped it. Because the causes overlap so much, the diagnostic approach is the same: work out whether the fault is wide (every site fails) or narrow (one site fails), then remove one middle layer at a time — router, cache, extensions, VPN, proxy, DNS, firewall — until pages load normally again.

Common causes

• Unstable internet connection: a weak Wi-Fi signal, a router that needs a restart, or packet loss from your internet provider can shut a connection down mid-load.
• VPN or proxy interference: an overloaded VPN server, a blocked VPN address, or a stale proxy rule can close the connection between you and the site.
• Corrupted browser cache or cookies: a damaged cached copy of the page can break the connection the moment Chrome tries to reuse it.
• Extensions that touch the network: ad blockers, VPN extensions, download managers, and security toolbars can end a connection before the page finishes arriving.
• Firewall, antivirus, or the site's own server: your security software can shut down connections it distrusts, and a crashing or overloaded site server can close connections on its own side.

How to fix ERR_CONNECTION_CLOSED — step by step

Work through these fixes in order. Most cases are fixed by step 1, 2, or 4.

1. Find out whether one site or all sites fail, then restart your router. Start by narrowing down the fault, because the fix depends on how wide it is. Try two or three unrelated websites. If every site fails, the problem is your connection or your computer, not the site you wanted. If only one site fails, that site's server is the likeliest culprit and the browser-side steps below are less likely to help. Either way, restart your network hardware: unplug your router and modem from power, wait a full 30 seconds, plug them back in, and wait until the indicator lights are steady before reloading the page. A router that has been running for weeks can hold stale connections that get closed mid-load, and a power cycle clears them.
2. Clear Chrome's cache and cookies, then test in incognito. A corrupted cached copy of a page can make Chrome's connection fail the moment it tries to reuse it. Press Ctrl + Shift + Delete on Windows (Cmd + Shift + Delete on a Mac), set the time range to All time, check Cached images and files and Cookies and other site data, and click Clear data. Then open an Incognito window with Ctrl + Shift + N and load the site there. Incognito uses no stored cache, no cookies, and no extensions, so if the site loads there, the fault is in your cached data or an extension rather than your network.
3. Disable extensions and reset Chrome's settings. Extensions that touch the network — ad blockers, VPN extensions, download managers, security toolbars, and script blockers — can close a connection before the page finishes arriving. Type chrome://extensions in the address bar and toggle every extension off, then reload the site. If it loads, re-enable the extensions one at a time, reloading after each, until the error returns and you have found the culprit. If disabling extensions does not help, go to Settings, then Reset settings, then Restore settings to their original defaults. This removes extension configurations and custom settings without deleting your bookmarks or saved passwords.
4. Disconnect your VPN and clear any proxy settings. A VPN or proxy sits between Chrome and every website, so it is a prime suspect when connections are shut down early. Disconnect your VPN completely — not just pause it — and reload the page. Then clear any stale proxy: on Windows, open Settings, go to Network and internet, then Proxy, and turn off Use a proxy server under Manual proxy setup. On a Mac, open System Settings, go to Network, select your Wi-Fi, click Details, then Proxies, and uncheck every option. Retest before moving on, because a leftover proxy rule can keep closing connections even after the VPN app itself is closed.
5. Flush DNS and reset the TCP/IP stack. Stale DNS records and a damaged network stack can cause connections to be closed as they are being set up. Open Command Prompt as Administrator and run ipconfig /flushdns, then netsh winsock reset, then netsh int ip reset, and restart your computer. On a Mac, open Terminal and run sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder. If the error continues, try a public DNS: on Windows go to Settings, Network and internet, Wi-Fi or Ethernet, edit the DNS server assignment, and enter 8.8.8.8 and 8.8.4.4. A different DNS provider rules out a bad record from your internet provider's own servers.
6. Check your firewall, antivirus, and whether the site is down. A firewall or antivirus web shield can shut down a connection it considers risky, and it often does so silently. On Windows, open Windows Security, then Firewall and network protection, then Allow an app through firewall, and confirm Google Chrome is checked for both Private and Public networks. Try pausing your antivirus web shield briefly as a test and switch it back on immediately afterward. Finally, check whether the site is down for everyone using a status checker: if it is up for others but closes on you, the site's own firewall or host may be dropping your connection, and waiting a few hours or contacting the site owner is the remaining move.

Did this fix it? Quick checklist

• Pages load without the closed-connection error
• Other websites work, so the connection is fine
• The site loads with the VPN disconnected
• The error is gone in an incognito window

If the error is gone in incognito but still appears in a normal window, an extension or corrupted browsing data is still the cause — keep extensions disabled and clear browsing data one more time with All time selected. If the error happens only on your home Wi-Fi but nowhere else, check your router's admin page for parental controls or attack-protection features that may be ending connections early, or ask your internet provider whether it blocks or throttles the site. And if one specific site keeps closing your connection after every step here while it is up for everyone else, the site's firewall is almost certainly dropping your connection — contact the owner, or try again after a day.