VPS SSH connection refused

Symptoms

• The SSH client says "connection refused", "connection timed out" or "no route to host".
• You can reach the server from the Client Area console, but not over SSH.
• The SSH login works for one user but not another.

Common causes

• The SSH service is stopped, or is listening on a different port.
• A firewall rule blocks the SSH port.
• The IP address or hostname in the client is wrong.
• The server was rebuilt or reset, and the SSH host key changed.

Safe initial checks

1. Confirm the address from your VPS details in the Client Area.
2. Confirm the port. Use the port set for your server. The default is 22, unless you changed it.
3. Open the console in the Client Area, and check the SSH service status there.

Do not disable the firewall to test. Use the rules that already protect the server.

Step-by-step solutions

1. SSH service stopped. Start the service from the console. See Access and SSH.
2. Wrong port. Set the port in your SSH client to the port the server uses.
3. Firewall blocks SSH. Allow the SSH port in the firewall rules. See Updates and firewall.
4. Host key changed. Stop and verify the new fingerprint through the console or a trusted support channel. Only after confirming an expected rebuild or key rotation should you replace the specific old entry in known_hosts. Never discard the warning blindly.

How to confirm the issue is fixed

• ssh user@your-server-address connects and shows the login prompt.

When to contact support

Contact support if the console shows the SSH service running, the firewall allows the port, and the connection is still refused.

Information to include in a support ticket

• The exact error text from the SSH client, and the port you used.
• The VPS name and the time of the last change.

Related articles

• Access and SSH
• SSH keys and root access
• Updates and firewall
• Server security checklist

Last reviewed

2026-10-28