Get an ingest token

An ingest token is the credential your server uses to identify itself to CerebRUST. It looks like this:

crst_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

One token, one server.

How to get one right now

Sign in and open Server access from the Owner tools menu. Every token on your account is listed there with its status and the server it is bound to, and there is a Copy button beside each one. That is the page to start from however you came by the token.

Payments are not open yet

The checkout on that page is not taking real payments — live card processing has not been switched on. Until it is, ask in the CerebRUST Discord: tell us the Steam account you sign in with and roughly what your server is, and we will put a token on your account. It appears on Server access like any other, and it keeps working when billing goes live.

How binding works

A fresh token is unbound. The first time your server calls in, the token locks to that server — specifically to its IP : game port : query port.

From then on:

• That token only works from that address. A copy pasted onto a second server is rejected.
• The server is linked to the account that the token was issued for, and shows up under My servers in the dashboard.
• The bind also creates the server’s first wipe record, which is what all telemetry is scoped to.

This is why you cannot share a token between servers, and why a token that has been used somewhere else will not work for you.

If your server address changes

Because the token is bound to IP : game port : query port, changing any of them breaks the bind and you will see a 409 error in your server console.

Common causes: migrating hosts, a provider reassigning your IP, or changing your query port.

Ask in Discord and the bind can be cleared or reissued. Don’t reinstall the plugin hoping it clears itself — it won’t, and the rebind has to happen on our side.

Multiple servers

You need a separate token per server. Each one appears in the dashboard as its own server, with its own settings, staff, map and leaderboard.

Keeping it safe

Treat it exactly like a password:

• Never paste it into a screenshot, a public channel or a support message
• Never commit oxide/config/Cerebrust.json to a public repository
• If it leaks, ask for a replacement — a leaked token lets someone submit fake telemetry as your server

Where the token goes

On most servers it goes into oxide/config/Cerebrust.json — see Install the plugin.

On a Pterodactyl server running the CerebRUST edition of the Rust egg it goes into the CerebRUST Ingest Token field on the Startup tab instead, and the panel writes it into that file on every start. There, the panel field is the source of truth and editing the file by hand does not stick.

Next

Install the plugin and drop the token into your config.