Troubleshooting

Common issues and what to check.

Stuck on "Waiting for first contact"?

The mod's first heartbeat lands about a minute after the server finishes booting, so give it a minute or two before you start digging. If it still hasn't flipped, work down this list in order — the first two catch nearly every case.

1. Is @SentinelEnforcer in -serverMod=? Not -mod=. It's server-only code; loaded as -mod= the engine treats it as a client mod and the mod never starts.
2. Is config.json in the server profile directory? The mod reads <server profile>/SentinelEnforcer/config.json — in mod terms $profile:SentinelEnforcer\config.json. A copy inside the mod folder is never read, and the server boots with no token at all.
3. Read the script log. Open your server's .RPT and search for [Sentinel]. Three lines settle it.

Setup is complete — the token decoded and was applied (a server that registered itself also prints this from its second start; if you never added this server on dayz.fyi, claim it with its code instead):

[Sentinel] Using saved credentials from config.json - server_id=<id>. Added this server on dayz.fyi? Setup is complete - no claim code needed.

Mod v0.23.0 and newer print that line. On older versions the success confirmation reads [Sentinel] Bootstrap token decoded; using credentials from token. server_id=<id> instead — same meaning.

The token is malformed — on v0.23.0 and newer these two lines arrive as a pair; older versions print only the first:

[Sentinel] WARNING: BootstrapToken doesn't start with 'sntl_v1.' — ignored.
[Sentinel] WARNING: the BootstrapToken in config.json was NOT applied (reason on the line above). Self-registration does NOT run while that field is non-empty - fix the token or clear the field, then restart.

The second line is the one that catches people out. A bad token does not quietly fall back to the claim-code path: the mod skips self-registration for as long as BootstrapToken holds anything at all, so instead of printing a claim code the server just sits silent. Re-copy the whole sntl_v1.… string from your setup page (a truncated paste is the usual cause), or empty the field to let the server self-register, then restart.

One token, two servers?

A token belongs to exactly one server. Copying a server's profile directory to a second box copies the credential along with it, so both boxes report as the same server and their stats interleave into one record. Your dashboard flags this on the server's setup panel.

The fix is to give the second box its own entry: hit Add server on your community page, then paste that server's token into its config. Each server needs its own entry — there's no way to share one.

My server shows 0 online / last heartbeat "never"

Population and last-seen refresh automatically about once a minute. If they read empty, the server most likely isn't reporting yet — give it a minute or two after boot and confirm the mod is loaded. To pull them immediately, use Request resync (owners only) under Ops → Settings → Sentinel administration. "0 online" with a recent heartbeat just means nobody's connected.

My server shows a placeholder name (not its real name)

The real name comes from dayz.fyi reading your server's Steam query — set steamQueryPort in your serverDZ.cfg (DayZ's default is 27016) and restart. Until then, just set the name yourself under Edit settings. On a multi-server box, give each a distinct steamQueryPort.

The mod isn't reporting

• Confirm the mod is in your -serverMod= load order (not -mod=) and the server restarted.
• Confirm the sntl_v1.… token from your setup page is in <server profile>/SentinelEnforcer/config.json, and check the .RPT for the [Sentinel] lines above — a token that doesn't decode is the common cause.
• Only if you never pasted a token: the server registers itself on first boot and writes a claim code instead. That's the fallback path, not the normal one — see Claiming a server.
• Rotating your dayz.fyi install token (stk_…) does not affect reporting — that's your ownership credential, not the mod's sntl_v1.… reporting credential. Don't paste it into the mod config.

I can't claim — "already claimed"

The server is owned by another account. Log in as that account, or rotate the token from the owning account to take it over.

Discord login fails

If the login round-trips but errors on return, the dayz.fyi admin may still be finalizing the OAuth setup — ping us on Discord.