What is a game server control panel?
A control panel is the web interface that runs your game server: power buttons, a live console, files, backups, schedules and resource graphs, without you ever touching a command line.
6 min read · Updated Oct 21, 2026 · By GuavaHost Team
The problem a panel solves
A game server is just a program running on a machine in a data centre. Without a panel, managing it means logging into that machine over SSH (a text-only remote shell), finding the right folder, starting the program inside something that keeps it alive when you disconnect, reading log files by hand, editing configs in a terminal editor, and remembering a different set of commands for every game you run.
All of that is learnable, and none of it is what you wanted to spend your evening on. A panel puts the same jobs behind buttons and a text editor in your browser, so changing a world setting takes thirty seconds instead of a tutorial.
What every decent panel gives you
Power control. Start, stop and restart the server, plus a force stop for when the process has hung and will not shut down politely. Crucially, the panel keeps the server running after you close the tab. See starting, stopping and restarting.
A live console. The console is the server's running commentary: startup messages, players joining and leaving, warnings, plugin output and, when something breaks, the error that explains it. A command box at the bottom sends commands straight to the server, which is how you op a player, ban someone or save the world on demand. Using the console command box covers the mechanics and reading logs and crash reports covers making sense of the output.
A file manager. Browse the server's folders, open a config file and edit it in the browser, upload a world or a modpack, unpack a .zip without a shell, and move things around. This is where server.properties, a Rust config or an ARK .ini lives. Editing configs in the file manager goes through it, and for anything big, SFTP is the better route.
Backups. A snapshot of every file on the server as it is right now, taken on demand or on a schedule, and restorable when something goes wrong. This is the feature people wish they had used before the thing that happened. Backups explains the mechanics and building a backup plan explains how often is often enough.
Schedules. Automatic jobs on a timer: a nightly restart, a daily backup, a console command before a wipe. Scheduling automatic restarts is the common case.
Sub-users. Let a co-owner or a moderator into the panel with only the permissions they need, so a moderator can use the console without being able to delete the server. See adding sub-users and least-privilege staff permissions.
Resource graphs. CPU, memory and storage over time, which is how you tell "we need more RAM" from "our plugins are too heavy". Reading the resource graphs covers what each line means, and CPU vs RAM covers which one you are actually short of.
An activity log. Who did what, and when. Invaluable when two people share a server and one of them changed something. See the activity log.
Panel versus SSH: an honest comparison
| Control panel | Raw SSH | |
|---|---|---|
| Learning curve | Minutes | Hours to days |
| Risk of breaking the box | Low, you only touch your server | High, one bad command and it is gone |
| Day to day admin | Faster | Slower |
| Editing a config | Click, type, save | Learn an editor first |
| Unusual or custom software | Limited to what the panel supports | Anything you like |
| Sharing access safely | Built in, per permission | Requires setting up users yourself |
| Watching several servers | One list | One session each |
The honest summary: SSH wins on total freedom, a panel wins on everything else. If you are running a community server for a game the host supports, a panel is not a compromise, it is the better tool. If you need to run arbitrary software of your own, that is a different product, and our guide on what a dedicated game server is explains where that line sits.
What runs underneath
GuavaHost's panel is built on Pterodactyl, the open-source game server management software that a large part of the hosting industry uses. Pterodactyl handles the parts that have to be right: each server runs isolated with its own files and its own resource limits, and the console, file access and power controls are hardened rather than handed straight to the machine.
What you see is GuavaHost's own panel on top of it, at customer.guavahost.com, which adds billing, plan changes, region transfers, per-game tools (such as Wipes for Rust, or Version and Plugins for Minecraft) and a single place for every server on your account.
There is also the classic game panel at panel.guavahost.com, which older accounts may have used before the customer panel existed. Logging in to the game panel covers which one you want and how sign-in works between them.
Finding your way around
Everything above lives on your server's page. Sign in at customer.guavahost.com, open My servers and click Manage. The tabs across the top are Overview, Console, Files and Settings, and the menu down the side holds Backups, Scheduled tasks, Manage plan and the rest.
Two guides take you through it properly:
- The panel tour walks every page of a server and says what each one is for.
- Getting around your new control panel is the wider tour, including billing and your account.
If you are brand new, read the panel tour first and then poke around. Nothing on those pages is destructive without asking, and when you are about to do something that is (a reinstall, a restore, a world reset) take a backup first and you have a way back.
Common questions
Do I need to keep the panel open for my server to stay online?
No. The server runs on the machine in the data centre, not in your browser. The panel is just a window onto it, so you can close the tab, shut your computer down and the server keeps running and keeps your players online.
Can I still use SSH or a command line if I want to?
You get file access over SFTP, which covers moving files and folders around with your own tools, but not a shell on the host machine. That is deliberate: it is what keeps every server on a machine isolated from the others. Anything the console cannot do, ask the team about rather than assuming you need a shell.
Is a panel slower than running the server myself?
No. The panel is a management interface, not something sitting between players and the game. Your server talks to players directly on its own port, and the panel uses no meaningful resources while you are not looking at it.
Can two people manage the same server?
Yes, and it is the right way to do it. Add each person as a sub-user with their own login and only the permissions they need, instead of sharing one password. The activity log then shows who did what, which saves a lot of guessing later.
Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.
- panel
- console
- files
- backups
- getting-started
Still need help? Our team is online 24/7 to answer questions.