Bot & Dashboard Errors
Fix bot token, intent, role, /setup, dashboard, custom domain, pull and backup problems with your RestoreCord bot.
Most bot problems come down to three things: an invalid bot token, disabled privileged intents, or the bot's role sitting too low. Find the message or symptom below for the fix. For errors members see on the verify page, see Verification Errors.
Bot status & token
| Symptom | Cause | Fix | Dashboard |
|---|---|---|---|
| “Invalid Bot Token — Your bot token is invalid or revoked.” The bot shows offline and members get error 990401. | The token was reset, or Discord disabled the bot | In the Developer Portal, open Bot → Reset Token, then paste it into the bot's Bot Token setting. If Discord deleted or disabled the bot, see below. | Go to Bots › Bot Token |
| “Privileged intents are disabled” warning on the bot | Server Members Intent or Message Content Intent is off | Click Restart Bot, which turns them on for bots in fewer than 100 servers. If the warning stays, turn both on in Developer Portal → Bot, then click Restart Bot again. Without them, the unverified role, auto kick and join tracking don’t work, and pulls are slower. | Go to Bots › Restart Bot |
| Bot offline; buttons and commands don’t respond | A token or intent problem, or a temporary issue | Click Restart Bot, then check the token and intents. If it’s still offline after 5 minutes, contact support. Web verification keeps working while the bot is offline. | Go to Bots › Restart Bot |
| “Bot is still initializing…” or “…not available right now. Please try again later.” | The bot is starting up | Wait a minute and try again | |
| “Bot Not in Server”, or the server is missing from the Discord Server picker | The bot was never invited, or was kicked | Click Invite Bot, then Refresh Servers | Go to General › Discord Server |
See Bot Management for rotating credentials and restarting the bot.
My bot got deleted or banned by Discord
Members authorize one specific bot application. If Discord deletes it, those authorizations are gone and can't be moved to a new bot.
- Set up a new bot with the custom bot guide.
- Link it to your server and run
/setupto publish a new verification message. - Ask your members to verify again with the new bot.
Own the bot with a dedicated Discord account that has 2FA turned on and never joins servers. See Secure Your Bot.
Roles & permissions
| Symptom | Cause | Fix |
|---|---|---|
| Roles aren’t given, or “I don’t have permission to perform this action.” | Role order, or the bot is missing Manage Roles | Move the bot’s role above the roles it manages (see 50013) |
| “2FA Required on Bot Owner Account” warning | The Discord server requires 2FA for moderator actions | Turn on 2FA on the account that owns the bot application, or turn off the setting in Discord’s Server Settings → Safety Setup |
| Import bans: “Bot is missing BAN_MEMBERS permission” | The bot can’t read the ban list | Give the bot Ban Members |
Members aren't getting the verified role
-
Ask the member for the error code shown on the verify page.
-
50013: the bot’s role must be above the verified role in Discord’s Server Settings → Roles. See 50013.
-
990403: make sure the bot has Manage Roles. If the server has Require 2FA for moderator actions on, the bot owner’s account needs 2FA. See 990403.
-
990404: the verified role was deleted. Pick a new one under Verified Role.
-
No error: check On Verify Action. In Remove Role mode no role is given; the unverified role is taken away instead.
-
Run
/syncrolesto fix members who verified earlier.
/setup & commands
| Symptom | Cause | Fix |
|---|---|---|
/setup: “I need the following permissions in #channel…” | The bot is missing channel permissions | Give the bot View Channel, Send Messages, Embed Links and Manage Webhooks in that channel |
/setup: “Server Not Registered” | This Discord server isn’t linked in RestoreCord; add it in the dashboard, or link it under Discord Server | Go to General › Discord Server |
/setup: “The saved verification message design could not be read” | The saved design is broken; re-save the Verification message | Go to General › Verification Message |
| Slash commands missing | Discord limits how often commands can be registered | They appear automatically within a day |
| “You don’t have permission to use this command…” | No permission has been set for that user; add the user or role under Manage Permissions | Go to Security › Manage Permissions |
/pull replies “Work In Progress” | The command isn’t available yet | Start pulls from the dashboard instead (see Pull Members) |
See Bot Commands for every command and who can use it.
Verify button does nothing or the link is broken
The verification message is out of date, for example after a domain or bot change. Run /setup again to republish it. If Private Server is on, the verify page has no Verify button at all.
Go to Security › Private Server
Dashboard
| Symptom | Cause | Fix |
|---|---|---|
| “Access Denied — You don’t have permission to manage this server.” | You’re a sub-user without the needed permission; the owner edits your permissions under Manage Sub-Users | Go to Extras › Sub-Users |
| Can’t delete a bot | Servers still use it | Delete or move those servers first. Deleting a bot also deletes all of its members and servers, and can’t be undone. |
| A setting is greyed out or shows an “Upgrade” badge | Your plan doesn’t include it | See Plans & Billing |
| Custom domain won’t verify | DNS isn’t set up or hasn’t propagated yet | Add a CNAME pointing to fallback.restorecord.com and wait up to 24 hours. Then add the new redirect URL in the Developer Portal and run /setup again. |
I changed my custom domain and verification broke
-
In the Developer Portal, add
https://<new domain>/api/callbackunder your bot’s OAuth2 → Redirects. The exact URL is shown under the bot's Redirect URL. -
Run
/setupto republish the verification message with the new domain.
Members using old links get error 10005 until the redirect is added. Domain settings are under Custom Domain.
My webhook logs stopped
Check that the webhook saved in Discord Webhook still exists in Discord. A deleted webhook breaks logging; create a new one and paste its URL in. IP addresses and locations only appear when Show Information in Webhook Logs is on. See Webhook Logs.
Go to Security › Discord Webhook Go to Security › Show Information in Webhook Logs
Pulls & backups
| Symptom | Cause | Fix |
|---|---|---|
| Pull stopped: “Re-invite the bot or grant its role the Create Instant Invite permission” | The bot left the destination server or lost the permission | Re-invite the bot, or give its role Create Instant Invite, then start the pull again |
| “Discord has limited member pulling for this server” | Discord paused joins or invites for that server | Re-enable invites in Discord’s Server Settings → Invites, or wait for Discord to lift the pause |
| Pull is running slowly | Discord’s rate limits set the speed | Nothing to change; large pulls can take hours and RestoreCord can’t speed them up |
| “Backup limit reached” | Your plan’s backup limit is reached | Delete old backups, or upgrade (see Plans & Billing) |
Why weren't all my members pulled?
Check the result counters on the finished pull:
| Counter | Meaning | What to do |
|---|---|---|
| Members Unauthorized | They removed your bot from their Discord account, so they can no longer be pulled | They must verify again |
| Members in Maximum Servers | They’re already in 100 servers (200 with Nitro) | They must leave a server |
| Members Banned | Banned from the destination server | Unban them in Discord |
| Members Blacklisted | Blocked by a firewall or blacklist rule; remove the rule under Firewall Rules | Go to Firewall › Rules |
| Members in Server | Already in the destination server; roles are still applied | Nothing to do |
Only members who verified with the same bot and haven't revoked access can be pulled. If the pull stopped, check the bot token and the Create Instant Invite permission. See Pull Members for the full guide.
Still stuck?
If none of these fixes work, contact support with the exact message, what you were doing and when it happened. Never share your bot token or client secret; if you have, reset it in the Developer Portal right away.