
Notifiarr
Unified notifications and Discord integration for your media server stack
Notifiarr - Unified Notifications Client
Notifiarr is the unified client for Notifiarr.com . It enables content requests from Media Bot in your Discord Server and provides comprehensive reports for Plex usage, system health monitoring, and much more. Perfect for users who want seamless Discord integration with their media automation stack.
What is Notifiarr?
Notifiarr is a powerful notification and integration platform that connects your media server ecosystem to Discord. Key features include:
🤖 Discord Media Bot
Request content directly from Discord with user-friendly commands
📺 Plex/Tautulli Integration
Monitor Plex usage and receive detailed activity notifications
🎬 *arr Stack Integration
Connect Radarr, Sonarr, Lidarr, Prowlarr, and more seamlessly
⬇️ Download Client Support
Integration with Deluge, qBittorrent, SABnzbd, NZBGet
💓 System Health Monitoring
Track service status and receive real-time alerts
🔍 Service Checks
Automated monitoring of all configured applications
Notifiarr.com Account Required
You’ll need a Notifiarr.com account to use this client. The API key from your account is required during configuration.
Installation
Install Notifiarr
Install the Notifiarr client for a specific user:
qb install notifiarr -u usernameAutomatic Integration Detection
The QuickBox installer automatically detects and configures integrations for any *arr applications, download clients, Plex, and Tautulli already installed for the user. Install your other applications first for seamless configuration.
Installation Process
During installation, QuickBox Pro will:
- Download the latest Notifiarr client from the official repository
- Generate SSL certificates for secure communication
- Auto-detect installed *arr applications (Radarr, Sonarr, Lidarr, etc.)
- Auto-detect download clients (Deluge, qBittorrent, SABnzbd, NZBGet)
- Auto-detect Plex and Tautulli installations
- Configure nginx reverse proxy for web access
- Set up systemd service for reliable operation
CLI Commands
Basic Operations
| Command | Description |
|---|---|
qb install notifiarr -u username | Install Notifiarr for a user |
qb reinstall notifiarr -u username | Reinstall Notifiarr (preserves config) |
qb update notifiarr -u username | Update to latest version |
qb remove notifiarr -u username | Remove Notifiarr completely |
qb help notifiarr | Display help information |
Usage Examples
Install Notifiarr:
qb install notifiarr -u myuserUpdate Notifiarr:
qb update notifiarr -u myuserReinstall (fix corrupted installation):
qb reinstall notifiarr -u myuserRemove Notifiarr and clean up:
qb remove notifiarr -u myuserSupported Integrations
QuickBox Pro automatically configures Notifiarr with your installed applications:
Enhanced Features
Notifiarr on QuickBox Pro includes several advanced features:
🔒 SSL/TLS Security
Auto-generated SSL certificates for secure client communication with per-user certificate isolation
⚡ Auto-Configuration
Automatically detects and configures API keys for all installed *arr applications
🔄 Reliable Service
Runs as a systemd service with automatic restarts and proper lifecycle management
📝 Structured Logging
Comprehensive logging with separate app, HTTP, and debug logs with automatic rotation
🌐 Reverse Proxy
Pre-configured nginx reverse proxy with WebAuth support for seamless dashboard access
💾 Automatic Backups
Configuration backups created during installation and available through QuickBox backup system
Service Management
Notifiarr runs as a systemd service for reliable operation:
Check Service Status
systemctl status notifiarr@usernameRestart Service
systemctl restart notifiarr@usernameView Live Logs
journalctl -u notifiarr@username -fView Application Logs
# Application log
tail -f /home/username/.config/Notifiarr/logs/app.log
# HTTP access log
tail -f /home/username/.config/Notifiarr/logs/http.log
# Debug log (when enabled)
tail -f /home/username/.config/Notifiarr/logs/debug.logAutomatic Recovery
The Notifiarr service is configured to automatically restart on failure (with a 10-second delay), ensuring continuous operation.
Configuration
Getting Your Notifiarr API Key
- Create an account at Notifiarr.com
- Navigate to your Profile or Integration settings
- Copy your API Key
- Add it to your Notifiarr configuration file
Configuration File Location
After installation, configure Notifiarr by editing:
nano /home/username/.config/Notifiarr/config/notifiarr.confKey Configuration Options
## Your API key from notifiarr.com (required)
api_key = "api-key-from-notifiarr.com"
## UI credentials (auto-configured during install)
ui_password = "username:password"
## Bind address (localhost only, proxied via nginx)
bind_addr = "127.0.0.1:5454"
## Enable debug mode for troubleshooting
debug = false
## Log rotation settings
log_file_mb = 100
log_files = 0Password Requirements
If your QuickBox user password is less than 9 characters, a secure password is automatically generated and saved to /home/username/.config/Notifiarr/config/.notifiarr.pass.txt.
Accessing Notifiarr
After installation, access the Notifiarr web interface at:
https://your-server-ip/username/notifiarr/Or via your QuickBox Pro dashboard navigation.
Web Interface Features
The Notifiarr web UI allows you to:
- View Integration Status - Check connectivity to all configured apps
- Test Notifications - Verify Discord webhook connections
- Configure Services - Add or modify application integrations
- Monitor Health - View service check results
- Access Logs - Review recent activity and errors
Directory Structure
Notifiarr files are organized as follows:
Troubleshooting
Common Issues
Notifiarr not connecting to apps:
# Check service status
systemctl status notifiarr@username
# Verify app configurations in notifiarr.conf
grep -E "url|api_key" /home/username/.config/Notifiarr/config/notifiarr.conf
# Check application logs
tail -50 /home/username/.config/Notifiarr/logs/app.logWeb interface not loading:
# Restart Notifiarr service
systemctl restart notifiarr@username
# Check nginx configuration
nginx -t
systemctl restart nginx
# Verify SSL certificates exist
ls -la /home/username/.ssl/Discord notifications not working:
# Enable debug mode temporarily
sed -i 's/debug = false/debug = true/' /home/username/.config/Notifiarr/config/notifiarr.conf
systemctl restart notifiarr@username
# Check debug log
tail -f /home/username/.config/Notifiarr/logs/debug.log
# Don't forget to disable debug mode after troubleshootingPermission errors:
# Fix ownership
chown -R username:username /home/username/.config/Notifiarr
chown -R username:username /opt/username/Notifiarr
# Or reinstall
qb reinstall notifiarr -u usernameUse Cases
Discord Content Requests
Enable your Discord server members to request content:
Movie Requests
TV Show Requests
Music Requests
Notification Hub
Centralize all your media notifications:
✅ Download Complete
Get notified when content is ready to watch
🆕 New Releases
Alerts for newly added media to your library
❌ Failed Downloads
Immediate notification of issues requiring attention
💓 Health Alerts
Service status changes and system health updates
System Monitoring
Keep track of your server health:
🔍 Service Checks
Automated monitoring of all apps with configurable intervals
📊 Uptime Tracking
Know immediately when services go down
💾 Resource Alerts
System health notifications for disk, CPU, and memory
Best Practices
Do
- Install your *arr applications before Notifiarr for automatic detection
- Use a strong, unique API key from your Notifiarr.com account
- Enable service checks for all critical applications
- Configure notification channels per service type in Discord
- Review debug logs when troubleshooting integration issues
- Keep Notifiarr updated for latest integration support
Don't
- Don't share your Notifiarr API key publicly
- Don't enable debug mode permanently in production
- Don't skip SSL certificate configuration for security
- Don't configure too many notification channels (spam risk)
- Don't forget to disable test notifications after setup
- Don't ignore failed service check alerts
Additional Resources
Related Applications
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.