Skip to main content
“Connection timed out” means your SSH client got no answer at all from that IP and port. The server is off or not booted, the IP is wrong, a firewall silently drops the traffic, the server’s network settings are broken, or your own network blocks the port. Check the server’s status in the VPS Panel, test the port with nc -vz -w 5 203.0.113.10 22, then fix the firewall or network from the VNC console.
On macOS the same problem reads Operation timed out.

​
Before you start

  • A timeout gives no clue on its own. Work through the causes in order: the first ones take seconds to rule out.
  • For fixes inside the server, use the VNC console on a VPS. On a dedicated server, open a ticket for KVM/IPMI access.
  • If the message says Connection refused instead, see SSH connection refused.
  • Commands use sudo. As root, leave it out.

​
Cause 1: The server is off, stuck or still booting

Check: open your server in the VPS Panel and look at its status. Then open the VNC console: a login prompt means the system is up; a boot error or a blank screen means it isn’t. Fix: boot or restart the server. If it stops at an error, see Linux server won’t boot.

​
Cause 2: Wrong IP address or port

Check: compare the IP in your command with the one on your server page. If you connect by domain, see which IP it resolves to:
Fix: connect by IP, and add -p if you changed the SSH port:

​
Cause 3: A firewall drops SSH

A firewall decides which network connections reach your server. A rule that drops traffic causes a timeout. UFW’s default policy drops everything you haven’t allowed, so ufw enable without an SSH rule gives exactly this error. Check on the console:
Your SSH port (22/tcp, OpenSSH or your custom port) must be listed as ALLOW IN.
Fix: allow SSH:
If you use our Firewall panel, check that its rules allow your SSH port too. Full recovery steps are in locked out after a firewall change.

​
Cause 4: The server’s network settings are broken

After an edit to Netplan, NetworkManager or /etc/network/interfaces, the server may have no working IP or route. Then nothing reaches it: not SSH, not ping, not your website. Check on the console:
You should see your public IP on the network interface (for example eth0 or ens3) and a default via route. If either is missing, or the ping fails, the network is down. Fix: undo your last change and apply it again (sudo netplan apply on Ubuntu, sudo nmcli connection up "System eth0" on AlmaLinux/Rocky; your connection name may differ). Compare your settings with the network settings in the panel and see configure a static IP with Netplan.

​
Cause 5: Your own network blocks the port

Office, school, hotel and some public Wi-Fi networks block outgoing SSH, especially on ports other than 22. Check from your computer:
Fix: try the same command from another network, such as your phone’s hotspot. If it works there, your local network is the block. Ask its administrator, or use a different network.

​
How to check it worked

debug1: Connection established. means the network path is open. Any error after that is about the login, not the connection.

​
Frequently asked questions

​
Ping works but SSH times out. Why?

The server is online, so a firewall drops the SSH port, or SSH listens on another port. Check Cause 3 and sudo ss -tlnp on the console.

​
Ping doesn’t work but the server is fine. Is that a problem?

Not necessarily. Some firewalls block ping (ICMP). Test the SSH port itself with nc or Test-NetConnection instead.

​
SSH times out only sometimes. What does that mean?

Intermittent timeouts point to packet loss or an overloaded server. Run mtr to your server and check its load with htop.

VPS and dedicated server guides

Every guide in this section.

Locked out after a firewall change

Recover from a rule that blocks SSH.

Check if a port is open from outside

Test any port from the internet.

Diagnose network latency

Find packet loss and slow routes.

SSH connection refused

When the server answers “no”.
Checked against the official OpenSSH ssh manual, Ubuntu’s firewall documentation and Microsoft’s Test-NetConnection reference on 4 November 2026; the ssh and nc timeout messages and the UFW rule (dry run) were tested on Ubuntu 24.04 LTS. The firewalld, NetworkManager and Windows commands were not tested.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to upgrade your hosting? Use code KB20 at checkout for 20% off your first order!
Last Updated: November 2026