Troubleshooting

Each entry links to the doc that covers the feature. If your problem is not here, write to [email protected].

Pairing and connection

The plugin says pairing failed. The claim token was already used or regenerated. In the dashboard, click New claim token, paste it into config.yml again, and restart. Steps: install the agent plugin.

The server is stuck on "waiting for agent". Check the server console for MCTotem lines. The server needs outbound HTTPS to mctotem.app; some hosts block outbound traffic by default. Details: install the agent plugin.

You removed a server in the dashboard, re-added it, and the agent never reconnects. Set the new claim token in config.yml and restart; on agent 0.1.2 or newer that is all it takes. Older agents keep using the old revoked credential and log "cannot reach" warnings that are really authentication rejections; on those, also clear the agent-token line before restarting, or better, upgrade the jar first.

The dashboard warns the agent plugin is outdated. Download the new jar from the link in the warning, replace the old one in plugins/, and restart. No new claim token is needed; the existing pairing carries over.

Saving a join address asks whether the port is right. The agent reports which port your server listens on, and the address you entered uses a different one. That is legitimate when your host or router forwards ports, so it asks rather than refuses. If you did not mean it, use the port your server actually listens on. Details: the test player.

Pterodactyl connects but shows no TPS or player counts. That is a panel API limitation, not a fault. Those two metrics need the agent plugin. Details: connect via Pterodactyl.

The test player

A test is refused with "not in this server's test commands". The test player only runs commands you listed. The refusal names the command; add it in Test commands on the server page, with what a successful reply looks like, and run the test again. Details: test commands.

A command is listed but the test says the test player could not see it. The test player joins as an ordinary player with no permissions. Grant the command's permission to the test player's account (or to everyone, if that is what you intend) and run another test. Details: test commands.

A command exists in game but never appears under "commands found on your server". Plugin descriptors only list commands declared up front. Commands registered while the server runs, from Skript and similar, show up after the test player has joined once, or you can add them by hand.

A test passes but did not really check anything. A command with no "success looks like" text is sent and never verified. Add the text the server replies with, and the test waits for it.

Diagnoses

The Log Doctor found no error in my log. The paste may not include the failure. Paste the full latest.log or the crash report from crash-reports/, including the lines before the error. Details: Log Doctor.

A diagnosis was wrong. Vote no on it. Three no votes flag it for automatic re-analysis, and your vote stops it being shown as confident to the next person. Details: reading a diagnosis.

"Deep analysis limit reached." Novel errors use a per-day budget that depends on your plan; known-issue matching keeps working regardless. Limits: plans and billing.

Discord

Slash commands do not appear. The bot must be invited with the applications.commands scope. Re-invite it with the link in the Discord bot setup steps; existing links survive a re-invite.

/status says no server is linked. Links are per-channel and codes expire after 15 minutes. Run /link with a fresh code in the channel you actually want. Details: Discord bot.

"Approving changes needs a MCTotem account." Commands that change your server need your Discord account connected to your MCTotem account, so the audit log names a person. Run /link-account and open the one-time link. Details: who can use which command.

Your account is connected but a command still refuses. Either the connected account has the viewer role in that organization, which reads but does not act, or it is not a member of the organization that owns the linked server. An owner can change the role in the dashboard.

That Discord account is already connected to another MCTotem account. One Discord account maps to one MCTotem account. Disconnect it on the other account first, under Connect Discord in the dashboard.

Actions

An action never ran and now shows expired. Actions expire 10 minutes after signing by design; approve again to get a fresh one. Details: how actions work.

Actions are enabled but nothing executes. Check the kill switch in the Action center; every server starts paused. Details: the safety model.

A config edit made things worse. Every config edit takes a backup first; use one-click rollback in the Action center. Details: the safety model.