Skip to main content

​
Your Server’s Emergency Monitor

Think of VNC as plugging a monitor and keyboard directly into your server. Normally, you connect to your VPS over the network using SSH or Remote Desktop. But what happens when the network itself is the problem? Maybe you accidentally blocked SSH with a firewall rule, or the server is stuck at a boot prompt, or you need to watch the operating system install from scratch. That is exactly where VNC saves the day. Virtual Network Computing (VNC) gives you raw, direct access to your server’s console — the same screen you would see if you were standing in front of a physical machine. It works through your web browser, requires no extra software, and does not depend on your server’s network being functional. If the server is powered on, VNC can reach it.

Difficulty

Intermediate

Time

3 Minutes

​
When You Need VNC

Before we walk through the steps, here are the real-world situations where VNC becomes your best friend:

Locked Out of SSH

You accidentally set a firewall rule that blocks port 22, changed the SSH port and forgot the new one, or disabled the SSH service entirely. SSH is dead, but VNC does not use the network stack inside your server — so you can log in, fix the mistake, and restore SSH access.

Watching the Boot Process

Your server is stuck and will not come up. With VNC, you can see exactly what is happening during boot — kernel panics, GRUB errors, filesystem check prompts, or services failing to start. Instead of guessing, you are looking at the actual error messages.

Installing a Custom OS

When you mount a custom ISO and need to walk through an installation wizard (selecting partitions, setting a hostname, configuring users), VNC is how you interact with that installer. There is no other way to click through a graphical setup.

Network Misconfiguration

You edited /etc/network/interfaces or netplan and now the server has no network at all. The server is running fine — you just cannot reach it over the internet. VNC connects through the hypervisor, completely bypassing your server’s networking, so you can log in and fix the configuration.

​
Enabling VNC Access

1

Navigate to Your Server

Log into the VPS Control Panel at cloud.freakhosting.com. Click on Servers in the top navigation bar, then click Manage next to the server you want to access.
2

Open the Options Tab

Click on the Options tab in the server management navigation.
3

Select the VNC Sub-Tab

You will land on the VNC sub-tab by default. You will see the message: “Virtual Network Computing (VNC) allows you to connect to the server as if you were in front of it. You should only enable this option if you are having issues or need to install using CD/DVD media.”
4

Enable VNC Access

Click the blue Enable VNC Access button. The system will initialize a VNC session and open a web-based console directly in your browser. No additional software or downloads required.
5

Use the Console

Once the console opens, you are looking at your server’s actual screen output. You can see the boot process, log in at the terminal prompt, interact with graphical installers, and even enter BIOS/UEFI settings. Type directly into the browser window just as you would on a physical keyboard.

​
Real-World Emergency Scenarios

Here are step-by-step walkthroughs for the most common VNC rescue situations:

​
Scenario 1: You Blocked SSH with a Firewall Rule

You ran ufw deny 22 or added an iptables rule that locked you out. SSH connections time out. Here is how to fix it:
  1. Enable VNC from the Options > VNC tab
  2. Log in at the console with your root credentials
  3. Fix the firewall:
# If using UFW
ufw allow 22/tcp
ufw reload

# If using iptables
iptables -A INPUT -p tcp --dport 22 -j ACCEPT
  1. Test SSH from your local machine to confirm it works
  2. Disable VNC when finished

​
Scenario 2: Server Stuck at Boot

Your server will not come up after a reboot. You need to see what is happening:
  1. Enable VNC from the Options > VNC tab
  2. Watch the boot output — look for error messages, filesystem check prompts, or services that hang
  3. If you see a filesystem check prompt (Press F to force fsck), follow the on-screen instructions
  4. If GRUB is showing an error, you may need to boot into Rescue Mode to repair the bootloader

​
Scenario 3: Broken Network Configuration

You edited network config files and lost connectivity:
  1. Enable VNC from the Options > VNC tab
  2. Log in at the console
  3. Check and fix your network configuration:
# View current network state
ip addr show

# For Debian/Ubuntu with netplan
nano /etc/netplan/01-netcfg.yaml
netplan apply

# For older Debian/Ubuntu
nano /etc/network/interfaces
systemctl restart networking
  1. Once your network is back, confirm SSH works, then disable VNC

​
VNC Tips and Best Practices

  • Keyboard Input — Some special key combinations (like Ctrl+Alt+Del) may be intercepted by your local computer instead of being sent to the server. Look for on-screen buttons in the VNC toolbar to send these special key sequences.
  • Performance — VNC streams a graphical view of your console over the web. A stable internet connection and a modern browser give the best experience. Expect a slight delay compared to SSH — this is normal.
  • Security — Disable VNC access as soon as you are done using it. It creates an additional access point to your server. SSH is faster, more secure, and better suited for everyday use. Think of VNC as an emergency tool, not your daily driver.
  • Clipboard — Copy and paste between your local machine and the VNC console can be limited. Many web-based VNC clients include a clipboard tool in the toolbar — look for a clipboard or paste icon to transfer text.
  • Credentials — VNC gives you a login prompt just like a physical monitor would. You still need your root/administrator password. If you have forgotten it, use the Password Reset feature first, then connect via VNC.
VNC access needs to be manually enabled from the Options > VNC tab. It is not active by default and should be treated as an on-demand troubleshooting tool. Enable it when you need it, disable it when you are done.
No. The web-based VNC console is provided through the control panel’s infrastructure, not through your server’s network. You do not need to open any ports, configure any firewall rules, or install any software on your server for VNC to work. This is exactly why it works even when your server’s network is completely broken.
The control panel provides a built-in web-based VNC client that works in any modern browser. External VNC client support depends on your specific configuration and may not be available. The built-in client is the recommended and most reliable option.
No. VNC is designed as a troubleshooting and recovery tool, not a replacement for SSH or Remote Desktop. Leaving it enabled creates an unnecessary access point. Enable it when you hit a problem, fix the problem, then disable it.
A blank screen usually means the server is powered off, is still booting, or is waiting for input. Try pressing Enter or a key to wake the console. If the screen stays blank, check the server’s power state on the Overview page and boot it if necessary. You can also try disabling and re-enabling VNC to refresh the session.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to get a new server? Use code KB20 at checkout for 20% off your first month!
Last Updated: March 2026 | VPS Support: VNC console access simplified.