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
Your new server is ready, and the first hour sets the tone for everything that follows. This roadmap takes you from the delivery email to a connected, updated server with a new password. It covers Linux VPS, Windows VPS and Windows Admin RDP, and points you to the right guide for each next step.
Before you start
- Your order is paid and the server shows in Services in your Dashboard.
- A password manager to store new passwords. A notes file on your desktop is not a safe place.
- About an hour, without rushing. Updates can take a while, especially on Windows.
Minute 0–5: find your login details
- Open the Dashboard and go to Services.
- Click your new server.
- Copy the IP address, username and password from the service page. Click Show to reveal the password.
While you are there, find the Open control panel button. It opens the control panel with power controls, OS reinstall and the browser console. You want to know where it is before you ever need it.
Minute 5–15: connect
Linux VPS
From PowerShell on Windows, or Terminal on macOS or Linux:
ssh [email protected]Type yes to accept the fingerprint, then paste the password. Nothing shows on screen while you type it.
Windows VPS or Admin RDP
RunRacks Windows servers use Remote Desktop on port 12230. On Windows, press Win + R, run mstsc and connect to:
203.0.113.10:12230On macOS or a phone, add a PC in Windows App with the same address. Use the exact username from the Dashboard.
Can't connect? Check that the server shows as running, then see Find your server IP, username and password for the details of each step.
Minute 15–25: change the password
The password in the Dashboard was generated for delivery. Change it to one only you know, and save it in your password manager before you log out.
On Linux, as root:
passwdEnter the new password twice. On success you see passwd: password updated successfully.
On Windows, press Ctrl + Alt + End inside the Remote Desktop session and choose Change a password. For more detail, see Change your Windows server password safely.
Test the new password in a second session before closing the first one. If it fails, you can still fix it from the session that is open.
Minute 25–50: install updates
A fresh image may be missing recent security fixes. Install them now, while nothing important runs on the server yet.
Ubuntu and Debian
apt update && apt upgrade -yAlmaLinux and Rocky Linux
dnf upgrade -yIf the kernel was updated, restart with reboot and reconnect after a minute or two.
Windows Server and Admin RDP
Open Settings → Windows Update (on Windows Server 2019, Settings → Update & Security → Windows Update) and click Check for updates. Let it install, then restart when asked. Windows updates can take 20 minutes or more; that is normal.
A restart disconnects you. If you run anything time-sensitive, such as a trading terminal, finish updates before you set it up.
Minute 50–60: plan your next steps
With the basics done, pick a track for what you want the server to do:
- Linux, any use: add a regular user with
sudo, set up SSH keys and turn on a firewall. Linux VPS first steps walks through each one in order. - Windows VPS: review Remote Desktop security and Windows Update settings. Keep the firewall rule for port 12230 in place.
- Admin RDP desktop: install the apps you need and set them to start after a reboot.
- Websites: point your domain at the server. RunRacks does not sell domains, so you manage DNS where you bought the domain.
Also decide now how you will back up your data. Copies stored on the same server do not protect you if that server has a problem.
Check it works
At the end of the hour you should be able to tick all of these:
- You can log in with your new password, and it is saved in your password manager.
- Updates are installed and the server has been restarted if it needed it.
- You know where the browser console is in the control panel.
- You have a written plan for the next step and for backups.
Troubleshooting
- SSH says "Connection refused" or times out: the server may still be booting. Wait two minutes and check its status in the Dashboard.
- Remote Desktop cannot connect: make sure the address ends in
:12230. - You changed the password and lost it: open the browser console from the control panel and reset it from there.
- Updates seem stuck: leave them running for at least 30 minutes before acting. Interrupting an update can do more harm than waiting.
Next steps
- Get to know the rest of the Dashboard: A tour of the RunRacks Dashboard.
- Windows users: follow Windows VPS first steps.
- Questions along the way? RunRacks AI answers at any time, or open a ticket.
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
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
Getting started
Use the built-in OpenSSH client in Windows Terminal
Connect to your Linux VPS from Windows 10 or 11 with the built-in ssh command, create and store keys in your .ssh folder, and add a Windows Terminal profile that opens your server in one click.
- Beginner
- Linux VPS
- 5 min read