If you can't reach your dedicated server over the network — for example, RDP or SSH isn't responding — you can still reach it through console access. For dedicated servers, the console connects through the server's built-in management controller (BMC/IPMI), giving you the same access as if you were standing in front of the machine with a monitor and keyboard. Everything runs in your web dashboard, with no software to install.
When to use console access
Use the console when you cannot reach your dedicated server 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 through the out-of-band management controller, it works even when the operating system's networking is down.
Step 1: Grant console access
Console access is enabled per server. Once it has been granted for your dedicated server, the Launch VNC / Panel button becomes available in the Control Panel and opens the server's Web Panel.
Step 2: Open and expand the Web Panel
Open your dashboard and go to the Control Panel tab for your dedicated server.
Launch the console. It first opens as a small floating Web Panel window in the lower-left corner.
Click the expand icon in the Web Panel title bar to enlarge it to full screen.
Step 3: Open Remote Control in the BMC
The Web Panel loads the server's management interface (BMC/IPMI — shown here as ASRockRack). Across the top of the Server Console you'll see quick-fill Username and Password fields with Send buttons, a CTRL + ALT + DELbutton, and a Connected status.
In the left sidebar of the ASRockRack dashboard, click Remote Control.
Step 4: Launch the KVM viewer
On the Remote Control (Remote KVM) page, you'll see viewer options.
Click Launch H5Viewer to open the browser-based KVM console. (H5Viewer runs in the browser and needs no download; JViewer is a Java-based alternative.)
Step 5: Send Ctrl+Alt+Del and log in
The KVM viewer opens a live view of the server's screen. If you see "Press Ctrl+Alt+Delete to unlock," send that combination from the viewer's menu bar — sending it from the toolbar (not your own keyboard) ensures it reaches the server.
In the viewer's top menu bar, click Send Keys.
In the dropdown, click Ctrl+Alt+Del (under "Press and Release").
3. And then 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 6: 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.
Under Network profile, select Private.
Other things to check
Firewall: make sure Remote Desktop is allowed through Windows Defender Firewall.
User permissions: confirm your account is listed under Select users that can remotely access this PC.
Service running: ensure the Remote Desktop Services service is started (
services.msc).
After enabling RDP and setting the network to Private, try connecting again with your Remote Desktop client.
Tips
The KVM 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, click Stop KVM in the viewer and close the Web Panel to free up the console.
If you can't log in, the viewer won't launch, or the panel doesn't appear, contact support so we can confirm console access has been granted for your server.