You click a link in Google Chrome and instead of loading the page, you see a white screen with ERR_CONNECTION_REFUSED. This is one of the most common Chrome errors worldwide — and unlike some browser errors, it has a precise technical meaning that points directly to where the problem is. This guide explains exactly what it means and walks you through 8 proven fixes, ordered by effectiveness and how often each cause appears in real support cases.
ERR_CONNECTION_REFUSED means Chrome cannot connect to the website's server. It is usually caused by: the website being down, your firewall blocking the connection, incorrect proxy settings, or a misconfigured hosts file.
Try these fixes in order:
- Check if the site is down (downdetector.com, isitdownrightnow.com)
- Disable VPN or proxy
- Flush DNS — Windows: ipconfig /flushdns | Mac: sudo dscacheutil -flushcache
- Reset Chrome flags (chrome://flags)
- Temporarily disable firewall or antivirus
What Does ERR_CONNECTION_REFUSED Mean?
To understand this error, it helps to know what happens when Chrome loads a website. First, Chrome resolves the domain name to an IP address via DNS. Then it attempts to open a TCP connection to that IP address on a specific port (usually port 80 for HTTP or port 443 for HTTPS). If the server receives the connection attempt but actively rejects it — either because the port is closed, the server is offline, or a firewall sent a "refused" signal — Chrome displays ERR_CONNECTION_REFUSED.
This is distinct from ERR_CONNECTION_TIMED_OUT (where the request is ignored and Chrome times out waiting) or ERR_NAME_NOT_RESOLVED (where DNS fails entirely). A "refused" error means something at the network level is actively blocking the connection.
8 Methods to Fix ERR_CONNECTION_REFUSED
Before changing anything on your computer, confirm whether the site itself is down. If the server is offline, no fix on your end will help — you simply need to wait.
How to check: Visit downdetector.com or isitdownrightnow.com and enter the site URL. These services check from multiple global locations and report real-time server status.
Also try: Open your phone on mobile data (not Wi-Fi) and visit the same URL. If it loads on mobile data but fails on your Wi-Fi computer, the problem is your local network, not the server.
If the site is confirmed down: wait 10–30 minutes and try again. If it is up everywhere except your computer, proceed to Method 2.
VPNs and proxy servers route your traffic through an intermediate server before reaching the destination. If that intermediate server is down, misconfigured, or blocking certain sites, you will see ERR_CONNECTION_REFUSED even when the destination site is fully operational.
Disable VPN: If you are running a VPN app (NordVPN, ExpressVPN, Surfshark, etc.), disconnect from it and test the site directly. If the error disappears, reconnect to a different VPN server or contact your VPN provider.
Disable Proxy on Windows:
Go to Settings > Network & Internet > Proxy. Under "Manual proxy setup," toggle off Use a proxy server. Under "Automatic proxy setup," toggle off Automatically detect settings if no proxy is required on your network.
Disable Proxy on Mac:
Go to System Settings > Network > select your active connection > click Details > click the Proxies tab. Uncheck all proxy protocols listed. Click OK and Apply.
Disable Proxy on Android:
Go to Settings > Wi-Fi > long-press your network > Modify Network > Advanced > Proxy > set to None.
Your operating system caches DNS lookups to speed up browsing. If a site changes its IP address (common after migrations or server moves) but your DNS cache still holds the old IP, Chrome will attempt to connect to a server that no longer exists at that address — resulting in ERR_CONNECTION_REFUSED.
Windows — Flush DNS:
After running these commands, restart your computer and test the site in Chrome.
Mac — Flush DNS Cache
Open Terminal (Cmd + Space, type "Terminal"). Run the following command and enter your admin password when prompted:
Flush Chrome's Internal DNS Cache
Chrome maintains its own separate DNS cache independent of the OS. Clear it by navigating to chrome://net-internals/#dns in the address bar, then clicking Clear host cache. Also go to chrome://net-internals/#sockets and click Flush socket pools.
Experimental Chrome flags — accessible at chrome://flags — can alter how Chrome handles connections, security protocols, and network behaviour. An enabled flag that conflicts with a site's server configuration can produce ERR_CONNECTION_REFUSED on specific URLs.
Reset all Chrome flags to default: Type chrome://flags in the address bar, press Enter, then click the Reset all button at the top of the page. Click Relaunch when prompted.
Full Chrome settings reset: Go to chrome://settings/reset and click Restore settings to their original defaults. This clears startup overrides, search engine changes, cookie permissions, and disabled extensions — without deleting your bookmarks or synced Google account data.
After relaunching Chrome, test whether the error is resolved.
Firewalls and antivirus programs can intercept and block Chrome's outbound connections — especially when they include web filtering or "safe browsing" features that flag certain sites or ports. This is a common cause of ERR_CONNECTION_REFUSED when the site is confirmed up and working on other devices.
Disable Windows Defender Firewall temporarily:
Go to Control Panel > System and Security > Windows Defender Firewall > Turn Windows Defender Firewall on or off. Select Turn off Windows Defender Firewall for both private and public networks. Test the site. If it loads, your firewall was blocking it — re-enable the firewall and add a specific exception for Chrome or the site in question.
Third-party antivirus (Norton, McAfee, Bitdefender, Kaspersky):
Look for a "Disable web protection" or "Pause protection" option in the antivirus tray icon. Disable it for 5–10 minutes and test. If that resolves the error, add the site to your antivirus whitelist instead of leaving protection disabled permanently.
On Mac: Go to System Settings > Network > Firewall. Toggle off the firewall temporarily. Also check any third-party security app such as Little Snitch or LuLu — these can silently block specific outbound connections.
The hosts file is a local text file that overrides DNS. If a domain is listed in the hosts file pointing to an incorrect IP address (such as 0.0.0.0 or 127.0.0.1), Chrome will attempt to connect to that wrong address and receive a refused connection — even though the site is perfectly operational.
Hosts file entries are commonly added by: ad blockers, parental control software, malware that redirects sites, and some VPN or network management tools.
Check hosts file on Windows:
Check Hosts File on Mac
Open Terminal and run: sudo nano /etc/hosts. Enter your admin password. Scroll through the file and look for any entries referencing the problematic domain. To delete a line, position your cursor on it and press Ctrl + K. Press Ctrl + X then Y to save. Then flush DNS with sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
Some routers have built-in content filtering, parental controls, or DNS-based blocking that can refuse connections to specific sites. Router firmware bugs can also cause connection issues that affect only certain destinations. A full power cycle clears the router's internal state and renews your external IP address, which can resolve blocks applied at the ISP or router level.
How to restart properly: Power off your modem and router (unplug from the wall). Wait a full 60 seconds. Power on the modem first, wait for it to fully connect (all lights stable). Then power on the router. Wait another 60 seconds before testing Chrome.
Check router settings: Access your router admin panel (usually 192.168.1.1 or 192.168.0.1 in a browser). Look for Parental Controls, Content Filtering, or Firewall sections. If the blocked site appears in any list, remove it.
If the error appears on multiple sites and none of the above fixes resolved it, a corrupt Chrome installation may be interfering with how Chrome handles network connections. A clean reinstall replaces all Chrome binaries and resets its internal networking stack.
Windows — Clean reinstall: Go to Settings > Apps > Installed apps, find Google Chrome, and uninstall it. Then open Run (Win + R), type %LOCALAPPDATA%\Google\Chrome and delete the Chrome folder manually. Download a fresh installer from google.com/chrome and install.
Mac — Clean reinstall: Drag Chrome from Applications to Trash. Open Finder, press Cmd + Shift + G, navigate to ~/Library/Application Support/Google/Chrome and delete the Chrome folder. Empty Trash. Download fresh from google.com/chrome.
After reinstalling, sign into Chrome with your Google account to restore synced bookmarks, passwords, and settings.
Quick Reference: ERR_CONNECTION_REFUSED Fixes by Platform
| Fix | Windows | Mac | Android | Priority |
|---|---|---|---|---|
| 1. Check if site is down | Yes | Yes | Yes | High |
| 2. Disable VPN / Proxy | Yes | Yes | Yes | High |
| 3. Flush DNS cache | Yes | Yes | Partial | High |
| 4. Reset Chrome settings / flags | Yes | Yes | N/A | Medium |
| 5. Disable firewall / antivirus | Yes | Yes | N/A | Medium |
| 6. Check hosts file | Yes | Yes | N/A | Medium |
| 7. Restart router / modem | Yes | Yes | Yes | Medium |
| 8. Reinstall Chrome | Yes | Yes | Yes | Last resort |
ERR_CONNECTION_REFUSED vs. Similar Chrome Errors
These Chrome network errors look similar but have different root causes:
- ERR_CONNECTION_REFUSED — The server actively rejected the connection. The server is reachable but refusing the request. Fix: check server status, firewall, proxy, DNS.
- ERR_CONNECTION_TIMED_OUT — Chrome sent the request but received no response within the timeout window. Often caused by a slow server, overloaded network, or a silent firewall rule. Fix: check network speed, try a different DNS server.
- ERR_NAME_NOT_RESOLVED — Chrome could not resolve the domain name to an IP address at all. DNS is failing. Fix: flush DNS, switch to Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1).
- ERR_SSL_PROTOCOL_ERROR — The connection was established but the SSL/TLS handshake failed. Fix: clear SSL state, update Chrome, check system clock.
8.8.8.8 (primary) and 8.8.4.4 (secondary) for Google DNS, or 1.1.1.1 and 1.0.0.1 for Cloudflare DNS.
Still Getting ERR_CONNECTION_REFUSED?
If none of these fixes worked, the cause may be a deeper network configuration issue, malware modifying your network stack, or a corrupted Windows/Mac network driver. IT Cares diagnoses and fixes Chrome connection errors remotely — usually in 30 minutes or less. Flat rate of $59.
Frequently Asked Questions
ERR_CONNECTION_REFUSED appears when Chrome successfully reaches the server's IP address via DNS but the server actively rejects the TCP connection. The most common causes are: the website's server is down or has a closed port, a firewall or antivirus on your computer is blocking Chrome's outbound connection, an active VPN or proxy is routing traffic to a dead endpoint, your router has a firewall rule or parental control blocking the site, or a misconfigured hosts file is redirecting the domain to an incorrect IP address such as 0.0.0.0 or 127.0.0.1.
It depends on where the error occurs. If ERR_CONNECTION_REFUSED only appears on one specific website and the same site loads fine on your phone using mobile data, the problem is on the server side — the site is down, its CDN is misconfigured, or the server's firewall has blocked your IP. If the error appears on multiple websites or all websites, the problem is on your computer or local network — most likely your VPN, proxy settings, firewall, or DNS cache. Use downdetector.com to check the site's status and try it on another device or network before making changes to your computer.
It can mean that, but it is not the most likely explanation for most users. When a server bans an IP address, it often sends a TCP RST (reset) packet, which Chrome interprets as ERR_CONNECTION_REFUSED. To test: connect to a VPN and try the same site — if it loads, your IP may have been blacklisted by the site's firewall or abuse protection system. You can also try accessing the site via a different network (mobile hotspot) to confirm. If an IP ban is confirmed, contact the website's support team to request removal, or wait 24–48 hours as many automated bans are temporary.
On Android, ERR_CONNECTION_REFUSED is most commonly caused by a VPN app running in the background or incorrect Wi-Fi proxy settings. Fix it in this order: (1) Disable any active VPN app completely. (2) Go to Settings > Wi-Fi > long-press your network > Modify Network > Advanced > Proxy and set it to None. (3) Forget the Wi-Fi network and reconnect. (4) Clear Chrome's cache: Settings > Apps > Chrome > Storage > Clear Cache. (5) Restart your phone and router. If the issue persists, update Chrome via the Play Store and also update Android System WebView, which Chrome depends on.
On Mac, start with DNS: open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (enter your admin password when prompted). Next, go to System Settings > Network > select your connection > Details > Proxies and make sure all proxy protocols are unchecked. Check that macOS Firewall (System Settings > Network > Firewall) is not blocking Chrome — click Options and verify Chrome is allowed. If you use Little Snitch or LuLu, check their logs for blocked Chrome connections. Reset Chrome at chrome://settings/reset if the issue persists. As a last step, create a new macOS user account and test there to rule out profile-level corruption.
Comments
The hosts file tip saved me. I had Malwarebytes set up months ago and it had added an entry blocking a site I legitimately need for work. I had no idea the hosts file even existed. Removed the line, flushed DNS, and it was fixed in under 5 minutes. Should be higher on the list honestly.
Disabling the proxy fixed it for me on Windows. I had set up a proxy for a work project months ago and forgot to remove it. ERR_CONNECTION_REFUSED was showing on random sites that my company's proxy server was blocking. Turned it off and everything loaded instantly. The guide explanation of what the error actually means helped a lot — most articles just list fixes without explaining anything.
For me it was the router. I have Eero and apparently a firmware update had turned on a content filter I did not even know existed. Logged into the Eero app, found the filter blocking the domain, removed it. The ipconfig /flushdns command on Windows was the second step that locked it in. Thanks for the detailed walkthrough — other guides I found were way too vague.
Leave a Comment