Restart your server and use the browser console
Restart cleanly from inside Windows, or use the control panel's power controls and browser console when Remote Desktop is not responding.
- Beginner
- Windows VPS · Admin RDP
- 2 min read
Most of the time you restart Windows from inside your Remote Desktop session. When RDP does not respond, the RunRacks control panel gives you power controls and a browser console that shows the server's screen directly, even with no network login.
Restart from inside Windows (preferred)
A restart from inside Windows lets programs close cleanly. Save your work, then:
- Start → Power → Restart, or
- press Ctrl + Alt + End in the session and use the power icon, or
- in PowerShell:
Restart-ComputerFrom Command Prompt, shutdown /r /t 0 does the same.
Open the control panel
- Log in to the client area and open Services.
- Select your server and click Open Control Panel. This signs you in to the server panel directly.
Use the power controls
The panel has start, stop and restart controls for your server.
- Use restart when Windows does not respond to RDP.
- Use stop only when you really need the server off. A stop from the panel is like pulling the power, so unsaved work is lost.
Avoid forced restarts while Windows is installing updates ("Working on updates" or "Do not turn off your computer"). Interrupting an update can leave Windows unable to start. Check the browser console first and wait if updates are in progress.
Use the browser console
The browser console shows the server's own screen in your browser. Use it to:
- watch Windows boot or install updates,
- sign in when RDP is blocked by a firewall rule, a changed port or an IP restriction,
- undo a setting that cut off Remote Desktop.
To sign in from the lock screen, Windows needs Ctrl + Alt + Del. Pressing it on your keyboard goes to your own computer, so look for the console's own option to send it.
The console is slower and has no clipboard, so keep commands short. Fix the access problem there, then switch back to Remote Desktop for normal work.
When to contact support
If the server does not start, the console shows an error you cannot get past, or the panel shows a state you do not expect, open a support ticket with the time and what you saw.
Next steps
- Fix "Remote Desktop can't connect"
- Reinstall the OS from the control panel (last resort: erases all data)
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