ERR_CONNECTION_REFUSED Error
The browser shows "This site can't be reached" with ERR_CONNECTION_REFUSED — it found your server at the right address, knocked, and the server actively said no.
Common signs of this issue
- The browser shows "This site can't be reached" or "refused to connect" with the code ERR_CONNECTION_REFUSED underneath.
- The error appears quickly — within a second or two — rather than after a long spinning wait.
- Other websites load normally on the same device and connection.
- It may affect everyone, or only one person, one office, or one network while everybody else sees the site fine.
- It sometimes starts right after a hosting move, a DNS change, or several failed login attempts.
- The site may work at one address form but not another — with www but not without, or over http but not https.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- First, find out how widespread it is: try the site on your phone using mobile data with wifi off, and run your domain through a free "is it down for everyone or just me" checker. This splits the problem in half — everyone versus just you.
- Try the address four ways: with and without www, and starting with http and https. If one form connects and another is refused, the server is alive but one variant is not set up — a configuration gap, not an outage.
- Ask whether anything moved recently. A new hosting company or a nameserver change can leave your domain pointing at a server that exists but is not yet set up to serve your site — that server answers the knock with a flat no.
- Check your hosting company's status page and your email, including spam. A crashed server, maintenance, and a suspended account are all announced there, and all three produce this exact error.
- If only one person or office sees the error, have them try a different network — a phone hotspot is perfect. If the site loads there, their normal network or security software is doing the blocking.
- Have the affected person turn off any VPN or proxy and pause their antivirus's "web protection" for a minute, then retry — security software that inspects web traffic often refuses connections on a single machine.
- Think about failed logins. Many servers automatically ban an internet address after repeated wrong passwords — and one person mistyping can get a whole office's shared address banned. Ask your host to lift the ban; it takes them moments.
What this usually means
ERR_CONNECTION_REFUSED is a specific kind of failure, and the wording matters. The browser successfully looked up your domain and found the server's address — so this is not a DNS problem — and it reached the machine, so it is not a timeout where nobody answered. The server heard the knock and actively turned the connection away.
If everyone sees the error, the refusal is happening at the server: the web server software has crashed or been stopped, the server's firewall is blocking the web port, the hosting account has been suspended or misconfigured, or — very common after a move — your domain now points at a new server that is not yet set up to serve your site. In all of these cases the conversation belongs with your hosting company — and the question did anything move recently? usually identifies the culprit.
If only some people see it while the site is fine for everyone else, the refusal is happening on their path to you: antivirus or firewall software intercepting the connection, a VPN or proxy in the way, a misbehaving browser extension, or — the sneaky one — the server's own security having banned their internet address, often after repeated failed logins from their network. That version looks alarming but is usually one phone call to your host.
What not to do
- Don't reinstall your website or restore a backup — a refused connection is about the server answering the door, not about your site's files, which are almost always untouched.
- Don't change DNS settings or nameservers to try to fix it. The address lookup already worked; changing it adds a second problem that takes hours to undo.
- Don't buy new hosting in a panic. If the current server is misconfigured or suspended, the same money spent on a support conversation fixes it faster.
- Don't permanently disable antivirus or a firewall just because pausing it made the site load. Add an exception for your site instead.
- Don't keep retrying a login that is failing. If the server's security bans addresses, each retry digs the hole deeper and can lock out everyone in your office.
- Don't assume one complaining visitor means the site is down for the world. Check from a second network before you escalate.
When to get help
If the site is refusing connections for everyone and your host's status page is quiet, that is the moment for a support ticket or a professional — restarting web server software, fixing a firewall rule, or completing a half-finished migration are jobs done on the server itself, which only your host or someone with server access can touch. It is especially worth an hour of expert help if this started after a hosting move: a half-finished migration is quick for someone who has seen it before and maddening to debug by guesswork. If the error only affects one office and switching networks fixes it, you do not need a website professional — you need your host to unban an address, or the office's IT person to add an exception.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
What does ERR_CONNECTION_REFUSED mean?
The browser found your server's address and reached it, but the server actively turned the connection away. It is different from a DNS error, where the address could not be found, and from a timeout, where the server never answered at all.
Is ERR_CONNECTION_REFUSED my fault or the server's?
Check whether everyone sees it. Down for everyone means the server side is refusing — crashed software, a firewall rule, or a suspended account. Only you or your office means the cause is on your side: security software, a VPN, an extension, or your address being banned by the server.
Why does only one person get connection refused on my site?
Their antivirus or firewall is intercepting the connection, a VPN or browser extension is interfering, or the server's security banned their internet address — often after repeated failed logins from their network.
Can failed login attempts cause ERR_CONNECTION_REFUSED?
Yes. Many servers automatically ban an address after several wrong passwords, and offices usually share one address — so one person's typos can lock out the whole building. Your hosting company can lift the ban in minutes once you ask.
What is the difference between connection refused and a timeout?
Refused fails fast — the server answered and said no, which points at a deliberate block or stopped software. A timeout hangs first — the server never answered at all, which points at an overloaded or unreachable server.
Why did ERR_CONNECTION_REFUSED start right after I moved hosts?
Your domain now points at the new server, but that server is not yet configured to serve your site — so it refuses the connection. Either the new host needs to finish setting up the site, or the DNS change went live before the migration was complete.