Work down this list. Each step rules out one cause.
1. Look at the First data checklist
In the Add a server wizard, or on the server's Settings page, the First data checklist has three ticks:
- Agent enrolled with its own key not ticked: the claim never succeeded. Go to claim code rejected.
- Enrolled, but First batch received not ticked: the server cannot reach ServerStats, or the agent is not running. Continue below.
- Batch received, but First readings stored not ticked: the server is paused by your plan (paused servers).
2. Run the agent's status command
It prints enrolment, the link state, the last send, the offline buffer, whether the server is paused and moderation state. The command per game is in troubleshoot by game. Read the link line first.
3. Test outbound HTTPS from the game machine
curl -sI https://serverstats.ccIf this fails, the host is blocking outbound HTTPS. Allow TCP 443 out. Some game hosts filter outbound traffic by default; their support can allow it. The agent re-tries on its own.
4. Check the clock
Requests are signed with a timestamp that must be within 5 minutes of ServerStats's clock. Agents correct for a drifting clock automatically, so this matters only when the host clock is far off. If status shows a stale_timestamp error, fix the machine's time.
5. Check you installed the right agent for the right game
The game picked in the wizard must match the agent. Picking FiveM and installing for RedM, or the other way round, is refused with wrong_game. Check the supported versions on Agent versions (wrong version).
6. Restart after editing the config
If you put the claim code in a config file, restart the server or reload the plugin. A code in a file that was never loaded does nothing.
7. Still nothing
Email [email protected] with the server name and the status command output. Do not paste a claim code: they are single-use but treat them like a password until used.