Can't connect to your server

If RDP or SSH suddenly stops working or your service isn't responding, go through the checks below in order. Most problems are solved within steps 1–5.

1. Is the server running?

Check the server status badge in your Dashboard.

Stopped → Click the Start (▶) button on the server details page.
Creating → The server is being prepared. Check again in a moment.
Error → Contact technical support.

2. Has the expiry date passed?

Check the expiry date card on the server details page. Expired servers may be stopped. Renewing your server

3. Does it say "Server not responding"?

If you see a "Server not responding" warning on the server details page, the server is on but isn't responding from outside.

A program inside the server may have frozen, the memory may be full, or the firewall settings may have changed.
Try steps 4–5 below.

4. Try rebooting

Click the Reboot (↺) button on the server details page, wait 1–3 minutes, then try connecting again. Running out of memory and frozen programs are mostly fixed by a reboot.

5. Check directly with the browser console (VNC)

Even when RDP/SSH doesn't work, the console takes you straight to the server's screen. Browser console guide

Things to check in the console:

Does the login screen appear normally? If it does, the server is alive, and the problem is most likely on the network/firewall side.
Have you changed the firewall recently? On Linux, log in to the console and reopen SSH with sudo ufw allow 22/tcp. Opening firewall ports
Is the disk full? On Linux, check with df -h. If usage is at 100%, clean up log files and the like.

6. Is it slow, or does it disconnect often?

If you see a "Speed limited" badge on your Dashboard, you've used up today's traffic. Buying more traffic
Your server's specs may not be enough. On Linux, check CPU and memory usage with htop (if it's not installed, sudo apt install -y htop).

7. Check for a service-wide outage

The problem may not be limited to your server. Check the service status page for any current outages.

If it still doesn't work

Server name and the time the problem started
Which steps above you tried and what happened (e.g., "Rebooted; the console shows the login screen")