Taking back control with the rescue console when RDP stops answering

Remote Desktop travels over the network and depends on a Windows service. If either fails — a bad firewall rule, a stopped service, an endless update, a lost password — RDP stops answering while the machine itself keeps running.

The Console in the client area is made for exactly that. It attaches you to the screen of the virtual machine at hypervisor level, as if you stood in front of a monitor plugged into the server. It works even when Windows has no network at all.

How do I open the rescue console for my VPS?

From My services, open your VPS, go to the Console tab, then click Ouvrir la Console: it appears in a new browser tab.

1. Go to My services and open your VPS.
2. Click the Console tab. It shows Console - your-hostname and the line "Accédez à la console VNC de votre VPS."
3. A note reminds you that "the console will open in a new window".
4. Click Ouvrir la Console. A new browser tab opens.
5. The status bar shows "Connexion à la console…", then Connected as soon as the screen arrives.

Nothing to install: the console runs in the browser, on any operating system.

Which controls does the console offer?

Two: Ctrl+Alt+Del, essential on Windows, and Reconnect, which restarts the session when the screen freezes.

• Ctrl+Alt+Del: the dedicated button sends the combination to the remote machine. It is essential on Windows, because your own computer always captures that shortcut.
• Reconnect: restarts the console session. Use it if the screen freezes or the status bar turns to Disconnected.

What you see is the machine's own screen: if Windows is booting you see the logo; if it is waiting for a reboot you see the dialogue box. That is precisely the point.

Why is the console unavailable on my VPS?

Because an installation is running: the console stays closed for about fifteen minutes, then reopens on its own.

Right after delivery and after every reinstallation, the tab is titled "Console (installation…)" and displays:

Console unavailable during installation — your machine is installing its operating system. The console is closed for this step so that no action can interrupt the installation.

The panel adds that there is nothing to do on your side, that the console will reopen on its own and that the other tabs of your service stay available, along with a countdown such as "Reopening in about N minutes." The page reloads itself when the time is up. The lock lasts around fifteen minutes and cannot be bypassed, not even through the direct console address.

If a "Console indisponible" message appears outside an installation, click Retry. If it keeps failing, open a ticket stating the exact time of the attempt.

When is the rescue console indispensable?

In five situations above all: the firewall locked you out, a reboot is blocking Windows, the password no longer works, the machine will not boot, or the network configuration is broken.

• The firewall locked you out. You deleted the Remote Desktop rule: open the console and restore it from wf.msc.
• Windows is waiting on a blocking reboot. An update shows a screen that RDP never displays. Here you see it and can act.
• The password no longer works. Change it directly in the local session with Ctrl+Alt+Del > Change a password.
• The machine no longer boots normally. You see the Windows recovery screen and can start the repair tools.
• You changed the network configuration. If the IP address was mistyped, the console is your only remaining way in.

How should I use the rescue console properly?

Open it before any risky change, use it to repair rather than to work, and close its tab as soon as you are finished.

1. Open the console before any risky change to the firewall or the network: you will know it works at the moment you need it.
2. The console is a screen, not a transfer channel: no comfortable copy and paste, no file transfer. Fix the problem in the console, then go back to RDP for the work.
3. Close the console tab when you are done. A session left open shows an open Windows session to anyone reaching your browser.
4. If the console works but RDP still refuses, the problem lies in Windows or its firewall — never in the By-Hoster network. That is valuable information to include in a ticket.