Troubleshooting and FAQ

Troubleshooting and FAQ

Slash commands don't appear

• Set DISCORD_GUILD_ID to your server's id — commands then register instantly. Without it, global registration can take up to an hour.
• Make sure the bot was invited with both the applications.commands and bot scopes.

Linking fails: "no matching Seerr user"

The Plex username/email entered must match an existing Seerr user. If the user has never signed into Seerr, their account may not be imported yet — have them log into Seerr once with Plex, then retry. See Account Linking.

Requests land as the wrong user / quotas not applied

That's exactly the problem VaultRequestrr solves — but only for requests made through the bot by linked users. Check /linkstatus, and check the dashboard Links page for remaps. If REQUIRE_LINKING=false, unlinked requests fall back to DEFAULT_SEERR_USER_ID.

Nobody gets approval DMs

• Configure approvers: ADMIN_DISCORD_IDS or dashboard Settings → Approvals & Issues → Request approvals.
• Users must allow DMs from server members for the bot's DMs to arrive; the optional approvals channel is a good fallback (Requests and Approvals).

Notifications are slow

Set up the Seerr webhook for near-instant delivery — without it the bot relies on polling (~2 min). See Notifications.

Webhook doesn't fire

• The endpoint is disabled until a WEBHOOK_SECRET (or dashboard webhook secret) is set.
• The URL must include the token: http://<host>:<WEB_PORT>/webhook/seerr?token=<secret>.
• Seerr must be able to reach the VaultRequestrr host/port (check Docker networking / firewalls).

No DMs for requests made in the Seerr web UI

Web-UI requests are only matched for users who have linked (made at least one request through the bot). Also check TRACK_EXTERNAL_REQUESTS is enabled. See Notifications.

Issues are attributed to the admin account in Seerr

Per-reporter attribution requires Seerr 3.4+. On older versions the reporter is recorded in the issue message instead, and DMs/dashboard still track the real reporter. See Issue Reporting and Re-grab.

/anime says it isn't configured

Set the anime instance id(s) on the dashboard Settings → Anime routing card. See Anime Requests.

An anime series was added without absolute numbering

Anime detection is Seerr's (via a TMDB keyword), not the bot's. Add the TMDB "anime" keyword or correct the series type in Sonarr. See Anime Requests.

Re-grab keeps pulling the same bad release

Re-grab blocklists the release that produced the bad file, so the identical release can't come back — but a different bad release can. Use Manual search on the dashboard Issues page to pick a specific release. See Issue Reporting and Re-grab.

Where is my data stored?

A single SQLite database at DATABASE_PATH (default data/vaultrequestrr.sqlite3; /data in Docker). Back that file up to preserve links, invites, and issue/request tracking.

Still stuck?

Check the Logs page on the Admin Dashboard (set LOG_LEVEL=DEBUG for more detail), then open an issue.