Skip to Content
Radarr

Radarr

Automated movie collection management with intelligent quality upgrades

Radarr is an independent fork of Sonarr reworked for automatically downloading movies via Usenet and BitTorrent. It monitors multiple sources for new releases, grabs them automatically, and upgrades quality when better versions become available. Inspired by CouchPotato, Radarr brings modern architecture and intelligent automation to movie library management.

Automatic Movie Downloads

Monitor movie releases and download automatically when available with quality selection

Quality Profiles

Define custom quality profiles with resolution, codec, and size preferences for different categories

Metadata & Artwork

Automatic movie posters, fanart, descriptions, and ratings from multiple sources

Smart Organization

Customizable file naming and folder structures with automatic renaming on import

Upgrade Management

Automatically upgrade existing movies when better quality releases become available

Multi-Indexer Support

Connect to multiple Usenet indexers and torrent trackers for maximum coverage

Notification System

Get notified when movies are grabbed, downloaded, or upgraded via Discord, Slack, Email, and more

Custom Scripts

Run custom scripts on grab, download, rename, or import events for advanced automation


Installation

Install from the Dashboard

Open App Dashboard → Package Management (/dashboard?mode=packages), find Radarr in the catalog (browse Media Management or search), and click Install. The dashboard streams the install log live and Radarr appears in your Application Control panel when it finishes. Reinstall and Remove are in the same Package Management panel. To update, use the amber Update badge on the Radarr row in the App Dashboard.

In the install dialog you can pick the release channel — Stable (default) or Nightly. Stable follows Radarr’s master branch, which carries Radarr 6. Nightly follows the nightly branch, which carries Radarr 7. Switching the channel later and updating moves Radarr to that channel’s latest build; the steps are in Move to Radarr 7. See Channels & Versions for how channels work.

For a dedicated 4K library, install Radarr4K — a separate instance with its own port, configuration directory (~/.config/Radarr4K), and quality profiles, so your standard and 4K libraries never conflict. It appears as its own catalog entry in Package Management; on the CLI it is the --4k flag on qb install radarr (see below).

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

Debian 11 (Bullseye) Compatibility
Important

QuickBox Pro automatically applies a SQLite compatibility patch on Debian 11 systems during installation and updates — no manual intervention required.

Install and manage from the CLI

The CLI runs the same scripts as the Dashboard and is the full power-user/automation surface. Install Radarr (stable) for a specific user:

bash
qb install radarr -u username

The complete command set:

CommandDescription
qb install radarr -u username
Install Radarr on the stable channel (master branch, Radarr 6) with automatic configuration
qb install radarr -u username --nightly
Install on the nightly channel (nightly branch), which carries Radarr 7
qb install radarr -u username --4k
Install a separate 4K instance (Radarr4K) for high-resolution content
qb install radarr -u username --nightly --4k
Install the 4K instance on the nightly branch
qb reinstall radarr -u username
Remove and install Radarr fresh (deletes its config folder and backups, so take a Full Backup first)
qb update radarr -u username
Update on the channel Radarr is set to (read from config.xml); never installs a lower major than the one you run
qb update radarr -u username --nightly
Switch to the nightly channel and update: a Radarr 6 install moves to Radarr 7 (see Move to Radarr 7)
qb remove radarr -u username
Remove the standard installation
qb remove radarr -u username --4k
Remove the 4K instance
qb help radarr
Display comprehensive help information
OptionDescriptionExample
-u, --usernameRequired

Specify the user for installation

-u john
-u john
--nightly

Use the nightly branch (Radarr 7). On install it installs from nightly. On update it switches the install to nightly, so a Radarr 6 install moves to Radarr 7

--4k

Install a dedicated 4K instance (Radarr4K) with its own config and port

How the 4K instance works
Note

--4k is a flag on the base Radarr package — it installs a dedicated Radarr4K instance with its own port, install directory (/opt/username/Radarr4K), configuration (~/.config/Radarr4K), and quality profiles, so your standard and 4K libraries never conflict. There is no separate radarr4k install command — you pass --4k to qb install radarr. In the Dashboard, Radarr4K appears as its own catalog entry you can install the same way.

