What root and administrator access mean on your server

Understand full root access on Linux and Administrator access on Windows, what you can change with them, the responsibilities that come with that control, and safe habits to adopt.

  • Beginner
  • All
  • 4 min read

By RunRacks Team · Published

Every RunRacks server comes with full control: root on a Linux VPS and Administrator rights on a Windows VPS or Admin RDP. That means nothing on the server is off limits to you. This guide explains what that power lets you do, what it makes you responsible for, and the habits that keep it from causing accidents.

Before you start

Your server's username and password are on the service page in your Dashboard. On Linux the first user is often root; on Windows it is an administrator account. Use the exact username shown.

What root means on Linux

Linux has one all-powerful account called root, with user ID 0. Root can:

  • Read, change or delete any file, including system files.
  • Install and remove software with apt or dnf.
  • Start, stop and configure services such as Nginx, MariaDB or SSH.
  • Create users, change any password and set permissions.
  • Change the firewall, network settings and kernel parameters.

Ordinary users are limited to their own files. Many admins work as a normal user and run single commands as root with sudo:

Terminal
sudo apt update

sudo asks for your own password, runs that one command with root rights and records it in the logs. It reduces the chance of an accidental system-wide change. See create a sudo user.

What Administrator means on Windows

On Windows, accounts in the Administrators group can:

  • Install programs and drivers for all users.
  • Change system settings, services and Windows Firewall rules.
  • Manage users and groups.
  • Add Windows Server roles and features on a Windows VPS.

Windows protects administrators with User Account Control (UAC). Even when signed in as an administrator, programs run with normal rights until you approve elevation. To run PowerShell with full rights, right-click it and choose Run as administrator.

What full control makes you responsible for

A self-managed server puts the software side in your hands:

  • Updates: apply operating system and app security updates.
  • Security: strong passwords or SSH keys, a firewall, and only the ports you need open.
  • Backups: make them, keep a copy off the server, and test restoring.
  • Software: install, configure and fix the apps you run.
  • Users: decide who gets access and remove access that is no longer needed.

RunRacks support helps with platform issues such as power, network reachability and reinstalls. See unmanaged vs managed VPS for where the line sits.

Safe habits

  1. Use the least privilege you need. Work as a normal user with sudo on Linux. On Windows, keep UAC on.
  2. Back up before big changes. Copy a config file before editing it, and take a backup before upgrades.
  3. Read commands before you paste them. Especially anything with rm -rf, chmod -R, disk tools or firewall rules.
  4. Change one thing at a time. Then test. It makes problems easy to trace.
  5. Keep a way back in. Before changing SSH, RDP or firewall settings, keep your current session open and test a new one.

Check it works

On Linux, confirm who you are and whether you have root rights:

Terminal
whoami
sudo -l

whoami prints your username. sudo -l lists what you may run with sudo.

On Windows, in PowerShell:

PowerShell
whoami /groups | findstr /i "Administrators"

A matching line means your account is in the Administrators group.

Troubleshooting

  • "Permission denied" on Linux: you are a normal user. Prefix the command with sudo, or check file ownership.
  • "user is not in the sudoers file": the account has no sudo rights. Log in as root and add it to the sudo group (Ubuntu, Debian) or wheel group (AlmaLinux, Rocky).
  • "Access is denied" on Windows: open the tool with Run as administrator.
  • You removed your own admin rights: sign in through the browser console with another admin account, or contact support through a ticket.

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