Start, stop and restart your server from the control panel
Use the power controls in the RunRacks Dashboard to start, stop and restart your server, learn the difference between them, and know when a forced restart is the right call.
- Beginner
- All
- 5 min read
Your RunRacks Dashboard has power controls for every server: start, stop and restart (shown as Reboot on the service page). They work like the power button on a physical computer, but from your browser. This guide explains what each one does, when to use it, and why a clean restart from inside the operating system is usually the better first choice.
Before you start
- You are signed in to the Dashboard.
- You know which service you want to control. Server names and IP addresses are listed under Services.
- Save your work. Anything open on the server, such as an unsaved document or a running trading terminal, stops when the server goes down.
Where the power controls are
- In the Dashboard, open Services and click your server.
- On the service page, find the Power controls. You can Start, Stop or Reboot the server from there.
- For more options, click Open control panel. The control panel holds the same power controls, plus OS reinstall and the browser console.
Each action asks you to confirm before it runs. After you confirm, the status on the page updates as the server stops or starts.
What each control does
Start
Powers on a stopped server. The operating system boots as normal. Give it a minute or two before you connect over SSH or Remote Desktop. Windows servers often take a little longer than Linux.
Stop
Powers the server off. Everything running on it stops until you start it again: websites go offline, bots stop, and Remote Desktop sessions end. Use it when you want the server off for a while, for example while you plan a migration.
Stopping a server does not cancel it. The service stays on your account, with its invoices, until you cancel it. To end a service, submit a cancellation request instead.
Restart (Reboot)
Stops the server and starts it again in one step. Expect it to be offline for a minute or two. A restart clears a hung process, applies updates that need a reboot, and frees memory after a leak.
Restart from inside the OS first
When you can still log in, a restart from inside the operating system is the gentlest option. It gives every program a chance to save data and close cleanly.
On a Linux VPS, connected over SSH:
sudo rebootOn a Windows VPS or Admin RDP, in PowerShell as Administrator:
Restart-ComputerYour SSH or Remote Desktop session drops straight away. Wait about two minutes, then reconnect. On Windows, remember the RunRacks RDP port: connect to 203.0.113.10:12230.
When a forced restart is the right call
Use the Reboot button in the Dashboard when you cannot restart from inside the server:
- SSH or Remote Desktop does not respond at all.
- The browser console shows a frozen screen or does not react to the keyboard.
- The server is so overloaded (memory full, CPU at 100%) that commands never finish.
A forced restart is like holding down the power button. It works, but programs do not get a chance to save their state.
A forced restart can lose unsaved data and, in rare cases, leave a database needing recovery. Only use it when a clean restart is not possible, and avoid doing it during large file copies or database writes.
If the server keeps freezing, restarting only treats the symptom. Look for the cause once you are back in: check memory, disk space and recent changes.
Check it works
- The status on the service page shows the server as running again.
- Test that it answers on the network. On a Linux VPS, from your own computer:
ssh [email protected]- On a Windows server, test the RDP port from PowerShell on your own computer:
Test-NetConnection 203.0.113.10 -Port 12230TcpTestSucceeded : True means Remote Desktop is reachable.
- Once logged in, confirm when the server last booted. On Linux,
uptime -sprints the boot time. On Windows, run(Get-CimInstance Win32_OperatingSystem).LastBootUpTimein PowerShell.
Troubleshooting
- The server shows as running but you cannot connect: wait two more minutes, as services may still be starting. Then open the browser console from the control panel to see what the screen shows.
- The power action fails or reports an error: refresh the page and try once more. If it still fails, open a ticket with the service name and the exact message.
- Windows shows "Getting Windows ready" after a restart: updates are being installed. Do not restart again. Watch progress in the browser console and let it finish.
- The server freezes again soon after every restart: something is using up memory or disk. Check resource use once you are in, or ask support to take a look.
Next steps
- Know what to check before you reach for the reboot button: Server not responding? First checks before contacting support.
- Learn when to use the browser console instead of SSH or RDP.
- Windows users: Restart a Windows VPS from the control panel and console.
- Need a clean start? Reinstall the OS from the control panel.
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
Getting started
Edit files with nano: a beginner's guide
Open, edit, search and save files with the nano text editor on a Linux server, including cutting and pasting lines, showing line numbers and safely editing system config files with sudo.
- Beginner
- Linux VPS
- 5 min read
Getting started
Your first hour with a new RunRacks server
A step-by-step roadmap for the first hour after your RunRacks server is delivered, from finding your login details to changing the password, updating the OS and picking your next guides.
- Beginner
- All
- 5 min read
Getting started
How to choose a server location
Pick a data center location based on where your users, broker or team are, confirm it with ping tests, and weigh the legal and latency points that come with each choice.
- Beginner
- All
- 4 min read