Update branch handling
Tip

When you run qb update radarr -u username, QuickBox reads your current branch from config.xml and updates on it. You don’t need --nightly unless you want to switch to the nightly channel, and there is no CLI flag that switches back to stable: use the dashboard channel control, covered in Move to Radarr 7.

Full flag reference: CLI Reference.


Directory Structure

Path
Description
/home/username
.config/
Radarr/
Radarr configuration directory
radarr.db
Main database, saved by Full Backup
config.xml
Core configuration (ports, URL base, branch)
logs/
Application logs
Radarr4K/
4K instance configuration (if --4k flag used)
radarr.db
4K instance database
config.xml
4K instance configuration
Media/
Media library root
Movies/
Standard HD movie collection
Movie Title (2024)/
Movies-4K/
4K/UHD movie collection (4K instance)
Movie Title (2024)/

Configuration Details

Standard instance:

Install location
/opt/username/Radarr/
Config directory
~/.config/Radarr/
Database
~/.config/Radarr/radarr.db
Default port
7878 (auto-generated if in use)
SSL port
9898 (auto-generated if in use)

4K instance (—4k flag):

Install location
/opt/username/Radarr4K/
Config directory
~/.config/Radarr4K/
Database
~/.config/Radarr4K/radarr.db
Ports
7879+ (auto-generated, typically starting at 7879)

Move to Radarr 7

Radarr 7 is published on Radarr’s nightly branch, which QuickBox calls the Nightly channel. The stable channel (master) stays on Radarr 6. To move a Radarr 6 install to Radarr 7, switch it to Nightly and update once.

Take a Full Backup first
Warning

Radarr 7 is a new major version, and an update will not move an install back to Radarr 6 afterwards (see Going back to stable). A Full Backup saves the install tree and a consistent copy of radarr.db, and a Rollback puts both back. See Back up and restore.

From the dashboard

The channel control is available to admins.

  1. Open the App Dashboard and stay on Application Control.
  2. On the Radarr row, find the version number. Click the small branch icon beside it (its tooltip reads Change release channel).
  3. In the Radarr — Channel Settings dialog, choose Nightly.
  4. Click Save Channel. Saving writes the channel into Radarr’s config.xml.
  5. Run the update: click the amber Update badge when it appears on the Radarr row (that dialog also has a channel picker and a Switch & Update Now button), or run the CLI command below.

The same control moves Radarr4K: use the Radarr4K row.

From the CLI

bash
qb update radarr -u username --nightly

This switches the install to the nightly branch and updates it in one step, so a Radarr 6 install lands on Radarr 7. For Radarr4K add --4k. After the switch, a plain qb update radarr -u username keeps updating on nightly.

What QuickBox does after the move

  • QuickBox follows the branch and the version you run. The update check only offers a version that is newer than the one installed, so an install on Radarr 7 is never offered Radarr 6.
  • A new install on Nightly gets Radarr 7 directly. qb install radarr -u username --nightly installs from nightly.

Going back to stable

An update never installs a lower major than the one you run. If you set the channel back to Stable (on Nightly, click the amber channel badge in the Version column instead of the branch icon) and update a Radarr 7 install, the update stops, changes nothing and reports that the newest release on the master branch is older than the version you run. Radarr keeps running on Radarr 7. To stay on Radarr 7, set the channel back to Nightly. A reinstall without --nightly starts fresh on Stable (Radarr 6) and deletes the config folder, so add --nightly to reinstall on Nightly. To get back to Radarr 6, roll back to a Full Backup taken before the move (it holds the install tree and the config folder, see Back up and restore). If the Version column still shows Nightly after the rollback, set the channel back to Stable with Save Channel.

