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.

1. Log in to Virtualizor and open List VPS. Locate the server using its identifier and address.
2. Refresh the displayed status. Review the state label and available controls rather than relying only on a coloured icon.
3. Open Manage and check for a pending task, suspension or recent operation. A rebuilding or migrating VPS may temporarily refuse other actions.
4. 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.
5. Test the actual service from a separate client, such as an HTTPS request to the hosted site or an authorized SSH connection.

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.

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.

• Checking RAM, storage, IP addresses and virtualization in Virtualizor
• Restarting a Virtualizor VPS safely
• Starting a stopped Virtualizor VPS
• Opening the Virtualizor VNC console

• Virtualizor: List VPS
• Virtualizor: Manage VPS