If you're having trouble connecting to your VPS over the network — for example, RDP or SSH isn't responding — you can still reach your server using console access. The console connects you to the machine over an out-of-band local network connection, so it works even when normal network access is down. You access it directly from your web dashboard, no extra software required.
When to use console access
Use the console when you cannot reach your VPS through your usual connection method, such as:
Remote Desktop (RDP) or SSH won't connect
The server is online but unreachable over the network
You've changed firewall or network settings and locked yourself out
You need to log in locally to troubleshoot the operating system
Because the console connects locally to the machine (out of band), it bypasses most network-level issues that would block a standard connection.
Step 1: Request console access
Console access is enabled per server. Once it has been granted for your VPS, the Launch VNC button becomes available in the Control Panel.
Step 2: Launch the console
Open your dashboard and go to the Control Panel tab for your server.
In the top-right corner, click the Launch VNC button.
Once the session starts, the button changes to Console Open and the VNC session window appears.
The console first opens as a small floating window in the lower-left of the screen. To make it easier to work in, click the expand icon in the VNC Session title bar to enlarge it to full screen.
Step 3: Connect to the system
The console opens a live view of your server's screen inside the web dashboard. If you see a lock screen with "Press Ctrl+Alt+Delete to unlock," follow the steps below to log in. Sending these keys through the toolbar (rather than your own keyboard) ensures they're delivered to the VPS and not to your local computer.
On the left edge of the session, click the keyboard ("A") icon to open the on-screen key panel.
In the key panel, click the Ctrl+Alt+Del button (the four-square icon at the bottom of the panel) to send the unlock combination to the server.
At the Administrator login screen, click the Password field and type the server's Administrator password, then press Enter (or click the arrow) to log in.
Step 4: Use the console toolbar
The toolbar on the left edge of the VNC session gives you the controls you need while connected:
Keyboard — send special keys and key combinations (such as Ctrl+Alt+Delete) to the server.
Clipboard — paste text between your local machine and the VPS.
Settings — adjust console and display options.
Disconnect — end the console session when you're finished.
Step 5: Restore Remote Desktop (RDP) access
Once you're logged in through the console, you can fix the most common reasons RDP stops working so you can get back to connecting normally.
Make sure Remote Desktop is enabled
Open the Start menu and go to Settings → System → Remote Desktop.
Confirm the Enable Remote Desktop toggle is set to On. If it's off, switch it on and confirm the prompt.
Make sure the network is set to Private
RDP can be blocked when the server's network is set to Public, because the firewall applies stricter rules. Setting it to Private allows Remote Desktop connections.
Go to Settings → Network & Internet → Status, then open the properties of your active connection (Ethernet or Wi-Fi).
Under Network profile, select Private.
Other things to check
Firewall: make sure Remote Desktop is allowed through Windows Defender Firewall (Control Panel → System and Security → Windows Defender Firewall → Allow an app through firewall).
User permissions: confirm your account is listed under Select users that can remotely access this PC on the Remote Desktop settings page.
Service running: ensure the Remote Desktop Services service is started (Services console, or run
services.msc).
After enabling RDP and setting the network to Private, try connecting again with your Remote Desktop client.
Tips
The console gives you the same access as sitting in front of the machine, so you can fix network, firewall, or login issues that would otherwise block you.
When you're done troubleshooting, close the session to free up the console.
If you still can't log in or the console doesn't appear, contact support so we can confirm console access has been granted for your server.