Get Started

First sign-in

At the end the installer prints a link to the setup wizard:

https://panel.example.com/admin/setup?token=…

Open it in a browser. The wizard has three steps.

1. Administrator

Enter the first administrator's e-mail and a password of at least 8 characters. You are signed in right away, and the setup link stops working — the token only protects the panel until the first user exists.

2. License

The panel can't be managed without a license. Choose one:

  • License key — a key like GPL-XXXX-XXXX-XXXX-XXXX from Licenses and the panel's domain.
  • 10-day trial — sign in with your account on this portal or create one right in the wizard. One trial per account. The password goes only to the portal; the panel doesn't store it.

If your portal account has two-factor authentication, the wizard can't sign in with it: take the trial key in Licenses and enter it as a regular key.

The panel server needs outbound HTTPS to this portal. Without it, use an offline license file (see Licensing).

3. Panel

The panel name, time zone and logo. You can skip this step and change everything later in Settings.

The token is in .env:

sudo grep SETUP_TOKEN /opt/game-panel/.env

Open https://<domain>/admin/setup?token=<value>. A wrong token counts as a failed sign-in, and repeated failures block the IP address for a while.

If the panel was installed without the installer and SETUP_TOKEN isn't set, Master generates a one-time token at start and writes the setup link to its log while there are no users:

docker compose logs master | grep setup

What to set up next

The Panel setup checklist on the Overview page links to every step:

  • S3 storage (Modules → Backups and S3 storages) — for game server backups, panel backups and add-on files. No S3 of your own — enable the built-in MinIO (see S3 storages).
  • A node — see Connect a node.
  • A game in the catalog (Games) — container image and launch parameters, see Game catalog.
  • A plan (Plans) — resources and limits you sell to customers.
  • A billing webhook (Webhooks) — panel events for your billing system.

The checklist disappears when everything is done; Hide removes it earlier. Step by step to a running server — Your first game server.