ERR_CONNECTION_REFUSED means your browser reached the server and the server actively said no. That’s different from a timeout, where nothing answers at all — and the distinction tells you a lot before you try a single fix.
Technically, your computer opened a TCP connection and got back a reset: “nothing is listening here.” The machine is online and reachable. Something on it — or between you and it — deliberately rejected the connection rather than ignoring it.
Key Takeaway:
Refused means someone answered and declined. That rules out most network problems immediately: DNS worked, routing worked, the host is up. The fault is a service, a port, or a filter — not your connection.
Which Error Are You Actually Getting?
Chrome’s three connection errors mean genuinely different things, and mixing them up sends you down the wrong path:
| Error | What Happened | Points To |
|---|---|---|
| CONNECTION_REFUSED | Server answered and rejected you | Service down, wrong port, firewall rejecting |
| CONNECTION_TIMED_OUT | Nothing answered at all | Network path, firewall dropping silently |
| NAME_NOT_RESOLVED | Couldn’t find the address at all | DNS — never got as far as connecting |
A useful detail: firewalls can either reject a connection (you get refused) or drop it silently (you get a timeout). Seeing “refused” usually means the rejection was deliberate and immediate.
First: Is It You or Them?
Two minutes here saves twenty minutes of pointless fixes.
- Try the site on mobile data with Wi-Fi off. Loads fine? The problem is your network, not the site.
- Try a different browser. Works there? It’s a browser setting or extension.
- Try another device on the same network. Also broken? Your router, firewall or ISP.
- Check whether the site is down globally using any “is it down” service.
If it’s down for everyone, stop — no amount of local troubleshooting will help.
If It’s Your Side: Fixes in Order
1. Check your proxy settings
The most common cause on Windows. A proxy that’s configured but not running refuses every connection instantly.
Settings → Network & Internet → Proxy → turn off “Use a proxy server”. On Mac: System Settings → Network → Details → Proxies, and untick everything.
2. Check your hosts file
Frequently missed, and a very common cause. Ad blockers, parental filters and some malware add entries mapping domains to 127.0.0.1 — your own machine. Your browser dutifully connects to itself, finds nothing listening, and reports connection refused.
- Windows:
C:\Windows\System32\drivers\etc\hosts - Mac / Linux:
/etc/hosts
Open it as administrator and remove any line pointing the affected domain at 127.0.0.1 or 0.0.0.0.
3. Disable browser extensions
Test in an incognito window with extensions disabled. Ad blockers and privacy extensions block connections by design and are a routine cause of this error on specific domains.
4. Temporarily disable firewall and antivirus
Security suites that inspect HTTPS traffic can refuse connections when their certificate handling breaks. Disable briefly to test — and if that’s the cause, add an exception rather than leaving protection off. See what a firewall does.
5. Clear browser cache and cookies
Chrome: Settings → Privacy and Security → Clear browsing data → cached images and cookies.
6. Reset the network stack
Command Prompt as administrator, then reboot:
ipconfig /flushdnsnetsh int ip resetnetsh winsock reset
More on the first one: flushing your DNS cache.
7. Check the URL and port
If the address includes a port — example.com:8080 — confirm it’s correct. Connecting to a port with no service behind it produces exactly this error. Also try https:// instead of http://, since many servers no longer accept plain HTTP at all.
If You’re a Developer: localhost
Getting this on localhost or 127.0.0.1 is almost always one of three things, and it’s rarely a browser problem:
- The service isn’t running. Check the terminal where you started it — it may have crashed on launch.
- Wrong port. The app is on 3000, you’re asking for 8080.
- Bound to the wrong interface. A service listening on
127.0.0.1won’t accept connections from other machines; one that should be reachable externally needs to bind0.0.0.0.
Confirm what’s actually listening with a port check — if nothing holds the port, the browser is telling you the truth.
If Your IP Has Been Blocked
Some sites reject connections from specific addresses or whole ranges — after too many requests, because of a shared address with a bad history, or because of your region. The tell is that the site loads fine on mobile data but refuses on your home connection.
Check whether your address has been flagged: IP address blacklists. Restarting your router may get you a new dynamic IP and clear it instantly.
A VPN also sidesteps an address-level block by giving you a different one:
Worth noting the reverse case too: if the error started after you connected a VPN, that server’s addresses may themselves be blocked. Switch servers or disconnect and retest.
Frequently Asked Questions
What does connection refused actually mean?
Your computer reached the server and the server sent back a refusal rather than accepting the connection. Nothing was listening on that port, or a filter rejected it outright.
Is it my fault or the website’s?
Test on mobile data. If it loads there, the problem is on your side. If it fails everywhere, the site’s service is down.
Why does it happen on only one website?
That points at something domain-specific — a hosts file entry, a blocking extension, or your address being blocked by that site. General network problems affect everything.
Will a VPN fix it?
Only if the cause is your IP being blocked or the content being geo-restricted. If the server’s service is down, a VPN changes nothing.
Why do I get this on localhost?
Your local service isn’t running, or isn’t on the port you’re requesting. The browser is accurately reporting that nothing answered.
Refused or timed out — what’s the difference?
Refused means you got an answer that said no. Timed out means you got no answer at all. Refused actually gives you more information, because it confirms the host is reachable.
Could my antivirus cause this?
Yes. Security software that inspects encrypted traffic sits between your browser and the site, and can refuse connections when something goes wrong on its end. Disable briefly to test.
Does clearing cookies help?
Occasionally, if a stale session or redirect is involved — but it’s a low-probability fix. Check proxy settings and your hosts file first.