Open the VPS control panel from your server’s page in the client area and use its Reboot button. If you can still log in by SSH, run sudo reboot instead, because it shuts your services down cleanly.
From the VPS control panel
- Sign in to the client area, open Services and click the VPS.
- Open the VPS control panel linked from the service page.
- Click Reboot (some panels say Restart) and confirm.
- Wait a minute or two, then reconnect. To watch the server start, open the VNC console in the same panel.
From the command line
If the server still responds, connect by SSH and run sudo reboot (or just reboot as root). This gives databases and other services time to close properly, which a panel reboot may not.
Reboot, power off or stop?
If the panel also offers Power off or Stop, that cuts the server off like pulling the plug. Use it only when a normal reboot doesn’t respond, and remember to press Start afterwards.
Managed cPanel VPS
Reboot from WHM: open System Reboot and choose Graceful Server Reboot. If the server doesn’t come back within a few minutes, open a ticket.
Still not responding after a reboot?
- Open the VNC console in the VPS control panel and read the last messages on screen. A full disk, a disk check in progress or a broken configuration file are common causes.
- If the disk is full, log in on the console and free space with
df -hto find it, then delete old logs or backups. - If the console is blank or the panel shows an error, open a ticket and say the server is down for everyone, so it is treated as critical.
If you find yourself rebooting often, the server is probably running out of memory. Check with free -h. Upgrading a KVM VPS happens in place, so your data stays put.
Still stuck? Open a support ticket or message us on WhatsApp +263 73 563 9917, Monday to Friday, 08:00–17:00 CAT.
Updated 6 November 2026. Something here out of date? Tell us.