Verify it is working
Check the connection
Run /thorium status. A healthy server reports the plugin version, the server
software, that the connection is up, and that telemetry is flowing.
The dashboard agrees: on the network’s Servers tab a connected server shows Connected. The setup checklist on your dashboard disappears once any server in the network has connected.
When it will not connect
| Symptom | Cause | Fix |
|---|---|---|
401 in the server log | The token is wrong or was rotated | Re-copy the token from Set up plugin |
404 / unknown_server_name | server-name does not match a server on the network, or the server was deleted | Fix server-name, or add the server in the dashboard |
400 / missing_server_name | server-name is empty | Set it to the server’s name from the dashboard |
402 / no_plan | The network has not been through checkout yet | Choose a plan, Free included, under Billing |
402 while another backend is connected | The Free plan covers one connected backend | See plans and billing |
4422 close code | The plugin is older than the minimum supported version | Download the current release |
| Connects, then drops | Outbound WebSocket traffic is being blocked | Allow outbound 443 to gateway.thorium.ac |
First detections
Detections appear under Detections in the dashboard, with the player, the check that fired, a confidence score and the captured evidence.
There is deliberately no “send a test detection” button: a synthetic alert would land in your real detection history, skew your counts and could fire your alert webhook at staff who are not expecting it. Connection status answers the same question without writing fiction into your data.
If you want to see a detection end to end on purpose, use a test server, a spare account and a cheat client you control — never a production network.