How to Solve ERR_CONNECTION_REFUSED in Chrome, Edge, and Firefox

Few browser errors are as blunt as ERR_CONNECTION_REFUSED. One moment you expect a website to load; the next, Chrome, Edge, or Firefox tells you the connection was rejected. The good news is that this error usually has a practical cause: your browser attempted to reach a server, but the server, your device, your network, or a security tool refused the connection. With a structured approach, you can often fix it in minutes.

TLDR: ERR_CONNECTION_REFUSED means your browser reached out to a website or local service, but the connection was actively denied. Start by checking whether the site is down, then restart your browser, router, and device. If that does not work, clear browser data, disable VPNs or proxy settings, flush DNS, and check firewall or antivirus rules. The steps below work for Chrome, Microsoft Edge, and Firefox.

What Does ERR_CONNECTION_REFUSED Mean?

ERR_CONNECTION_REFUSED is a network-level error. It does not usually mean your internet is completely broken. Instead, it means your browser tried to connect to a specific address and port, but the destination rejected the request or something in between blocked it.

You may see this error in slightly different forms depending on the browser:

• Google Chrome: “This site can’t be reached” followed by ERR_CONNECTION_REFUSED.
• Microsoft Edge: “Hmmm… can’t reach this page” with a connection refused message.
• Mozilla Firefox: “Unable to connect” or “Firefox can’t establish a connection to the server.”

Although the wording differs, the underlying problem is similar. The browser requested a connection, but the target did not accept it.

Common Causes of ERR_CONNECTION_REFUSED

Before jumping into fixes, it helps to understand what might be causing the issue. The most common reasons include:

• The website is down: The server may be offline, overloaded, or misconfigured.
• Incorrect URL: A typo, wrong port number, or outdated bookmark can lead to a refused connection.
• Browser cache problems: Corrupted cached files or cookies can interfere with loading.
• Firewall or antivirus blocking: Security software may mistakenly block the site or browser.
• VPN or proxy issues: A misconfigured VPN or proxy can prevent the connection.
• DNS problems: Your device may be resolving the domain incorrectly.
• Local server not running: If you are visiting localhost, the app or service may not be active.

1. Check Whether the Website Is Actually Down

The fastest first step is to determine whether the problem is on your side or the website’s side. Try opening the same website on another device, such as your phone using mobile data. You can also visit another website to confirm your internet connection is working.

If other sites load normally but one site fails, the issue may be with that website. You can use a website status checker by searching for “is this site down” and entering the domain. If the site is down for everyone, there is little you can do besides wait.

If the website works on another device or network, continue troubleshooting your browser, computer, or local network.

2. Double-Check the URL

This sounds basic, but it is surprisingly common. A small typo can point your browser to the wrong server or port. Make sure the address is correct, especially if it includes:

• http versus https
• A specific port, such as :3000, :8080, or :8443
• A subdomain, such as app.example.com instead of example.com

If you are using a bookmark, type the address manually instead. Old bookmarks can point to pages or services that no longer exist.

3. Restart the Browser, Device, and Router

Simple restarts fix more network problems than most people expect. Browsers maintain sessions, cached DNS data, extensions, and background processes. Routers also keep connection tables that can become stale.

1. Close Chrome, Edge, or Firefox completely.
2. Reopen the browser and try the site again.
3. If the error remains, restart your computer or phone.
4. Unplug your router for about 30 seconds, then plug it back in.

After the router reconnects, test the website again. This refreshes your local network path and may clear temporary connection issues.

4. Clear Browser Cache and Cookies

Cached files help websites load faster, but outdated or corrupted data can sometimes trigger connection problems. Clearing cache and cookies is a safe and common fix.

In Chrome

1. Click the three dots in the top-right corner.
2. Go to Settings > Privacy and security.
3. Select Delete browsing data.
4. Choose Cached images and files and Cookies and other site data.
5. Click Delete data.

In Microsoft Edge

1. Click the three dots in the top-right corner.
2. Go to Settings > Privacy, search, and services.
3. Under Clear browsing data, choose Choose what to clear.
4. Select cookies and cached files, then click Clear now.

In Firefox

1. Click the menu button in the top-right corner.
2. Go to Settings > Privacy & Security.
3. Find Cookies and Site Data.
4. Click Clear Data and confirm.

After clearing data, close and reopen the browser before testing the site again.

5. Disable Extensions Temporarily

Browser extensions can block scripts, redirect traffic, enforce privacy rules, or interfere with secure connections. Ad blockers, VPN extensions, security add-ons, and developer tools are frequent suspects.

To test this quickly, open the website in a private browsing window:

• Chrome: Press Ctrl + Shift + N or Cmd + Shift + N.
• Edge: Press Ctrl + Shift + N or Cmd + Shift + N.
• Firefox: Press Ctrl + Shift + P or Cmd + Shift + P.

If the site works in private mode, an extension may be responsible. Disable extensions one by one until you identify the culprit. Once found, update it, change its settings, or remove it.

