ERR_CONNECTION_RESET in Chrome: what it means and how to fix it
ERR_CONNECTION_RESET means the connection to the site was cut off abruptly by a TCP reset, either by the site's server or by something between you and it. First work out whether the problem is on your side (try another network or browser), then check extensions, VPN, proxy settings and security software, and reset the network stack on Windows if needed.
On this page
What it means
ERR_CONNECTION_RESET is a Chromium network error (code -101). In the Chromium source it is described as a connection that was reset, corresponding to a TCP RST. In plain terms, your browser started talking to a site, and the connection was torn down abruptly instead of closing politely.
The catch is that a reset can come from several places: the website's server, or a device along the way such as a firewall, antivirus, proxy, router or your internet provider's equipment. The browser only sees that the reset happened, not who sent it or why. So this is less a single bug than a symptom, and the fix is mostly a matter of narrowing down where it comes from.
Chrome, Edge, Brave, Opera and other Chromium browsers show it. The steps below were written around Chrome, and the network reset steps are for Windows.
Symptoms and causes
You are likely dealing with this problem if:
- The page does not load and Chrome shows "This site can't be reached" with "The connection was reset" and ERR_CONNECTION_RESET.
- It may happen on one site only, or on all HTTPS sites.
- It may or may not happen on other networks or devices, which is the main clue to where the problem is.
The usual causes, most common first:
- Security or network software on your computer
- A firewall, an antivirus that scans HTTPS traffic, a VPN, or an ad-blocking or privacy extension can reset connections it does not like.
- Proxy settings or a proxy server
- A proxy configured in Windows, or one that is misbehaving, can interfere with the connection.
- VPN dropping or reconnecting
- If the VPN connection drops or reconnects, traffic may be blocked or reset in the meantime.
- Damaged TCP/IP or Winsock configuration on Windows
- Corrupted network stack settings can cause connections to fail abruptly.
- Browser problems
- A bad cache, an outdated browser or a faulty extension can trigger the error.
- Your router or internet provider
- A router, carrier-level NAT, or filtering equipment on the path can reset connections.
- The website's server
- The server may be down or overloaded, a server-side firewall may be dropping you, or the application behind it may have crashed. If one site fails for everyone on every network, this is the likely answer.
How to fix it
Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.
1.Find out whether the problem is local
This tells you whether to keep troubleshooting your own setup or give up and wait for the site owner.
- Open a different website. If only one site fails, note that.
- Try the same page in another browser and in an Incognito window (CtrlShiftN).
- Try another network, for example a phone hotspot, or another device on your normal network.
- Read the result: if it fails on every network, the cause is on your computer. If one site fails everywhere, the site's server is at fault and only its owner can fix it.
2.Reload the page and restart your router
A one-off reset from a hiccup in the router or connection often clears with a restart.
- Reload the page once.
- Unplug your router from power, wait about a minute, then plug it back in and let it reconnect.
3.Clear Chrome's cached data
A bad cache is one of the browser-side causes.
- In Chrome open Settings > Privacy and security > Clear browsing data.
- Tick Cached images and files and click Clear data.
4.Test without extensions and the VPN, and update Chrome
Extensions, a VPN, or an old browser version can each cause resets.
- Open the page in an Incognito window, where extensions are normally off unless you allowed them. If it loads there, disable your extensions one at a time to find the culprit.
- If you use a VPN, disconnect it or reconnect it, then reload the page.
- Update Chrome to the latest version and restart it.
5.Check the proxy setting in Windows
A proxy you do not need, or a leftover one, can reset your connections.
Before you start: If your workplace or school requires a proxy, do not change this setting without asking whoever manages your network. Note the original values first.
- Open the Start menu, search for Internet Options and open it.
- Go to the Connections tab and click LAN settings.
- Untick Use a proxy server for your LAN and tick Automatically detect settings.
- Click OK, then reload the page.
6.Test your firewall or antivirus briefly
Security software that inspects HTTPS traffic can reset connections. This is a test to identify the cause, not a fix.
Before you start: Only do this for a moment, and turn protection back on right after the test. Avoid visiting unfamiliar sites while it is off. If it turns out to be the cause, add an exception for the site or app instead of leaving protection off.
- Temporarily turn off the third-party antivirus or firewall, then reload the page.
- Turn it back on straight away.
- If the page loaded while it was off, open the program's settings and add an exception, or disable its HTTPS scanning feature if it has one.
7.Reset the network stack
This repairs a damaged TCP/IP or Winsock configuration on Windows.
Before you start: This resets network settings, so custom static IP settings or some VPN and network software configurations may need to be set up again. Note any manual network settings first. Your internet connection will drop briefly.
- Open Command Prompt as administrator (search for it, right-click, Run as administrator).
- Run these commands one at a time, pressing Enter after each.
netsh winsock reset netsh int ip reset ipconfig /release ipconfig /renew ipconfig /flushdns - Restart the computer and try the page again.
Check that it worked
- The page that failed now loads normally in Chrome.
- The page also loads after restarting the browser, with extensions and VPN back on if you use them.
If it still fails
- If the error appears on every network and device, or on one site only for everyone, the cause is almost certainly the site's server. Contact the site owner or support and give them the time and the exact error.
- If it only happens on one particular network and works on a phone hotspot, ask your internet provider or network administrator, since equipment on that network may be resetting the connection.
- If you run the site yourself, check your web server, reverse proxy, firewall and WAF logs for dropped or reset connections, and read the documentation for your server software.
Questions
What is the difference between ERR_CONNECTION_RESET and ERR_CONNECTION_REFUSED?
In Chromium's error list, a reset (-101) corresponds to a TCP RST that tore the connection down, while refused (-102) means the connection attempt itself was refused. ERR_CONNECTION_CLOSED (-100) is a normal, orderly close.
Sources
- net_error_list.h (Chromium source)Official · Chromium / Google
- RFC 9293: Transmission Control Protocol (TCP)Official · IETF / RFC Editor
- Fix ERR_CONNECTION_RESET · Kinsta