With ERR_CONNECTION_REFUSED, your browser reached the server's address, but nothing was accepting connections there, so the server (or something in front of it) refused straight away. Unlike a timeout, the answer comes back quickly.
If the site is down for everyone, its web server has probably stopped. If it's only you, look at your proxy, VPN, firewall or a stale DNS entry.
Is it down for everyone?
Test the address in our website checker. A failed check from our servers means the website is down; a successful one means the problem is local to you.
Fixes to try
- Check the address, including
http://versushttps://and any port number such as:8080. - Disable any proxy. In Windows go to Settings, Network & internet, Proxy. On a Mac, System Settings, Network, your connection, Details, Proxies.
- Turn off your VPN and security extensions, then reload.
- Clear DNS caches with
ipconfig /flushdnsandchrome://net-internals/#dns. If the site moved to a new server, you may still be going to the old one. - Check your firewall or antivirus isn't blocking the browser or the site.
- Restart your router and try on mobile data to rule out your network.
If it's your own site or local server
Make sure the web server is running and listening on the right port, and on the right interface: 127.0.0.1 only accepts local connections, while 0.0.0.0 accepts connections from other machines. Check that the server's firewall allows the port.
Questions
What's the difference between connection refused and timed out?
Refused means something at the address quickly said no, usually because no service is listening on that port. Timed out means nothing answered at all before the browser gave up.
Why do I get ERR_CONNECTION_REFUSED on localhost?
Your local development server isn't running, crashed, or is listening on a different port from the one in the address bar.