ERR_CONNECTION_CLOSED
Chrome connected, but the other side hung up before sending anything back. Something in the path, or the server, ended the connection.
Quick checks
- Try another network (mobile data).
- Turn off VPNs and proxies.
- Check whether the site is blocked on your network (school, office, country).
Fixes on Mac
Disable proxies and VPNs
- System Settings › Network › Wi-Fi › Details › Proxies: turn off unused proxies.
- Disconnect VPNs and quit filtering apps.
Reset Chrome's connections
- Flush
chrome://net-internals/#socketsand clear#dns. - Run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
- Flush
Try a different DNS
- Some networks block sites by returning a wrong address. Set
1.1.1.1in System Settings › Network › Details › DNS.
- Some networks block sites by returning a wrong address. Set
Fixes on Windows
Reset the network
netsh winsock reset,netsh int ip reset,ipconfig /flushdns, then restart.
Other devices
Router
- Restart the router; check its parental controls or blocklists.
Still not working?
If one site closes connections on several networks, the server or its firewall rejects you, or the site is down. If many sites do it on one network, that network filters traffic.
See what’s happening
LightAtom's connections view shows short-lived connections and which app or proxy made them (turn off Active only to keep closed ones visible).
Frequently asked questions
What is the difference between ERR_CONNECTION_CLOSED and ERR_CONNECTION_RESET?
Both mean the connection ended unexpectedly. CLOSED: it closed cleanly before data arrived. RESET: an abrupt reset packet ended it. The fixes overlap.
Can my ISP cause ERR_CONNECTION_CLOSED?
Yes. Network-level blocking often closes connections to blocked sites. Encrypted DNS or a VPN can confirm it.
Why does the site work on my phone but not my Mac?
Something on the Mac interferes: a proxy setting, a VPN profile, security software or a content filter extension.