home / browser errors / err-connection-refused

[ REPAIR GUIDE ] BROWSER ERRORS

How to fix ERR_CONNECTION_REFUSED

ERROR DETECTED >This site can't be reached. example.com refused to connect. ERR_CONNECTION_REFUSED

UPDATED NOVEMBER 20262 MIN READ8 FIXES

QUICK FIX

Check the address and port, then turn off any proxy or VPN and reload. If it is your own localhost site, make sure the server is actually running on that port.

What it means

Your browser reached the address, but nothing there accepted the connection, or something blocked it. Common reasons are the site being down, a wrong port, a proxy or firewall in the way, or a local server that is not running.

Common causes

  • The website or server is down or not accepting connections
  • A wrong address or port number
  • A proxy or VPN that is not working
  • A firewall or antivirus blocking the connection
  • Old DNS data pointing to the wrong server
  • A local development server that is stopped or listening on another port

How to fix it

Work down the list. Each fix is safe to try before moving on to the next.

FIX 01Check the address and test other sitesEASY

  1. Check the address for typos, including any port number after a colon, such as :8080.
  2. Reload with F5 (Windows) or Cmd + R (Mac).
  3. Open the same site on another device using mobile data. If it fails there too, the site is down.

Why it helps: Rules out typos and confirms whether the site itself is refusing everyone.

FIX 02Turn off proxy and VPNEASY

  1. Disconnect any VPN app or extension.
  2. Windows 11: Settings > Network & internet > Proxy, turn off manual proxy settings you did not add.
  3. Mac: System Settings > Network, select your connection, then Details > Proxies and turn off proxies you did not add.
  4. Reload the page.

Why it helps: A dead proxy is one of the most common reasons every site is refused.

FIX 03Restart router and browserEASY

  1. Unplug your router for 30 seconds, then plug it back in.
  2. Quit the browser completely and reopen it.

Why it helps: Clears temporary network glitches.

FIX 04Clear browsing data and test extensionsEASY

  1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac), choose All time, tick cookies and cached files, and delete.
  2. Open an Incognito window with Ctrl + Shift + N (Windows) or Cmd + Shift + N (Mac) and try the site.
  3. If it works there, turn off extensions at chrome://extensions one by one.

Why it helps: Removes stale data and rules out blocking extensions.

FIX 05Flush the DNS cacheMEDIUM

  1. Windows: run Command Prompt as administrator and type ipconfig /flushdns.
  2. Chrome: go to chrome://net-internals/#dns and select Clear host cache.
  3. Reload the page.

Why it helps: Old lookups can send you to a server that no longer accepts connections.

FIX 06Check firewall and antivirusMEDIUM

  1. Windows: open Windows Security > Firewall & network protection and select Allow an app through firewall to check your browser is allowed.
  2. Check your antivirus for a block notice.
  3. If you pause protection to test, turn it back on right away.

Why it helps: Security tools can refuse connections to certain sites or ports.

// RUN THIS SITE? FIXES FOR SITE OWNERS

FIX 07Start your local server (localhost)MEDIUMSITE OWNERS

  1. Make sure your development server is running and has no startup errors.
  2. Check which port it reports, and use exactly that port in the address.
  3. If you run it inside a container or VM, make sure the port is published to your computer.
  4. Try http:// instead of https:// if the server does not use a certificate.

Why it helps: Localhost refuses connections when nothing is listening on that port.

FIX 08Check the web server and firewall rulesADVANCEDSITE OWNERS

  1. Confirm the web server service is running and listening on ports 80 and 443.
  2. Check the server and hosting firewall allow inbound traffic on those ports.
  3. Make sure your DNS records point to the right server IP address.

Why it helps: If the server is not listening or the port is blocked, every visitor is refused.

Check it's fixed

  • The page loads normally.
  • It loads on another device and network.
  • For localhost, the server logs show your request arriving.

When to get help

If the site refuses everyone, contact the site owner or host. If every site is refused, check with your internet provider or IT team.

Questions

What does "refused to connect" mean?

The device at that address answered but would not accept a connection, or something on the way blocked it.

Why does localhost refuse to connect?

Usually the local server is not running, crashed on start, or is using a different port than the one in your address.

Is ERR_CONNECTION_REFUSED my fault?

Not always. If the site is down or blocking connections, only its owner can fix it.

Related fixes

How to fix ERR_CONNECTION_RESETRestart your router and the browser, then turn off any VPN or proxy and reload. If the page works on another network, your network or a filtHow to fix ERR_CONNECTION_TIMED_OUTRestart your router, turn off any VPN or proxy, and reload. If the site times out on every network, the website is likely down or overloadedHow to fix "This site can't be reached"Check the address for typos, make sure you are online, and restart your router. Then look at the error code under the message and follow theHow to fix ERR_ADDRESS_UNREACHABLEMake sure you are connected to the same network as the device you are trying to reach and that the address is right. Then turn off any VPN o

Still stuck?

Paste the exact message and the repair bot will find the closest fix, or search it on Google, Microsoft, Apple, Reddit and YouTube.

Sources