Choose a power action
Use a graceful guest restart when approved and possible. Forced stop and start needs an operator risk and recovery decision.
A guest reboot asks the OS to stop services; a forced power cycle switches the VM off and on, potentially interrupting writes or requiring application or database recovery. Neither replaces the operating system.
The labels and implementation available in a Virtualizor panel depend on the configured hypervisor and provider controls. For a managed VPS, request the action through the operator unless your agreement grants it. First verify current guest and service state using the related status guide.
Check whether an interruption is acceptable
Record the incident, affected services and current time. Check for active database writes, backups, migrations, maintenance, failover dependencies and users who would be interrupted. Confirm a current recoverable backup and an application restart plan where the service warrants it. A reboot is not a substitute for finding a full disk, failed configuration or account suspension; those causes can recur immediately after startup.
If the application is still responsive, use its documented graceful maintenance procedure before a guest-level action. If the guest is frozen, have the authorised operator assess console state and whether a clean shutdown request can complete.
Use the least disruptive supported action
If the operating system is responsive and a restart is approved, prefer its supported graceful reboot path or the panel’s documented restart action with operator oversight. Watch the state transition and allow the guest to stop and boot. If it fails to respond, a forced stop/start or power-off may be considered by the authorised operator after weighing data integrity and recovery risk. Do not repeatedly press restart or combine panel and in-guest commands while state is changing.
A panel “Power Off” may not mean a graceful guest shutdown in every setup. Confirm the actual semantics for this hypervisor with the provider. If the VPS is stopped for maintenance or suspended, a start command may be inappropriate or rejected.
Illustrative choice: a responsive guest serving database writes should use an approved graceful shutdown path. A frozen console calls for a recorded risk decision before any forced power action.
Check the whole service after startup
Confirm the panel returns to Running, then inspect the console for a completed boot. Check time-sensitive services, application pages, database connectivity and external network reachability. Review logs for unclean shutdown or filesystem recovery only through authorised guest access. If the machine cannot boot, preserve the console error and follow the boot investigation guide; do not leap to reinstall.
If a restart did not repair the original fault, report the before-and-after symptoms and avoid another cycle until the root cause is investigated. Keep the maintenance record and notify affected service owners according to the agreed process.
A successful boot after a power cycle does not prove database integrity; test the application operation that was in progress.
Common questions
Will a reboot erase the VPS? Normally no, but service interruption and unflushed data risk remain.
Is power off the same as reboot? No. It may be a separate, more abrupt action.
Can I restart a managed VPS myself? Follow the actual managed-service authority and panel permissions.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.