The VNC console provides access to the virtual display and keyboard. It is useful when a guest firewall, network configuration or boot problem prevents SSH or Remote Desktop from working.
IN THIS ARTICLE
What you need before you begin
Use the trusted HTTPS panel and confirm the VPS ID. Keep the guest login credentials available: opening a console does not bypass the operating system login. Console availability depends on the virtualization type and the features enabled for your service.
01 Open the Virtualizor VNC console
- Open List VPS > Manage for the affected server.
- Select VNC and open the browser-based HTML5 console offered by the panel. Allow a popup only for the verified panel site if your browser blocks it.
- Check the displayed boot or login screen before typing. Click inside the console to focus the keyboard, and check its keyboard layout if special characters appear incorrectly.
- Sign in using an authorized operating-system account. For network troubleshooting, begin with read-only checks of addresses, routes and service status before changing configuration.
- Close the console when finished. Do not share console URLs or connection credentials, which can expose privileged access.
How do I test Virtualizor console access?
Confirm keystrokes reach the intended guest and that you can see its state independently of guest networking. After fixing a network issue, test the normal SSH or Remote Desktop connection from a separate client.
Troubleshoot unexpected results
If the console is blank, refresh it once and check the VPS power state. If connection fails, check browser popup restrictions and report the error to support. Use the current HTML5 client; do not install obsolete Java browser plugins or weaken browser security to revive an old console tutorial.