Hetzner Server Unreachable (SSH Timeout)

How to fix it

// try these in order, the most common fix is first

1. FIX 1Check the status page and lock

   Copy steps
   1. 01Look at status.hetzner.com for your location
   2. 02Run traceroute to the IP; blocked.hetzner.com means the server is locked
   Did this fix it? Yes No

2. FIX 2Check firewalls

   Copy steps
   1. 01In the Console open the server's Firewalls tab and allow TCP 22
   2. 02If you use ufw, check it from the console
   Did this fix it? Yes No

3. FIX 3Use the web console (cloud)

   Copy steps
   1. 01Open the server in the Hetzner Console
   2. 02Click the console icon to get a VNC-style terminal
   3. 03Fix sshd or network settings and reboot
   Did this fix it? Yes No

4. FIX 4Boot the rescue system and fix the network

   Copy steps
   1. 01Enable rescue and power cycle
   2. 02SSH in as root
   3. 03Mount the root partition to /mnt
   4. 04Check the real interface name and edit the network config under /mnt/etc
   5. 05Reboot to leave rescue
   Did this fix it? Yes No

5. FIX 5Ask for KVM on a dedicated server

   Copy steps
   1. 01In Robot open a support request for the server
   2. 02Choose Remote Console and pick a time slot
   Did this fix it? Yes No

Symptoms

SSH times out, ping fails, websites stop loading, often right after a reboot, OS upgrade or firewall change.

Why it happens

• C-01Hetzner Cloud Firewall or ufw/iptables blocks port 22
• C-02Network interface name changed after an OS upgrade or hardware swap
• C-03Wrong netplan or /etc/network/interfaces config
• C-04Server locked by Hetzner abuse team (traceroute ends at blocked.hetzner.com)
• C-05Location network incident

// this guide also covers

• hetzner server not reachable
• hetzner ssh timeout
• hetzner server no network after reboot
• hetzner server down

The 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)
• Can't SSH Into Linode: Connection Refused or Timed Out (Linode)
• EC2 SSH Connection Timed Out (AWS)

Other Hetzner errors

• Hetzner Account Verification Rejected
• Hetzner Cloud Server Currently Unavailable
• Hetzner Server Limit Reached
• Hetzner Rescue System Not Working
• Hetzner Server Locked (Netscan / Abuse)
• Hetzner Port 25 Blocked (Can't Send Email)
• Hetzner Price Increase After Rescale
• Hetzner Charging for a Powered-Off Server