How to Fix ERR_CONNECTION_REFUSED in Chrome
What ERR_CONNECTION_REFUSED means
ERR_CONNECTION_REFUSED means your request reached the server but the server refused to talk — the connection was actively rejected rather than lost in transit. This is different from a timeout: nothing waited around. Something answered "no," and that something is usually a firewall, a misbehaving proxy or VPN, or a server that simply is not running.
Most often the refusal comes from one of four places: your VPN or proxy routing traffic into a dead end, your firewall or antivirus silently blocking Chrome, a DNS record pointing you at a server that is not listening, or the website's own firewall blocking your IP address. Because the error appears instantly, the troubleshooting is a fast process of elimination: strip away each layer — VPN, proxy, cache, extensions, firewall, DNS — until the page loads, and the last layer you removed was the problem.
Common causes
- VPN or proxy rerouting your traffic: a disconnected VPN with a stale proxy setting is the single most common cause — traffic goes nowhere and the connection is refused instantly.
- Firewall or antivirus blocking Chrome: Windows Firewall rules or a third-party web shield can silently reject Chrome's outbound connections to specific sites or ports.
- The website's server is down or not listening: the server may be offline, restarting, or running on a port your address does not have access to.
- Stale DNS or a bad hosts-file entry: your computer may be sending the request to the wrong server address entirely.
- The site's firewall blocking your IP: rate limits, country blocks, or security rules on the site's side can refuse your connection on purpose.
How to fix ERR_CONNECTION_REFUSED — step by step
Work through these fixes in order. Most cases are fixed by step 1, 2, or 4.
- Confirm the site is online and your connection works. Before changing anything, rule out the obvious: open two or three other major websites. If everything fails, the problem is your connection — unplug your router and modem for 30 seconds, plug them back in, and wait for the lights to stabilize. If only the one site fails, check DownDetector or isitdownrightnow.com to see whether it is down for everyone. Also try loading the site on your phone with Wi-Fi off; if it works on mobile data, your home network or ISP is the problem.
- Disconnect your VPN and clear your proxy settings. A VPN or proxy is the most common cause of refused connections. Disconnect your VPN completely and reload the page. Then check for a stale proxy: on Windows, open Settings, go to Network & internet, then Proxy, and make sure Use a proxy server is turned off under Manual proxy setup. On a Mac, open System Settings, go to Network, click your Wi-Fi, then Details, then Proxies, and uncheck everything. If you use a corporate or school proxy, leave its settings alone and contact IT — the block may be deliberate.
- Clear Chrome's cache and test in incognito. Corrupted cached data or a bad stored redirect can produce a refusal that no longer exists. Press Ctrl + Shift + Delete (Cmd + Shift + Delete on a Mac), set the time range to All time, check Cached images and files and Cookies and other site data, and click Clear data. Then open an Incognito window (Ctrl + Shift + N) and try the site there — incognito disables extensions and uses no cache, so if it works, an extension or cached entry was the culprit.
- Disable extensions and check your firewall. Type chrome://extensions in the address bar and toggle off every extension, then reload the site. If it loads, re-enable extensions one by one until the error returns — the last one enabled is interfering. Next, check your firewall: on Windows, open Windows Security, then Firewall & network protection, then Allow an app through firewall, and confirm Google Chrome is checked for both Private and Public networks. A third-party antivirus web shield can also refuse connections, so try pausing it briefly as a test and re-enable it immediately after.
- Flush DNS and reset the network stack. A stale or poisoned DNS record can point Chrome at a server that refuses connections. Open Command Prompt as Administrator and run ipconfig /flushdns, then netsh winsock reset, then netsh int ip reset, and restart your computer. If the error persists, change your DNS servers: on Windows, open Settings, go to Network & internet, then Wi-Fi or Ethernet, click your connection, edit the DNS server assignment, and enter 8.8.8.8 and 8.8.4.4 (Google Public DNS). Restart Chrome and try the site again.
- If it is only one site: check the URL, hosts file, and the site owner. When every other site works, double-check the address for typos — a wrong port or subdomain can be refused outright. Then inspect your hosts file at C:\Windows\System32\drivers\etc\hosts (open Notepad as Administrator); entries here can redirect or block a domain, and entries you did not add suggest malware — scan with Windows Security. Finally, the site's own firewall may be blocking your IP (rate limiting or country blocks do exactly this). Contact the site owner with your IP address and the exact error, or wait and retry later.
Did this fix it? Quick checklist
- The site loads within a few seconds
- No VPN or manual proxy is enabled
- The error is gone in an incognito window
- It works on a second network (mobile hotspot)
If the site loads in incognito but not in a normal window, an extension or a piece of cached data is still the problem — leave extensions off and clear browsing data once more with All time selected. If the refusal happens only on your home Wi-Fi and everywhere else works, log into your router and check whether it has parental controls or an "attack protection" mode blocking the site, or ask your ISP whether they block that domain. And if the site is up for everyone else but still refuses you after all six steps, it is almost certainly your IP being blocked on the site's end — reaching the owner through their social media is usually faster than their contact form.
Frequently asked questions
What does ERR_CONNECTION_REFUSED mean?
It means your request reached the server but the server actively refused the connection — no connection was ever established. This is different from a timeout: a refusal happens immediately and usually means nothing is listening on the server's end, or a firewall (yours, your ISP's, or the site's) blocked it.
What is the difference between ERR_CONNECTION_REFUSED and ERR_CONNECTION_TIMED_OUT?
A refused connection is rejected immediately by the server or a firewall, while a timed-out connection waits about 30 seconds for an answer that never comes. Refused means "no, go away now"; timed out means "no answer at all." The refusal is more likely to be caused by a firewall, proxy, or server that is simply not running.
Can a VPN cause ERR_CONNECTION_REFUSED?
Yes — this is one of the most common causes. The VPN's exit server may be blocked by the site's firewall, or a stuck VPN proxy setting can route traffic nowhere. Disconnect the VPN entirely as a test, and also check that no manual proxy is set in your operating system's network settings.
Why does only one website refuse my connection?
That points at something specific to that site: its server may be down or not listening, its firewall may have blocked your IP, or a wrong URL is sending you to a port that is not open. If other sites work fine and down-checkers say the site is up for everyone else, contact the site owner — you are likely blocked on their end.
Is ERR_CONNECTION_REFUSED caused by a virus?
Rarely, but malware is worth ruling out. Some malware edits your hosts file or installs a rogue proxy that redirects traffic and then refuses it. Check the hosts file for entries you did not add, confirm no unknown proxy is set, and run a full scan with Windows Security or your antivirus if anything looks suspicious.