Troubleshooting
Work top to bottom — the checks are ordered by how often they turn out to be the answer.
First: is it you or us?
Section titled “First: is it you or us?”Check status.cerebrust.xyz before digging into your server. If the platform is degraded, the plugin will recover on its own once it is back.
“CerebRUST ingest initialized.” never appears
Section titled ““CerebRUST ingest initialized.” never appears”Nothing about CerebRUST in the console at all
Section titled “Nothing about CerebRUST in the console at all”The plugin is not loading. Check:
- The file is at
oxide/plugins/Cerebrust.cs, spelled exactly that way - It is the
.csfile, not a zip or a renamed copy - Oxide is actually installed and loading other plugins
- Look for a compile error in the console — usually means a truncated or edited download
Re-download the file and try again.
It loads but complains about the token
Section titled “It loads but complains about the token”The IngestToken in oxide/config/Cerebrust.json is empty, malformed, or wrapped in whitespace.
A token starts with crst_.
Check the JSON is valid too — a missing comma or quote and Oxide falls back to defaults.
HTTP 409
Section titled “HTTP 409”The token is bound to a different server. A token locks to the first IP : game port : query port that uses it.
You will hit this if you have:
- Migrated to a new host or been reassigned an IP
- Changed your game or query port
- Reused a token from another server
The bind has to be cleared on our side — ask in Discord. Reinstalling the plugin will not fix it. See Get an ingest token.
HTTP 401 or 403
Section titled “HTTP 401 or 403”The token is not recognised. Check for a copy-paste error — a truncated token or a stray space is the usual cause. If it looks right, ask in Discord.
Timeouts, or no HTTP response at all
Section titled “Timeouts, or no HTTP response at all”Your server cannot reach the API. Confirm outbound HTTPS to api.cerebrust.xyz on port 443 is
allowed, and that DNS resolves from the server. Managed hosts sometimes firewall outbound traffic
by default.
It worked, then stopped
Section titled “It worked, then stopped”Give it two minutes first. The plugin pauses a failing endpoint and retries with a backoff of up to two minutes, replaying anything it queued. Brief outages heal themselves — you do not need to reload.
If it stays down, set verbose_logging to true, reload, and read what the plugin says it is
doing. Turn it back off afterwards — it is extremely noisy.
The map is blank
Section titled “The map is blank”Almost always the expected behaviour, not a fault.
The map image only uploads when no players are online. It is a big upload, so the plugin waits for the server to be empty. On a busy server that can mean waiting for a quiet period or a restart.
Markers still work in the meantime; they just have no background to sit on. A new map is only uploaded when the world changes — i.e. at wipe.
Player markers are offset from the map
Section titled “Player markers are offset from the map”Alignment is calculated from your world size and needs no configuration, so a small offset should not happen. If you see one, the map image is most likely from a previous wipe — check it has re-uploaded since your last wipe.
If it persists on a freshly uploaded map, that is a bug worth reporting rather than something to tune at your end.
Tool cupboards are missing or stale
Section titled “Tool cupboards are missing or stale”Cupboards are snapshotted every five minutes, so a very recent one may not have been picked up yet. Placement, destruction and auth changes report immediately; upkeep figures move on the five-minute cycle.
If a cupboard never appears, confirm the player is actually authorised on it — the list is built from cupboard auth lists.
The leaderboard has not moved
Section titled “The leaderboard has not moved”It compiles on a schedule, roughly hourly, rather than live. Kills and gathers are recorded as they happen and appear in the standings at the next compile.
A settings change did not apply
Section titled “A settings change did not apply”Settings reach your server on the next heartbeat, within 15 seconds. If a change has not taken after a minute:
- Confirm the server is still ingesting (is the player count live?)
- Confirm you saved the change on the right server
- Do not edit
plugin_settings_cachein the config by hand — it is overwritten from the dashboard, and hand edits are lost
If a mod toggle specifically will not apply, o.reload Cerebrust and report it in Discord — toggles
are meant to work live and that is a bug worth knowing about.
A gameplay feature is behaving oddly after a Rust update
Section titled “A gameplay feature is behaving oddly after a Rust update”Start with furnace boost — see Updating the plugin. It replaces Rust’s smelting loop and is the most likely casualty of a monthly update.
Turn the feature off in the dashboard to get back to vanilla behaviour immediately, then report it.
Still stuck
Section titled “Still stuck”Ask in the CerebRUST Discord. Bring:
- Your plugin version (from the load line in your console)
- What you expected and what happened
- Relevant console output, with
verbose_loggingon if you can
Never paste your ingest token. If you think you have leaked it, say so and ask for a replacement.
