Day-to-day, most VPS management happens over SSH inside the server itself. Virtualizor’s panel matters most for the moments SSH doesn’t work, or when you need control at a level the guest OS can’t provide on its own.
Basic power controls
From VPS > Manage VPS, selecting a specific VM gives you Start, Stop, and Restart buttons. These act at the hypervisor level — equivalent to pulling power on a physical machine (Stop) or pressing the reset button (Restart) — which matters because they work even if the OS inside is completely frozen or misconfigured.
Graceful vs forced reboot
Where possible, reboot from inside the OS itself over SSH (reboot) so running services and the filesystem shut down cleanly. Reserve Virtualizor’s Restart button for when the VM is genuinely unresponsive to SSH — a forced restart is equivalent to cutting power, which carries a small risk of filesystem inconsistency if something was mid-write.
Console access (VNC)
The VNC console shown in Virtualizor gives you exactly what a monitor plugged into the machine would show — boot messages, a login prompt, kernel panics — independent of whether the network stack inside the VM is even working. This is the tool to reach for when you’ve locked yourself out via a bad firewall rule or broken network config, since SSH itself depends on that same network stack being functional.
Checking resource usage
The VM’s management page also typically shows current CPU, RAM and bandwidth usage at a glance — useful for a quick health check without needing to SSH in and run top yourself.
When to use each tool
- SSH reboot — routine maintenance, planned restarts.
- Virtualizor Restart — SSH unresponsive, but you just need it back online quickly.
- VNC console — diagnosing why it won’t come back, or fixing a network-level lockout.