Verify page error codes and who fixes them
When a member says verification failed, the code on their screen tells you whether to fix your server or to walk them through a quick change on their side.
Short answer
Errors 401, 403, 404 and 990047 come from your bot, roles or server settings and need the owner. VPN, 100-server limit, cancelled authorisation, missing email, password and captcha errors are fixed by the member. Firewall, alt, blacklist and blocked-server errors mean your rules worked.
Errors only the owner can fix
No amount of retrying on the member's side changes these. Check them first whenever several members report the same problem.
| Code | What it means | The fix |
|---|---|---|
| 403 | The bot is missing permissions for the verified role | Drag the bot role above the verified role, then reselect the verify role in the dashboard |
| 401 | The bot token is no longer valid | Reset the token in the Discord Developer Portal and paste it into Dashboard, Bots |
| 404 | The verified role couldn't be added | The role was deleted or changed. Pick the role again in your server settings |
| 990047 | The server has invites disabled | Re-enable invites in Discord's Server Settings |
Error 403 is by far the most common. Discord never lets a bot manage a role that sits above its own highest role, so a new role created at the top of the list breaks verification until the bot role is moved up. The 403 alert on the verify page includes a link to a permission fix for exactly this reason.
Why are some roles missing permissions?
Discord bots can only assign roles positioned below their own role in the server hierarchy.
Go to Server Settings → Roles in Discord and drag Nova Guard above the role you want to assign.
Two messages appear without a numeric code: Custom bot not found and Owner account not found. Both mean the server is no longer linked to a working bot or account in your dashboard. Reconnect the bot before anyone else tries.
Errors the member can fix
| Code | What the member sees | What to tell them |
|---|---|---|
| 306 | VPN or proxy not allowed | Switch off the VPN, proxy extension or iCloud Private Relay and try again |
| 30001 | Discord's 100-server limit reached | Leave one server, then verify again |
| 990049 | Authorisation cancelled | Click Verify again and choose Authorize on Discord |
| 990048 | Email permission missing | Verify again and keep Email enabled on Discord's screen |
| 990032 / 990033 | Password required or incorrect | Enter the current verification password |
| 777 | Captcha required | Complete the captcha before clicking Verify |
For VPN problems, RestoreCord's VPN and proxy help page walks members through apps, network proxies and iPhone settings, which saves your staff from explaining it every time.
Errors that mean your protection worked
- 305: the account was matched as an alt of someone who already verified
- 307: the member is on your blacklist
- 304: the server blocks cellular connections and the member is on mobile data
- 990031: a custom firewall rule denied access
- 990046: the member is in a server you blocked
If a real member hits one of these by mistake, don't loosen the rule for everyone. Find their attempt in the firewall activity log and grant temporary access, or add a narrow allow rule for their user ID.
Triage a report in a minute
Ask the member for the code shown after the word Error, a screenshot of the page, and roughly when it happened. Then:
- Look the code up in the tables above to see whose side the fix is on
- For firewall-related codes, search the activity log by the member's Discord user ID to see which check fired
- Fix the setting or send the member the matching instruction, then ask them to try once more
Catch errors before members do
After any change to roles, your bot or the firewall, run a verification from a spare account. Then send verification events to a staff channel with webhook logs, so a broken role shows up in minutes rather than in a stream of complaints. For the order of steps behind these codes, read what happens when a member clicks Verify.
Before you reply to a member
Get the exact code
"It didn't work" has a dozen causes. The code narrows it to one.
Check whether others are affected
Several reports at once point to an owner-side code like 403.
Search the activity log
The member's user ID shows which firewall check stopped them.
Send one clear instruction
Pair the fix with a request to press Verify once more.
Verify error questions
A verify page that explains itself
RestoreCord tells members and owners exactly what went wrong, so fixes take minutes.