6. Turn Off VPN or Proxy Settings

VPNs and proxies change the path between your browser and the website. If the VPN server is blocked, overloaded, or misconfigured, the website may refuse the connection. Temporarily disconnect your VPN and try again.

You should also check your system proxy settings:

On Windows

1. Open Settings.
2. Go to Network & Internet > Proxy.
3. Turn off proxy settings unless you specifically need them.

On macOS

1. Open System Settings.
2. Go to Network.
3. Select your connection and check Proxies.
4. Disable unnecessary proxy options.

If the site loads after turning off the VPN or proxy, the issue is not your browser. It is the routing service you were using.

7. Flush DNS Cache

DNS translates website names into IP addresses. If your DNS cache contains outdated information, your browser may try to connect to the wrong server. Flushing DNS forces your device to request fresh address information.

Windows

Open Command Prompt as administrator and run:

ipconfig /flushdns

macOS

Open Terminal and run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux

The command varies by distribution, but common options include:

sudo systemd-resolve --flush-caches

After flushing DNS, restart your browser and try visiting the site again.

8. Change DNS Servers

If flushing DNS does not help, your current DNS provider may be returning incorrect or delayed results. Switching to a public DNS provider can improve reliability.

Popular options include:

• Google DNS: 8.8.8.8 and 8.8.4.4
• Cloudflare DNS: 1.1.1.1 and 1.0.0.1
• Quad9 DNS: 9.9.9.9 and 149.112.112.112

You can change DNS settings in your operating system’s network settings or directly on your router. Changing it on the router applies the new DNS to all devices connected to your network.

9. Check Firewall and Antivirus Rules

Security software exists to block suspicious traffic, but it can occasionally block legitimate websites or browsers. If ERR_CONNECTION_REFUSED started after installing or updating antivirus software, firewall rules may be involved.

Temporarily disable your firewall or antivirus web shield only long enough to test the site. If the website loads, re-enable protection immediately and create a proper exception for your browser or the website. Do not leave your system unprotected.

Also make sure your browser is allowed through the operating system firewall. On Windows, search for Allow an app through Windows Firewall and verify that Chrome, Edge, or Firefox has permission for private and public networks as needed.

10. Reset Network Settings

If several sites are failing and basic fixes have not worked, resetting network settings can help. This clears deeper configuration issues, including bad adapters, corrupted settings, or problematic network stacks.

Windows

1. Open Settings.
2. Go to Network & Internet.
3. Select Advanced network settings.
4. Choose Network reset.
5. Restart your PC.

macOS

Remove and re-add your Wi-Fi or Ethernet service from System Settings > Network. You can also create a new network location to refresh configuration.

Remember that resetting network settings may remove saved Wi-Fi networks, VPN configurations, and custom DNS settings.

11. If You Are Using Localhost, Check the Local Server

Developers often encounter ERR_CONNECTION_REFUSED when visiting addresses like localhost:3000, 127.0.0.1:8000, or localhost:8080. In this case, the browser is trying to connect to a service running on your own computer.

Check the following:

• Is the local server running? Start your development server again.
• Are you using the correct port? A React app, Node server, Django app, or Docker container may use a different port.
• Did the app crash? Look at your terminal logs for errors.
• Is Docker mapped correctly? Make sure container ports are exposed to the host.
• Is another process using the port? Stop the conflicting process or change your app’s port.

For local development, this error almost always means the browser is fine, but the local service is not listening where you expect it to be.

12. Update or Reset Your Browser

An outdated browser can create compatibility and security problems. Update Chrome, Edge, or Firefox to the latest version, then restart it.

If the problem affects only one browser, try resetting that browser’s settings. This will usually disable extensions, reset startup pages, and restore default search and content settings without deleting bookmarks.

• Chrome: Settings > Reset settings > Restore settings to their original defaults.
• Edge: Settings > Reset settings > Restore settings to their default values.
• Firefox: Type about:support in the address bar and choose Refresh Firefox.

When the Problem Is Not Yours to Fix

Sometimes ERR_CONNECTION_REFUSED is caused by the website owner’s server configuration. The server may be offline, the web service may have crashed, a firewall may be rejecting traffic, or the site may not be listening on the expected port. If you have tried multiple devices, browsers, and networks with the same result, the issue is likely on the server side.

In that case, your best options are to wait, contact the website owner, or check the site’s official status page or social media channels for outage updates.

Final Thoughts

ERR_CONNECTION_REFUSED looks intimidating, but it is usually solvable with logical troubleshooting. Start with the simplest possibilities: confirm the site is online, check the URL, restart your browser and router, and clear cached data. Then move on to VPNs, proxies, DNS, firewalls, and network resets.

The key is to test one change at a time. That way, when the page finally loads, you know what fixed it. Whether you use Chrome, Edge, or Firefox, the error points to the same basic issue: the connection was refused. Once you identify who is refusing it—the browser, your network, a security tool, or the server—you are already most of the way to solving it.