Skip to Content
Notifiarr

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 from the Dashboard

Open App Dashboard → Package Management (/dashboard?mode=packages), find Notifiarr in the catalog (browse the Automation category or search), and click Install. The dashboard streams the install log live and Notifiarr appears in your Application Control panel when it finishes. Reinstall, Update, and Remove are available from the same panel.

What you see is gated by your account: admins manage any user’s apps; regular users manage their own. See App Management for the full flow.

The installer downloads the latest Notifiarr client, generates per-user SSL certificates, auto-detects your installed *arr apps, download clients, Plex, and Tautulli to wire up their integrations, and registers a systemd service behind the nginx reverse proxy.

Automatic Integration Detection

The 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.

Install from the CLI (automation)

The CLI runs the same scripts as the Dashboard and is suited to automation and scripting:

qb install notifiarr -u username qb reinstall notifiarr -u username qb update notifiarr -u username qb remove notifiarr -u username qb help notifiarr

Full flag reference: CLI Reference.


Supported Integrations

QuickBox Pro automatically configures Notifiarr with your installed applications:

Media Servers

Features

Discord NotificationsMedia Bot RequestsService Health ChecksSystem Monitoring

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@username

Restart Service

systemctl restart notifiarr@username

View Live Logs

journalctl -u notifiarr@username -f

View 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.log
Automatic 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

  1. Create an account at Notifiarr.com 
  2. Navigate to your Profile or Integration settings
  3. Copy your API Key
  4. Add it to your Notifiarr configuration file

Configuration File Location

After installation, configure Notifiarr by editing:

nano /home/username/.config/Notifiarr/config/notifiarr.conf

Key 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 = 0
Password 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:

Application Files
/opt/username
Notifiarr/
└── notifiarr# Application binary
User Configuration
/home/username
.config/
└── Notifiarr/
│ ├── config/
│ │ ├── notifiarr.conf# Main configuration
│ │ └── .notifiarr.pass.txt# Generated password (if needed)
│ └── logs/
│ │ ├── app.log# Application log
│ │ ├── http.log# HTTP access log
│ │ └── debug.log# Debug log (when enabled)
.ssl/
├── notifiarr.crt# SSL certificate
└── notifiarr.key# SSL private key
System Files
/usr/local/bin/username
notifiarr# Symlink to application binary

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.log

Web 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 troubleshooting

Permission errors:

# Fix ownership chown -R username:username /home/username/.config/Notifiarr chown -R username:username /opt/username/Notifiarr # Or reinstall qb reinstall notifiarr -u username

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



Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

Dedicated Support
Feature Previews
Community Configs
Active Discussions
Join Discord Server
Last updated on