How to Fix ERR_CONNECTION_REFUSED in Browsers

Seeing ERR_CONNECTION_REFUSED in Chrome, Edge, Firefox, Brave, or another browser can be frustrating because it usually appears suddenly and gives little detail. In plain terms, the browser tried to connect to a website or local web service, but the connection was actively rejected. This does not always mean the website is permanently down; it can be caused by local network settings, browser data, proxy configuration, DNS problems, firewall rules, or a server-side issue.

TLDR: ERR_CONNECTION_REFUSED means your browser attempted to reach a server, but the server or something between you and the server refused the connection. Start by checking whether the website is down, then restart your router, clear browser cache, disable proxy or VPN settings, flush DNS, and check firewall or antivirus rules. If the error affects only one website, the problem may be on that site’s server; if it affects many sites, the cause is more likely on your device or network.

What ERR_CONNECTION_REFUSED Means

The error ERR_CONNECTION_REFUSED is most commonly associated with Google Chrome and Chromium-based browsers, but similar messages can appear in other browsers. It indicates that your device reached the destination address, or attempted to, but the connection was rejected. This is different from a timeout, where the server does not respond at all.

A refused connection often means that no service is listening on the requested port, a firewall is blocking the request, a proxy is misconfigured, or the target server is rejecting traffic. For regular users, it may appear when opening a public website. For developers, it often appears when connecting to localhost, a testing server, or a web application running on a specific port.

1. Check Whether the Website Is Down

Before changing your device settings, confirm whether the problem is actually with the website. Try opening the same site from another browser, another device, or a mobile network. You can also use a reputable website status checker to see whether other users are reporting the same issue.

• If the website fails everywhere: the site may be offline, overloaded, or misconfigured.
• If the website works on another device: your computer, browser, DNS, firewall, or network settings may be responsible.
• If only one browser fails: the issue is likely related to browser cache, extensions, or browser-specific settings.

This first step is important because it prevents unnecessary troubleshooting. If the server is down, there is usually nothing you can fix locally except wait or contact the website owner.

2. Restart Your Browser, Device, and Router

Simple restarts often resolve temporary connectivity faults. Close the browser completely, reopen it, and try the site again. If the error persists, restart your computer or phone. After that, restart your router or modem by unplugging it from power for about 30 seconds, then plugging it back in.

This can clear temporary network states, renew connections to your internet service provider, and resolve small routing errors. Although it sounds basic, it is a reliable first-line fix, especially when the error appears after sleep mode, a network change, or a brief internet outage.

3. Clear Browser Cache and Cookies

Browsers store cached files and cookies to make websites load faster. However, outdated or corrupted cached data can sometimes cause connection problems, particularly if a website recently changed its configuration, security certificate, redirects, or server address.

In Chrome or Edge, you can usually clear browsing data by opening Settings, going to Privacy and security, and selecting Clear browsing data. Choose cached images and files, cookies, and site data if appropriate. For a less disruptive approach, clear data only for the affected website.

Note: clearing cookies may sign you out of websites. If you use two-factor authentication or complex passwords, make sure you can log back in before clearing all cookies.

4. Disable Browser Extensions Temporarily

Extensions can interfere with connections, especially ad blockers, privacy tools, web security extensions, VPN extensions, and script blockers. To test this, open the site in a private or incognito window with extensions disabled. You can also disable extensions one by one and reload the page after each change.

1. Open your browser’s extensions or add-ons page.
2. Disable all nonessential extensions.
3. Restart the browser.
4. Try visiting the website again.
5. Re-enable extensions one at a time to identify the cause.

If the site works after disabling an extension, update that extension or replace it with a more reliable alternative. Avoid installing multiple tools that perform the same function, such as several privacy filters or security scanners, because they may conflict with each other.

5. Check Proxy Settings

A misconfigured proxy is one of the most common causes of ERR_CONNECTION_REFUSED. A proxy acts as an intermediary between your browser and the internet. If your browser or operating system is set to use a proxy server that is unavailable, incorrect, or blocked, connections may be refused.

On Windows, open Settings, go to Network & Internet, and select Proxy. Unless your employer, school, or network administrator requires a proxy, disable manual proxy configuration. On macOS, open System Settings, go to Network, select your active connection, and review proxy settings.

If you are on a corporate or school network, do not remove required proxy settings without approval. Instead, ask IT support whether the proxy is experiencing an outage or whether your device should use a specific configuration script.

6. Turn Off VPN Temporarily

VPN services can improve privacy and help secure traffic on public networks, but they can also cause access problems. Some websites refuse connections from known VPN servers, and some VPN clients may route traffic incorrectly after an update or interrupted session.

Disconnect from the VPN and reload the website. If the error disappears, try switching to another VPN server location, updating the VPN app, or resetting the VPN protocol. If you need the VPN for work, contact your administrator before making permanent changes.

