Troubleshooting
Start with the logs:
cd /opt/game-panel docker compose ps docker compose logs --tail 100 master
On a node: journalctl -u game-agent -n 100.
Installation
“port 80 (443, 4222) is already in use” — another web server or NATS runs on the server. Stop it, or pass --skip-checks if you know what you are doing.
“the domain doesn't resolve / resolves to another address” — the A/AAAA record doesn't point to this server yet. Behind NAT or a 1:1 IP the warning is expected; answer “yes” or pass --skip-checks.
“the archive's SHA-256 is …, expected …” — the download is damaged or the command is from another release. Copy the command from Downloads again.
Download fails with 403/404 — the link was reissued or the account has no active license. Check Licenses and copy a fresh command.
“Master didn't become healthy” — see docker compose logs master; the most common cause is a broken docker-compose.override.yml or a manual edit of .env.
Certificate
The browser warns about the certificate — Let's Encrypt hasn't issued it yet. See docker compose logs certbot: usually the domain doesn't point to the server or port 80 is closed. Attempts repeat every 15 minutes.
Sign-in
Lost the setup link — sudo grep SETUP_TOKEN /opt/game-panel/.env, see First sign-in.
“Too many attempts” — failed sign-ins block the e-mail and IP address for a while. Wait and try again.
License
The panel's System → License page shows the last renewal error:
- Unknown key — the key was replaced; enter the current one from Licenses.
- License inactive — the subscription has ended or the license was revoked; renew it.
- No free installation slots — the license already serves as many panels as it allows; free a slot in Installations or buy one more.
- Another installation already uses this domain — delete or unlink the old installation in Installations.
- Can't reach the portal — the panel needs outbound HTTPS to this portal. The panel keeps working on its last file for up to 7 days.
- A trial was already used — one trial per account; choose a plan.
Nodes
The node doesn't appear — the node must reach https://<panel domain> and port 4222 of the panel. A join token works once; issue a new one. Check the license limit on nodes.
The node is offline — systemctl status game-agent on the node; check the time on the node (certificates fail with a wrong clock) and the firewall to port 4222.
“Update the agent” — the node's agent is older than the panel; see Updates.
Game servers
“Server creation is temporarily unavailable” — this is what customers see when the license limit is reached or the panel is locked; administrators see the reason in a banner.
A server doesn't start — open the server's console and the job list in the panel; check that the node has free resources and ports.
Still stuck
Open a ticket in Support and attach:
- the panel version (shown in Installations);
- the output of
docker compose psand the last 200 lines ofdocker compose logs master; - for a node —
journalctl -u game-agent -n 200.
Remove passwords and keys from the logs before sending.