Check power state
Read the selected VPS power state before inferring anything from an SSH or site outage. Running does not prove guest health.
A Running badge describes VM power, not guest networking or application health. Check only a VPS you are authorised to view; use the console guide to inspect the guest or the boot guide if startup fails.
For VM Start with Managed OS, the customer retains root access and Novasean supplies agreed OS and VM work. Coordinate disruptive power or recovery actions with the responsible operator. Do not assume either entitlement from the presence of a generic Virtualizor documentation screenshot.
Read the actual panel and account state
Sign in through the verified service route, select the correct VPS identifier, and record its reported state and the time. Virtualizor’s end-user list exposes VPS status and available management actions, but a provider may hide or restrict controls. Distinguish Running, Stopped or a transitional state from any billing suspension, lock or network suspension shown in the service account. A suspended service needs provider or billing resolution, not repeated power commands.
If the panel says Running, check a known application endpoint and, if authorised, a console view. A network timeout with an active console points away from simple power state. If the panel says Stopped, identify whether a maintenance window, requested shutdown or provider action explains it before starting.
Choose the next owner by evidence
Running with a responsive console but dead website suggests an application, web service or firewall issue; take the relevant service diagnostic path. Running with a console showing boot failure belongs to the boot-investigation guide. Stopped without an approved reason should be escalated to the accountable operator before a start, especially for managed guests. A panel state that disagrees with recent provider notices or a failed power action needs provider confirmation.
Record the VPS ID, observed state, dashboard timestamp, recent change and exact network symptom. Do not post IP addresses, console screenshots containing secrets or account tokens publicly.
Illustrative branch: Running plus a console login prompt and failed HTTPS points to guest network or application checks. A Stopped panel state needs an approved start decision first.
Verify without repeated power toggles
After the authorised operator resolves the cause, refresh the panel and check the console reaches a login or expected operating-system state. Then test the application from outside the guest. A single successful ping is insufficient: ICMP can be filtered and a running guest may still have broken services. If a state remains transitional, wait for the panel or operator response rather than issuing start and stop in rapid succession.
If a self-managed customer performed an authorised start and it fails, preserve the panel error and move to console boot evidence. If an operation worsens service, tell the operator what was changed and when; do not reinstall to “fix” an uncertain state.
If panel and console disagree, preserve both timestamps and ask the operator to reconcile state before repeating power actions.
Common questions
Does no SSH mean the VPS is off? No. Check panel and console state first.
Can a suspended VPS be restarted? Suspension and power are separate; resolve the account or provider restriction.
Does Running mean the site is healthy? No. Test the guest and application separately.
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.