Radarr keeps its own login through the move. An update never sets or changes an app login, so keep Radarr’s login on under Settings → General → Security inside Radarr, with Authentication Method set to Forms and Authentication Required set to Enabled. An install or reinstall sets that login for you from your QuickBox credentials.


Accessing Radarr

After installation, Radarr is accessible through QuickBox’s nginx reverse proxy with SSL:

InstanceAccess URLNotes
Standardhttps://your-server-ip/username/radarr
Default installation
4K Instancehttps://your-server-ip/username/radarr4k
Separate 4K instance
QuickBox Dashboard Integration
Tip

Radarr is automatically integrated into your QuickBox dashboard. Find it on the App Dashboard (the default control view), stay on Application Control and expand its row for port and status. The API & Secrets section shows the Radarr API key masked, with buttons to reveal it and copy it. Click Open to launch the web interface.

To install, reinstall, and remove applications, use the Package Management tab instead.

Network Configuration

QuickBox automatically configures:

  • URL Base: /username/radarr (or /username/radarr4k)
  • Bind Address: 127.0.0.1 (local only - proxied through nginx)
  • Port: Auto-assigned (typically 7878 for standard, 7879+ for 4K)
  • SSL: Handled by nginx reverse proxy (port 443)

Initial Configuration

1. Configure Download Client

Navigate to Settings → Download Clients → Add (+) and select your client:

Download Client Examples

QuickBox-friendly paths and auth settings for the most common clients

All examples assume Use SSL enabled on port 443.

Deluge

HTTPS
Hostlocalhost or server IP
Port443
URL Base/username/deluge
AuthPassword

Flood

HTTPS
Hostlocalhost or server IP
Port443
URL Base/username/flood
AuthUsername & Password

NZBGet

HTTPS
Hostlocalhost or server IP
Port443
URL Base/username/nzbget
AuthUsername & Password

qBittorrent

HTTPS
Hostlocalhost or server IP
Port443
URL Base/qbittorrent
AuthUsername & Password

rTorrent

HTTPS
Hostlocalhost or server IP
Port443
URL Path/usernameSCGI routed here by QuickBox
AuthUsername & Password

SABnzbd

HTTPS
Hostlocalhost or server IP
Port443
URL Base/username/sabnzbd
AuthAPI Key (from SABnzbd settings) and Username & Password (SABnzbd credentials)

Transmission

HTTPS
Hostlocalhost or server IP
Port443
URL Base/username/transmission
AuthUsername & Password

Test connection and save.

Prowlarr provides centralized indexer management:

  1. Install Prowlarr: qb install prowlarr -u username
  2. In Prowlarr, go to Settings → Apps
  3. Add Radarr as an application
  4. Indexers automatically sync to Radarr
Why Prowlarr?
Tip

When you add or remove indexers in Prowlarr, they automatically sync to Radarr (and Sonarr, Lidarr, etc.). This centralized management saves time and ensures consistency across all your *arr applications.

Alternative: Manual indexers via Settings → Indexers → Add (+)

3. Set Root Folder

Navigate to Settings → Media Management → Root Folders and add your movie directory:

  • Standard instance: /home/username/Media/Movies
  • 4K instance: /home/username/Media/Movies-4K (separate folder recommended)

4. Quality Profiles & Upgrades

Configure quality preferences and automatic upgrades:

  1. Settings → Profiles
  2. Edit or create quality profile
  3. Set Upgrade Until to your desired maximum quality
  4. Enable Upgrades Allowed

Example workflow:

  • Download WEBDL-1080p when movie is released
  • Radarr automatically upgrades to Bluray-1080p when available
  • Stops at your cutoff (e.g., Bluray-1080p) to avoid massive remuxes
Smart Upgrading
Tip

Set upgrade cutoffs to prevent endless upgrading. For example, setting cutoff to Bluray-1080p prevents automatic upgrades to 4K remuxes unless you specifically want them. This saves bandwidth and storage space.

5. File Naming Configuration

Settings → Media Management:

