This guide helps diagnose common SSH connection problems with a BinaryLane Cloud Server.

If you are setting up SSH for the first time, see:

First, identify the error


The error message helps narrow down the cause:


ErrorUsually means
Connection timed outTraffic is not reaching the SSH service. Check the network path and firewall rules.
Connection refusedThe server is reachable, but SSH is not listening on that port.
Permission denied (publickey)The server was reached, but the username or SSH key was not accepted.
REMOTE HOST IDENTIFICATION HAS CHANGEDThe saved host key differs from the server's current host key, commonly after a rebuild or IP reassignment. Verify before removing the old saved key.


Check the server address and status

Confirm that you are using the correct public IP address or hostname, and that the server is powered on in mPanel.


If you use a hostname, try the public IP address directly. This rules out a DNS issue:


ssh username@YOUR_SERVER_IP

Check from another network

Try connecting from another independent internet connection, such as a mobile hotspot.


Corporate networks, public Wi-Fi, endpoint-security software and local firewalls can block outbound SSH traffic. If SSH works from another network, the issue is local to the original network or device.


For more detail from the SSH client, run:


ssh -vvv username@YOUR_SERVER_IP


Include the output in a support ticket if you need help.


Check the External Firewall


If you have configured the VPS's External Firewall in mPanel, make sure it allows SSH traffic to the server.


A rule allowing SSH commonly uses:

  • Source: your public IP address, or 0.0.0.0/0 if SSH must be available from any IPv4 address
  • Destination: Server Public Addresses
  • Port: 22
  • Protocol: TCP
  • Action: Allow

If you use a final 'block all' rule, an SSH allow rule must appear before it. See External Firewall for details.


Ingress and egress traffic within our networks remain completely unfiltered. We do not impose traffic filtering, shaping or rules beyond those customers configure through the External Firewall for their VPS.


Check the server's own firewall and SSH service


If you can access the server through the mPanel console, check that the SSH service is running and listening on the expected port.


On Ubuntu or Debian:


sudo systemctl status ssh
sudo ss -ltnp | grep ':22'
sudo ufw status


If SSH is configured to use another port, use that port when connecting:


ssh -p PORT username@YOUR_SERVER_IP


The server's own firewall must allow the SSH port. Common firewall tools include UFW, firewalld, nftables and iptables.


If you receive 'Permission denied (publickey)'


This means the connection reached your server, but the supplied key was not accepted.


Check that:

  • You are using the correct username. Many standard Linux installations use root, but custom images or cloud-init configurations may use another user.
  • You are using the private key that matches the public key deployed to the server.
  • You specify the required private-key file if it is not in the default location:

ssh -i /path/to/private_key username@YOUR_SERVER_IP


If you are unsure whether an SSH key was selected during deployment, review your keys at SSH Keys. A key with Default For Future Installations set to Yes is automatically pre-selected for new Cloud Server installations.


This setting does not add the key to servers that already exist. If the key was not selected when the server was deployed or rebuilt, it will not be installed automatically.


For setup guidance, see Set a default SSH key for all new Cloud Server installations.


If the connection still fails


Submit a support ticket with:


  • The server's public IP address
  • Your approximate location and internet provider
  • Whether SSH works from another network
  • The exact error message
  • Output from ssh -vvv username@YOUR_SERVER_IP


Do not include private keys, passwords or other credentials.