ERR_CONNECTION_REFUSED: What It Means and How to Fix It

ERR_CONNECTION_REFUSED is one of the more alarming browser errors because it implies the server actively rejected your connection — not just that something was slow or broken. The reality is it has several possible causes, and most of them are straightforward to fix.

What Does ERR_CONNECTION_REFUSED Mean?

When your browser tries to connect to a website, it sends a request to the server on a specific port (usually port 80 for HTTP or 443 for HTTPS). If the server responds with a TCP RST (reset) packet, your browser shows ERR_CONNECTION_REFUSED.

In plain terms: the connection was refused at the network level. Either nothing is listening on that port, a firewall blocked the connection, or the service is down.

This is different from a timeout (where the connection just hangs) or a DNS error (where the domain can't be resolved at all).

Is It a Server Problem or a Client Problem?

This is the first question to ask. ERR_CONNECTION_REFUSED can happen on either side:

Server-side causes:

• The web server (Nginx, Apache) has crashed or isn't running
• A firewall is blocking the connection
• The server is listening on the wrong port
• The service was recently deployed to a new port without updating the proxy config

Client-side causes:

• A local firewall or antivirus software is blocking outbound connections
• A VPN or proxy is interfering with the connection
• Browser extensions blocking the request
• The URL has the wrong port specified (e.g. http://example.com:8080 when it should be :443)

How to Diagnose ERR_CONNECTION_REFUSED

Check if the Problem Is Just You

Try loading the site from a different device, network, or using an online tool like downforeveryoneorjustme.com. If others can reach it, the issue is on your end. If nobody can, it's a server problem.

You can also use our website down checker to test from multiple locations.

Test the Connection Directly

Use curl or telnet to check if the port is open:

curl -v http://yourdomain.com
telnet yourdomain.com 80
telnet yourdomain.com 443

If you get "Connection refused" in the terminal too, the service definitely isn't listening on that port.

Check if the Web Server Is Running

SSH into your server and check:

# Nginx
sudo systemctl status nginx

# Apache
sudo systemctl status apache2

# Check what's listening on port 80/443
sudo ss -tlnp | grep -E ':80|:443'

If Nginx or Apache isn't running, start it:

sudo systemctl start nginx
sudo systemctl start apache2

Check Your Firewall

# UFW (Ubuntu)
sudo ufw status

# iptables
sudo iptables -L -n | grep -E '80|443'

If port 80 or 443 is blocked, open it:

sudo ufw allow 80/tcp
sudo ufw allow 443/tcp

Common Scenarios and Fixes

After a Server Reboot

The most common cause of ERR_CONNECTION_REFUSED. Services don't always restart automatically after a reboot. Make sure Nginx or Apache is set to start on boot:

sudo systemctl enable nginx
sudo systemctl enable apache2

After a New Deployment

If you recently changed which port your app runs on, check that your proxy config still points to the right place. A single digit difference in a port number will cause this error immediately.

Behind Cloudflare or a CDN

If you're using Cloudflare, ERR_CONNECTION_REFUSED might mean Cloudflare can reach the internet but your origin server (the one behind Cloudflare) isn't accepting connections. This can look like a Cloudflare 521 error from the Cloudflare side.

On a Local Development Server

If you're seeing this while running a local dev server, the server may not have started, may have crashed, or may be running on a different port than you think. Check your terminal for the port it's actually listening on.

Client-Side Fixes to Try

If it's definitely a client-side problem:

1. Clear your browser cache — corrupted cache entries can sometimes cause connection issues
2. Disable VPN or proxy — these can interfere with connections to specific servers
3. Try incognito mode — rules out browser extensions
4. Flush your DNS cache — ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS
5. Check your antivirus/firewall software — some security tools block connections to sites they consider risky

Don't Wait to Find Out Your Site Is Down

ERR_CONNECTION_REFUSED from the server side means your site is completely unreachable. Nobody can visit it, buy from it, or contact you through it.

Having uptime monitoring in place means you'll get an alert within a minute of your server going down — before customers start seeing this error. Set up downtime alerts with Domain Monitor and stop finding out about outages from your users.

Related Articles

• 503 Service Unavailable - What It Means and How to Fix It
• Connection Timed Out Error - What It Means and How to Fix It
• DNS_PROBE_FINISHED_NXDOMAIN - What It Means and How to Fix It