When to use the browser console instead of SSH or RDP
The browser console in the RunRacks control panel gives you your server's screen in a browser tab. Learn when to use it, such as after a firewall or network mistake, and how to get back to SSH or RDP.
- Beginner
- All
- 4 min read
SSH and Remote Desktop both travel over the network, so anything that breaks the network path, such as a firewall rule, a changed port or a bad network setting, locks you out. The browser console in the RunRacks control panel works differently. It shows the server's screen directly, as if you had a monitor and keyboard plugged in. This guide explains when to reach for it and how to use it to fix the problem.
Before you start
- You are signed in to the Dashboard.
- You know the server's username and password. The console uses the server's own login, not your Dashboard login. If you changed the password, use the new one.
- Pop-ups are allowed for the site, as the control panel may open in a new tab.
How the console differs from SSH and RDP
- SSH and Remote Desktop connect over the network to a service running on the server. They need the server's network, its firewall and the service itself to be working.
- The browser console connects to the server's screen from the hosting side. It works even when the network service, the firewall or the network configuration is broken.
The trade-off is comfort. The console is a basic screen: copy and paste can be limited, the display is small and it can feel slow. Use it to fix the problem, then go back to SSH or Remote Desktop for normal work.
When to use the browser console
- You changed the firewall and locked yourself out. For example, you enabled UFW on Linux without allowing SSH, or removed the Windows Firewall rule for port 12230.
- You changed the SSH port or the Remote Desktop port and the new one does not work.
- Network settings are wrong, for example after editing the IP configuration.
- SSH or Remote Desktop has stopped and you need to start it again.
- The server does not boot properly and you want to see the error on screen.
- You forgot the server password and need to reset it from a recovery option.
- Windows is installing updates and you want to watch progress without breaking anything.
Open the console
- In the Dashboard, open Services and click the server.
- Click Open control panel.
- Open the browser console. A screen appears showing the server's display.
- Click inside the console so it receives your keyboard input.
- Log in:
- Linux: at the
login:prompt, type the username (for exampleroot), press Enter, then type the password. Nothing appears while you type the password. - Windows: use the console's Ctrl + Alt + Del button to reach the login screen, then sign in.
Long passwords are awkward to type in a console. Type carefully, and check your keyboard layout: a console may assume a US layout, so symbols can land on different keys.
Fix common lockouts
Linux: firewall blocked SSH
On Ubuntu or Debian with UFW:
ufw allow 22/tcp
ufw statusOn AlmaLinux or Rocky Linux with firewalld:
firewall-cmd --permanent --add-service=ssh
firewall-cmd --reloadIf you moved SSH to another port, allow that port number instead of 22.
Linux: SSH service stopped
systemctl restart sshOn AlmaLinux and Rocky Linux the service is named sshd.
Windows: Remote Desktop blocked
Open PowerShell as Administrator in the console and re-create the allow rule for the RunRacks RDP port:
New-NetFirewallRule -DisplayName "Remote Desktop (TCP 12230)" `
-Direction Inbound -Protocol TCP -LocalPort 12230 -Action AllowDo not reset the firewall, change the Remote Desktop port or disable network adapters from the console unless you know the way back. One wrong change in a console session can leave you depending on the console until it is fixed.
Check it works
After the fix, test normal access from your own computer:
- Linux:
ssh [email protected]should reach the password prompt. - Windows:
Test-NetConnection 203.0.113.10 -Port 12230in PowerShell should showTcpTestSucceeded : True. Then connect with Remote Desktop to203.0.113.10:12230.
Once that works, sign out of the console.
Troubleshooting
- The console is black: the screen may be asleep. Click inside it and press a key, such as Shift.
- Login fails in the console but the password is right: check the keyboard layout and Caps Lock. Try typing the password in the username field to see what characters appear, then clear it.
- The control panel or console will not open: allow pop-ups, try another browser, or open a ticket.
- The console shows boot errors: screenshot them and open a ticket with the service and IP.
Next steps
- Start with the basic checks: Server not responding? First checks before contacting support.
- Avoid lockouts on Linux: Change the SSH port safely.
- Use the console on Windows: Restart a Windows VPS from the control panel and console.
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Troubleshooting
Fix Nginx 413 Request Entity Too Large
Nginx returns 413 Request Entity Too Large when an upload is bigger than client_max_body_size. Raise the limit for one site or the whole server, match PHP's limits, and test.
- Beginner
- Linux VPS
- 5 min read
Troubleshooting
Is your ISP or router blocking port 12230? How to tell
Work out whether your internet provider, home router, parental controls or a proxy is blocking RDP port 12230, and collect the details support needs to help.
- Intermediate
- Windows VPS · Admin RDP
- 5 min read
Troubleshooting
Fix "Your credentials did not work" in Remote Desktop
Fix rejected RDP logins: username format, the right password, stale saved credentials, account lockout and Remote Desktop permissions.
- Beginner
- Windows VPS · Admin RDP
- 3 min read