fren
Log In

Use a VPS VNC console

2 min read07 November 2026

SSH sometimes fails at the worst moment: a misapplied firewall rule, a broken network interface or a service that blocks boot. The panel VNC console stays reachable even when the VPS network no longer answers. It shows the container screen and lets you log in locally, as if you were at a physical keyboard.

When to use the console

  • SSH refuses connections after a firewall or sshd_config change.
  • The VPS does not answer pings while the panel shows it running.
  • A service blocks boot and you need to read the messages on screen.
  • You need a clean reboot without waiting for remote access.
  • You lost the root password and must use a local account.

Open the console

  1. Sign in to https://dash.neoheberg.fr.
  2. Open the VPS service.
  3. Start the noVNC console: it opens in a browser tab.
  4. Log in with an existing local account.

The console does not depend on your internet connection or on SSH. It is attached to the container and works as long as the container runs.

Fix things without a network

Once logged in, you can repair whatever cut remote access:

  • Correct the address in /etc/network/interfaces or the Netplan configuration.
  • Inspect the firewall with ufw status verbose, then temporarily disable it if a rule blocks SSH.
  • Check disk space with df -h: a full disk often stops sshd from writing session keys.
  • Read boot errors with journalctl -xb.
  • Edit /etc/ssh/sshd_config, validate with sshd -t, then restart the service.

Copy and paste is limited and the keyboard layout may differ. Type short commands and check every output.

Reboot cleanly

Always prefer a software shutdown:

Bash
sudo systemctl reboot

or sudo shutdown -r now. If the system is frozen, use the panel power action. Avoid repeated forced stops: they can corrupt the filesystem and hide the real cause.

Console limits

The console does not replace SSH: no file transfer, slow graphical rendering and a lost session if the container stops. Use it to diagnose and repair, not to work all day. Keep SSH as the primary access and the console as a safety net.

Advertisement

Was this article helpful?

Read next