Reach your server without SSH or RDP using the VNC Console
The VNC Console gives you access to your server's screen and keyboard from the browser, independently of the server's network settings. This guide explains when the console helps, the keyboard layout traps at login and how to fix the most common lockouts with commands.
How does the VNC Console work?
SSH and RDP depend on the server's network connection and on those services running. The VNC Console shows the virtual machine's screen directly, much like plugging a monitor and keyboard into a physical server. That is why you can still log in from the console even if the firewall blocks every connection, the IP settings are broken or the SSH service never starts.
The console connection is relayed through the client area; you do not need direct access to the ESXi host or any open port. The console only opens while the server is running. If the server is powered off, start it first with Start Server; you can open the console right after to watch the boot messages.
When do you need the console?
The console is the first tool to reach for whenever you cannot get in over the network. Reading the symptom correctly also tells you which command to run first on the console:
| Symptom | Likely cause | First command on the console | Permanent fix |
|---|---|---|---|
| SSH times out while the panel shows the server running | A firewall rule | ufw status numbered / firewall-cmd --list-all | Add the SSH rule |
| "Connection refused" error | The SSH service is not running | systemctl status ssh, sshd -t | Fix the configuration |
| The server does not respond to any connection | Broken network settings | ip -4 addr, ip route | Reapply them with Network Config |
| "emergency mode" on the screen | An /etc/fstab error | journalctl -xb | Fix the broken line |
| RDP does not connect | Remote Desktop disabled or blocked | Get-Service TermService | Enable Remote Desktop and its rule |
The console is also handy for watching the boot after a Force Stop or Hard Reset; the power actions guide explains which power action suits which situation.
Logging in: passwords, keyboard layout and special characters
On the console you log in with a username and password. SSH keys are of no use here, because keys only work with the SSH protocol. If you turned off root login or password login for SSH, console login is not affected, since those settings apply to the SSH service only. If you locked the root account (passwd -l root), log in with your sudo user.
The most common problem is the keyboard layout. The console forwards the keys you press in the browser to the server, and the characters they turn into depend on the browser, the console client and the keyboard layout on the server. If you use a Turkish Q keyboard and the server uses the US layout, most letters and digits come out right, but i and the dotless i, Turkish letters such as ş, ğ and ç, and symbols such as @, | and " can turn into other characters. Since the password is not shown while you type it, you do not notice the mistake and the password is rejected.
For a quick test, type the special characters from your password into the username field at the login prompt (login:), see how they appear and delete them with Backspace without pressing Enter. Never type the whole password into that field.
The reliable fix is to temporarily change the password to one made only of letters and digits before you use the console:
- In the panel, use Reset Root Password to set a long temporary password made of uppercase letters, lowercase letters and digits. Linux requires 8 to 128 characters; Windows requires at least 8 characters and at least three of the four character classes. This combination meets both rules.
- Log in on the console with this password and fix the problem.
- When you are done, change the password from the panel again, this time to a strong one.
Reset Root Password works through VMware Tools and signs in to the server with the password stored in the panel. If you previously changed the password inside the server with passwd, the tool fails; in that case you have to log in on the console with your current password and change it back to the stored one.
Linux recovery scenarios
The firewall locked you out
Look at the rules first, then allow SSH only. Turning the firewall off completely is a last resort, and you must enable it again when you are done.
# UFW (Ubuntu / Debian)
ufw status numbered
ufw allow OpenSSH # if you use a custom port: ufw allow 2222/tcp
# Last resort, temporarily: ufw disable
# firewalld (AlmaLinux)
firewall-cmd --list-all
firewall-cmd --permanent --add-service=ssh
firewall-cmd --reloadIf you manage rules directly with iptables, be careful: running iptables -F while the default policy is DROP deletes the allow rules and cuts off all access except the console. Set the policy to ACCEPT first, then flush only the INPUT chain. Flushing every chain also deletes Docker's network rules, in which case you need systemctl restart docker.
# List the rules with line numbers
iptables -L INPUT -n --line-numbers
# Set the default policy to ACCEPT first, then flush only the INPUT chain
iptables -P INPUT ACCEPT
iptables -F INPUT
# If you use nftables
nft list rulesetFor a permanent rule set, see the UFW and firewalld guide.
The SSH service does not start
# Ubuntu / Debian: the service is ssh; AlmaLinux: sshd
systemctl status ssh --no-pager
journalctl -u ssh -b --no-pager | tail -n 30
# Shows configuration errors with file and line number
sshd -t
# After fixing
systemctl restart sshIf sshd -t prints nothing, the syntax is correct. On Ubuntu 24.04 and later, SSH can be started by a systemd socket (ssh.socket); check with systemctl status ssh.socket, and if you changed the port, run systemctl daemon-reload and systemctl restart ssh.socket. On AlmaLinux, SELinux blocks a non-default port; allow it with semanage port -a -t ssh_port_t -p tcp 2222. If the host keys were deleted, ssh-keygen -A regenerates the missing keys. See the SSH guide for details.
The network connection is gone
Your server's IPv4 address is assigned statically from Hostimor's pool; DHCP cannot be used. If you edited the network files (netplan, NetworkManager or /etc/network/interfaces) by hand, or a tool broke them, look at the current state first:
ip -4 addr show
ip route
resolvectl status 2>/dev/null || cat /etc/resolv.conf
# After Network Config has been applied
ping -c 3 1.1.1.1If the address or the default gateway (default via) is missing, do not try to fix the files by guesswork. Reapply the network settings and DNS resolvers with the panel's Network Config tool, which works through VMware Tools. Then test outbound connectivity with the ping command above. See IP addresses and DNS settings for details.
The boot is stuck in emergency mode or a file system check
If the screen says "You are in emergency mode", the system usually failed to mount a line in /etc/fstab: a removed disk, a wrong UUID or a typo. Log in with the root password and find the error:
journalctl -xb -p err --no-pager | tail -n 40
mount -o remount,rw /
vi /etc/fstab # or nano; comment out the broken line with # or add nofail
systemctl daemon-reload
mount -a # should print no errors
systemctl rebootIf Ubuntu or Debian shows an (initramfs) prompt and the message "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY", the root file system is not mounted yet and repairing it is safe. Run fsck -y /dev/sda1 for the device named in the message (take the device name from the message), then type exit to continue booting. On systems that use XFS, the repair tool is xfs_repair. Never run a repair on a file system that is mounted read-write.
The console on Windows
The Windows sign-in screen asks for Ctrl+Alt+Del. If you press this combination on your own keyboard, your own computer catches it; if the console toolbar offers an option to send Ctrl+Alt+Del, use that instead. Then sign in as Administrator with your password.
If RDP has been turned off, enable the Remote Desktop setting on the Local Server page in Server Manager, or run PowerShell as administrator and apply these commands:
# Allow Remote Desktop connections
Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -Value 0
# Enable the RDP rules in Windows Firewall
Enable-NetFirewallRule -Name 'RemoteDesktop-UserMode-In-TCP','RemoteDesktop-UserMode-In-UDP'
# Check the Remote Desktop service
Get-Service TermServiceFor connection and security details, see connecting with RDP and RDP security.
Sign out when you leave the console
Closing the console window does not end the session on the server; the root shell stays open, and anyone with panel access who opens the console later can pick it up where you left it. When you are done, type exit or logout on Linux, and sign out from the Start menu on Windows. To have forgotten shells close on their own, set an idle timeout:
cat > /etc/profile.d/tmout.sh <<'EOF'
TMOUT=900
readonly TMOUT
export TMOUT
EOFThis setting closes interactive Bash sessions after 15 minutes without input, and it covers SSH sessions too.
After fixing a problem from the console, make the permanent fix and confirm that you can connect again over SSH or RDP. The console is a recovery tool, not a tool for day-to-day administration.
Frequently asked questions
The VNC Console does not open, or I see a black screen.
The console only opens while the server is running, so check the server's status in the panel first. A black screen may simply be a screen saver; press Enter to bring the login prompt back. If the problem persists, close the console and open it again.
Can I log in to the console with my SSH key?
No. The console is a keyboard and screen connection, and logging in requires a username and password. If you do not know your password, set a new one from the panel with Reset Root Password.
Copy and paste does not work on the console.
The console forwards keyboard input, and pasting from the clipboard may not work in every browser and console client. Type short commands by hand. Instead of typing a long configuration on the console, restore network access first and connect over SSH.
Related articles
Thanks for your feedback!