> RestoreCord setup troubleshooting for owners: fix missing verified roles, Invalid Redirect URL, disabled intents and verify messages stuck on old text.

Source: https://restorecord.help

# Something off with your RestoreCord setup? Start with the symptom.

Nearly every snag owners hit traces back to four things: role order, one Developer Portal setting, a missing redirect or a message that was never republished. Find yours below and you're usually done in minutes.

[Browse common problems](https://restorecord.help/#problems)[Open the dashboard](https://restorecord.com/dashboard)

None of these fixes need a plan change or a support ticket.

## The four problems behind most setup tickets

Flip through them. Each one shows what you'd see in Discord or the dashboard, and the change that clears it.

### Members verify and still can't see anything

Discord only lets a bot manage roles below its own. New roles land above the bot by default, so the role change is silently refused after a perfectly good verification.

* Drag the bot role above Verified (or above Unverified in remove-role mode)
* Administrator doesn't bypass the hierarchy
* Members who got stuck are already backed up

## What /setup checks before it posts

Running /setup in Discord is the quickest way to re-post or move your verification message. It's admin-only, it never edits permissions, and it stops you before you post somewhere members can't read.

* Choose the configured channel or the one you're in; the current one becomes the new verify channel
* View Channel, Send Messages, Embed Links and Manage Webhooks are checked right before publishing
* If unverified members can't see the destination, you get a warning and a separate Send anyway step
[Republishing a verify message](https://restorecord.help/verification-message-not-updating)

## Six checks for a clean setup

Tick these off after any change to your bot, roles or domain. If all six pass, verification is working.

Status dot is green

Dashboard → Bots shows your bot connected to Discord. Grey or warning text means intents or credentials need a look first.

Bot role sits high enough

It's above the verified role, or above the unverified role in remove-role mode, and Manage Roles is switched on.

Callback is listed in Discord

The redirect URL on your bot card appears under OAuth2 → Redirects in the Developer Portal, character for character.

Unverified members can see #verify

@everyone has View Channel there, and the bot can view, send, embed links and manage webhooks.

Message slot isn't flagged

The Verification message row has no Republish required warning, so Discord shows your latest design.

A spare account got through

An account with no staff roles verified, received the right role and showed up in your log channel.

Setup flagged Needs attention?

RestoreCord already rolled its own changes back. The setup guide shows exactly what each step touches, so you can fix the cause and run it again.

[Read the setup guide](https://restorecord.com/docs/guides/setup-permissions)

## Why a failed setup never leaves your server half-done

Set up verification picks a verify channel, writes the message and publishes it. The only permission it edits is View Channel, and only on channels you approved. Staff, ticket and log channels are always left as they are, so your verified role can never leak into them.

If any step fails, RestoreCord puts each channel's permissions back the way they were, removes the message it posted and flags the setup, which means a broken run costs you nothing but a retry. [The usual culprit is role order](https://restorecord.help/verified-role-not-given)

## Quick answers for server owners

### 

### 

### 

### 

### 

## Setup sorted. Now RestoreCord does the work

With a clean setup, every member who verifies is backed up and screened automatically, and a lost server is a restore away instead of a rebuild.

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