The SolusVM VNC console shows the virtual screen even when the guest network is misconfigured. It can help diagnose boot problems, firewall mistakes or an installation that needs keyboard input.
IN THIS ARTICLE
What you need before you begin
Use the trusted HTTPS management panel and identify the VPS. Have an authorized guest login ready. Console permission depends on account role and service state; opening a console does not bypass the guest login screen.
01 Use the SolusVM browser console for VPS recovery
- Open the server inside its project and select the VNC or console control.
- Use the current browser-based console supplied by the panel. Allow a popup only for the trusted panel hostname if required. Do not install an obsolete Java browser plugin.
- Read the screen before typing. If it is a login prompt, sign in using the operating-system account, not the panel email and password.
- For a network fault, begin with read-only checks of interface addresses, routes and service status. Record the original configuration before editing it.
- After repair, test the normal SSH or Remote Desktop route from another client and then close the console session.
02 Example: interpret what the recovery console shows
| Observation | What to check next |
|---|---|
| The guest login prompt is visible, but SSH fails | Sign in with an authorized guest account, then inspect networking, SSH service state and access rules. |
| The screen reports a boot or filesystem error | Capture the exact message and recent storage changes before starting a recovery procedure. |
| The browser cannot connect to the console itself | Check panel permissions, VPS power and pending platform tasks; this is different from a guest password failure. |
Verify the server ID before typing. If a normal remote connection works after repair, test it from a fresh client session before closing the console. Do not share the temporary console URL in a public message or screenshot.
How do I verify console access works?
Confirm keyboard input reaches the correct VPS and the screen reflects the expected guest. A working console with failed SSH usually points toward a guest service, firewall, authentication or networking issue rather than complete loss of the VM.
Troubleshoot unexpected results
If the console cannot connect, check the server power state, panel permissions and any running task. If the screen is blank, try one reconnection and inspect the boot state before restarting. Send support the console error and VPS ID; never publish a console URL or expose raw VNC access as a workaround.