Smart Home & Tech

ERR_CONNECTION_REFUSED: What It Means and How to Troubleshoot

By Tech Home Tips Editors Published October 5, 2026 Updated October 5, 2026 5 min read Report a correction

A practical guide to understanding the ERR_CONNECTION_REFUSED browser error, why it happens, and step-by-step troubleshooting for general web users.

Quick meaning

The browser reached the server IP, but the server actively refused the connection on the requested port.

ErrorERR_CONNECTION_REFUSED
FamilyBrowser Connection

Safe first actions

  1. Test the site on another device or network
  2. Check global site status via DownDetector or similar
  3. Disable VPN/proxy temporarily
  4. Clear browser cache and cookies
  5. Flush local DNS cache

What not to do

  • Do not edit the hosts file unless you know the correct IP
  • Do not leave antivirus/firewall disabled permanently
  • Do not assume the site is down based on one device
  • Do not ignore browser extensions that may block connections

When the website or provider must fix it

If the site is down for everyone, or if you manage the site and the web service (Apache, Nginx, IIS, etc.) is not listening on port 80/443, the server administrator must start the service, correct the port binding, adjust server firewall rules, or fix application crashes. No client-side action can resolve a server-side refusal.

What Is ERR_CONNECTION_REFUSED?

ERR_CONNECTION_REFUSED is a browser error that appears when your browser tries to connect to a website's server but the server actively rejects the connection attempt. Unlike a timeout, where the server does not respond at all, a refused connection means the server received the request and explicitly said "no." This error typically shows in Chrome, Edge, Firefox, and other Chromium-based browsers with a message such as "This site can't be reached" or "The connection was refused."

Why Does This Error Happen?

The error usually stems from one of three areas: the website's server, your local network or device, or security software interfering with the connection. On the server side, the web service may be down, misconfigured, or listening on a different port than expected. On your side, a firewall, antivirus, VPN, or proxy may be blocking the outbound request. Browser cache corruption or outdated DNS entries can also trigger the error even when the site is reachable for others.

Quick Checks Before Deep Troubleshooting

  • Try opening the same site in a different browser or on a different device (phone, tablet, another computer). If it works elsewhere, the issue is likely local to your device or browser.
  • Check if the site is down for everyone using a status checker like DownDetector or IsItDownRightNow. If the site is globally down, the problem is on the provider's side and you must wait for them to fix it.
  • Disable any active VPN or proxy temporarily and reload the page. Some VPN exit nodes are blocked by certain sites.

Step-by-Step Troubleshooting on Windows and Mac

Follow these steps in order. Stop when the site loads.

  1. Clear browser cache and cookies. In Chrome: Settings → Privacy and security → Clear browsing data → select "Cached images and files" and "Cookies and other site data" → Clear data. In Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data.
  2. Flush DNS cache. On Windows: open Command Prompt as administrator and run ipconfig /flushdns. On macOS: open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (enter your password when prompted).
  3. Restart your router and modem. Unplug both, wait 30 seconds, plug the modem in first, wait for lights to stabilize, then plug in the router.
  4. Temporarily disable firewall or antivirus. Turn off third-party antivirus/firewall for a few minutes and test the site. If it works, add an exception for the browser or the site in the security software settings, then re-enable protection.
  5. Check proxy settings. On Windows: Settings → Network & Internet → Proxy → ensure "Use a proxy server" is off unless you intentionally use one. On macOS: System Settings → Network → select your connection → Details → Proxies → ensure no unwanted proxies are enabled.
  6. Try a different DNS provider. Change DNS to Cloudflare (1.1.1.1, 1.0.0.1) or Google (8.8.8.8, 8.8.4.4) in your network adapter settings or router admin page.
  7. Reset network stack (Windows). In an elevated Command Prompt, run these commands one by one: netsh winsock reset, netsh int ip reset, ipconfig /release, ipconfig /renew. Restart the computer after.

Common Mistakes to Avoid

  • Assuming the site is down just because it fails on one device. usually cross-check with another device or network.
  • Leaving a VPN or proxy enabled while troubleshooting. These often mask the real cause.
  • Editing the hosts file without knowing the correct IP. An incorrect entry can permanently block the site until removed.
  • Disabling antivirus permanently. Only disable briefly for testing, then re-enable and configure exceptions properly.
  • Ignoring browser extensions. Ad blockers, privacy tools, or script blockers can interfere with connection handshakes. Try an incognito/private window with extensions disabled.

When the Website or Provider Must Fix It

If the site loads on other networks or devices but not on yours after completing the steps above, the issue may be your ISP blocking the IP or a routing problem. Contact your ISP's support. However, if the site is down for everyone, or if you see the error on a site you manage, the fix must come from the server side. The server administrator needs to verify that the web service (Apache, Nginx, IIS, Node, etc.) is running, listening on the correct port (usually 80 for HTTP, 443 for HTTPS), and that firewall rules on the server allow inbound traffic on those ports. Application-level crashes, exhausted connection pools, or misconfigured virtual hosts can also cause the server to refuse connections. In those cases, no client-side troubleshooting will resolve the error; the service provider must restore the service.

ERR_CONNECTION_REFUSED often appears alongside other connection errors. If you encounter a gateway problem instead, see HTTP 502 Bad Gateway: What It Means and How to Troubleshoot. For request-rate limiting issues, review HTTP 429 Too Many Requests: What It Means and How to Fix It.

When to Get Help or Stop

Stop troubleshooting locally if:

  • The site works on another network (mobile hotspot, neighbor's Wi-Fi) but not yours — contact your ISP.
  • The site is confirmed down globally — wait for the provider.
  • You manage the site and the web service will not start — check server logs, then engage your hosting support or a sysadmin.

For persistent local network issues that survive a router reboot and DNS change, consider a professional network diagnostic. For device-specific problems that remain after a clean browser profile and network reset, the OS network stack may need repair or a clean OS install.

Last reviewed October 5, 2026. Suggest a correction

Sources and methodology

Claims that depend on an outside authority are tied to the references below. Product details change. Confirm the current specification sheet before you buy or install anything.

  1. Securing Wireless Networks — CISA (government), accessed October 5, 2026. General guidance on securing wireless networks, relevant to router and network troubleshooting steps.
  2. Guidelines for Securing Wireless Local Area Networks (WLANs) — NIST (government), accessed October 5, 2026. NIST guidelines for securing WLANs, supports best practices for network configuration and DNS hygiene.

Information on this site is for general educational purposes and is not professional advice.

Parent topic: Smart Home & Tech