Access your VPS with the Virtualizor VNC console

The VNC console shows your VPS screen as if a monitor were plugged in. It works even when the network inside the VPS is broken, the firewall blocks SSH, or the server is stuck during boot. It is the most important rescue tool in Virtualizor.

Before you start

• Access to the Virtualizor panel.
• VNC is available on KVM virtual servers. OpenVZ containers use a different console method.
• Your VPS root (or Windows Administrator) password, because the console shows the normal login prompt.

Open the browser console

1. Log in to Virtualizor and open your VPS.
2. Click VNC (or Console / HTML5 VNC).
3. A new window opens with the noVNC console. Click inside it to give it keyboard focus.
4. Press Enter if the screen is black; a sleeping console wakes up.
5. Log in as root with your password.

The keyboard layout in VNC is US by default. If special characters in your password do not work, use the noVNC side panel to send text, or temporarily set a simpler password through the panel.

Use an external VNC client

1. On the VNC page, note the VNC IP, Port and Password.
2. Open a VNC viewer such as TightVNC, RealVNC or TigerVNC.
3. Connect to vnc-ip:port and enter the VNC password.

External clients can be smoother for long sessions, but your network must allow the VNC port. The browser console works over HTTPS and is easier.

Change the VNC password

Go to the VPS Settings and choose VNC Password (or Change VNC Password). Set a new password and save. The change applies after the VPS is restarted on some versions.

Send special keys

The noVNC toolbar has buttons for Ctrl+Alt+Del (needed to log in to Windows) and other key combinations that your own computer would intercept.

Common rescue tasks in VNC

• Fix a firewall that locked you out: run ufw disable or systemctl stop firewalld, then correct your rules.
• Fix network configuration: edit /etc/netplan/*.yaml (Ubuntu) or the NetworkManager profile, then restart networking.
• Unban your IP from Fail2Ban: fail2ban-client unban YOUR.IP.
• Watch boot errors: restart the VPS with the console open to read messages.

Troubleshooting

• Console window is blank or says "Failed to connect": the VPS may be stopped – start it first. Browser extensions or a corporate proxy can block the WebSocket connection; try a private window or another network.
• Keyboard does not respond: click inside the console. Some layouts mis-map keys; type the password in the clipboard/text panel.
• Login incorrect: Linux does not show characters while you type the password. Reset the root password from the panel if needed.
• VNC button missing: your provider disabled it or the VPS is not KVM. Contact support.

Next steps

• Recover a VPS with rescue mode.
• Reset the root password.
• Power controls in Virtualizor.