When the console helps
The console can show whether the guest reaches a login prompt when SSH fails. Check the correct VPS and power state first; the screen alone does not identify the cause.
Use the console during boot or when SSH, Remote Desktop or a firewall change blocks remote access. Have the correct VPS ID and authorised guest login ready; keep passwords and secret-bearing screenshots out of messages. A console view does not repair the guest.
Open and inspect
- Sign in through your service's authorised VPS management link and select the correct VPS.
- Confirm its power state. Open the VNC or console action and launch the browser client if available.
- Read the screen before restarting. A login prompt suggests the guest booted; a boot error, full disk or emergency shell points to a guest problem. Record the exact visible message and time.
- If keyboard input behaves unexpectedly, check the console's keymap before changing passwords or configuration.
Illustrative check: the panel says Running and the console shows a normal login prompt, but SSH times out. Record that split result; investigate the guest network or SSH path before changing power state.
Read the console before changing state
| Console view | Possible implication | First safe action |
|---|---|---|
| Normal login prompt | Guest booted; network or login service may be the issue | Check IP configuration and SSH/RDP service from an authorised account. |
| Emergency mode or filesystem error | Guest boot or disk problem | Capture the exact text and check recovery options and backup. |
| Black screen while panel says running | Boot delay, display or platform problem | Wait briefly, refresh once, then record panel state for support. |
| Installer screen | Boot order or attached ISO may have changed | Do not continue an install until the intended image is confirmed. |
A guest firewall cannot normally block the out-of-band console, so a working console with failed SSH points investigation towards guest networking or the SSH service. A console that cannot open at all warrants a panel or host-side check.
An installer screen is a stop condition: confirm boot order and attached media with the operator before pressing a key that could start installation.
Narrow the fault
If the console works but SSH does not, check the guest's IP configuration, SSH service and guest firewall from an authorised account. If there is no console image, verify the VPS is powered on and allow for boot time. Repeated forced restarts may worsen filesystem damage. Capture the panel state and error text before asking support to inspect host-side availability.
Responsibility
For an unmanaged VPS, the customer administers the guest operating system, accounts and applications. Novasean can investigate the hosting platform and console availability. Managed-service responsibilities depend on the agreed schedule; a console symptom alone does not establish that a guest fault is a host fault. Include the VPS identifier, time, observed screen and steps already attempted in a ticket.
Close the session safely
Use the smallest necessary intervention. Avoid pasting passwords into browser consoles where session recording or clipboard history is unknown. After diagnosis, log out of the guest and close the VNC tab. If you changed the guest firewall to regain access, document the rule and verify normal remote access from a trusted network. Ask support before a hard power-off when the guest may be writing data.
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.