Skip to content

Diagnose SSH timeout, refused connection, and permission denied

Separate a network problem from authentication or a changed server identity.

Protect your data firstKeep a current off-server backup before reinstalling, updating, changing firewall rules, or running an application installer.
On this page

Identify the error

Timeout usually points to reachability, routing, filtering, or an unresponsive server. Connection refused means the endpoint responded but nothing accepted that port. Permission denied means the SSH connection reached authentication, but the login was rejected.

Check without changing the VPS

Confirm the service is running, use its current IP and configured SSH port, and check the username and selected key. From PowerShell on your own Windows computer, replace the example IP:

Test-NetConnection -ComputerName 203.0.113.10 -Port 22

This tests TCP access; it does not verify your password or grant access. A nonstandard SSH port must replace 22.

Host-key warnings

An unexpected host-key change can indicate the wrong server or interception. Verify the fingerprint through a trusted console or support channel before accepting it. Do not turn off host verification or remove known-host entries merely to silence the warning.

Was this not enough?Include the service number, exact error, and time of the problem. Never send a password or private key.
Contact support