Troubleshoot issues with SSH connection

SSH connections use port 22. When a connection attempt fails, the most common causes are a blocked port, incorrect credentials, or an OS-level misconfiguration.

Check port 22 availability

Test whether port 22 is reachable using telnet:

telnet <server_IP> 22

A successful response confirms the port is open:

Trying 92.000.000.00...
Connected to 92.000.000.00.
Escape character is '^]'.
SSH-2.0-OpenSSH_7.2 FreeBSD-20161230
Connection closed by foreign host.

Alternatively, use PuTTY: enter the server IP in the Host Name field, confirm the port is set to 22, then click Open.

Verify credentials

If port 22 is open but the SSH client reports an authentication error, the credentials may be incorrect. To retrieve the correct login and password from the Hosting portal:

1. In the Hosting portal, open Products/Services → Virtual private servers.
2. Select the server row, then click Instructions in the toolbar.

3. In the Server information section, find the User and Password fields. Use these credentials to connect.

The Instructions page shows the credentials set when the server was created. If the OS password was changed after provisioning, the updated password won’t appear here.

Access the OS directly

If port 22 is not reachable (telnet returns “Connection refused” or times out), the SSH service may be stopped or misconfigured at the OS level. Access the server console to diagnose the issue:

• Virtual private server — connect via VNC using VMmanager. The VMmanager credentials are listed on the same Instructions page.
• Dedicated server — connect via IPMI using DCImanager. The DCImanager credentials are also in the Instructions page.

If the issue persists after checking all of the above, contact support.