A tour of the RunRacks Dashboard
A quick tour of the RunRacks Dashboard, where you find your servers, login details, power controls, invoices, support tickets and RunRacks AI.
- Beginner
- All
- 5 min read
The RunRacks Dashboard is where you manage everything you buy from us: your servers, their login details, power controls, invoices and support tickets. This tour walks through each area so you know where to look when you need something. It takes about ten minutes to read, and you can follow along in a second browser tab.
Before you start
- A RunRacks account. If you do not have one yet, you create it when you place your first order on Pricing.
- You are signed in. Open /dashboard in your browser. If you are not signed in, you are sent to the login page first.
- At least one active service helps, but you can explore billing and support without one.
The overview page
The first page you see after signing in is the overview. It gives you a short summary of your account at a glance:
- Active servers: how many services are running.
- Unpaid invoices: anything that needs payment, with a hint when a payment is due or overdue.
- Open tickets: support conversations that are still in progress.
- Announcements: news from RunRacks, such as planned work or new features.
Treat this page as a status board. If every number looks as you expect, there is usually nothing to act on. If an invoice is due or a ticket has a reply, open it from here.
The menu on the left (or behind the menu button on a phone) takes you to every other section. You can also use the quick search in the menu to jump straight to a page by name.
Services: your servers
The Services list shows every server on your account. Each row shows the service name, its IP address, its status, the next due date and the price.
Click a service to open its details page. This is where you spend most of your time:
- Login details. The IP address, username and password for the server. The password is hidden until you click Show, and you can copy each value.
- Power controls. Start, stop or reboot the server directly from the service page.
- Open control panel. Opens the server control panel, which holds the power controls, OS reinstall and the browser console.
The browser console gives you a screen and keyboard for the server inside your browser. It works even when SSH or Remote Desktop does not, so it is your way back in after a firewall mistake.
An OS reinstall wipes the server's disk. Back up anything you need before you use it.
Billing and invoices
Open /invoices to see every invoice on your account. You can filter by Paid, Unpaid and Cancelled. Each invoice shows its date, due date, total and status.
Click an invoice to see its line items, totals and the payment options. Unpaid invoices can be paid from that page. Paid invoices stay in the list as your billing history.
The account area also holds your billing profile, saved payment methods and contacts. Keep them up to date so invoices and replies reach the right people.
Support tickets
The Support section lists your tickets with their status, such as Open, Answered or Closed. To start a new conversation, go to /tickets/new, choose the department and the related service, and describe the issue.
When support replies, the ticket shows as answered. Open it to read the reply and respond in the same thread. This keeps the full history in one place, which helps if a different engineer picks it up later.
RunRacks AI
RunRacks AI answers questions at any time. Use it for setup questions ("how do I open a port on Ubuntu?") or to understand an error message. For anything that needs someone to look at your account or your server, open a ticket instead.
Account and security
The account area covers your profile, contacts and security settings. In Security you can change your password, set up two-factor authentication with an authenticator app and change the email you sign in with. Spend five minutes here after you sign up. Secure your RunRacks account explains each option.
Check you can find everything
Run through this short checklist to confirm you know your way around:
- Open one service and reveal its password, then hide it again.
- Find the Open control panel button on the same page.
- Open /invoices and find your most recent invoice.
- Open the Support section and see whether you have any tickets.
- Open RunRacks AI and ask it a simple question.
If you managed all five, you know the Dashboard well enough for daily use.
Troubleshooting
- You are sent back to the login page: your session has expired. Sign in again, and check that your browser is not blocking cookies for the site.
- A new server is not in the Services list yet: the order may still be awaiting payment. Check /invoices for an unpaid invoice.
- The password field says it is not available yet: the server is still being set up. Wait a few minutes and refresh the page.
- The control panel does not open: allow pop-ups for the site, then try again. If it still fails, open a ticket.
Next steps
- Get your login details and connect: Find your server IP, username and password.
- Learn what each power button does: Start, stop and restart your server from the control panel.
- Follow the first-day checklist: Your first hour with a new RunRacks server.
- Need another server? Compare plans on Pricing.
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