The power-on action starts an existing VPS from its configured boot device. It is appropriate when the server is intentionally or unexpectedly stopped and you have confirmed that starting it is safe.
IN THIS ARTICLE
What you need before you begin
Check the reason for the stopped state, any ongoing maintenance and the server ID. A suspended account or compute resource in maintenance mode may restrict power actions until the administrator resolves that condition.
01 Start a stopped VPS in SolusVM
- Open the correct project and VPS in SolusVM. In a legacy interface, select the server from its VPS list.
- Refresh the state and check for pending tasks. If it already runs, investigate the console or application rather than submitting a duplicate start.
- Select the power-on or Start action; older SolusVM interfaces may label it Boot. Confirm the intended VPS.
- Monitor the task and open the console to observe startup. Check that it is booting from the normal system disk unless a rescue or ISO boot was deliberately configured.
- Once the operating system is ready, test its network and important services. Restore traffic or scheduled work only after those checks succeed.
How do I confirm a started VPS is usable?
Confirm a normal guest login and a real application request. Review startup logs for storage, network or service failures. The panel changing to running is only one part of the check.
Troubleshoot unexpected results
If the start operation fails, save the exact platform message and contact support with the VPS ID. If the guest enters an installer, stop before accepting disk-format prompts and correct the boot mode. Do not delete and recreate the VPS as a response to an unexplained start error when you need its existing data.