Settings Download Clients

Download Clients

Overview

Downloading and importing is where most people experience issues. From a high level perspective, the software needs to be able to communicate with your download client and have access to the files it downloads. There is a large variety of supported download clients and an even bigger variety of setups. This means that while there are some common setups there isn't one right setup and everyone's setup can be a little different. But there are many wrong setups.

Download Clients

• Usenet

1. Radarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings.
   1. Examples: movies, tv, series, music, ect.
2. Radarr will monitor your download clients active downloads that use that category name. It monitors this via your download client's API.
3. When the download is completed, Radarr will know the final file location as reported by your download client. This file location can be almost anywhere, as long as it is somewhere separate from your media folder and accessible by Radarr
4. Radarr will scan that completed file location for files that Radarr can use. It will parse the file name to match it against the requested media. If it can do that, it will rename the file according to your specifications, and move it to the specified media location.
5. Leftover files from the download will be sent to your trash or recycling.

• BitTorrent - If you're downloading using a BitTorrent client, the process is slightly different:

1. Completed files are left in their original location to allow you to seed the file (ratio or time can be adjusted in the download client or from within Radarr under the specific download client). When files are imported to your media folder by default Radarr will copy the file, which uses twice the disk space.
2. An advanced option to hardlink can be enabled (Settings > Media Management > Importing) which will attempt to hardlink the media to your Series folder. A hardlink will allow not use any additional disk space. If the hardlink creation fails, Radarr will fall back to the default behavior and copy the file.
3. If the "Completed Download Handling - Remove" option is enabled in Radarr's settings, Radarr} will delete the original file and torrent from your client, but only if the client reports that seeding is complete and torrent is stopped.

Complete Download Handling

Radarr

Completed Download Handling is how Radarr imports media from your download client to your series folders. Many common issues are related to bad Docker paths and/or other Docker permissions issues.

Sonarr

Text

Lidarr

Text

Readarr

Text

Failed Download Handling

Radarr/Lidarr/Readarr

Failed Download Handling is compatible with SABnzbd and NZBGet.

There are a couple components that make up the failed download handling process:

1. Check Downloader:
   • Queue - Check your downloader's queue for password-protected (encrypted) releases
   • History - Check your downloader's history for failure (eg. not enough to repair, or extraction failed)
   • When Radarr finds a failed download it starts processing them and does a few things:
   1. Adds a failed event to Radarr's history
   2. Removes the failed download from Download Client to free space and clear downloaded files (optional)
   3. Starts searching for a replacement file (optional)
2. Blacklisting Allows automatic skipping of nzbs when they fail, this means that nzb will not be automatically downloaded by Radarr ever again (You can still force the download via a manual search).

There are 2 advanced options (on 'Download Client' settings page) that control the behavior of failed downloading in Radarr, at this time, they are all on by default.

• Redownload - Controls whether or not Radarr will search for the same file after a failure
• Remove - Whether or not the download should automatically be removed from Download Client when the failure is detected

Sonarr

Insert Text

Remote Path Mapping

Radarr

Remote Path Mapping acts as a dumb find Remote Path and replace with Local Path This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.

Sonarr

Remote Path Mapping acts as a dumb find Remote Path and replace with Local Path This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.

Lidarr

Remote Path Mapping acts as a dumb find Remote Path and replace with Local Path This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.

Readarr

Remote Path Mapping acts as a dumb find Remote Path and replace with Local Path This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.

Templates

Template:settings_download_clients_download_clients