iFastHostingHow to fix ERR_CONNECTION_REFUSED
Nothing answered on the other end at all — here is how to tell whether that is the server, the address, or something on your own network.
ERR_CONNECTION_REFUSED means your browser found an IP address for the domain and tried to open a connection to it, and that connection was actively rejected. This is a distinct failure from a slow or missing response — something on the other end said "no" quickly and explicitly, rather than the request simply going nowhere or timing out.
That distinction is useful. It tells you the network path to the address works, at least as far as reaching a machine that responds. The question is why that machine is refusing the connection.
Try the same address from a different network — a phone on mobile data with Wi-Fi off is the fastest test. If it loads there, the problem is local to your original network or device, not the website, and everything below about the server is not the cause.
The causes, in the order worth checking
1. The web server or a specific service on it is not running
If the web server process itself has stopped — during a restart, an update, or a genuine fault — nothing is listening on the port the browser tries to connect to, and the connection is refused rather than accepted. This is the core hosting-side explanation, and it's the one worth checking your control panel's status page or contacting support about if the site was working recently and nothing changed on your end.
2. DNS is pointing at an IP address that no longer runs your site
After a server migration, an old DNS record left in place will happily resolve to an address that is either no longer running any web server, or is now running something else entirely. The browser gets a real IP address, connects to a real machine, and that machine — reasonably — refuses a connection for a domain it knows nothing about. Checking what IP address the domain currently resolves to, and comparing it against what your hosting control panel says your site's actual IP address is, will confirm or rule this out directly.
3. A firewall is blocking the specific port
Every connection is made to a specific port — 443 for HTTPS, 80 for HTTP. A firewall on the server, or one imposed by a network in between, can block one of these while leaving the other open, or can block both while still allowing other kinds of traffic through, such as email. If the site loads over one protocol but not the other, that narrows it to a single port worth checking specifically rather than a general outage.
4. Something on your own network is intercepting or blocking the request
VPNs, corporate proxies, antivirus software with web filtering, and some public or restrictive Wi-Fi networks can all refuse connections to specific addresses or ports before the request ever leaves your device. This is exactly what the network-switch test at the top of this article is designed to catch, and it accounts for a meaningful share of reports that turn out to have nothing to do with the site at all.
5. The URL specifies a non-standard port that nothing is listening on
If the address being used includes an explicit port number — something like yourdomain.com:8080 — and nothing on the server is configured to listen on that port, the connection will be refused even though the standard site on port 443 works perfectly well. Double-check the URL doesn't carry a leftover port number from testing or from an old bookmark.
Confirming what's actually listening
From a command line, curl -v https://yourdomain.com shows exactly where the attempt fails — whether it connects and then gets refused, or fails before that. Comparing this against a request to a known-working site on the same network isolates whether the issue is specific to your domain or general to your connection.
A connection refusal is a specific, deliberate response, which is a different thing from a request that never gets answered at all. Treating every instance as "the server is down" skips past the DNS, port and local-network causes above, which between them explain most reports of this error.
If it's confirmed on the server side
Once you've ruled out your own network and confirmed DNS points at the correct address, contact support with the exact domain, the IP address it currently resolves to, and the time you first saw the error. That combination lets us check the server's own status immediately rather than working through the list again from our side.
Frequently asked questions
Is ERR_CONNECTION_REFUSED the same as the site being down?
It is one specific way a site can appear down, but not the only one. It means a connection attempt reached an IP address and was actively rejected — a different address, a slow server, or a DNS failure would each show a different Chrome error rather than this one, which is actually useful for narrowing things down.
Could this be my computer rather than the website?
Yes, and it is worth ruling out early. A VPN, a restrictive office or public network, or security software blocking a specific port can all produce a connection refusal that has nothing to do with the site itself. Testing the same address from a different network settles this in under a minute.
Related reading
Your browser could not turn the domain name into an address at all — here is how to work out why DNS has nothing to give it.
How to fix "This site can't be reached"One heading covers several completely different faults — here is how the small print underneath tells you which one you actually have.
How to tell if your site is down for everyoneA site that looks down to you might only be down for you — here is how to check from outside your own network before assuming the worst.
How to fix "Error establishing a database connection"A blank page with one line of text, and five possible causes. Here is how to tell which one you have, in the order worth checking.