> Privileged intents disabled, Invalid Redirect URL or a reset token? Match the RestoreCord bot card warning to its cause and get the bot back online in minutes.

Source: https://restorecord.bot/fix-discord-bot-token-intents

# Fix Discord bot token, intent and redirect URL errors

A red warning on your RestoreCord bot card nearly always has a two-minute fix in the Developer Portal. Match what you see to the cause below.

[Open my bots](https://restorecord.com/dashboard/bots)[Bot management docs](https://restorecord.com/docs/guides/bot-management)

Short answer

Invalid Redirect URL means the callback is missing from your Discord application's OAuth2 settings. Privileged intents are disabled means the Server Members or Message Content switch is off. Rejected credentials mean the token or secret was reset. Fix it in Discord, save in RestoreCord, then press Restart Bot.

## Start with the bot card

Open **Bots** in the dashboard. Each card shows the bot's username, client ID and a live status dot, which turns green once RestoreCord has the bot connected to Discord. Any warning sits right on the card, so you rarely need to guess.

A

### Aurora Gatekeeper

Shared

Aurora Gatekeeper • 123456789012345678

Manage BotInvite Bot

| What you see                    | Cause                             | Fix                                                        |
| ------------------------------- | --------------------------------- | ---------------------------------------------------------- |
| Invalid Redirect URL            | Callback missing in OAuth2        | Copy the URL from the card into Discord's OAuth2 redirects |
| Privileged intents are disabled | Intent switches off in the portal | Enable both intents, then Restart Bot                      |
| Credentials rejected            | Token or secret regenerated       | Paste the new value and save                               |
| Verified role never arrives     | Bot role sits too low             | Drag the bot role above the verify role                    |

## Invalid Redirect URL

The callback shown on the bot card isn't registered in your application. In the Developer Portal open **OAuth2**, add it under redirects and save. Without a custom domain it is:

Default callbacktext

```
https://restorecord.com/api/callback
```

With a custom domain, it's that domain plus `/api/callback`. Changed domains recently? Keep the old redirect too until the new one is tested.

## Privileged intents are disabled

Discord rejected the bot's gateway intents, so it restarted without member and message-content events. Verification and role changes depend on those events.

1. 1In the Developer Portal, open your application and go to the Bot page.
2. 2Switch on Server Members Intent and Message Content Intent, then save.
3. 3Back in RestoreCord, press Restart Bot so it reconnects with the new intents.
4. 4Watch for the green status dot on the bot card.

## A reset or leaked token

Resetting the token in Discord retires the old one instantly. RestoreCord validates credentials as you type, and a green ring around the field means Discord accepted the new value. Save before you run any server operation such as a pull. The same applies to the client secret.

## Members verify but get no role

Discord only lets a bot assign roles below its own. Open Server Settings → Roles and drag the bot's role above the verified role, and above any other role it should add or remove.

### Why are some roles missing permissions?

Discord bots can only assign roles positioned below their own role in the server hierarchy.

Server Settings\>Roles

Admin

Verified

Member

RestoreCord

BOT

Move RestoreCord above Verified

Go to **Server Settings** → **Roles** in Discord and drag **RestoreCord** above the role you want to assign.

## Restart, never delete

**Restart Bot** simply reconnects to Discord and is the right move after any credential or intent change. **Delete Bot** is a different thing entirely.

Deleting a bot removes it and every member and server record attached to it, and can't be undone. Servers still depending on it come back as a list to handle first. Rotate credentials instead.

### Still stuck?

Ask in the RestoreCord Discord server, where the team typically replies within 12 hours, or use the [contact page](https://restorecord.com/contact). Mention which warning the card shows and when you last changed credentials. If the bot was never set up correctly, retrace [the setup guide](https://restorecord.bot/create-custom-discord-bot), or read how to [secure the bot](https://restorecord.bot/secure-discord-bot-account) once it's green. Back to [RestoreCord Bot](https://restorecord.bot/).

## From red warning to green dot

1. 1  
### Read the bot card  
Open Bots in the dashboard and check the status dot and any warning shown on the card.
2. 2  
### Match the warning to a fix  
Invalid Redirect URL means a missing callback, a disabled intents warning means the portal switches are off, rejected credentials mean a reset token.
3. 3  
### Apply it in the Developer Portal  
Add the callback, enable the intents or copy the fresh token, then save the change in Discord.
4. 4  
### Save and restart  
Paste any new credentials into RestoreCord, press Restart Bot and test verification with a staff account.

## Bot error questions

### 

### 

### 

## Get your bot back to green

Open the RestoreCord dashboard, read the bot card and apply the matching fix in minutes.

[Open my bots](https://restorecord.com/dashboard/bots)[View pricing](https://restorecord.com/pricing)