7. Flush DNS and Renew Your IP Address

DNS translates domain names into IP addresses. If your device has an outdated or incorrect DNS record cached, the browser may attempt to connect to the wrong destination. Flushing DNS forces your system to request fresh records.

On Windows, open Command Prompt as administrator and run:

ipconfig /flushdns
ipconfig /release
ipconfig /renew

On macOS, the command depends on the version, but many recent versions use:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

After running the command, restart your browser and test the site again. You may also try changing DNS servers to a trusted provider, such as your ISP’s DNS, Google Public DNS, Cloudflare DNS, or Quad9. Use reputable DNS providers and avoid unknown services that could log or manipulate your traffic.

8. Review Firewall and Antivirus Rules

Firewalls and antivirus tools can block suspicious traffic, but they may also block legitimate browser connections. If ERR_CONNECTION_REFUSED started after installing security software, updating your firewall, or changing network profiles, review the rules.

• Make sure your browser is allowed to access the internet.
• Check whether the affected website or port is blocked.
• Temporarily disable web filtering only for testing, then turn it back on.
• Update your security software to the latest version.

Do not leave your firewall or antivirus disabled permanently. If disabling a security feature resolves the problem, create a specific allow rule or contact the software vendor for guidance. A careful fix is safer than simply turning protection off.

9. Check the Hosts File

Your operating system has a hosts file that can manually map domain names to IP addresses. If a website is incorrectly listed there, your browser may be sent to the wrong location, causing a refused connection. This sometimes happens after developer testing, malware activity, or manual troubleshooting.

On Windows, the hosts file is usually located at:

C:WindowsSystem32driversetchosts

On macOS and Linux, it is usually located at:

/etc/hosts

Open the file with administrator privileges and look for entries related to the website that is failing. Do not delete lines unless you understand their purpose. If you find an old entry pointing the domain to 127.0.0.1 or another unexpected address, that may explain the error.

10. If You Are Accessing Localhost

Developers frequently encounter ERR_CONNECTION_REFUSED when accessing a local application, such as http://localhost:3000 or http://127.0.0.1:8000. In this case, the browser is usually working correctly; the local server is not running, is listening on a different port, or is bound to the wrong address.

Check the following:

• Is the development server running? Restart it and watch the terminal for errors.
• Are you using the correct port? Confirm whether the app uses 3000, 5000, 8000, 8080, or another port.
• Is another process occupying the port? Stop the conflicting process or change the port.
• Is the app bound to localhost only? If testing from another device, bind to the correct network interface.

For Docker or virtual machines, also confirm that ports are properly exposed and forwarded. A container may be running successfully internally while the host machine still refuses external connections because the port mapping is missing or incorrect.

11. Reset Browser or Network Settings

If the error continues and affects multiple websites, consider resetting browser settings. This can disable problematic extensions, restore default search and startup behavior, and remove modified site permissions. In Chrome or Edge, look for Reset settings in the settings menu.

You can also reset network settings at the operating system level. On Windows, Network reset reinstalls network adapters and restores networking components to default settings. On macOS, removing and re-adding the active network service can produce a similar effect. Use these options carefully, as you may need to reconnect to Wi-Fi networks and reconfigure VPN or static IP settings afterward.

12. When the Problem Is Server-Side

If you own or manage the website, ERR_CONNECTION_REFUSED may indicate a server configuration issue. The web server may be stopped, the firewall may be blocking ports 80 or 443, the reverse proxy may be misconfigured, or the hosting provider may be experiencing an outage.

Server administrators should verify that the web server process is running, ports are open, SSL configuration is valid, and recent deployments did not introduce errors. Review logs for services such as Nginx, Apache, IIS, Node.js, or the application framework in use. Also check whether security groups, cloud firewall rules, or load balancer health checks are preventing traffic from reaching the application.

Final Checklist

To resolve ERR_CONNECTION_REFUSED efficiently, work from the simplest explanations to the more technical ones:

1. Confirm whether the website is down for everyone or only for you.
2. Restart the browser, device, and router.
3. Clear cache and cookies for the affected site.
4. Disable extensions, VPNs, and proxy settings temporarily.
5. Flush DNS and consider changing DNS servers.
6. Review firewall, antivirus, and hosts file settings.
7. For localhost, confirm the server is running on the correct port.
8. If you manage the site, inspect server logs and firewall rules.

ERR_CONNECTION_REFUSED is not a single-cause error, but it is usually solvable with a structured approach. By checking the website status first, then testing local browser, network, DNS, and security settings, you can identify the source without making unnecessary changes. If the issue points to a server you do not control, the most appropriate action is to wait, report the problem, or contact the website owner with clear details about the error and when it occurred.