Can't Connect to a Cloud Server
If you've just started a new cloud server or are starting one up after a shutdown/reboot, it will need a few minutes to start up. Even if it displays the IP address on the website, the cloud server itself may still be starting up.
This means connections and pings may time out or be refused even though you can see the IP address. Give the cloud server 5 minutes or so to start up and then try again.
Note: Make sure you are using the PUBLIC IP of the server and not the PRIVATE IP.
If you are getting a "Connection Timeout", keep in mind that your connectivity is dependent on SSH. That means that your router or firewall/network security policy has to allow SSH, port 22/TCP, outgoing connections.
Please check to be sure port 22 is permitted. Sometimes corporate, school, or public networks have this blocked by default. We can provide an IP White-list by request.
If you can connect using Public Hostname but not Public IP address for your server, try running dig on the public hostname of your server in a terminal application. Check to verify that the IP address it returns matches the public IP address listed in your Cloud Server tab. If it does not match, stop and restart the server, and then run `dig` on the public hostname again. If the IP addresses now match, attempt to connect again.
If you have verified all of the above and are still having issues, feel free to reach out to our Support team at firstname.lastname@example.org!