How to Fix ERR_CONNECTION_REFUSED in Chrome

Chrome shows "This site can't be reached. [website] refused to connect. ERR_CONNECTION_REFUSED." This means your browser reached the server, but the server said "no" — it actively refused the connection.

This is different from a timeout (server unreachable) or DNS error (can't find server). The server is there, it just won't let you in.

Fix 1: Check if the Site is Down

Before troubleshooting your end, check if the site is down for everyone:

• Try the same URL on your phone (using mobile data, not WiFi)
• Ask someone else to try it
• Check downdetector.com

If it is down for everyone, the problem is on the server side — nothing you can do but wait.

Fix 2: Clear Browser Cache

Stale cached data can cause connection issues:

1. Press Ctrl + Shift + Delete
2. Select "All time"
3. Check "Cached images and files" and "Cookies"
4. Click Delete
5. Try the site again

Fix 3: Check Your Proxy Settings

A misconfigured proxy blocks connections:

Windows: Settings → Network & Internet → Proxy → make sure "Use a proxy server" is OFF (unless you intentionally use one)

Mac: System Settings → Network → WiFi → Details → Proxies → make sure nothing is checked

Chrome: Settings → System → "Open your computer's proxy settings" → verify no proxy is configured

Fix 4: Disable VPN

VPNs can route your traffic through servers that the website blocks. Turn off your VPN and try again.

Fix 5: Disable Firewall/Antivirus Temporarily

Your firewall or antivirus might be blocking the connection:

• Windows Firewall: Settings → Privacy & Security → Windows Security → Firewall → temporarily turn off
• Antivirus: Temporarily disable web protection
• If the site loads, add an exception and re-enable

Fix 6: Flush DNS and Reset Network

Windows:

ipconfig /flushdns
netsh winsock reset

Restart your computer.

Mac:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Fix 7: Try a Different Port

If you are accessing a specific service (like localhost:3000 or 192.168.1.1:8080), the port might be wrong:

• Check if the service is actually running on that port
• Try the default port (80 for HTTP, 443 for HTTPS)
• Use our Port Scanner to check which ports are open

Fix 8: Check the hosts File

Your hosts file might redirect the domain to the wrong address:

Windows: C:\Windows\System32\drivers\etc\hosts Mac/Linux: /etc/hosts

Look for the domain. If it points to 127.0.0.1 or 0.0.0.0, remove that line.

Fix 9: Reset Chrome

If the error happens on multiple sites: Chrome Settings → Reset settings → "Restore settings to their original defaults"

This resets extensions, settings, and cached data without deleting bookmarks or passwords.

For Website Owners

If users report ERR_CONNECTION_REFUSED on your site:

• Is the web server running? → systemctl status nginx
• Is it listening on the right port? → ss -tlnp | grep 80
• Is the firewall blocking? → Check with our Port Scanner
• Did the server crash? → Check logs: journalctl -u nginx --since "1 hour ago"

Common Causes Summary

Related Tools

• Port Scanner — check if a port is open on the server
• DNS Toolbox — verify DNS resolves correctly
• SSL Server Test — check if HTTPS is configured
• What's My IP — verify your connection
• Fix 'Site Can't Be Reached'
• How to Check if a Port Is Open
• Port Forwarding Guide