Claim code invalid, expired or already used

Claim codes work once and last 30 minutes. How to get a new one, and what wrong_game and a key rejected after moving hosts mean.

TroubleshootingUpdated 2 min read

A claim code looks like SS-XXXX-XXXX-XXXX. It is single use, expires after 30 minutes and is shown once.

Invalid

Usually a typo or a missing part. Copy the whole code. The match is forgiving about case, dashes and spaces. A code belongs to one dashboard server: use the code of the server you created for this install.

Expired, used or revoked

Open the server's Settings (the General tab) and click New claim code, then claim again. A refused code is reported once and not retried automatically.

"wrong_game"

The game you picked for the server differs from the agent's game. FiveM and RedM are separate. Create the server again with the right game. This does not use up the code.

Too many attempts

Enrolment allows 10 attempts per address, then 2 a minute. Wait a minute.

Key rejected after moving hosts or restoring a backup

Claiming again, with a new code, replaces the stored key at once, so an older install of the same agent stops being accepted. The old agent keeps buffering and re-checks every 10 minutes. To move a server to a new machine: create a new claim code, claim on the new machine, and stop the old agent. To resume a rejected agent: claim with a fresh code.

Where to type it

The claim command is per game, for example serverstats claim SS-XXXX-XXXX-XXXX on Paper, serverstats.claim on Rust, /serverstats claim on Hytale, or serverstats claim in the FiveM console. See troubleshoot by game.

Questions

Can I reuse a claim code on a second server?

No. A code works once and decides which dashboard server the agent becomes. Create one code per server.

Will re-claiming lose my history?

No. Re-enrolling replaces only the agent's key. The server keeps its history, and the agent sends anything it buffered.

Still stuck? Email [email protected] with the server name and what you see. For a rejected claim code or no data, include the output of the agent’s status command.