Why does my SSH connection time out?
A timeout usually means the SSH exchange did not complete within the allowed time. It can arise from an unreachable address, filtered port, routing problem or an unresponsive server. Start by testing the exact endpoint rather than changing authentication settings.
Instructions
1. Confirm the assigned endpoint
Check the current server address and SSH port in your authorised service details. A stopped server or an address changed during migration cannot be corrected by a different password.
2. Test the TCP connection from Windows
Replace 22 if the service uses another port.
Test-NetConnection 203.0.113.10 -Port 22 -InformationLevel DetailedRead TcpTestSucceeded, RemoteAddress and SourceAddress. This is a TCP check, not a successful SSH login.
3. Bound the SSH attempt and compare evidence
Use one short diagnostic attempt, then inspect the provider status and server-side listener through a trusted console if it still fails.
ssh -o ConnectTimeout=10 -o ConnectionAttempts=1 adminuser@203.0.113.10These client limits avoid an unnecessarily long wait. They do not bypass a network restriction.
Check the result
- The tested address and port match the current service configuration.
- A subsequent SSH attempt reaches host verification or authentication.
Troubleshooting
- TCP fails from one network only
- Check that network’s outbound rules or VPN routing and the server’s approved source-address allowlist.
- Ping succeeds but SSH times out
- ICMP reachability does not prove that the TCP SSH port is permitted or that sshd is responsive.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.