How to setup Secure Shell (SSH) to one of my Servers
Posted by Somnath Kadam on 31 January 2013 06:03 PM


Each Linux based server has Secure Shell (SSH) access once created. You will need the following things in order to setup any of your servers for SSH access:

  • Your server password (learn how to reset your password from your control panel here)
  • Your publicly accessible IP address


Step 1. Log into your Cloud Control Panel using your Username and Password


Step 2. Click on the Network tab


Step 3. Select server you wish to grant remote SSH access to then click on the New rule button


Step 4. Complete the rule creation form specifying your IP range and ports, then click OK

External Address: This is the publically accessible IP. (Used later when accessing server).
Port: 22
Virtual Machine: Select the server (Virtual Machine) you wish the rule to apply.
Source Address: Your publically accessible IP address or “” for any IP.


Step 5. Connect to your server (terminal or Putty), login as root then enter your password


Congratulations, you should now have an established SSH connection to your new server.




  • If you have added / chosen additional storage Data Disks to your server, you will need to mount these from within SSH. This is not done for you.
  • I can see the “login as:” prompt, but do not know username. The default username is “root”. Your password is given when you create a server and you can reset this from your Cloud Control Panel.
  • I can’t connect to via SSH after creating the NAT rule. Please double check you are connecting to the right IP address.
    • You must connect via the External Address (typically 112.x.x.x)
    • and not the internal address which is listed under the server name (typically 172.x.x.x).
    • If this is still not successful, please confirm the correct SSH port 22 is specified in the NAT rule.
  • When entering port 22, I get an error “Port already in use”. This will occur if at any point in time and IP address is already mapped to port 22. Typically, you will get this if you are incorrectly setting up SSH on two or more servers and trying to use port 22. You can randomize the External Address port and map it to the servers default SSH (port 22) or Assign a new IP which will generate a public IP for you to use and bill you accordingly.


(42 vote(s))
Not helpful

Comments (0)