Quick answer for advanced users: flush DNS, reset Winsock, disable proxy, disable your antivirus temporarily, and check for malware.
Now, the longer answer. ERR_CONNECTION_RESET shows up when your browser establishes a TCP connection to a server, then the connection is dropped before the HTTP response completes. That's not the same as a timeout, where the server never answers. A reset means something actively terminated the connection. The culprit is almost always one of three things: a local network filter (antivirus or firewall), a broken proxy configuration, or a corrupted network stack on your machine.
I've seen this error on Windows 10 and 11 more than any other platform. It also appears on macOS, but the fixes are different. Since most of you are on Windows, I'll focus there first.
Fix 1: Clear DNS and reset Winsock
Your system caches DNS lookups. If that cache gets corrupted with a stale or wrong IP, the connection can get killed mid-handshake. Winsock is the API that apps use to talk to the network. Resetting it clears any leftover junk from misbehaving software.
- Open Command Prompt as Administrator. Hit Start, type "cmd", right-click, and select "Run as administrator".
- Run these commands one at a time, hitting Enter after each:
ipconfig /flushdns
netsh winsock reset
netsh int ip reset
Restart your computer. That alone fixes a surprising number of ERR_CONNECTION_RESET cases. The Winsock reset is the heavy hitter here because it rebuilds the network catalog from scratch.
Fix 2: Turn off proxy settings
If you're on a corporate network or use a VPN, a misconfigured proxy can cause this exact error. Chrome and Firefox each have their own proxy settings, but on Windows, they all go through the system proxy configuration.
- Press Win + R, type
inetcpl.cpl, and hit Enter. - Go to the Connections tab and click LAN settings.
- Uncheck "Use a proxy server for your LAN".
- Make sure "Automatically detect settings" is checked.
Click OK, then restart your browser. If you're using a VPN, disconnect it and try the site again. VPNs frequently inject themselves as proxies and can break things when they fail.
Fix 3: Check your antivirus or firewall
This is the sneaky one. Antivirus software like Norton, McAfee, or even Windows Defender itself can block connections it deems suspicious. The error often appears on sites that use HTTPS with certificates the AV doesn't trust.
Temporarily disable your antivirus's real-time protection. Don't uninstall it—just turn it off for a minute and test the site. If the error goes away, you've found the culprit. Add an exception for the site or adjust the SSL scanning settings.
Firewalls can also cause this. On Windows, you can check the Windows Firewall logs, but that's a rabbit hole. Simpler: temporarily disable the firewall (not recommended for long), test, then re-enable.
Fix 4: Clear browser cache and reset flags
Chrome and Edge have experimental flags that can break network behavior. If you've been messing with flags like --enable-quic or --force-effective-connection-type, those can cause resets on certain sites.
- In Chrome, go to
chrome://flags. - Click "Reset all to default" at the top right.
- Also clear your cache:
Ctrl+Shift+Del, select "Cached images and files", and clear.
On Safari for macOS, go to Preferences > Privacy > Manage Website Data and remove everything. That often fixes reset errors on Mac.
Fix 5: Scan for malware
Malware that messes with your network stack can cause ERR_CONNECTION_RESET. Browser hijackers and adware are famous for this. They install their own proxy or modify your hosts file to redirect traffic, and when the proxy fails, you get a reset.
Run a full scan with Malwarebytes (free version works) or your AV's offline scanner. Also check your hosts file at C:\Windows\System32\drivers\etc\hosts. It should only have lines starting with # and the default 127.0.0.1 localhost entry. Anything else is suspect.
I've seen hosts file entries that point facebook.com to a malicious IP, and when the attacker's server dies, you get a reset. Deleting those lines fixes it.
What if nothing works?
Try a different browser or a private/incognito window. If it works there, it's a browser-specific extension. Disable extensions one by one.
If the error happens on all devices on your network, the issue is your router or ISP. Power-cycle the router, and if that fails, call your ISP. Also, try using a different DNS server like Google's (8.8.8.8) or Cloudflare's (1.1.1.1) — sometimes your ISP's DNS is the problem.
One last thing: check your system clock. If your date/time is wrong by more than a few minutes, SSL certificates fail validation and the connection gets reset. I've seen this more than once on machines with dead CMOS batteries.
Prevention tips
- Keep your OS and browser updated. Old versions have bugs that cause resets.
- Don't install random browser extensions. They can conflict with network settings.
- Periodically reset Winsock and flush DNS to keep your network stack clean.
- Use a reputable ad-blocker like uBlock Origin—it also blocks malicious scripts that can trigger resets.
That's the full rundown. Start with the DNS and Winsock reset—it's the quickest and most likely to work. Then move to proxy and antivirus checks. Most people don't need to scan for malware, but if you're here after trying everything else, it's worth the time.