Quick Answer: ERR_CONNECTION_RESET means Chrome connected to the site but the connection was abruptly cut before the page finished loading. The most common causes are security software or a router firewall interrupting the connection, a bad extension, corrupted site data, or a weak Wi-Fi signal dropping the link mid-request. Clearing the site’s cache and testing in an incognito window resolve most cases.
What Causes This Error
- Antivirus or firewall software (including router-level firewalls) interrupting the connection
- An ad blocker or privacy extension interfering with scripts the page needs to finish loading
- Corrupted cache or cookies stored for that specific site
- A weak or dropping Wi-Fi signal breaking the connection partway through
- The server itself resetting connections, often due to rate limiting or a misconfiguration on its end
How to Fix It
Step 1: Hard reload the page
Press Shift + Ctrl + R to reload while bypassing the cache. A one-off reset often clears 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 by default there, 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 the site after each one, to isolate the culprit.
Step 4: Clear cache and cookies for the site
Corrupted site data is a frequent trigger. See how to clear cache and cookies on a Chromebook for the full steps, or clear data for just that one site from the padlock icon in the address bar.
Step 5: Check your Wi-Fi signal
Move closer to the router or check the signal strength icon in the status area. A weak signal can drop the connection mid-load, which Chrome reports as a reset rather than a timeout.
Step 6: Restart your router and Chromebook
Restarting the router clears stuck firewall states; restarting the Chromebook clears any stuck network sockets on your end.
Still Not Fixed?
If the reset only happens on one specific site while everything else loads fine, the issue is very likely on that site’s server — rate limiting, a misconfigured server, or active blocking of certain regions or IP ranges. If it happens across many different sites, focus on your router, antivirus software, or ISP instead.
FAQ
Is ERR_CONNECTION_RESET the same as ERR_CONNECTION_REFUSED?
No. A refused connection never gets established at all. A reset means the connection was made and then cut off partway through, which points to different causes.
Can antivirus software really cause this?
Yes. Security software that inspects HTTPS traffic can interrupt connections it flags as suspicious, even when the site is legitimate.
Will this fix itself over time?
Sometimes, if the cause is server-side rate limiting or a temporary server issue. If it persists for more than a day on a site that normally works fine, the cause is more likely local to your network or device.
