
Requestrr
Discord chatbot for media requests
Requestrr is a Discord chatbot that simplifies requesting content from Sonarr, Radarr, and Ombi through Discord chat commands. Instead of a web interface, users request movies and TV shows directly in Discord using slash commands like /movie and /tv, and get notified when their requests are available. With automatic command cleanup, approval workflows, and integration with your existing media management tools, Requestrr brings media requests directly into your Discord community. QuickBox Pro installs Requestrr from official GitHub releases with systemd service and web configuration interface.
💬 Discord Integration
Native Discord bot with slash commands for movie and TV show requests
📡 Media Management
Integrates with Sonarr, Radarr, and Ombi for automated request handling
🔔 Discord Notifications
Automatic notifications when requested content is downloaded and available
🔍 Smart Search
Search and browse content directly in Discord with rich metadata and images
⚙️ Approval Workflows
Configurable auto-approval or manual approval for user requests
🧹 Auto Message Cleanup
Automatically delete command messages to keep Discord channels clean
Discord Bot Application
Requestrr is a Discord bot, not a web application. Users interact via Discord slash commands (/movie, /tv) instead of a web interface. A web configuration panel is provided for bot setup only.
Installation
Symptoms
- QuickBox Pro v3 installed and configured
- Discord server where you have admin/bot permissions
- Sonarr and/or Radarr configured with media libraries
- Optional: Ombi for multi-user request management
Resolution
- Use QuickBox's qb command for installation
- Automatic download from GitHub releases
- Per-user installation with isolated configuration
- Web configuration interface at port 17200
Basic Installation
Install Requestrr for a specific user:
qb install requestrr -u usernameCLI Commands
| Command | Description |
|---|---|
qb install requestrr -u username | Install Requestrr with automatic configuration |
qb reinstall requestrr -u username | Reinstall Requestrr (preserves configuration) |
qb update requestrr -u username | Update to latest GitHub release |
qb remove requestrr -u username | Remove Requestrr and clean up files |
qb help requestrr | Display comprehensive help information |
Automatic Port Assignment
QuickBox automatically assigns ports starting at 17200 (HTTP) and 17301 (HTTPS), auto-incremented per user. Access the web configuration at https://your-server-ip/username/requestrr.
Auto-Configuration
During installation, Requestrr is automatically configured with AutomaticallyPurgeCommandMessages enabled to keep Discord channels clean by deleting command messages after execution.
Accessing Requestrr
After installation, access the web configuration panel at:
https://your-server-ip/username/requestrrQuickBox Dashboard Integration
Requestrr is automatically integrated into your QuickBox dashboard. Find it in the Service Control panel with port and status information. Click the LAUNCH icon to open the configuration interface.
Setup Steps:
- Create Discord bot application and get bot token
- Configure Requestrr via web interface
- Connect to Sonarr, Radarr, or Ombi
- Invite bot to your Discord server
- Users can start requesting via
/movieand/tvcommands!
Initial Configuration
1. Create Discord Bot Application
Before configuring Requestrr, create a Discord bot:
- Go to Discord Developer Portal - https://discord.com/developers/applications
- Click New Application
- Enter application name (e.g., “Requestrr Media Bot”)
- Navigate to Bot tab in left sidebar
- Click Add Bot → Confirm
- Under Token section, click Copy to copy bot token
- Under Privileged Gateway Intents, enable:
- Server Members Intent (required)
- Message Content Intent (required)
- Save Changes
- Navigate to OAuth2 → URL Generator:
- Scopes - Select
botandapplications.commands - Bot Permissions - Select:
- Send Messages
- Embed Links
- Use Slash Commands
- Manage Messages (for auto-cleanup)
- Scopes - Select
- Copy the Generated URL at bottom (you’ll use this later to invite the bot)
2. Configure Requestrr via Web Interface
Connect Requestrr to Discord:
- Open Requestrr web configuration:
https://your-server-ip/username/requestrr - Navigate to Bot Configuration
- Enter Discord Bot Token (from step 1)
- Configure bot settings:
- Command Prefix - Default is
/(for slash commands) - Status Message - Custom status text (e.g., “Ready to request media!”)
- Auto Delete Messages - Enable to keep channels clean
- Auto Delete Delay - Seconds before deleting command messages (default: 60)
- Command Prefix - Default is
- Click Test Connection to verify bot token
- Once verified, click Save
3. Connect Media Management Services
Configure Sonarr, Radarr, or Ombi integration:
Option A: Direct Sonarr/Radarr Integration
-
Go to TV Shows Configuration:
- Client - Select “Sonarr”
- Hostname -
localhost - Port - Your Sonarr port (default
8989) - API Key - Copy from Sonarr → Settings → General → API Key
- Base URL - Leave blank
- Use SSL - Uncheck
- Quality Profile - Select default profile
- Root Path - Select TV shows directory
- Language Profile - Select language
- Default User - QuickBox username for requests
- Approval Required - Enable for manual approval workflow
- Click Test, then Save
-
Go to Movies Configuration:
- Client - Select “Radarr”
- Hostname -
localhost - Port - Your Radarr port (default
7878) - API Key - Copy from Radarr → Settings → General → API Key
- Quality Profile - Select default profile
- Root Path - Select movies directory
- Minimum Availability - Select preference
- Default User - QuickBox username
- Approval Required - Enable if desired
- Click Test, then Save
Option B: Ombi Integration
- Go to TV Shows Configuration and Movies Configuration
- Client - Select “Ombi”
- Hostname -
localhost - Port - Your Ombi port (default
5000) - API Key - From
/home/username/.config/Ombi/ombi_api.txt - Base URL - Leave blank
- Use SSL - Uncheck
- Click Test, then Save
Service Management
Requestrr runs as a per-user systemd service.
systemctl status requestrr@username # Check status
systemctl restart requestrr@username # Restart service
journalctl -u requestrr@username -f # View live logs
systemctl enable requestrr@username # Start on boot (already enabled)
systemctl disable requestrr@username # Prevent auto-startTroubleshooting
Requestrr Won’t Start
journalctl -u requestrr@username -fCheck configuration file:
cat /home/username/.config/Requestrr/config/settings.json
# Verify JSON is valid and not corrupted
# If corrupted, restore from backup:
cp /opt/quickbox/backups/software/username/requestrr/default/settings.json \
/home/username/.config/Requestrr/config/settings.json
# Restart Requestrr
systemctl restart requestrr@usernameDiscord Bot Won’t Connect
Symptoms
- Bot shows offline in Discord server
- Test connection fails in web configuration
- Error: 'Invalid Discord bot token'
- Bot doesn't respond to slash commands
Resolution
- Verify bot token is correct (regenerate if needed)
- Ensure Privileged Gateway Intents are enabled (Server Members, Message Content)
- Check Requestrr service is running: systemctl status requestrr@username
- Verify bot has correct permissions when invited to server
- Check logs: journalctl -u requestrr@username -f | grep -i discord
Sonarr/Radarr Connection Failed
# Verify services are running
systemctl status sonarr@username
systemctl status radarr@username
# Test API connectivity
curl http://localhost:7878/api/v3/system/status?apikey=YOUR_RADARR_API_KEY
curl http://localhost:8989/api/v3/system/status?apikey=YOUR_SONARR_API_KEY
# Check API keys match Requestrr configuration
# Radarr: Settings → General → Security → API Key
# Sonarr: Settings → General → Security → API Key
# Verify URL configuration in Requestrr
# Use: localhost (not 127.0.0.1)
# Port: Default ports (7878 for Radarr, 8989 for Sonarr)
# SSL: Disabled (not needed for local connections)Slash Commands Not Appearing in Discord
# Verify bot has applications.commands scope
# Re-invite bot with correct OAuth2 URL Generator settings
# Check bot permissions in Discord server
# Server Settings → Integrations → Bots → Requestrr
# Ensure "Use Slash Commands" permission is enabled
# Restart Discord client (sometimes required for slash commands to appear)
# Right-click Discord system tray icon → Quit Discord → Reopen
# Check Requestrr logs
journalctl -u requestrr@username -f | grep -i commandRequests Not Sending to Sonarr/Radarr
# Check Requestrr logs for errors
journalctl -u requestrr@username -f | grep -i error
# Verify client is configured correctly
# Web config → TV Shows/Movies → Check settings
# Check quality profiles exist
# Ensure quality profile selected in Requestrr matches Sonarr/Radarr
# Verify root paths are configured
# Ensure root path exists and has correct permissions
# Test manual request via Discord
# Use /movie or /tv command → Check Requestrr logsNotifications Not Working
# Verify notifications are enabled
# Web config → TV Shows/Movies → Enable "Send Notifications"
# Check Discord channel permissions
# Bot needs "Send Messages" and "Embed Links" permissions
# Verify notification channel is configured
# Web config → Bot Configuration → Notification Channel ID
# Test notification manually
# Make a request and wait for content to download
# Check logs: journalctl -u requestrr@username -f | grep -i notifBest Practices
Do
- Enable auto message deletion to keep Discord channels clean and organized
- Configure approval workflows for moderation if server has many users
- Set up separate Discord channels for requests and notifications
- Use Discord roles to restrict who can use request commands
- Regularly backup settings.json configuration file
- Test bot connection after any Discord developer portal changes
- Monitor Requestrr logs for failed requests and connection issues
- Use Ombi backend for multi-user request tracking and quotas
Don't
- Don't share Discord bot token publicly—regenerate if exposed
- Don't disable Privileged Gateway Intents—bot requires them to function
- Don't manually edit settings.json while Requestrr is running
- Don't configure multiple media management backends for same content type
- Don't ignore failed notifications—check bot permissions in Discord
- Don't forget to set root folders—requests will fail without valid paths
- Don't allow unlimited requests without quotas—use Ombi for user management
- Don't use same bot token for multiple Requestrr instances—create separate bots
Use Cases
Discord Community Media Server
- Users request content directly in Discord without leaving chat
- Slash commands provide intuitive, autocomplete-friendly interface
- Automatic notifications when requested content is ready
- Keeps Discord channels clean with auto message deletion
Streamlined Request Workflow
- Users type
/movie The Matrixto search and request - Bot shows search results with posters and descriptions
- User selects correct result, bot sends to Radarr automatically
- User notified in Discord when movie is downloaded
Multi-User Request Management
- Integrate with Ombi for user quotas and approval workflows
- Discord roles control who can request content
- Moderators approve requests before sending to Sonarr/Radarr
- Track request history and user activity via Ombi dashboard
Related Applications
Additional Resources
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.