Quick Answer: ERR_CONNECTION_CLOSED means the connection to the server closed unexpectedly before Chrome could load the page, similar to ERR_CONNECTION_RESET but typically triggered by the server or an intermediate network device deliberately ending the connection rather than an abrupt drop. Reloading, testing in an incognito window, and checking for interfering extensions resolve most cases.
What Causes This Error
- The destination server closing the connection due to load or a configuration issue
- A firewall or security extension terminating the connection mid-request
- An outdated or corrupted SSL/TLS handshake with the specific site
- A proxy or VPN extension interfering with the connection lifecycle
- Server-side rate limiting after too many rapid requests
How to Fix It
Step 1: Hard reload the page
Press Shift + Ctrl + R to reload while bypassing the cache. A one-off closed connection often loads normally on the next attempt.
Step 2: Test in an incognito window
Open an incognito window (Ctrl + Shift + N) and load the same site. Extensions are disabled there by default, so if the page loads fine, an extension is the cause.
Step 3: Disable extensions one at a time
Go to chrome://extensions and turn off ad blockers, privacy tools, and VPN extensions individually, reloading after each to isolate the culprit.
Step 4: Clear cache and cookies for the site
A stale SSL session or corrupted cookie for that specific site can trigger this error. See how to clear cache and cookies on a Chromebook, or clear data for just that one site from the padlock icon in the address bar.
Step 5: Check the site on a different network
Try a phone hotspot briefly. If it loads fine there, a firewall or security appliance on your usual network is closing the connection, not the site itself.
Step 6: Wait and retry
If you’ve made several rapid requests to the same site, a temporary rate limit may be closing new connections deliberately. Waiting a few minutes often clears this.
Still Not Fixed?
If the error only happens on one specific site while everything else loads fine, the fault is very likely on that site’s server, an overloaded backend, an expired certificate, or active rate limiting. If it happens across many different sites, focus on your router, security software, or ISP instead, similar to troubleshooting ERR_CONNECTION_RESET.
FAQ
Is ERR_CONNECTION_CLOSED the same as ERR_CONNECTION_RESET?
They’re closely related and share most causes and fixes. A reset typically means the connection was abruptly cut, while a closed connection is more often the server or a proxy ending it in a controlled way.
Can antivirus or security extensions cause this?
Yes. Security software that inspects HTTPS traffic can close connections it flags as suspicious, even when the site is legitimate.
Will this fix itself over time?
Sometimes, especially if the cause is server-side rate limiting or a temporary backend issue. If it persists for more than a day on a site that normally works fine, look locally at your network or browser extensions instead.
