ssh: connect to host port 22: Operation timed out
Your Mac sent the connection request and nothing came back. Something between you and the server is dropping the traffic, or the server is unreachable.
Quick checks
- Check the IP address is current (cloud servers can change IP on restart).
- Try `nc -vz -w 5 host 22`.
- Try another network: some public and office networks block port 22.
Fixes on Mac
Test reachability
ping -c 3 host(some servers block ping, so no reply isn't conclusive).traceroute -n hostto see where packets stop.
Try a different network or port
- If port 22 is blocked on your network, try mobile hotspot, or use a server listening on 443 if you control it.
- Disconnect VPNs that may route the server's address elsewhere.
Fixes on Windows
Same checks
Test-NetConnection host -Port 22in PowerShell shows whether the TCP connection succeeds.
Other devices
Cloud servers
- AWS, GCP, Azure: allow inbound TCP 22 from your IP in the security group or firewall rule.
- Check the instance is running and has a public IP.
Still not working?
If it times out from everywhere, the server is down or its firewall drops port 22. Use the provider's web console to get in and check sshd and the firewall.
See what’s happening
LightAtom's connections view shows the SSH connection stuck in SYN_SENT while it waits, confirming no reply ever arrives.
Frequently asked questions
Why does SSH time out?
No reply to the connection request: a firewall or security group dropping port 22, a wrong or changed IP address, the server being off, or your network blocking outbound SSH.
How do I test if port 22 is open?
From your Mac: nc -vz -w 5 host 22. “succeeded” means the port is reachable; a timeout means something drops it.
Does my Wi-Fi block SSH?
Some public, hotel and office networks block outbound port 22. Try another network to check.