You start loading a page, it hangs for a second, then Safari or Chrome throws it back at you: "The connection was reset" — or in Chrome, ERR_CONNECTION_RESET. Unlike "server cannot be found," this one means the connection started and then something cut it off mid-load. The good news: on a Mac, the cause is almost always local and fixable in a few minutes.
First: is it one site, or every site?
Open a second, unrelated site (try apple.com and your bank). If only one site resets, the problem is that site, a security tool blocking it, or its data cached on your Mac. If every site resets, the problem is your network path — router, VPN, DNS, or firewall. That single test tells you which half of this list to work through.
The fixes, fastest first
1. Reload, then try a Private window
Press Command-R to reload. Still reset? Open a Private window (Safari: File › New Private Window; Chrome: Command-Shift-N) and load the same page. A Private window ignores extensions and most cached data — if the page loads there, the culprit is an extension or this site’s stored data, handled in the next two steps.
2. Turn off your VPN, proxy, and content blockers
A VPN or proxy is the number-one cause of a connection that resets mid-load — the tunnel drops and the browser sees a severed connection. Fully quit any VPN app (don’t just toggle it) and reload. Then check System Settings › Network › (your connection) › Details › Proxies and make sure nothing is enabled that you didn’t set. Disable content blockers and privacy extensions too — an over-aggressive blocker can kill a connection it doesn’t like.
3. Clear this site’s data
Corrupt cached data for one site produces resets on that site only. In Safari: Settings › Privacy › Manage Website Data, search the site, Remove. In Chrome: click the icon left of the address bar › Cookies and site data › Manage › delete that site’s data. Reload.
4. Flush the DNS cache and try a public DNS server
Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Then set a clean public DNS: System Settings › Network › Details › DNS, add 1.1.1.1 and 8.8.8.8, remove the others, and reload. A stale or poisoned DNS entry can route you to a dead endpoint that resets every attempt.
5. Check date, time, and any firewall
A wrong clock breaks the security handshake and can surface as a reset. Set System Settings › General › Date & Time to update automatically. If you run a third-party firewall or antivirus (Little Snitch, LuLu, Norton), pause it and reload — these tools sometimes cut connections silently.
6. Restart the Mac and the router
If every site resets, power-cycle the router: unplug it for 30 seconds, plug it back in, wait for it to fully come up. Restart the Mac too. This clears a huge share of "every site resets" cases where the router’s NAT table or the Mac’s network stack got wedged.
7. Try another browser and another network
Load the page in a different browser, then on a different network (a phone hotspot). If the hotspot works, your home network or ISP is dropping the connection. If every browser on every network resets on the same site, that site is genuinely down or blocking you — not your Mac.
The honest part: when it is not the browser
If resets follow you across browsers and networks and a clean reinstall, and especially if they come with random Wi-Fi drops, kernel panics, or a Mac that runs hot doing nothing, you may be looking at a failing Wi-Fi card or a Mac that can’t hold macOS updates anymore. On very old Intel Macs stuck on an unsupported macOS, modern sites will increasingly fail the security handshake outright.
At that point a newer Mac is the fix, not another Terminal command. A refurbished M1 MacBook Air starts at $569.99 at LuxuriousComputers, and our Apple clearance section is where the best-priced current models land. Every machine is tested, cleaned, and covered by our own one-year warranty — so the connection resets stop being your problem.
Frequently Asked Questions
What does "the connection was reset" mean?
The connection to the server was established and then abruptly closed mid-transfer — by a VPN dropping, a firewall or extension cutting it, a flaky router, or the server itself. It is different from "server cannot be found" (a DNS failure, where no connection ever started).
Why does it happen on only one website?
Almost always cached site data on your Mac, a content blocker or extension objecting to that site, or the site actively resetting connections from your IP. Clear that site’s data (step 3) and test in a Private window first.
Does ERR_CONNECTION_RESET mean I have a virus?
Rarely on a Mac. It is far more often a VPN, proxy, extension, or router issue. If you never installed a VPN or proxy and one is enabled in Network settings, remove it — that is worth checking, but it is a misconfiguration, not typically malware.
Why does Chrome show ERR_CONNECTION_RESET but Safari loads the site?
Usually a Chrome extension or a Chrome-specific proxy/VPN setting. Try the site in a Chrome Incognito window; if it loads, disable extensions one at a time to find the one resetting the connection.
The page loads but keeps resetting halfway — is that the same thing?
Yes, that is the classic reset signature: enough connection to start, not enough to finish. Work the VPN, DNS, and router steps (2, 4, 6) — those cover the great majority of mid-load drops.