The server state in SolusVM indicates the virtualization platform state. A running VPS can still have a broken network, stopped web service or full filesystem, so use the panel state alongside a console and application check.
IN THIS ARTICLE
What you need before you begin
Identify the correct project and VPS ID. Review scheduled maintenance and any current service notice. If another administrator is installing, restoring or migrating the server, coordinate with them before starting a competing operation.
01 Check the power state of a SolusVM VPS
- Open your SolusVM project and select the server. In an older panel, choose the VPS from the server list.
- Refresh the server overview and read its state. Distinguish stopped, running, suspended and an operation in progress.
- Check the server task history where exposed. A pending rebuild or migration can make normal controls unavailable temporarily.
- For a stopped server, establish why it stopped before using the power-on control. For a running but unreachable server, open the VNC console and inspect the guest.
- Test the actual service, such as an HTTPS request to the website or an authorized SSH connection. Ping alone is inconclusive because guest or network rules can block it.
02 Example: the panel says running but the website is offline
Suppose SolusVM shows Running, but the website does not respond. That result confirms a powered virtual machine, not a healthy web service.
- Open the assigned console. A login prompt indicates that the guest has booted far enough to offer local access.
- Check the guest network and web-service status through your authorized administrator session.
- Test the website from a second network and record the HTTP error or connection failure.
If the console instead shows a boot or filesystem error, capture that message for recovery. If the guest works locally but no external service can connect, investigate the assigned addresses, routes and firewall path. These observations identify the failing layer without guessing that a reinstall is required.
How do I check the actual VPS power state?
Compare the refreshed power state with the console and service test. Record whether the failure is at the platform, boot, network or application layer; this makes the next troubleshooting step much clearer.
Troubleshoot unexpected results
If a state stays unknown or a task does not finish, send support the VPS ID and task details. Avoid repeated forced power operations. If the console shows a boot error, capture the text before making changes. Reinstalling destroys the old system and is not a routine way to correct a status indicator.