If you cannot reach a server, the cause is nearly always one of four things. Check them in this order and you will usually find it in a minute.
1. Does the server have a public address?
A server on a private network has no route from the internet. Open Cloud Servers and look for a Floating IP on the server. If there is none, add one by following Give your server a public address.
2. Is the port open?
A fresh server allows very little inbound traffic. Even with a public address, the browser or SSH client cannot get in until the port is open in a security group attached to the server. Open the port you need using How to open a port on your server. Remember that web traffic needs 80 and 443, and SSH needs 22.
3. Is the server actually running?
Open Cloud Servers and check the status. It should read Active. If it shows Shutoff, start it from the server's actions menu and give it a minute to boot.
4. Are you looking at the right region?
Your resources live in one region, either Nairobi, Kigali or Huye. If the server list looks empty or the server is missing, switch to the region it was created in.
If all four check out and it still will not connect, the problem is usually inside the server: the web server or application is not running, or it is listening on a different port than the one you opened. Log in over SSH (see How to connect to your Cloud Server) and check the service. If you are still stuck, contact support with the server name and region.