Restarting a VPS interrupts its workload and starts the guest operating system again. Use it for an identified maintenance or recovery need, and check whether restarting just one failed application service would be sufficient.
IN THIS ARTICLE
What you need before you begin
Confirm the project and server ID, notify affected users and review running backups, database work and system updates. Keep console access available and ensure recent important data has an independent backup.
01 Restart a SolusVM VPS safely
- For a responsive guest, use its normal operating-system restart. On a systemd-based Linux server, an authorized administrator can run
sudo systemctl reboot. - When using SolusVM, open the server overview and choose its restart or reboot action. Read the confirmation for the selected VPS.
- Submit the request once and monitor the task. Avoid issuing additional power commands while a restart is still in progress.
- If remote access does not return promptly, inspect the VNC console. Updates or filesystem checks can take longer than an ordinary boot, so use the displayed progress rather than a fixed timeout alone.
- After startup, verify networking and the application that motivated the restart. Check relevant logs for a recurring fault.
02 Example: record the result of a maintenance restart
For a planned web-server restart, record the VPS ID, maintenance start time and the service that should recover. After the guest boots, check the website, database connection and any worker that processes background jobs.
| Check | Expected result |
|---|---|
| Guest startup | A fresh uptime and no unresolved boot error in the console. |
| Website | A real page or health endpoint responds over the intended HTTPS hostname. |
| Background processing | A controlled test job completes and is not duplicated. |
If the same application error returns immediately, record the new log event and investigate its cause. Repeating the VPS restart does not explain why the application fails.
How do I confirm the VPS restarted successfully?
Confirm the guest has a new uptime and that a real application request succeeds. Review services configured to start automatically, particularly databases, web servers and scheduled workers.
Troubleshoot unexpected results
If the console shows a boot failure, preserve the message and assess the latest change. A stuck platform task should be reported with the VPS ID and time. Do not repeatedly force a restart or reinstall the operating system just because the panel shows the VPS running while the application remains unavailable.