Unmanaged vs managed VPS: what RunRacks support covers

Learn the difference between managed and self-managed servers, what you control on a RunRacks server, and how RunRacks support helps with platform issues such as power, network and reinstalls.

  • Beginner
  • All
  • 4 min read

By RunRacks Team · Published

Hosting providers describe servers as managed or unmanaged (also called self-managed). The difference is who looks after the software running on the server. RunRacks servers are self-managed: you control the operating system and everything on it, and RunRacks looks after the platform it runs on. This guide explains what that means and where to get help.

Before you start

It helps to know what root and Administrator access are. If you are new to them, read what root and administrator access mean first.

Managed vs unmanaged in general

Managed server

With a managed service, the provider's team handles much of the software: operating system updates, security hardening, monitoring, backups and sometimes the web stack. You get less control and usually pay more.

Unmanaged or self-managed server

You get a working server with an operating system installed and full root or Administrator access. Everything inside the operating system is yours to configure and maintain. You get maximum freedom and, typically, a lower price.

What you control on RunRacks

On a RunRacks Linux VPS, Windows VPS or Admin RDP, you are responsible for the software side:

  • Operating system updates and security patches.
  • Installing and configuring software: web servers, databases, PHP, Docker, trading platforms, desktop apps.
  • Security: passwords, SSH keys, firewall rules, which ports are open, user accounts.
  • Backups: creating them, storing a copy off the server and testing restores. Do not assume backups are included.
  • Your data and apps: fixing app errors, plugin conflicts and configuration mistakes.

You can use the many guides in this library for each of these tasks.

What the platform gives you

Your Dashboard gives you tools to manage the server itself without contacting anyone:

  • The server's IP address, username and password.
  • Power controls: start, stop and restart.
  • OS reinstall for a clean start.
  • A browser console that works even when SSH or Remote Desktop does not.

What RunRacks support helps with

Support helps with problems on the platform side, for example:

  • The server will not power on, or stays stuck in a power state from the control panel.
  • The server is unreachable on the network even though it is running and the firewall inside it is open.
  • An OS reinstall fails or does not finish.
  • Problems using the Dashboard, the browser console or the control panel.
  • Questions about your plan, billing and invoices.

When you are unsure whether something is a platform issue, ask. Open a support ticket or use contact us. For general questions at any time, RunRacks AI at /ai can help you work through a problem or find the right guide.

Check which side a problem is on

Before you open a ticket, run through these quick checks:

  1. Is the server running? Check its status in the Dashboard.
  2. Can you reach the browser console? If yes, the server is up and the issue is likely inside the operating system.
  3. Does the server answer on the network? Test with ping or a port test to SSH or RDP port 12230.
  4. Did anything change recently? Updates, firewall rules, new software.

If the server is running but unreachable from everywhere, and nothing changed inside it, it may be a platform issue: include your checks in the ticket. See server not responding: first checks.

Troubleshooting

  • You locked yourself out with a firewall rule: log in through the browser console and undo the rule.
  • The OS is badly broken: reinstall from the Dashboard after saving any data you can reach. A reinstall erases the disk.
  • You want someone to run the server for you: consider hiring a sysadmin or using a managed service on top of your server.
  • Billing or plan questions: these are always support topics. Open a ticket from the Dashboard.

Next steps

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.

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