The web console provides direct, browser-based access to your server's display and keyboard input through VNC (Virtual Network Computing) technology. Unlike SSH, the web console works even when your server's network is misconfigured, the SSH service is down, or the firewall is blocking connections.

This guide explains how to launch the web console, common use cases, and tips for getting the most out of this tool.

When to Use the Web Console

The web console is invaluable in situations where standard SSH access is not available:

• Network misconfiguration — If you accidentally changed network settings and lost connectivity.
• Firewall lockout — If firewall rules are blocking SSH connections.
• SSH service failure — If the SSH daemon crashed or was disabled.
• Boot issues — If the server is stuck at a boot prompt, GRUB menu, or filesystem check.
• Rescue mode — When diagnosing and repairing a server that cannot boot normally.
• OS installation — When performing manual operating system installations or reinstalls.

Launching the Web Console

The console connects directly to your server's virtual display. You will see whatever the server is currently showing — a login prompt, a desktop environment, a boot screen, or error messages.

Logging In via the Console

When the console opens, you will typically see a login prompt. Enter your credentials:

server login: root
Password: **

Type your username and press Enter, then type your password and press Enter. Note that the password field does not display characters as you type — this is normal behavior for Linux terminals.

If you have forgotten your root password, you may need to boot into recovery mode or use a rescue system to reset it. See Forgot Password — How to Reset.

Console Features

Keyboard Input

The web console captures keyboard input and sends it directly to the server. Most standard key combinations work, including:

• Ctrl+C — Interrupt a running process.
• Ctrl+D — Log out of the current shell session.
• Tab — Command autocompletion.
• Arrow keys — Navigate command history and text.

Clipboard Operations

Copy and paste between your local machine and the web console may require a special clipboard panel:

The exact clipboard mechanism varies by browser and console implementation.

Screen Resolution

The default console resolution is typically 800x600 or 1024x768. For most command-line tasks, this is sufficient. If you need a different resolution, you can change it from within the operating system:

# Check current resolution
xrandr
Set a new resolution (if supported)
xrandr -s 1280x1024

Note that resolution options depend on the virtual display driver and may be limited.

Common Console Tasks

Fixing Network Configuration

If you have locked yourself out by misconfiguring the network:

# View current network configuration
ip addr show
Restart networking service
sudo systemctl restart networking    # Debian/Ubuntu
sudo systemctl restart NetworkManager  # CentOS/AlmaLinux
Manually set an IP address (temporary)
sudo ip addr add 203.0.113.10/24 dev eth0
sudo ip route add default via 203.0.113.1

Fixing Firewall Rules

If your firewall is blocking SSH:

# UFW (Ubuntu/Debian)
sudo ufw allow 22/tcp
sudo ufw reload
firewalld (CentOS/AlmaLinux)
sudo firewall-cmd --permanent --add-service=ssh
sudo firewall-cmd --reload

Restarting SSH Service

If the SSH daemon is not running:

sudo systemctl status sshd
sudo systemctl restart sshd
sudo systemctl enable sshd

Checking Boot Errors

If the server is not booting properly, the console will show boot messages, including any errors. Common issues include:

• Filesystem corruption requiring fsck
• Missing boot configuration
• Failed service preventing boot completion

Console Limitations

• Performance — The web console is slower than SSH for interactive work. Use it for troubleshooting and repair, then switch back to SSH for regular administration.
• File transfer — You cannot transfer files through the console directly. Use SSH/SCP/SFTP once connectivity is restored.
• Session persistence — If you close the browser tab, the console session may disconnect. The server itself continues running — only your view is disconnected.
• Copy/paste — Clipboard operations are more limited than with SSH terminal emulators.

Tips for Effective Console Use

What to Do Next

• Managing SSH Keys — Set up SSH key authentication for secure access.
• Server Not Booting — Rescue Mode Guide — Diagnose and fix boot problems.
• Firewall Blocking Legitimate Traffic — Resolve firewall lockout issues.
• Understanding Your Server Dashboard — Explore all dashboard features.