---
title: My Servers
description: "**My Servers** is the control surface for game and application servers bought from your provider. It gives you power controls, live resource graphs, a console, SFTP details and — where your provider allows it — the server's startup configuration. Two…"
url: "https://rackhelm.com/documentation/my-servers/"
updated: "2026-09-24"
category: "Client Portal: Managing Your Services"
---

# My Servers

**My Servers** is the control surface for game and application servers bought from your provider. It gives you power controls, live resource graphs, a console, SFTP details and — where your provider allows it — the server's startup configuration. Two panel types are supported and each gets a slightly different page, so this article covers both.

## Before you start

The **My Servers** sidebar entry appears when your account has an active game-server package on the Pterodactyl panel. If your server runs on GameCP the sidebar entry may not appear; reach it through **My Services → All Services** or go to `/servers` directly.

A server only opens once it has finished being set up. Until then it appears on the All Services list with a **View Status** button instead.

## The server list

![The My Servers list with live status badges and Manage buttons](/wp-content/uploads/rackhelm-docs/portal-services-servers-index.png)
The status badge on each row is fetched live from the panel when the page loads.

`/servers` lists fifteen servers per page with four columns: **Details** (the product name), **Status**, **Resources** (the CPU percentage and memory allowance in MB recorded on your package) and **Actions**.

The status badge starts as a spinner and is then replaced with the live state read from the panel: *Running*, *Online*, *Starting*, *Stopping*, *Offline*, *Suspended*, *Installing*, *Failed* or *Error*. If the portal cannot reach the panel the badge reads *Error*; the server itself may well be fine.

## Power controls

The buttons at the top right of the server page send a signal to the panel and report the result in the console pane rather than reloading the page.

| Button | What it does |
| --- | --- |
| **Start** | Boots the server. |
| **Restart** | Stops and starts it again. |
| **Stop** | Asks the server to shut down cleanly. |
| **Kill** | Terminates the process immediately. Asks you to confirm "Force Kill? This may corrupt data." Use it only when Stop has not worked. |

The cog button next to them holds **Reinstall Server** and, while the service is active, **Cancel Service**.

> **Warning:** **Reinstall Server** re-runs the panel's install script over the server's disk. All data may be lost. It asks you to confirm and then asks for your account password before it runs. Take a backup first.

## Console & Stats

![The server console tab showing CPU, memory, disk and network cards above a live terminal](/wp-content/uploads/rackhelm-docs/portal-services-server-console.png)
The four metric cards and the terminal update live over a websocket to the node.

The first tab shows four metric cards — **CPU Load**, **Memory**, **Disk Usage** (with uptime underneath) and **Network (I/O)** — above the terminal, and three rolling charts below it: **CPU History**, **Memory History** and **Network History**. Each chart keeps the last 60 samples. Where your package sets a limit, the CPU chart is scaled to that limit and unlimited disk or memory shows as `∞`.

The terminal streams console output with its colours preserved. It scrolls automatically until you scroll up, at which point a round button appears in the corner to jump back to the bottom. Type into the **Type a command…** box and press Enter to send a command to the server; failures are printed back into the console as `[System] Command Failed: …`.

Lines beginning `[System]` are generated by the portal, not by your server — they report power actions, connection problems and installation progress.

## Startup & Configuration

The second tab is where you connect over SFTP and adjust how the server starts. How much of it you see depends on what your provider enabled for the product; a card you have no permission for is simply not rendered.

| Card | Contents |
| --- | --- |
| **SFTP Details** | **Host Address**, **Port** (2022 unless your provider changed it) and **Username** in the form `panel-username.server-id`. The password is your panel password, not your portal password. |
| **Service Configuration** | **Nest** and **Egg** selectors — the game or application the server runs — plus a checkbox to skip the install scripts. Saving this reinstalls the server, so it goes through a red confirmation dialog and then asks for your password. |
| **Docker Image** | The container image the server runs on, listed from the images the selected egg offers. **Update Image** applies it. |
| **Startup Command** | The command line the server boots with. **Save Command** applies it; **Restore Default** puts back the egg's own default. |
| **Startup Variables** | One box per variable, each with its own **Save** button, the variable's environment name, its description and the validation rules it must satisfy. Variables your provider locked are shown greyed out. |

> **Note:** Changing the nest or egg is a reinstall. Changing a startup variable or the startup command is not — it takes effect the next time the server starts.

## Servers on the GameCP panel

GameCP servers use the same page layout with these differences:

- Power controls are **Start**, **Restart** and **Stop** only. There is no Kill and no in-portal reinstall — reinstalling is done in the GameCP panel.
- The header carries an **Open in GameCP** button that signs you straight into the panel, and the same link appears above the console as **Live console in GameCP** and on the **Server Details** card as **Manage in GameCP Panel**.
- The fourth metric card is **Players** (online now / maximum) rather than Network (I/O), and there are two rolling charts rather than three — **CPU History** and **Memory History**.
- There is no live streaming console. Metrics are polled every 5 seconds and log lines every 6 seconds; the note beneath the input box says "Log output is polled periodically. For the live streaming console, open the GameCP panel."
- The command box sends an RCON command rather than a console command, and the reply is printed back into the pane.
- A **Server Details** card lists the game, the connect address, and the memory, CPU and disk limits.
- **Startup Variables** works the same way, when your provider has enabled it.

## Troubleshooting

| Symptom | Cause / fix |
| --- | --- |
| The console badge stays on *connecting…* and the terminal prints a message ending "Retrying in Ns." | The portal could not obtain a console session. It retries automatically with a growing delay. The panel allows only a handful of console handshakes a minute across the whole portal, so during busy periods a wait of up to a minute is normal — leave the tab open. |
| `[System] Session token rejected, requesting a new one…` | Usually follows a restart of the node your server runs on: every session issued before the restart is refused. The portal asks for a fresh one automatically. If it repeats, reload the page. |
| The console connects but the server shows *Offline* and nothing streams. | The server is genuinely stopped. Press **Start**. |
| Status reads *Installing* and offline messages are ignored. | An install or reinstall is running. The console shows the install output and switches back to *Offline* when it finishes. |
| "Client API Key Invalid" or "Configuration Error" at the top of the page. | The portal's credentials for the panel are wrong or the panel is unreachable. This is a provider-side problem — open a ticket. |
| Saving a startup variable reports nothing changed. | Your provider has not granted permission to edit that field. The value is dropped server-side even if the input looked editable. |
| On a GameCP server, **Open in GameCP** reports "GameCP did not return an SSO login link." | The panel refused the single sign-on request. Try again shortly, or sign in to the panel directly. |