SettingRecommended Configuration
Rename Movies✓ Enabled - Ensures consistent naming across your library
Replace Illegal Characters✓ Enabled - Removes filesystem-incompatible characters
Standard Movie Format{Movie Title} ({Release Year}) {Quality Full}
Movie Folder Format{Movie Title} ({Release Year})
Create Empty Folders✓ Enabled - Pre-creates folders for monitored movies

Adding Movies

  1. Click Movies in the main menu
  2. Click Add New button
  3. Search for your movie by title
  4. Select the movie from search results
  5. Configure:
    • Root Folder: Choose storage location
    • Quality Profile: Select quality tier
    • Monitor: Choose monitoring option
  6. Click Add Movie

Monitoring Options

OptionBehavior
YesMonitor and download when available
NoAdd to library but don't search automatically
SkipAdd to library without monitoring or searching

Service Management

Radarr runs as a systemd service for reliability and automatic startup.

Standard Instance Commands

CommandDescription
systemctl status radarr@usernameCheck service status
systemctl restart radarr@usernameRestart Radarr service
systemctl stop radarr@usernameStop Radarr service
systemctl start radarr@usernameStart Radarr service
journalctl -u radarr@username -fView live logs
systemctl enable radarr@usernameEnable auto-start on boot
systemctl disable radarr@usernameDisable auto-start on boot

4K Instance Commands

CommandDescription
systemctl status radarr4k@usernameCheck 4K service status
systemctl restart radarr4k@usernameRestart 4K service
journalctl -u radarr4k@username -fView 4K live logs

Back up and restore

QuickBox backs Radarr up for you from the dashboard or the CLI, and the app keeps running while it does. Every backup is saved to /home/username/.QuickBox/software/radarr/backup/, named with the version and the date. For the 4K instance, replace radarr with radarr4k and Radarr with Radarr4K in the paths and commands below.

BackupWhat it saves
Config Onlyconfig.xml, the small configuration file. Your library, movies and history are in the database, so use Full Backup for them
Full BackupTwo archives: radarr-<version>-config_<date>.tar.gz holds your config folder /home/username/.config/Radarr/ (the radarr.db database, taken as a consistent copy, plus config.xml), and radarr-<version>-application_<date>.tar.gz holds the install tree /opt/username/Radarr/. The logs, MediaCover (poster cache), Backups and UpdateLogs folders are left out
NginxRadarr’s nginx config, username.radarr.conf

From the dashboard: open the App Dashboard, stay on Application Control, expand the Radarr row and open Operations. Backup offers Full backup, Config Only and Nginx Only, and Restore lists every saved backup; for a full backup its button reads Rollback and puts back both the install tree and the config archive. Restore appears only when your account is allowed to restore backups. You can also open Content → Asset Management Center (AMC in the sidebar), choose the Application Backups tab, expand the Radarr row and click Back up now; that row lists every saved file with download and delete buttons. See App Management → Application Backups for who can see the tab.

From the CLI:

bash
# Config Only: config.xml
qb manage software -o backup -u username -s radarr
 
# Full Backup: config folder with the database, plus the install tree
qb manage software -o backup -o app -u username -s radarr
 
# Roll back to a Full Backup: pick the version from a menu, then confirm
qb manage software -o rollback -o app -u username -s radarr

Every option is described in the qb manage reference.

A rollback stops Radarr, clears the stale -wal, -shm and -journal files beside each restored database, puts the archives back, and starts Radarr again. If Radarr was running before the rollback, it also waits for Radarr to answer on its port, and if it does not come back the command reports an error instead of finishing quietly.

Remove and reinstall delete your backups
Caution

qb remove radarr and qb reinstall radarr both delete /home/username/.config/Radarr/ (the database and settings) and the backup folder /home/username/.QuickBox/software/radarr/ with every backup in it, and clear the rollback list. Before either one, download the Full Backup from the Application Backups tab, or copy the folder somewhere QuickBox does not manage:

bash
cp -a /home/username/.QuickBox/software/radarr/backup /home/username/radarr-backup-saved

