Can't SSH Into Linode: Connection Refused or Timed Out
Workaround available Linux, Cloud Manager Updated November 14, 2026Based on 4 user reportsHow we research
Quick answer
SSH fails when sshd is stopped, another service holds the port, SSH runs on a non-standard port, or a firewall (iptables, UFW, fail2ban) blocks you. Open Lish, check sshd and the firewall rules.
Most likely fix: Check connectivity, then open Lish
How to fix it
Try these in order — the most common fix is first.
1. Check connectivity, then open Lish
- Ping the Linode IP. If ping fails, use the 'Linode unreachable' guide first
- In Cloud Manager open the Linode and click Launch LISH Console (Weblish)
- Log in as root or your user (Lish does not need the network)
Did this fix it?2. Check and restart sshd
- Run sudo systemctl status sshd -l
- If stopped: sudo systemctl restart sshd
- If it will not start: sudo journalctl -u sshd -u ssh
- If the log says 'Address already in use', stop the other service or bind SSH to another port in /etc/ssh/sshd_config
Did this fix it?3. Find a non-standard port
- Run sudo netstat -plntu | grep ssh
- Connect with ssh user@IP -p PORT
Did this fix it?4. Check the firewall
- Run sudo iptables-save and sudo ip6tables-save, or sudo ufw status / sudo firewall-cmd --state
- Make sure incoming TCP on your SSH port is allowed for NEW connections
- Chains starting with f2b or fail2ban mean fail2ban may have banned your IP: unban it from Lish
- Also check any Cloud Firewall attached to the Linode in Cloud Manager
Did this fix it?
Symptoms
ssh: connect to host ... port 22: Connection refused, or the connection hangs and times out, or you get disconnected after a few failed attempts.
Why it happens
- The SSH daemon is not running
- Another service is already using port 22 (Address already in use)
- SSH was moved to a non-standard port
- iptables, UFW or FirewallD does not allow incoming TCP on the SSH port
- fail2ban banned your IP after failed attempts
This guide also covers
- can't ssh into linode
- linode ssh connection refused
- linode ssh connection timed out
- ssh port 22 connection refused linode
Still not working?
If Linode keeps failing, you're not alone. See every Linode problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All not loading, error messages & connection guides →
DigitalOcean Droplet SSH Connection Refused or Timed Out (DigitalOcean)
Vultr SSH Connection Timed Out (Vultr)
EC2 SSH Connection Timed Out (AWS)
Other Linode errors
- Linode SSH Permission Denied (publickey)
- Linode Unreachable After Reboot, Maintenance or Firewall Change
- Linode Lish Console Not Working or Login Fails
- Linode Outbound Email Blocked: Ports 25, 465 and 587
- Linode Out of Memory: OOM Killer Kills MySQL, Apache or Node
- Linode Account Pending, Verification Required or Limit Reached
- Linode Still Charging After Powering Off: You Must Delete It
- How to Cancel Linode (Akamai Cloud) Account and Stop Billing