Technical guide on using the out-of-band HTML5 VNC console in SolusVM 2. Learn to troubleshoot kernel panics, firewall lockouts, and network misconfigurations when SSH is unreachable.
Accessing and Utilizing the Out-of-Band HTML5 VNC Console
The HTML5 VNC Console provides "out-of-band" access to your Virtual Private Server. Unlike SSH, which depends on a functioning operating system, a configured network stack, and an active SSH daemon, the VNC console connects directly to the hypervisor's display output. This is the virtual equivalent of plugging a monitor and keyboard directly into your server.
1. When to Use the VNC Console
You should utilize the VNC console in scenarios where standard remote access (SSH) is unavailable:
- Firewall Lockouts: If you accidentally blocked port 22 or your own IP via
iptablesorufw. - Network Misconfiguration: If a change to
/etc/netplan/or/etc/network/interfaceshas disabled connectivity. - Boot Failures: Diagnosing kernel panics, GRUB errors, or filesystem checks (fsck) during the boot sequence.
- OS Installation: When installing a custom OS via an ISO image.
2. Launching the Console
- Log in to vm.hovixa.com.
- Select your VM and ensure it is in the Running state.
- Click the VNC button located in the top action bar.
- A new browser window will open, initializing an noVNC session.
3. Key Functions within the VNC Interface
The HTML5 console includes specific tools to interact with the guest OS that standard keyboard input may not handle correctly:
- Send Ctrl+Alt+Del: Used to trigger a soft reboot of the guest OS without a hard power cycle.
- Power Controls: Direct access to Reboot and Shutdown signals from the console sidebar.
- On-Screen Keyboard: Useful if your local keyboard layout is interfering with character input (especially during password entry).
4. Troubleshooting Common VNC Issues
| Issue | Diagnostic / Solution |
|---|---|
| Blank/Black Screen | The OS may be in "Screen Save" mode. Press Enter or Space to wake the display. |
| "Failed to connect to server" | Usually a transient network issue or the VM process is hung. Try a Force Stop and Start, then re-open VNC. |
| Keyboard Mismatch | Ensure your local OS keyboard layout matches the language set within the guest Linux OS. |
5. Technical Implementation Details
- Protocol: SolusVM 2 utilizes WebSockets to tunnel RFB (Remote Frame Buffer) traffic through your browser over HTTPS.
- Security: VNC sessions are temporary and tokens expire after a short period of inactivity. This access is independent of your Linux user permissions; you still need your root credentials to log in to the terminal.
- Performance: Because the console transmits frame buffer updates, it may experience lag on high-latency connections. It is intended for text-based CLI troubleshooting, not for desktop environments.
Sysadmin Tip: If you are locked out by a firewall, log in via VNC and run ufw disable or iptables -F to flush all rules and restore SSH access immediately.
