The VNC console in your VPS control panel shows the server’s screen, as if a monitor and keyboard were plugged into it. It works independently of the network inside your VPS, so you can log in even when SSH is down, the firewall blocks you, or the network configuration is broken. It’s the most important recovery tool you have.

When to use it

Situation Why VNC helps
Firewall rule blocked SSH (UFW, iptables, nftables) Log in locally and fix the rule
SSH config error (sshd won’t start, wrong port, keys only but key lost) Edit sshd_config from the console
Network misconfiguration (netplan, interfaces, wrong IP) Fix the config while offline
Server won’t boot fully (fstab error, failed disk mount) Watch boot messages, enter maintenance mode
Windows: RDP disabled or blocked Log in via the console and re-enable RDP
Watching an OS reinstall or boot See what’s happening

Open the console

  1. Log in to the client area, and open your VPS’s control panel.
  2. Choose VNC (or “Console”). It opens in the browser (HTML5/noVNC), or shows connection details for a VNC client.
  3. Click into the console window, and press Enter to get a login prompt.

The exact layout depends on the panel, but every VPS.DO VPS includes VNC console access.

Logging in

  • Use a local user and password (root, or your sudo user). SSH keys don’t help here, because this is a local console login.
  • That’s why it’s worth keeping a strong local password on your sudo user, even with SSH password login disabled.
  • Lost every password? Use the panel’s root password reset if available, or boot into single-user mode with GRUB (advanced). As a last resort, reinstall the OS after rescuing what you can. See reinstall the OS.

Keyboard tips

  • Browser consoles sometimes mis-map keys (especially on non-US layouts). Use the console’s “Send Ctrl+Alt+Del” button, or its virtual keyboard if available.
  • Copy/paste often doesn’t work into VNC. Type commands carefully, or use short commands. Some consoles offer a “paste text” feature.
  • Linux virtual terminals: switch with Alt+F1…F6 (or the panel’s key menu).

Common fixes from the console

Firewall locked you out (UFW):

ufw allow 22/tcp      # or your custom SSH port
ufw status
# or temporarily: ufw disable

Broken SSH config:

sshd -t                               # shows the config error
nano /etc/ssh/sshd_config
systemctl restart ssh                 # "sshd" on RHEL-family

See SSH permission denied (publickey) and disable root SSH login.

Network config mistake (Ubuntu/netplan):

nano /etc/netplan/50-cloud-init.yaml  # file name varies
netplan apply
ip addr; ip route

See static IP with netplan.

Boot stuck because of /etc/fstab: at the emergency prompt, enter the root password, then:

mount -o remount,rw /
nano /etc/fstab          # comment out the bad line, or add "nofail"
reboot

Fail2ban banned your IP:

fail2ban-client set sshd unbanip 203.0.113.50

See Fail2ban.

Windows Server: log in on the console, then re-enable Remote Desktop, and allow it in Windows Firewall. See Windows Server firewall with PowerShell and RDP black screen fix.

Prevent lockouts

  • Before changing firewall or SSH settings, keep your current SSH session open, and test a new connection in a second terminal.
  • With UFW, allow SSH before enabling it: ufw allow 22/tcp && ufw enable.
  • Use netplan try, which reverts automatically if you lose connectivity.
  • Allowlist your own IP in Fail2ban (ignoreip).

Security note

The console is protected by your client area login. Use a strong password and 2FA for the client area if available. Anyone with access to it can reach your server’s console.

Quick reference

Problem Console fix
UFW blocks SSH ufw allow 22/tcp
sshd won’t start sshd -t, edit config, restart
Network broken Fix netplan/interfaces, netplan apply
fstab boot failure Remount rw, fix /etc/fstab
Banned by Fail2ban fail2ban-client set sshd unbanip <ip>

Related: VPS root access and Linux server hardening checklist.

  • VPS Guide
  • Troubleshooting
  • Linux