Troubleshooting

Fix the most common VPS problems, and know what to send to support when you need help.

Work through the section that matches your problem. Most issues can be solved from the control panel without contacting support.

I cannot connect

Check that the VPS is online

In List VPS, the Status must be Online. If it is not, start it, see Power controls. Check the status page as well, in case of a wider problem.

Check the IP address and user

Use the IP address shown in the panel (copy it with the copy icon), not an old one. The user is root on Linux and Administrator on Windows Server. See Connect to the VPS.

Check the port

SSH uses port 22 and RDP uses port 3389. If you changed the port of the service, connect to the new port, for example ssh -p 2222 root@203.0.113.256.

Check the password

Permission denied means the password (or key) was refused. If you are not sure of the password, set a new one and restart the VPS.

Check your own network

Some company, school or public networks block outgoing SSH or RDP. Try another network, for example your phone's connection.

Check the firewall

A firewall on the VPS (ufw, Windows Defender Firewall) may be blocking your connection. Use the VNC console to log in and review the rules. For example, ufw status lists the rules, and ufw allow OpenSSH allows SSH.

Use the VNC console

If SSH or RDP still fail, open the VNC console. If you can log in there, the problem is in the network or service configuration. If the console shows a boot problem, use Rescue Mode.

SSH shows a host key warning

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! is expected after you reinstall the OS. Remove the old entry with ssh-keygen -R 203.0.113.256 and connect again. If you did not reinstall the server, do not continue and contact support.

I forgot the password

Set a new one from the panel, you do not need the old one. See Change the VPS password. If you also lost access to the panel, use Forgot Password on the Virtualizor login page, or log in from your billing account with Go to Server.

The VPS does not respond

The server is online but frozen, very slow, or SSH and RDP time out. Try these in order:

  1. Restart from the panel. See Power controls. This is a graceful reboot.
  2. If it does not come back, use Power off, wait a moment, then Start it. Power off is like pulling the plug and can cause data loss, so use it only when Restart has no effect.
  3. Open the VNC console to see what the server shows on screen. Look for a stuck boot, a disk error or a prompt waiting for input.
  4. Check the Overview and Graphs tabs for a full disk, 100% CPU or exhausted memory, see Monitoring.
  5. Contact support with the information listed below.

The disk is full

A full disk can stop services, prevent logins and corrupt data. Check Disk Usage on the Overview tab, then log in and find what takes the space.

df -h
du -sh /* 2>/dev/null | sort -h

The du command lists the size of each top-level folder. Repeat it on the biggest folder, for example du -sh /var/* | sort -h, until you find the cause. The usual suspects are:

  • logs in /var/log. Reduce the systemd journal with:

    journalctl --vacuum-size=200M
  • the package cache: apt clean;

  • old backups, dumps and uploads that you can move off the server;

  • Docker images and containers, if you use Docker: docker system df shows what Docker uses.

If you cannot log in because the disk is full, use the VNC console or Rescue Mode to free some space. If you need more room, you can add extra disk space when you upgrade the service.

RDP problems (Windows Server)

  • Use the IP address from the panel, the user Administrator and the correct password, see Connect to the VPS.
  • If RDP is refused or times out, the VPS may be blocking it. Log in through the VNC console and check that Remote Desktop is enabled and that Windows Defender Firewall allows port 3389.
  • When you reinstall the OS with Windows Server, choose the recipe Allow RDP and PING on Windows Server, so that RDP and ping are allowed from the start.
  • If you restricted RDP to certain IP addresses, remember that your own IP may have changed.
  • If the session is slow or frozen, restart the VPS.

Contact support

If you could not solve the problem, contact support and include:

  • the service name and the IP address of the VPS;
  • the hostname and the operating system;
  • what you were doing, the exact error message and when it started (date, time and timezone);
  • what you already tried, for example a restart or the VNC console;
  • screenshots of the error, the Overview tab or the Tasks And Logs tab.

Never send your passwords or your private SSH key.