Verify it is working

Check the connection

Run /thorium status. A healthy server reports that it is connected, the detection engine version, and the round-trip latency to the gateway.

The dashboard agrees: on the network page a connected server shows a green dot and 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 the server was deleted in the dashboard	Re-copy the token from Set up plugin
402 in the server log	The trial has ended, or the network is over its server allowance	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

Note

A lapsed subscription never disconnects a server that is already running. It stops the next connection — so a restart after expiry is when coverage actually stops.

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 Discord 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.