You have typed your command, hit Enter, expecting to connect to your server. Instead, you’re greeted with the frustrating SSH Connection Refused error rather than a welcoming shell prompt.
ssh: connect to host your-server port 22: Connection refused
That flat, unhelpful line is one of the most frustrating messages in server management. No explanation. No suggested fix. Just a door slammed in your face.
I have been there more times than I’d like to admit, particularly after spinning up new VPS instances where I’d forgotten to note the custom SSH port, or after a firewall rule I applied broader than intended cut off my own access.
The good news: SSH Connection Refused is almost always fixable in minutes once you know what to check. This guide walks through every real cause I have encountered in practice, with the exact commands that diagnose and resolve each one.
What this guide covers: the meaning behind the error, causes, step-by-step fixes, a prevention checklist, and the FAQs I actually hear from developers.
Who it’s for: anyone managing a Linux server, whether it’s your first VPS or your hundredth.
TL;DR
- SSH Connection Refused means the server is actively rejecting your connection attempt
- The most common causes: wrong port, service not running, firewall blocking, wrong credentials, and SSH not installed
- Most fixes take under 5 minutes from your terminal
- Always verify the fix by attempting to reconnect before assuming the problem is solved
- Prevention: use non-default ports, configure fail2ban, and restrict SSH to specific IPs
What Does “SSH Connection Refused” Actually Mean?
Let’s be precise, because understanding the mechanics changes how you debug.
“Connection Refused” is TCP’s way of saying: I heard you, but I’m not accepting this connection. The server received your SYN packet, processed it, and sent back a RST (reset) flag. This is fundamentally different from a timeout (where the server never responds at all) or an authentication failure (where the server accepts the connection but rejects your credentials).
In SSH terms, this means the SSH daemon, sshd , either isn’t listening on the port you are targeting, isn’t running at all, or something network-level is intercepting the request before it reaches the daemon.
The practical difference matters: if you see “Connection Refused”, you at least know the server is reachable over the network. That’s useful diagnostic information.
If you want to learn more about how SSH works internally, including its configuration options and authentication process, the official OpenSSH documentation provides detailed explanations.
How to Diagnose SSH Connection Refused
Before fixing anything, verify. The most common mistake I see is jumping to conclusions, changing the SSH port when the problem was the firewall, or reinstalling SSH when the service just needed a restart.
Here’s the diagnostic sequence I follow, in order:
Step 1: Confirm the server is reachable at all
ping -c 3 your-server-ip
If ping fails, you have a network connectivity issue, possibly the server is down, or it’s on an unreachable network. That’s a different problem than Connection Refused.
Step 2: Check if the SSH port is reachable
nc -zv your-server-ip 22
# or if the port is non-standard:
nc -zv your-server-ip 2222
If this shows “Connection refused”, you have confirmation the problem is at the SSH layer.
Step 3: Use SSH verbose mode for more detail
ssh -v username@your-server-ip -p PORT
The -v flag (use -vvv for maximum verbosity) shows exactly where the connection attempt stalls.
This alone often points you directly to the problem.
Read Full Article: https://serveravatar.com/ssh-connection-refused
Top comments (0)