The Virtualizor state tells you whether the virtualization platform considers the VPS powered on. It is a starting point for diagnosis, not a complete website or operating-system health check.
IN THIS ARTICLE
What you need before you begin
Have the VPS ID or assigned IP address available. If there is a known maintenance window or provider incident, review that information before issuing power commands that might interfere with recovery.
01 Check whether a Virtualizor VPS is running
- Log in to Virtualizor and open List VPS. Locate the server using its identifier and address.
- Refresh the displayed status. Review the state label and available controls rather than relying only on a coloured icon.
- Open Manage and check for a pending task, suspension or recent operation. A rebuilding or migrating VPS may temporarily refuse other actions.
- If it is stopped and there is no planned reason, review the recent activity before choosing Start. If it is running but inaccessible, open the console to inspect the operating system.
- Test the actual service from a separate client, such as an HTTPS request to the hosted site or an authorized SSH connection.
How do I verify the VPS is actually running?
Compare the panel state, console display and service test. A server can be running while SSH is blocked or the web server is stopped. Conversely, ping may be blocked even though a website responds normally.
Troubleshoot unexpected results
If the panel state remains unknown or a task is stuck, send support the VPS ID, operation and approximate start time. Avoid repeated forced restarts. If the console shows a boot error, record it before changing disks or reinstalling; reinstalling is destructive and is not a routine status repair.