Nobody has run /login here, or the link was removed. An admin runs /login account or /login apikey.

The dashboard login is captcha-protected, and a bot cannot solve it. Use /login apikey instead — it links the server with your service API key and is not affected.

Wrong email/username or password, or the account signs in with Google only and has no password set. Google-only accounts must use /login apikey.

The 2FA prompt was left open too long. Run /login account again.

The account owns no service yet. Create one in the dashboard first.

The service's API key was regenerated, or the service was disabled. Re-run /login to store the current key.

The service has an IP allowlist and the bot's host is not on it. Add the bot host's IP under the service's allowed IPs, or clear the allowlist.

The dashboard binds one Discord server to one service. The bot still links locally and works normally — only the dashboard's own binding field is left pointing at the first service.

The key belongs to a different service, or it was mistyped. Check with /lookup key:<value> — that searches both activated and unredeemed keys on the selected service.

The key is bound to another Discord account here. Issue a new one with /whitelist, or free it with /unwhitelist on the account that holds it.

The member never pressed Redeem, or their key expired or was revoked. /lookup user:@them shows what they actually hold.

The key has no device bound yet — there is nothing to reset — or the service's own reset cooldown is still running. That cooldown is configured per service in the dashboard and is separate from the server-side cooldown in /settings hwid.

The member's server-side cooldown. Use /force-resethwid user:@them to bypass it without consuming their next reset.

Lifetime keys have no expiry to extend, so /compensate skips them by design.

Discord only lets a bot manage roles ranked beneath its own. In Server Settings → Roles, drag the bot's role above the buyer role.

Usually the ranking above, or the bot is missing Manage Roles. Re-invite with the default permissions if it was stripped.

The role was deleted. Set a new one with /settings roles buyer:@Role.

The panel row was deleted — usually because its service was unlinked. Post a fresh one with /setpanel.

The bot lacks View Channel or Send Messages in the target channel.

Newly published global commands can take up to an hour to propagate. Fully closing and reopening the Discord client usually surfaces them sooner.

You are neither an admin nor holding the manager role. Ask an admin for /settings roles manager:@YourRole.