Restore your library after a reinstall

Because the rollback list is cleared, a Full Backup you saved before a reinstall cannot be rolled back from the dashboard afterwards. Put back the database only and keep the new config.xml, which matches the nginx config QuickBox just wrote. First stop Radarr from its row in the App Dashboard with the Stop Radarr button. Then run the file commands as your own account, and start Radarr again with the Start Radarr button. An admin with shell access can stop and start it with sudo systemctl stop radarr@username and sudo systemctl start radarr@username instead.

bash
rm -f /home/username/.config/Radarr/radarr.db-wal /home/username/.config/Radarr/radarr.db-shm
tar -xzf /home/username/radarr-backup-saved/radarr-<version>-config_<date>.tar.gz -C /home/username/.config/Radarr ./radarr.db

Removing the two -wal/-shm files first stops the new install’s journal from being applied to the restored database.


Troubleshooting

Radarr Won’t Start (Debian 11 Bullseye)

Symptoms

  • Service fails to start on Debian 11
  • SQLite version errors in logs
  • libsqlite3.so not found errors
  • Database corruption on Debian 11

Resolution

  • QuickBox automatically applies SQLite patch on Debian 11
  • Check patch: ls -la /opt/username/Radarr/libe_sqlite3.so
  • Update to apply patch: qb update radarr -u username
  • View logs: journalctl -u radarr@username -n 50

Port Conflicts

Check current port configuration:

bash
grep '<Port>' ~/.config/Radarr/config.xml
# Standard: 7878, 4K: Auto-generated (typically 7879+)

Downloads Not Appearing

Common Issues

  • No releases found in manual search
  • Movies not automatically downloading
  • Download client connection errors
  • Movie shows as monitored but nothing happens

Quick Fixes

  • Verify indexers: Settings → Indexers → Test
  • Check download client: Settings → Download Clients → Test
  • Ensure movie is monitored (check monitor icon)
  • Try manual search: Movie page → Manual Search icon

Permission Issues

bash
qb fix permissions -u username
systemctl restart radarr@username

Database Issues

Database Problems

  • Database locked errors in logs
  • Radarr becomes unresponsive
  • Missing movies or corrupted data
  • Slow loading or timeouts

Recovery Steps

  • Check database integrity: sqlite3 ... "PRAGMA integrity_check;"
    sqlite3 ~/.config/Radarr/radarr.db "PRAGMA integrity_check;"
  • Take a Full Backup before you change anything (Back up and restore)
  • Vacuum database: sqlite3 ... "VACUUM;"
    sqlite3 ~/.config/Radarr/radarr.db "VACUUM;"
  • If the integrity check fails, roll back to your last Full Backup from the App Dashboard (expand the Radarr row, Operations, Restore, then Rollback)
  • Do not reinstall to repair the database: qb reinstall radarr deletes the config folder, database included

Best Practices

Do

  • Use Prowlarr for centralized indexer management across all *arr apps
  • Set reasonable quality profiles—avoid unnecessary 4K downloads if you don't need them
  • Configure proper file naming for consistent library organization
  • Take a Full Backup before every update or reinstall, and download a copy from the Application Backups tab in the Asset Management Center (Back up and restore)
  • Use download client categories to separate Radarr downloads
  • Set upgrade cutoffs to prevent endless quality chasing
  • Use separate root folders for standard and 4K instances
  • Enable notifications to track downloads and failed grabs

Don't

  • Don't set upgrade cutoff too high (remuxes are huge and may not be necessary)
  • Don't use too many indexers—causes rate limits and excessive API hits
  • Don't download to system drive—use dedicated media storage
  • Don't ignore failed download warnings—investigate and resolve issues
  • Don't mix standard and 4K content in same instance—use separate 4K instance
  • Don't disable authentication if Radarr is exposed to the internet
  • Don't skip Full Backups, because corruption can happen and a reinstall or remove deletes the database and the backup folder with it
  • Don't manually edit the database (radarr.db)—use the web interface


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