Vultr SSH Connection Timed Out

How to fix it

Try these in order — the most common fix is first.

1. 1. Check the Vultr Firewall group

   Copy steps
   1. Open the instance in the Vultr Console
   2. Check whether a Firewall Group is attached
   3. Add an inbound rule for TCP port 22 (or temporarily unlink the group to test)
   Did this fix it? Yes No

2. 2. Use View Console to inspect the server

   Copy steps
   1. Click View Console on the instance
   2. Run: systemctl status ssh (or sshd)
   3. Check the listening port: ss -tlnp | grep ssh
   4. Check ufw status and iptables -L and allow SSH
   Did this fix it? Yes No

3. 3. Confirm IP and port

   Copy steps
   1. Copy the main IP from the instance page
   2. If you changed the port in /etc/ssh/sshd_config use ssh -p PORT user@IP
   Did this fix it? Yes No

Symptoms

ssh user@IP hangs and ends with 'Connection timed out'.

Why it happens

• Instance is linked to a Vultr Firewall group that does not allow port 22
• UFW or iptables on the server denies port 22
• sshd listens on a custom port
• Wrong IP or the instance is not running

This guide also covers

• vultr ssh connection timed out
• vultr can't ssh
• vultr ssh not working

The same problem in other apps

All not loading, error messages & connection guides →

• DigitalOcean Droplet SSH Connection Refused or Timed Out (DigitalOcean)
• Can't SSH Into Linode: Connection Refused or Timed Out (Linode)
• EC2 SSH Connection Timed Out (AWS)

Other Vultr errors

• Vultr SSH Permission Denied
• Vultr Firewall Blocking Connections
• Vultr Server Stuck Pending or Installing
• Vultr Account Suspended or Needs Verification
• Vultr SMTP Port 25 Blocked
• Vultr Still Charging After Stopping Server
• Vultr Server Null Routed (DDoS)
• How to Cancel Vultr Account and Stop Billing