← Docs / Troubleshooting
My server is unreachable — what to check first
Before anything else, open the browser console from your server's page in the portal. It connects to the machine directly and does not depend on networking inside your server — which is what makes it the useful test.
If the console works
- Check you are testing the right port. Windows does not answer ping and does not run SSH — test 3389, not ICMP and not 22. Linux answers SSH on 22 unless you changed it.
- Check your own firewall. A rule added inside the server, or a changed SSH port, locks you out from the network while the console still works. Fix it from the console.
- Check the service is running. `systemctl status sshd` on Linux. If it is stopped, start it.
Use the port checker to test a TCP service on your own public server. An open port does not prove that authentication or the application works.
A failed ping to a Windows server tells you nothing. It is behaving exactly as designed. Several tickets a month are this and nothing more.
If the console does not work
Reboot from the portal. That is a hardware-level restart and does not need the server to be responsive.
If it is still unreachable after a reboot, open a ticket — at that point it is ours to fix.
What to include if you do open a ticket
- Whether the browser console works
- The IP you are testing, and from where
- What you have already tried
That turns a two-day exchange into one reply.
Still stuck? Open a ticket — tell us what was missing and the article gets fixed.