Confirm the VPS ID, notify affected users and avoid interrupting a backup, database migration or package installation. Check that important data is backed up and that console access is available if the server does not boot normally.

1. If the operating system is responsive, use its normal restart method. On a systemd-based Linux VPS, an authorized administrator can run sudo systemctl reboot. On Windows, use the approved Restart action.
2. For a panel restart, open List VPS > Manage and choose Restart. Review the confirmation for the selected server.
3. Submit the operation once and monitor its progress. Do not send repeated restart or power-off requests while the first task is running.
4. Watch the console if startup takes longer than usual. Filesystem checks, updates and application startup can extend the time before a service responds.
5. When the system is available, verify the intended change and check the main application, database and scheduled services.

Confirm the guest uptime has restarted, required services are active and a real customer request succeeds. A green power state alone does not show that the website or mail service has recovered.

If startup fails, capture the console message and inspect recent changes. Escalate a stuck platform operation with the VPS ID and task time. Use a forced power-off only after assessing the data risk and exhausting a normal shutdown; do not reinstall to resolve an unexplained slow boot.

• Gracefully shutting down or forcibly powering off a Virtualizor VPS
• Starting a stopped Virtualizor VPS
• Opening the Virtualizor VNC console
• Checking whether a Virtualizor VPS is running

• Virtualizor: Manage VPS