English
€EUR
  • vnc console
  • vps
  • ssh
  • emergency access
  • troubleshooting
  • firewall

VNC console: regain control of your VPS when SSH stops responding

A bad firewall rule, a dead SSH service or a banned IP: the VNC console on Infrawire VPS gives you direct access to your server, with no reinstall.

  • 5 min read
  • Sarah Belkacem
VNC console: regain control of your VPS when SSH stops responding

One firewall rule typed too quickly, one SSH service that refuses to restart, and your server goes silent. In that situation, the VNC console in your Infrawire client area shows you the machine's screen, as if you had plugged a keyboard and a monitor into it. You take control again, fix the mistake, and the VPS is reachable once more.

This emergency access does not go through your server's network. Whatever is blocking SSH or remote desktop has no effect on it. For a business, that is the difference between ten minutes of fixing and a day of restoring.

Access that is independent of the server's network

SSH depends on three things: a service that is listening, a network interface and a firewall. If any one of them fails, the connection fails, even though the server is still running. The VNC console works differently: it is served by the hypervisor, which reads the virtual machine's display and passes your keystrokes to it.

As long as the VPS is powered on, you can see what it displays, even if its network configuration is completely broken.

Incidents it helps you resolve

These situations come up regularly, including for experienced administrators:

  • a firewall rule that blocks the administration port, sometimes the one you had just configured;
  • a mistake in the SSH configuration, discovered only when the service restarts;
  • an IP address banned by a protection tool after a few failed login attempts;
  • an invalid network configuration after a change or an update;
  • a full disk that prevents any new session from opening.

In every one of these cases the machine is not damaged. It is simply unreachable by the usual route, and the console gives you an alternative route to undo the error.

What it changes for your business

Without emergency access, the only way out is often to reinstall the server or restore a backup. That costs time, risks losing recent data and ties up someone who had not planned to spend the day on it.

With the console, you fix the exact cause of the incident and carry on with your system as it was. This is particularly useful for:

  • an online shop or an application whose customers expect it to respond;
  • a service provider who manages servers for several clients and cannot improvise;
  • a trader whose Forex VPS environment must stay operational;
  • a small team with no dedicated system administrator, which needs to be able to troubleshoot on its own.

What to prepare before you need it

The console requires a local login with a username and password. Yet many servers are set up to accept only SSH keys, and their accounts have no password at all. The result: the screen appears, but nobody can log in.

The fix is simple: at install time, set a long, unique password for your administration account and store it in a password manager. This does not weaken SSH, because you can keep refusing passwords there. The password is only for the emergency door.

A second tip: open the console once, cold, while everything is fine. You will learn how it behaves, in particular with the keyboard layout (often QWERTY by default) and copy-paste, which is not always available. It is better to find that out on a quiet Tuesday than in the middle of an outage.

Linux and Windows: the same principle

On a Linux server, the console gives you the login prompt. On a Windows VPS, it shows the desktop, even when Remote Desktop (RDP) is unreachable because of a firewall rule or a port change. The pattern is the same: direct access that bypasses the network so you can restore normal connectivity.

If you manage a fleet of machines, this logic applies in the same way from one server to the next, which simplifies your internal procedures. Our tutorials cover the firewall configurations to adopt in order to limit mistakes.

Choosing a VPS with troubleshooting in mind

When comparing plans, people look at CPU, memory and storage. They often forget to ask what happens the day they lock themselves out. Emergency access belongs among the criteria that matter as much as raw performance.

Infrawire Linux VPS plans include this rescue console and full root access. You can compare all plans on the VPS page, then pick the location closest to your users.

The console remains a safety net, not a daily working tool: for routine administration, SSH or RDP are more comfortable.

FAQ

Yes. It goes through the hypervisor, not through the machine's network interface. As long as the VPS is powered on, you can see its screen and send it commands.

Your account most likely has no local password. You will then need to use your distribution's rescue or recovery mode to reset it, which takes longer. That is why it is better to set one in advance.

Access goes through your client area, so protecting that account becomes essential. Choose a strong, unique password and never share your credentials.

It is not recommended. Copy-paste is limited, the display is less comfortable and typing is less smooth than in a terminal. Keep it for troubleshooting and work over SSH or RDP the rest of the time.

Sarah Belkacem

Author

Sarah Belkacem

Marketing Manager, Infrawire

Related articles

Stay up to date with the latest offers, discounts and special promotions.

View promotions

We use cookies

We use analytics cookies to improve your experience on our site. No data is sold to third parties. Learn more in our privacy policy.