My VPS Is Unreachable: Troubleshooting Steps Print

  • 0

If you cannot reach your VPS over SSH or your website is down, work through these steps in order. Most "server down" cases turn out to be configuration issues inside the server that you can fix yourself in minutes.

Step 1: Check the DoRoyal Status Page

Visit status.doroyal.com. If there is an active incident affecting your node, we are already on it; no ticket needed.

Step 2: Check Power State in the King Panel

Log in to the King Panel and confirm your VPS is running. If it is stopped, boot it. If it shows an error state, note the message and skip to Step 6.

Step 3: Test Basic Connectivity

From your local machine:

ping YOUR_SERVER_IP
  • Ping replies, SSH fails: the server is up; the problem is the SSH service or a firewall rule. Go to Step 4.
  • No ping replies: could be the server, the network, or ICMP being blocked by your own firewall rules. Continue to Step 4 either way.

Step 4: Use the VNC Console

Open the Console in the King Panel. This connects directly to the server's screen, bypassing the network entirely.

  • Console shows a login prompt: the server is running fine. Your issue is network configuration inside the OS; log in on the console and check:
    systemctl status sshd        # is SSH running?
    ufw status                    # firewall blocking port 22?
    ip addr                       # correct IP configured?
  • Console shows a boot error / kernel panic: your OS is failing to boot. You can attempt recovery from the boot menu, or reinstall the OS (see How to Reinstall Your VPS Operating System).
  • Console is blank or will not connect: go to Step 6.

Step 5: Common Self-Inflicted Causes

  • Firewall lockout: a UFW/firewalld/iptables rule blocking SSH. Fix from the console.
  • fail2ban banned your own IP: from the console:
    fail2ban-client unban YOUR_HOME_IP
  • SSH config error: a typo in /etc/ssh/sshd_config stops SSH from starting. Check journalctl -u sshd from the console.
  • Out of disk space or memory: services crash or the server hangs. Check df -h and free -m from the console.
  • Website down but SSH works: not a connectivity issue; check your web server and application logs.

Step 6: When to Open a Ticket

Contact us via a support ticket when the evidence points to hardware or network, which is covered under your unmanaged plan:

  • The King Panel shows an error state or actions (boot/reboot) fail
  • The VNC console will not connect at all
  • The console works but the server has no network route to the internet despite correct OS configuration
  • status.doroyal.com shows an incident on your node

In your ticket, include: your VPS hostname/IP, what you tried from this guide, and what you saw in the console. This lets us skip the basics and dig in immediately.


Was this answer helpful?

« Back