Servarr - User contributions [en]

Docker Guide

2021-07-12T20:25:40Z

Bakerboy448:

[https://wiki.servarr.com/docker-guide Moved to the new wiki]

Docker ARM Synology

2021-07-12T20:25:33Z

Bakerboy448:

[https://wiki.servarr.com/en/docker-arm-synology Moved to the new wiki]

Docker ARM Synology

2021-07-12T20:24:55Z

Bakerboy448: Removed redirect to Https://wiki.servarr.com/en/docker-arm-synology

#REDIRECT https://wiki.servarr.com/en/docker-arm-synology

Docker ARM Synology

2021-07-12T20:24:44Z

Bakerboy448: Redirected page to Https://wiki.servarr.com/en/docker-arm-synology

#REDIRECT [[https://wiki.servarr.com/en/docker-arm-synology]]

Docker Guide

2021-06-20T06:36:04Z

Bakerboy448: Replaced content with "[https://wikijs.servarr.com/docker-guide Moved to the new wiki]"

[https://wikijs.servarr.com/docker-guide Moved to the new wiki]

Main Page

2021-06-20T06:32:22Z

Bakerboy448:

<div style="text-align: center;"> Servarr Wiki </div>

{| class="wikitable" style="width:70%; text-align:center; margin:auto; border=1px; border-color=#add8e6"
! style="color:red" | '''NOTE to all users'''
|-
|'''This wiki is only for V3 Radarr, V3 Sonarr, V1 Lidarr & V0.1 Readarr
|}
 Welcome to the consolidated wiki for [[Lidarr]], [[Radarr]], [[Readarr]], which are all forks of [[Sonarr]]. Collectively they are commonly referred to as "*Arr" or "*arrs". They are designed to automagically download, sort, organize, and monitor your Music, Movie, E-Book, or TV Show collections respectively.

== Main Wiki Pages ==
* [https://wikijs.servarr.com See the New Wiki]
* [[Radarr]]
* [[Sonarr]]
* [[Lidarr]]
* [[Readarr]] Note: Incomplete and Work-In-Progress due to Pre-Alpha state
* [[Docker Guide]]
* [[Useful Tools]]
* [[Cloud Setup|Cloud Setup - MergerFS, Google Drive, and Rclone]]
* [[Definitions|Defined Terms]]
* [[Docker ARM Synology]]

MediaWiki:Sidebar

2021-06-20T06:30:26Z

Bakerboy448:

MediaWiki:Sidebar

2021-06-20T06:29:00Z

Bakerboy448:

MediaWiki:Sidebar

2021-06-20T06:28:39Z

Bakerboy448:

Radarr FAQ

2021-06-08T09:37:12Z

Bakerboy448: /* Where did Wanted and Cut-off Unmet go? */

== How does Radarr work? ==
[[#how_does_radarr_work|anchor]] 
[[#How_does_Radarr_work|alt-anchor]] 
* Radarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Radarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Radarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Radarr's Release-Push API endpoint along with an IRC announce channel to push releases to Radarr for processing which can happen in near real time and with less overhead on the indexer and Radarr as Radarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== How does Radarr find movies? ==
[[#how_does_radarr_find_movies|anchor]] 
* Radarr does ''not'' regularly search for movie files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted movies, then compares that with its list of movies that are missing or need to be upgraded. Any matches are downloaded. This lets Radarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a movie, you'll need to set the correct path, profile and monitoring status then use the Start search for missing movie checkbox. If the movie hasn't been released yet, you don't need to initiate a search.
* Put another way, Radarr will only find movies that are newly uploaded to your indexers. It will not actively try to find movies you want that were uploaded in the past.
* If you've already added the movie, but now you want to search for it, you have a few choices. You can go to the movie's page and use the search button, which will do a search and then automatically pick one. You can use the Search tab and see ''all'' the results, hand picking the one you want. Or you can use the filters of <code>Missing</code>, <code>Wanted</code>, or <code>Cut-off Unmet</code>.
* If Radarr has been offline for an extended period of time, Radarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Radarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed movies.

== What is Minimum Availability? ==
[[#what_is_minimum_avalability|anchor]] 
- '''Announced''': Radarr shall consider movies available as soon as they are added to Radarr. This setting is recommended if you have good private trackers (or really good public ones, e.g. rarbg.to) that do not have fakes.

- '''In Cinemas''': Radarr shall consider movies available as soon as movies hit cinemas. This option is not recommended.

- '''Released''': Radarr shall consider movies available as soon as the blu-ray or streaming version is released. This option is recommended and likely should be combined with an Availability Delay of `-14` days.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Radarr/Radarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs can be found here].
'''''As of 5/27/2021 the logic is as follows'''''
# Quality
# Custom Format Score
# Protocol
# Indexer Priority
# Indexer Flags
# Seeds/Peers (If Torrent)
# Age (If Usenet)
# Size

== What are Lists and what can they do for me? ==
[[#what_are_lists_and_what_can_they_do_for_me|anchor]] 
* Lists are a part of Radarr that allow you to follow a given list creator.
* Let's say that you follow a given list creator on Trakt/TMDb and really like their Marvel Cinematic Universe film section and want to watch every movie on their list. You look in your Radarr and realize that you don't have those movies. Well instead of searching one by one and adding those lists and then searching your indexers for those movies. You can do this all at once with a List. The Lists can be set to import all the movies on that curators list as well as be set to automatically assign a quality profile, automatically add, and automatically monitor that movie.
* '''CAUTION:''' If lists are done improperly they will absolutely wreck your library with a bunch of trash you have no intention of watching. So make sure of what you're importing before you click save.
* ie. physically look at the list before you even go to Radarr.

== With the release of Radarr V3, what release should I download? ==
[[#with_the_release_of_radarr_v3_what_release_should_i_download|anchor]] 
Please see better information [[Radarr FAQ#How do I update Radarr?|here]]

== Why did the GUI / UI Change? Can it be changed back? ==
[[#why_did_the_gui_ui_change|anchor]] 
* Radarr is a fork of [[Sonarr]] which has the new UI.
* No it cannot be changed back. No it will not be changed back.
* You may, however, check out [https://github.com/gilbN/theme.park Theme Park]


== Where did Wanted and Cut-off Unmet go? ==
[[#where_did_wanted_and_cutoff_unmet_go|anchor]] 
* Movie Index (AKA 'Movies') -> Filter (top right corner) -> <code>Wanted</code> and <code>Cut-off Unmet</code>
** Wanted - Movie is missing, monitored, and available
** Missing - Movie is missing and monitored
[[File:radarr-where-did-wanted-and-cutoff-unmet-go.png|thumb|none|750px|alt=This is where wanted and Cut-off Unmet went|This is where wanted and Cut-off Unmet went]]

== Why can't I add a new movie to Radarr? ==
[[#why_cant_i_add_a_new_movie_to_radarr|anchor]] 
* Radarr uses [http://themoviedb.org The Movie Database (TMDb)] for movie information and images like fanart, banners and backgrounds. Generally, there are a few reasons why you may not be able to add a movie:
* TMDb doesn't like special characters to be used when searching for movies through the API (which Radarr uses), so try searching a translated name, and/or without special characters.
* You can also add by TMDb ID or, if TMDb has it, the IMDb ID
* The movie hasn't been added to TMDb yet, follow their [https://www.themoviedb.org/bible/new_content#59f7933c9251413e93000006 guide] to get it added.

== Can all my movie files be stored in one folder? ==
[[#can_all_my_movie_files_be_stored_in_one_folder|anchor]] 
* Not yet and the reason is that Radarr is a fork of [[Sonarr]], where every show has a folder. This limitation is a known pain point for many users and will maybe come in a future version.
:If you're looking to moving all your movies from one folder to individual folders check [[Radarr Tips and Tricks#Create a Folder for Each Movie|here]]

== Can I put all my movies in my library into one folder ==
[[Radarr FAQ#Can I put all my movies in my library into one folder|anchor]]

We get asked this a lot. There are no plans to support <code>\data\Movies\Movie1.mkv</code>, <code>\data\Movies\Movie2.mkv</code>, etc.

The [https://github.com/Radarr/Radarr/issues/153 Custom Folder GitHub Issue] technically covers this request, but it is no guarantee that all movie files in one folder will be implemented at that time.

A slight hack-ish solution is noted below. Please note that you mustn't trigger a rescan or it will show as missing and regardless the movie will never be upgraded.

* Use a Custom Script
** the script should be triggered on import
** it should be designed to move the file whenever you want it
** it then needs to call the Radarr API and change the movie to unmonitored.

== How can I rename my movie folders? ==
[[#how_can_i_rename_my_movie_folders|anchor]] 
# Movies
# Movie Editor
# Select what movies need their folder renamed
# Change Root Folder to the same Root Folder that the movies currently exist in
# Select "Yes move files"

== Movie File and Folder Naming ==
[[#movie_file_and_folder_naming|anchor]] 
* Currently, Radarr requires that each movie be in a folder with the format containing at minimum <code>Movie Title (Year)/</code>, optionally <code>_</code> or <code>.</code> are valid separators. To facilitate correct quality and resolution identification during import, a file name like <code>Movie Title (Year) [Quality-Resolution].ext</code> is best, again <code>_</code> or <code>.</code> are valid separators too.
* A useful tool for making these changes to your collection is [http://www.filebot.net/#download filebot] which has paid version in both the Apple and Windows stores, but can be found for free on their legacy [https://sourceforge.net/projects/filebot/files/latest/download SourceForge] site. It has both a GUI and CLI, so you can use whatever you’re comfortable with. For the above example, <code>{ny}</code> expands to <code>Name (Year)</code> and <code>{vf}</code> gives the resolution like <code>1080p</code>. There is nothing to infer quality, so you can fake it using <code>{ny}/{ny} [{dim[0] >= 1280 ? 'Bluray' : 'DVD'}-{vf}]</code> which will name anything lower than 720p to <code>[DVD-572p]</code> and greater or equal to 720p like <code>[Bluray-1080p]</code>.
See [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] for more details.

== Movie Folders Named Incorrectly ==
[[#movie_folders_named_incorrectly|anchor]] 
* Even if your movies are in folders already, the folders may not be named correctly. The folder name should be <code>Movie Title (Year)</code>, having the title and year in the folder’s name is critical right now.
* Examples that will work well:
** <code>/mnt/Movies/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** <code>/mnt/Kid Movies/Frozen (2013)/Frozen (2013) [Bluray-1080p].mkv</code>
* Examples that will work, but will require manual management:
** By letters: <code>/mnt/Movies/A-D/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By rating: <code>/mnt/Movies/R/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By genre: <code>/mnt/Movies/Crime, Drama, Sci-Fi/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** These examples will require manual management when the movie is added. Each of the examples will have many root directories, like <code>A-D</code> and <code>E-G</code> in the first letter example, <code>R</code> and <code>PG-13</code> in the rating example and you can guess at the variety of genre folders. When adding a new movie, the correct base folder will need to be selected for this format to work.
* Examples that won’t work:
** Single folder: <code>/mnt/Kid Movies/Frozen (2013) [Bluray-1080p].mkv</code>
*** At this time, movies simply have to be in a folder named after the movie. There is no way around this until development work is done to add this feature.
**'''Movie''' Folder Naming Formats from v0.2 that include '''File''' properties in the '''movie folder''' name such as <code>{Movie.Title}.{Release Year}.{Quality.Full}-{MediaInfo.Simple}{`Release.Group}</code> will not work in v3.
*** Folders are related to the movie and independent of the file. Additionally, this will break with the planned multiple files per movie support.
*** The other reason it was removed was it caused frequent confusion, database corruption, and generally was only half baked.
* The [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.

== How can I mass delete movies from the wanted list? ==
[[#how_can_i_mass_delete_movies_from_the_wanted_list|anchor]] 
* Use Movie Editor -> Select movies you want to delete -> Delete

== Why doesn't Radarr work behind a reverse proxy ==
[[#why_doesnt_radarr_work_behind_an_nginx_reverse_proxy|anchor]] 
* Starting with V3 Radarr has switched to .NET Core and a new webserver. In order for SignalR to work, the UI buttons to work, database changes to take, and other items. It requires the following addition to the location block for Radarr:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

* Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
* [https://github.com/aspnet/AspNetCore/issues/17081 See this ASP.NET Core issue]
* If you are using a CDN like Cloudflare ensure websockets are enabled to allow websocket connections.

== How do I update Radarr? ==
[[#how_do_i_update_my_radarr|anchor]] 
# Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
# Under the Development section change the branch name to <code>master</code> or <code>develop</code>
# Save
''This will not install the bits from that branch immediately, it will happen during the next update.''

* master (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. This is currently v3. This version will receive updates approximately monthly. On GitHub, this is the <code>master</code> branch.
* develop (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first. This is currently v3. This version will receive updates either weekly or biweekly depending on development. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is a snapshot of the <code>develop</code> branch at a point in time.
* nightly (Nightly): The bleeding edge. Released as soon as code is committed and passed all automated tests. '''''Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.''''' This is currently v3. This version is updated immediately. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is the <code>develop</code> branch.

* Note: If your install is through Docker append <code>:release</code>, <code>:latest</code>, or <code>:testing</code> to the end of your container tag depending on who makes your builds.
{| class="wikitable"
|+
!Current Versions
!master
!develop
!nightly
|-
|
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Frelease%2FVERSION.json Current Master/Latest]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Ftesting%2FVERSION.json Current Develop/Beta]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Fnightly%2FVERSION.json Current Nightly/Alpha]
|}
<center>
{| class="wikitable"
|-
! Release Channel Type !! Branch: master (stable) (v3.2.1) !! Branch: develop (beta) (v3.2.1) !! Branch: nightly (unstable) (v3.2)
|-
|[https://hub.docker.com/r/hotio/radarr hotio]||<code>hotio/radarr:release</code>||<code>hotio/radarr:testing</code>|| If you have to ask, you should not be on it.
|-
|[https://hub.docker.com/r/linuxserver/radarr LinuxServer.io]||<code>linuxserver/radarr:latest</code>||<code>linuxserver/radarr:develop</code>|| If you have to ask, you should not be on it.
|}
</center>

=== Installing a newer version ===
If Native:
# Go to System and then the Updates tab
# Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
If Docker:
# Repull your tag and update your container

== Can I switch from nightly back to develop? ==
[[#can_i_switch_from_nightly_back_to_develop|anchor]] 

[[Radarr_FAQ#Can I switch between branches?|See this related question]]

== Can I switch between branches? ==
[[#can_i_switch_between_branches|anchor]] 
* You can (almost) always increase your risk.
* <code>master</code> can go to <code>develop</code> or <code>nightly</code>
* <code>develop</code> can go to <code>nightly</code>
* Check with the development team to see if you can switch from <code>nightly</code> to <code>master</code>; <code>nightly</code> to <code>develop</code>; or <code>develop</code> to <code>master</code> for your given build.
* Failure to follow these instructions may result in your Radarr becoming unusable or throwing errors. You have been warned.
** The most common error is something like <code>Error parsing column 45 (Language=31 - Int64)</code> or other similar database errors around missing columns or tables.

* '''May 28 2021 Update'''
** <code>3.2.1</code> has been released as master/stable
** For those on nightly and are still on <code>3.2.1.5068</code> or lower you can safely downgrade to master or develop.
*** Develop can also downgrade to master as well.
*** Please note that if you're on nightly there will be no update to install given your build is higher than the current develop/master.

== How does radarr handle foreign movies or foreign titles? ==
[[#how_does_radarr_handle_foreign_movies_or_foreign_titles|anchor]] 
* Radarr uses both Alt Titles and Translations for parsing and searching. Search will use the Original Title, English Title, and Translated Title from whatever languages you have preferred (in profile and CFs). Parsing should look for a match in all Translations and Alt Titles.

* To get a movie in a foreign language set your Profile Language to Original (Movie's Original Language), a specific language for that profile, or any and use custom formats to determine which language to grab.
* Note that this does not include any indexer languages specified as multi.

== How does radarr handle "multi" in names? ==
[[#how_does_radarr_handle_multi_in_names|anchor]] 
* Radarr by default assumes multi is english and french unless specified in your indexer's advanced settings in Radarr.

* Note that multi definitions only help for release parsing and not for foreign titles or movies searches.

== Help, Movie Added, But Not Searched ==
[[#help_movie_added_but_not_searched|anchor]] 

* Neither Radarr nor Sonarr ''actively'' search for missing movies automatically. Instead, a periodic query of new posts is made to all indexers configured for RSS. When a wanted or cutoff unmet movie shows up in that list, it gets downloaded. This means that until a movie is posted (or reposted), it won’t get downloaded.
* If you’re adding a movie that you want now, the best option is to check the “Start search for missing movie” box, to the left of the ''Add Movie'' ('''1''') button. You can also go to the page for a movie you’ve added and click the magnifying glass “Search” ('''2''') button or use the Wanted view to search for Missing or Cutoff Unmet movies.

[[File:start search for missing movie.png|thumb|none|750px|alt=Add and Search for movie|Add and Search for movie]]
[[File:Search selected movie.png||thumb|none|750px|altt=Search selected movie|Search selected movie]]

== Root path for movies imported from lists becomes “C:” or other weird paths ==
[[#root_path_for_movies_imported_from_lists_become_c_or_other_weird_paths|anchor]] 
* Sometimes you can get a problem that movies that are imported from your lists, gets imported with the root path set to “C:” or other weird paths.

* This is a known issue for when the root path is either not setup during the creation of the list, or if the root path has been deleted after the list was created. Note that this problem can still occur even if the list is '''edited''' and the correct root path is set.

* Use the Movie Editor to fix paths of existing movies.

== Movie Imported, But Source File And Torrent Not Deleted ==
[[#movie_imported_but_source_file_and_torrent_not_deleted|anchor]] 
* Check if you have Completed Download Handling - Remove turned on. (This does not work if you are using rtorrent.)

[[File:Remove turned on.png|thumb|none|750px|alt=Settings|Settings > Download Clients]]

* If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.

== My Custom Script stopped working after upgrading from v0.2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v0.2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== I am using a Pi and Raspbian and Radarr will not launch ==
[[#i_am_using_a_pi_and_raspbian_and_radarr_will_not_launch|anchor]] Raspbian has a version of libseccomp2 that is too old to support running a docker container based on Ubuntu 20.04, which both hotio and LinuxServer use as their base for v3. You either need to use <code>--privileged</code>, update libseccomp2 from Ubuntu or get a better OS (We recommend Ubuntu 20.04 arm64)

'''Possible Solution:'''

Managed to fix the issue by installing the backport from debian repo. Generally not recommended to use backport in blanket upgrade mode. Installation of a single package may be ok but may also cause issues. So got to understand what you are doing.

Steps to fix:

First ensure you are running Raspbian buster e.g using <code>lsb_release -a</code>

Distributor ID: Raspbian

Description: Raspbian GNU/Linux 10 (buster)

Release: 10

Codename: buster

''If you are using buster:''
<code>Add the line `deb <nowiki>http://deb.debian.org/debian</nowiki> buster-backports` main to `/etc/apt/sources.list`
Run apt-get update
apt-get -t buster-backports install libseccomp2</code>

== Why are lists sync times so long and can I change it? ==
[[#why_are_lists_sync_times_so_long_and_can_i_change_it|anchor]]

Lists never were nor are intended to be <code>add it now</code> they are <code>hey i want this, add it eventually</code> tools

You can trigger a list refresh manually, script it and trigger it via the API, add the movies to radarr, use Ombi, or any similar app that adds them right away

This change was due to not have our server get killed by people updating lists every 10 minutes.

== Why doesn't Radarr work behind an nginx reverse proxy ==

[[Radarr_FAQ#Why_doesn.27t_Radarr_work_behind_a_reverse_proxy|See this section]]

== Can I disable the refresh movies task ==
[[#can_I_disable_the_refresh_movies_task|anchor]]

No, nor should you through any SQL hackery. The refresh movies task queries the upstream Servarr proxy and checks to see if the metadata for each movie (ids, cast, summary, rating, translations, alt titles, etc.) has updated compared to what is currently in Radarr. If necessary, it will then update the applicable movies.

A common complaint is the Refresh task causes heavy I/O usage. This is partly due to the setting "Analyze video files" which is advised to be enabled if you use tdarr or otherwise externally modify your files. If you don't you can safely disable "Analyze video files" to reduce some I/O. The other setting is "Rescan Movie Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to <code>Manual</code>. Do not change this to <code>Never</code> unless all changes to your library (new movies, upgrades, deletions etc) are done through Radarr. If you delete movie files manually or via Plex or another third party program, do not set this to <code>Never</code>.

{{FAQ|ARRNAME=Radarr|ARRDISCORD=https://radarr.video/discord|ARRPORT=7878}}

Prowlarr Troubleshooting

2021-06-08T02:03:08Z

Bakerboy448:

[https://wikijs.servarr.com/prowlarr/troubleshooting#logging-and-log-files Moved to WikiJS]

Prowlarr Troubleshooting

2021-06-08T02:02:39Z

Bakerboy448: Removed redirect to Https://wikijs.servarr.com/prowlarr/troubleshooting#logging-and-log-files

#REDIRECT [https://wikijs.servarr.com/prowlarr/troubleshooting#logging-and-log-files]

Prowlarr Troubleshooting

2021-06-08T02:02:18Z

Bakerboy448: Redirected page to Https://wikijs.servarr.com/prowlarr/troubleshooting#logging-and-log-files

#REDIRECT [[https://wikijs.servarr.com/prowlarr/troubleshooting#logging-and-log-files]]

MediaWiki:Sidebar

2021-06-06T21:19:40Z

Bakerboy448:

MediaWiki:Sidebar

2021-06-06T21:19:16Z

Bakerboy448:

Radarr FAQ

2021-05-28T16:22:51Z

Bakerboy448:

== How does Radarr work? ==
[[#how_does_radarr_work|anchor]] 
[[#How_does_Radarr_work|alt-anchor]] 
* Radarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Radarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Radarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Radarr's Release-Push API endpoint along with an IRC announce channel to push releases to Radarr for processing which can happen in near real time and with less overhead on the indexer and Radarr as Radarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== How does Radarr find movies? ==
[[#how_does_radarr_find_movies|anchor]] 
* Radarr does ''not'' regularly search for movie files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted movies, then compares that with its list of movies that are missing or need to be upgraded. Any matches are downloaded. This lets Radarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a movie, you'll need to set the correct path, profile and monitoring status then use the Start search for missing movie checkbox. If the movie hasn't been released yet, you don't need to initiate a search.
* Put another way, Radarr will only find movies that are newly uploaded to your indexers. It will not actively try to find movies you want that were uploaded in the past.
* If you've already added the movie, but now you want to search for it, you have a few choices. You can go to the movie's page and use the search button, which will do a search and then automatically pick one. You can use the Search tab and see ''all'' the results, hand picking the one you want. Or you can use the filters of <code>Missing</code>, <code>Wanted</code>, or <code>Cut-off Unmet</code>.
* If Radarr has been offline for an extended period of time, Radarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Radarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed movies.

== What is Minimum Availability? ==
[[#what_is_minimum_avalability|anchor]] 
- '''Announced''': Radarr shall consider movies available as soon as they are added to Radarr. This setting is recommended if you have good private trackers (or really good public ones, e.g. rarbg.to) that do not have fakes.

- '''In Cinemas''': Radarr shall consider movies available as soon as movies hit cinemas. This option is not recommended.

- '''Released''': Radarr shall consider movies available as soon as the blu-ray or streaming version is released. This option is recommended and likely should be combined with an Availability Delay of `-14` days.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Radarr/Radarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs can be found here].
'''''As of 5/27/2021 the logic is as follows'''''
# Quality
# Custom Format Score
# Protocol
# Indexer Priority
# Indexer Flags
# Seeds/Peers (If Torrent)
# Age (If Usenet)
# Size

== What are Lists and what can they do for me? ==
[[#what_are_lists_and_what_can_they_do_for_me|anchor]] 
* Lists are a part of Radarr that allow you to follow a given list creator.
* Let's say that you follow a given list creator on Trakt/TMDb and really like their Marvel Cinematic Universe film section and want to watch every movie on their list. You look in your Radarr and realize that you don't have those movies. Well instead of searching one by one and adding those lists and then searching your indexers for those movies. You can do this all at once with a List. The Lists can be set to import all the movies on that curators list as well as be set to automatically assign a quality profile, automatically add, and automatically monitor that movie.
* '''CAUTION:''' If lists are done improperly they will absolutely wreck your library with a bunch of trash you have no intention of watching. So make sure of what you're importing before you click save.
* ie. physically look at the list before you even go to Radarr.

== With the release of Radarr V3, what release should I download? ==
[[#with_the_release_of_radarr_v3_what_release_should_i_download|anchor]] 
Please see better information [[Radarr FAQ#How do I update Radarr?|here]]

== Why did the GUI / UI Change? Can it be changed back? ==
[[#why_did_the_gui_ui_change|anchor]] 
* Radarr is a fork of [[Sonarr]] which has the new UI.
* No it cannot be changed back. No it will not be changed back.
* You may, however, check out [https://github.com/gilbN/theme.park Theme Park]


== Where did Wanted and Cut-off Unmet go? ==
[[#where_did_wanted_and_cutoff_unmet_go|anchor]] 
* Movie Index (AKA 'Movies') -> Filter (top right corner) -> <code>Wanted</code> and <code>Cut-off Unmet</code>
[[File:radarr-where-did-wanted-and-cutoff-unmet-go.png|thumb|none|750px|alt=This is where wanted and Cut-off Unmet went|This is where wanted and Cut-off Unmet went]]

== Why can't I add a new movie to Radarr? ==
[[#why_cant_i_add_a_new_movie_to_radarr|anchor]] 
* Radarr uses [http://themoviedb.org The Movie Database (TMDb)] for movie information and images like fanart, banners and backgrounds. Generally, there are a few reasons why you may not be able to add a movie:
* TMDb doesn't like special characters to be used when searching for movies through the API (which Radarr uses), so try searching a translated name, and/or without special characters.
* You can also add by TMDb ID or, if TMDb has it, the IMDb ID
* The movie hasn't been added to TMDb yet, follow their [https://www.themoviedb.org/bible/new_content#59f7933c9251413e93000006 guide] to get it added.

== Can all my movie files be stored in one folder? ==
[[#can_all_my_movie_files_be_stored_in_one_folder|anchor]] 
* Not yet and the reason is that Radarr is a fork of [[Sonarr]], where every show has a folder. This limitation is a known pain point for many users and will maybe come in a future version.
:If you're looking to moving all your movies from one folder to individual folders check [[Radarr Tips and Tricks#Create a Folder for Each Movie|here]]

== Can I put all my movies in my library into one folder ==
[[Radarr FAQ#Can I put all my movies in my library into one folder|anchor]]

We get asked this a lot. There are no plans to support <code>\data\Movies\Movie1.mkv</code>, <code>\data\Movies\Movie2.mkv</code>, etc.

The [https://github.com/Radarr/Radarr/issues/153 Custom Folder GitHub Issue] technically covers this request, but it is no guarantee that all movie files in one folder will be implemented at that time.

A slight hack-ish solution is noted below. Please note that you mustn't trigger a rescan or it will show as missing and regardless the movie will never be upgraded.

* Use a Custom Script
** the script should be triggered on import
** it should be designed to move the file whenever you want it
** it then needs to call the Radarr API and change the movie to unmonitored.

== How can I rename my movie folders? ==
[[#how_can_i_rename_my_movie_folders|anchor]] 
# Movies
# Movie Editor
# Select what movies need their folder renamed
# Change Root Folder to the same Root Folder that the movies currently exist in
# Select "Yes move files"

== Movie File and Folder Naming ==
[[#movie_file_and_folder_naming|anchor]] 
* Currently, Radarr requires that each movie be in a folder with the format containing at minimum <code>Movie Title (Year)/</code>, optionally <code>_</code> or <code>.</code> are valid separators. To facilitate correct quality and resolution identification during import, a file name like <code>Movie Title (Year) [Quality-Resolution].ext</code> is best, again <code>_</code> or <code>.</code> are valid separators too.
* A useful tool for making these changes to your collection is [http://www.filebot.net/#download filebot] which has paid version in both the Apple and Windows stores, but can be found for free on their legacy [https://sourceforge.net/projects/filebot/files/latest/download SourceForge] site. It has both a GUI and CLI, so you can use whatever you’re comfortable with. For the above example, <code>{ny}</code> expands to <code>Name (Year)</code> and <code>{vf}</code> gives the resolution like <code>1080p</code>. There is nothing to infer quality, so you can fake it using <code>{ny}/{ny} [{dim[0] >= 1280 ? 'Bluray' : 'DVD'}-{vf}]</code> which will name anything lower than 720p to <code>[DVD-572p]</code> and greater or equal to 720p like <code>[Bluray-1080p]</code>.
See [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] for more details.

== Movie Folders Named Incorrectly ==
[[#movie_folders_named_incorrectly|anchor]] 
* Even if your movies are in folders already, the folders may not be named correctly. The folder name should be <code>Movie Title (Year)</code>, having the title and year in the folder’s name is critical right now.
* Examples that will work well:
** <code>/mnt/Movies/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** <code>/mnt/Kid Movies/Frozen (2013)/Frozen (2013) [Bluray-1080p].mkv</code>
* Examples that will work, but will require manual management:
** By letters: <code>/mnt/Movies/A-D/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By rating: <code>/mnt/Movies/R/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By genre: <code>/mnt/Movies/Crime, Drama, Sci-Fi/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** These examples will require manual management when the movie is added. Each of the examples will have many root directories, like <code>A-D</code> and <code>E-G</code> in the first letter example, <code>R</code> and <code>PG-13</code> in the rating example and you can guess at the variety of genre folders. When adding a new movie, the correct base folder will need to be selected for this format to work.
* Examples that won’t work:
** Single folder: <code>/mnt/Kid Movies/Frozen (2013) [Bluray-1080p].mkv</code>
*** At this time, movies simply have to be in a folder named after the movie. There is no way around this until development work is done to add this feature.
**'''Movie''' Folder Naming Formats from v0.2 that include '''File''' properties in the '''movie folder''' name such as <code>{Movie.Title}.{Release Year}.{Quality.Full}-{MediaInfo.Simple}{`Release.Group}</code> will not work in v3.
*** Folders are related to the movie and independent of the file. Additionally, this will break with the planned multiple files per movie support.
*** The other reason it was removed was it caused frequent confusion, database corruption, and generally was only half baked.
* The [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.

== How can I mass delete movies from the wanted list? ==
[[#how_can_i_mass_delete_movies_from_the_wanted_list|anchor]] 
* Use Movie Editor -> Select movies you want to delete -> Delete

== Why doesn't Radarr work behind a reverse proxy ==
[[#why_doesnt_radarr_work_behind_an_nginx_reverse_proxy|anchor]] 
* Starting with V3 Radarr has switched to .NET Core and a new webserver. In order for SignalR to work, the UI buttons to work, database changes to take, and other items. It requires the following addition to the location block for Radarr:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

* Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
* [https://github.com/aspnet/AspNetCore/issues/17081 See this ASP.NET Core issue]
* If you are using a CDN like Cloudflare ensure websockets are enabled to allow websocket connections.

== How do I update Radarr? ==
[[#how_do_i_update_my_radarr|anchor]] 
# Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
# Under the Development section change the branch name to <code>master</code> or <code>develop</code>
# Save
''This will not install the bits from that branch immediately, it will happen during the next update.''

* master (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. This is currently v3. This version will receive updates approximately monthly. On GitHub, this is the <code>master</code> branch.
* develop (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first. This is currently v3. This version will receive updates either weekly or biweekly depending on development. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is a snapshot of the <code>develop</code> branch at a point in time.
* nightly (Nightly): The bleeding edge. Released as soon as code is committed and passed all automated tests. '''''Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.''''' This is currently v3. This version is updated immediately. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is the <code>develop</code> branch.

* Note: If your install is through Docker append <code>:release</code>, <code>:latest</code>, or <code>:testing</code> to the end of your container tag depending on who makes your builds.
{| class="wikitable"
|+
!Current Versions
!master
!develop
!nightly
|-
|
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Frelease%2FVERSION.json Current Master/Latest]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Ftesting%2FVERSION.json Current Develop/Beta]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Fnightly%2FVERSION.json Current Nightly/Alpha]
|}
<center>
{| class="wikitable"
|-
! Release Channel Type !! Branch: master (stable) (v3.2.1) !! Branch: develop (beta) (v3.2.1) !! Branch: nightly (unstable) (v3.2)
|-
|[https://hub.docker.com/r/hotio/radarr hotio]||<code>hotio/radarr:release</code>||<code>hotio/radarr:testing</code>|| If you have to ask, you should not be on it.
|-
|[https://hub.docker.com/r/linuxserver/radarr LinuxServer.io]||<code>linuxserver/radarr:latest</code>||<code>linuxserver/radarr:develop</code>|| If you have to ask, you should not be on it.
|}
</center>

=== Installing a newer version ===
If Native:
# Go to System and then the Updates tab
# Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
If Docker:
# Repull your tag and update your container

== Can I switch from nightly back to develop? ==
[[#can_i_switch_from_nightly_back_to_develop|anchor]] 

[[Radarr_FAQ#Can I switch between branches?|See this related question]]

== Can I switch between branches? ==
[[#can_i_switch_between_branches|anchor]] 
* You can (almost) always increase your risk.
* <code>master</code> can go to <code>develop</code> or <code>nightly</code>
* <code>develop</code> can go to <code>nightly</code>
* Check with the development team to see if you can switch from <code>nightly</code> to <code>master</code>; <code>nightly</code> to <code>develop</code>; or <code>develop</code> to <code>master</code> for your given build.
* Failure to follow these instructions may result in your Radarr becoming unusable or throwing errors. You have been warned.
** The most common error is something like <code>Error parsing column 45 (Language=31 - Int64)</code> or other similar database errors around missing columns or tables.

* '''May 28 2021 Update'''
** <code>3.2.1</code> has been released as master/stable
** For those on nightly and are still on <code>3.2.1.5068</code> or lower you can safely downgrade to master or develop.
*** Develop can also downgrade to master as well.
*** Please note that if you're on nightly there will be no update to install given your build is higher than the current develop/master.

== How does radarr handle foreign movies or foreign titles? ==
[[#how_does_radarr_handle_foreign_movies_or_foreign_titles|anchor]] 
* Radarr uses both Alt Titles and Translations for parsing and searching. Search will use the Original Title, English Title, and Translated Title from whatever languages you have preferred (in profile and CFs). Parsing should look for a match in all Translations and Alt Titles.

* To get a movie in a foreign language set your Profile Language to Original (Movie's Original Language), a specific language for that profile, or any and use custom formats to determine which language to grab.
* Note that this does not include any indexer languages specified as multi.

== How does radarr handle "multi" in names? ==
[[#how_does_radarr_handle_multi_in_names|anchor]] 
* Radarr by default assumes multi is english and french unless specified in your indexer's advanced settings in Radarr.

* Note that multi definitions only help for release parsing and not for foreign titles or movies searches.

== Help, Movie Added, But Not Searched ==
[[#help_movie_added_but_not_searched|anchor]] 

* Neither Radarr nor Sonarr ''actively'' search for missing movies automatically. Instead, a periodic query of new posts is made to all indexers configured for RSS. When a wanted or cutoff unmet movie shows up in that list, it gets downloaded. This means that until a movie is posted (or reposted), it won’t get downloaded.
* If you’re adding a movie that you want now, the best option is to check the “Start search for missing movie” box, to the left of the ''Add Movie'' ('''1''') button. You can also go to the page for a movie you’ve added and click the magnifying glass “Search” ('''2''') button or use the Wanted view to search for Missing or Cutoff Unmet movies.

[[File:start search for missing movie.png|thumb|none|750px|alt=Add and Search for movie|Add and Search for movie]]
[[File:Search selected movie.png||thumb|none|750px|altt=Search selected movie|Search selected movie]]

== Root path for movies imported from lists becomes “C:” or other weird paths ==
[[#root_path_for_movies_imported_from_lists_become_c_or_other_weird_paths|anchor]] 
* Sometimes you can get a problem that movies that are imported from your lists, gets imported with the root path set to “C:” or other weird paths.

* This is a known issue for when the root path is either not setup during the creation of the list, or if the root path has been deleted after the list was created. Note that this problem can still occur even if the list is '''edited''' and the correct root path is set.

* Use the Movie Editor to fix paths of existing movies.

== Movie Imported, But Source File And Torrent Not Deleted ==
[[#movie_imported_but_source_file_and_torrent_not_deleted|anchor]] 
* Check if you have Completed Download Handling - Remove turned on. (This does not work if you are using rtorrent.)

[[File:Remove turned on.png|thumb|none|750px|alt=Settings|Settings > Download Clients]]

* If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.

== My Custom Script stopped working after upgrading from v0.2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v0.2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== I am using a Pi and Raspbian and Radarr will not launch ==
[[#i_am_using_a_pi_and_raspbian_and_radarr_will_not_launch|anchor]] Raspbian has a version of libseccomp2 that is too old to support running a docker container based on Ubuntu 20.04, which both hotio and LinuxServer use as their base for v3. You either need to use <code>--privileged</code>, update libseccomp2 from Ubuntu or get a better OS (We recommend Ubuntu 20.04 arm64)

'''Possible Solution:'''

Managed to fix the issue by installing the backport from debian repo. Generally not recommended to use backport in blanket upgrade mode. Installation of a single package may be ok but may also cause issues. So got to understand what you are doing.

Steps to fix:

First ensure you are running Raspbian buster e.g using <code>lsb_release -a</code>

Distributor ID: Raspbian

Description: Raspbian GNU/Linux 10 (buster)

Release: 10

Codename: buster

''If you are using buster:''
<code>Add the line `deb <nowiki>http://deb.debian.org/debian</nowiki> buster-backports` main to `/etc/apt/sources.list`
Run apt-get update
apt-get -t buster-backports install libseccomp2</code>

== Why are lists sync times so long and can I change it? ==
[[#why_are_lists_sync_times_so_long_and_can_i_change_it|anchor]]

Lists never were nor are intended to be <code>add it now</code> they are <code>hey i want this, add it eventually</code> tools

You can trigger a list refresh manually, script it and trigger it via the API, add the movies to radarr, use Ombi, or any similar app that adds them right away

This change was due to not have our server get killed by people updating lists every 10 minutes.

== Why doesn't Radarr work behind an nginx reverse proxy ==

[[Radarr_FAQ#Why_doesn.27t_Radarr_work_behind_a_reverse_proxy|See this section]]

== Can I disable the refresh movies task ==
[[#can_I_disable_the_refresh_movies_task|anchor]]

No, nor should you through any SQL hackery. The refresh movies task queries the upstream Servarr proxy and checks to see if the metadata for each movie (ids, cast, summary, rating, translations, alt titles, etc.) has updated compared to what is currently in Radarr. If necessary, it will then update the applicable movies.

A common complaint is the Refresh task causes heavy I/O usage. This is partly due to the setting "Analyze video files" which is advised to be enabled if you use tdarr or otherwise externally modify your files. If you don't you can safely disable "Analyze video files" to reduce some I/O. The other setting is "Rescan Movie Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to <code>Manual</code>. Do not change this to <code>Never</code> unless all changes to your library (new movies, upgrades, deletions etc) are done through Radarr. If you delete movie files manually or via Plex or another third party program, do not set this to <code>Never</code>.

{{FAQ|ARRNAME=Radarr|ARRDISCORD=https://radarr.video/discord|ARRPORT=7878}}

Radarr FAQ

2021-05-28T02:49:27Z

Bakerboy448: /* How does Radarr find movies? */

== How does Radarr work? ==
[[#how_does_radarr_work|anchor]] 
[[#How_does_Radarr_work|alt-anchor]] 
* Radarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Radarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Radarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Radarr's Release-Push API endpoint along with an IRC announce channel to push releases to Radarr for processing which can happen in near real time and with less overhead on the indexer and Radarr as Radarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== How does Radarr find movies? ==
[[#how_does_radarr_find_movies|anchor]] 
* Radarr does ''not'' regularly search for movie files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted movies, then compares that with its list of movies that are missing or need to be upgraded. Any matches are downloaded. This lets Radarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a movie, you'll need to set the correct path, profile and monitoring status then use the Start search for missing movie checkbox. If the movie hasn't been released yet, you don't need to initiate a search.
* Put another way, Radarr will only find movies that are newly uploaded to your indexers. It will not actively try to find movies you want that were uploaded in the past.
* If you've already added the movie, but now you want to search for it, you have a few choices. You can go to the movie's page and use the search button, which will do a search and then automatically pick one. You can use the Search tab and see ''all'' the results, hand picking the one you want. Or you can use the filters of <code>Missing</code>, <code>Wanted</code>, or <code>Cut-off Unmet</code>.
* If Radarr has been offline for an extended period of time, Radarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Radarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed movies.

== What is Minimum Availability? ==
[[#what_is_minimum_avalability|anchor]] 
- '''Announced''': Radarr shall consider movies available as soon as they are added to Radarr. This setting is recommended if you have good private trackers (or really good public ones, e.g. rarbg.to) that do not have fakes.

- '''In Cinemas''': Radarr shall consider movies available as soon as movies hit cinemas. This option is not recommended.

- '''Released''': Radarr shall consider movies available as soon as the blu-ray or streaming version is released. This option is recommended and likely should be combined with an Availability Delay of `-14` days.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Radarr/Radarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs can be found here].
'''''As of 5/27/2021 the logic is as follows'''''
# Quality
# Custom Format Score
# Protocol
# Indexer Priority
# Indexer Flags
# Seeds/Peers (If Torrent)
# Age (If Usenet)
# Size

== What are Lists and what can they do for me? ==
[[#what_are_lists_and_what_can_they_do_for_me|anchor]] 
* Lists are a part of Radarr that allow you to follow a given list creator.
* Let's say that you follow a given list creator on Trakt/TMDb and really like their Marvel Cinematic Universe film section and want to watch every movie on their list. You look in your Radarr and realize that you don't have those movies. Well instead of searching one by one and adding those lists and then searching your indexers for those movies. You can do this all at once with a List. The Lists can be set to import all the movies on that curators list as well as be set to automatically assign a quality profile, automatically add, and automatically monitor that movie.
* '''CAUTION:''' If lists are done improperly they will absolutely wreck your library with a bunch of trash you have no intention of watching. So make sure of what you're importing before you click save.
* ie. physically look at the list before you even go to Radarr.

== With the release of Radarr V3, what release should I download? ==
[[#with_the_release_of_radarr_v3_what_release_should_i_download|anchor]] 
Please see better information [[Radarr FAQ#How do I update Radarr?|here]]

== Why did the GUI / UI Change? Can it be changed back? ==
[[#why_did_the_gui_ui_change|anchor]] 
* Radarr is a fork of [[Sonarr]] which has the new UI.
* No it cannot be changed back. No it will not be changed back.
* You may, however, check out [https://github.com/gilbN/theme.park Theme Park]


== Where did Wanted and Cut-off Unmet go? ==
[[#where_did_wanted_and_cutoff_unmet_go|anchor]] 
* Movie Index (AKA 'Movies') -> Filter (top right corner) -> <code>Wanted</code> and <code>Cut-off Unmet</code>
[[File:radarr-where-did-wanted-and-cutoff-unmet-go.png|thumb|none|750px|alt=This is where wanted and Cut-off Unmet went|This is where wanted and Cut-off Unmet went]]

== Why can't I add a new movie to Radarr? ==
[[#why_cant_i_add_a_new_movie_to_radarr|anchor]] 
* Radarr uses [http://themoviedb.org The Movie Database (TMDb)] for movie information and images like fanart, banners and backgrounds. Generally, there are a few reasons why you may not be able to add a movie:
* TMDb doesn't like special characters to be used when searching for movies through the API (which Radarr uses), so try searching a translated name, and/or without special characters.
* You can also add by TMDb ID or, if TMDb has it, the IMDb ID
* The movie hasn't been added to TMDb yet, follow their [https://www.themoviedb.org/bible/new_content#59f7933c9251413e93000006 guide] to get it added.

== Can all my movie files be stored in one folder? ==
[[#can_all_my_movie_files_be_stored_in_one_folder|anchor]] 
* Not yet and the reason is that Radarr is a fork of [[Sonarr]], where every show has a folder. This limitation is a known pain point for many users and will maybe come in a future version.
:If you're looking to moving all your movies from one folder to individual folders check [[Radarr Tips and Tricks#Create a Folder for Each Movie|here]]

== Can I put all my movies in my library into one folder ==
[[Radarr FAQ#Can I put all my movies in my library into one folder|anchor]]

We get asked this a lot. There are no plans to support <code>\data\Movies\Movie1.mkv</code>, <code>\data\Movies\Movie2.mkv</code>, etc.

The [https://github.com/Radarr/Radarr/issues/153 Custom Folder GitHub Issue] technically covers this request, but it is no guarantee that all movie files in one folder will be implemented at that time.

A slight hack-ish solution is noted below. Please note that you mustn't trigger a rescan or it will show as missing and regardless the movie will never be upgraded.

* Use a Custom Script
** the script should be triggered on import
** it should be designed to move the file whenever you want it
** it then needs to call the Radarr API and change the movie to unmonitored.

== How can I rename my movie folders? ==
[[#how_can_i_rename_my_movie_folders|anchor]] 
# Movies
# Movie Editor
# Select what movies need their folder renamed
# Change Root Folder to the same Root Folder that the movies currently exist in
# Select "Yes move files"

== Movie File and Folder Naming ==
[[#movie_file_and_folder_naming|anchor]] 
* Currently, Radarr requires that each movie be in a folder with the format containing at minimum <code>Movie Title (Year)/</code>, optionally <code>_</code> or <code>.</code> are valid separators. To facilitate correct quality and resolution identification during import, a file name like <code>Movie Title (Year) [Quality-Resolution].ext</code> is best, again <code>_</code> or <code>.</code> are valid separators too.
* A useful tool for making these changes to your collection is [http://www.filebot.net/#download filebot] which has paid version in both the Apple and Windows stores, but can be found for free on their legacy [https://sourceforge.net/projects/filebot/files/latest/download SourceForge] site. It has both a GUI and CLI, so you can use whatever you’re comfortable with. For the above example, <code>{ny}</code> expands to <code>Name (Year)</code> and <code>{vf}</code> gives the resolution like <code>1080p</code>. There is nothing to infer quality, so you can fake it using <code>{ny}/{ny} [{dim[0] >= 1280 ? 'Bluray' : 'DVD'}-{vf}]</code> which will name anything lower than 720p to <code>[DVD-572p]</code> and greater or equal to 720p like <code>[Bluray-1080p]</code>.
See [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] for more details.

== Movie Folders Named Incorrectly ==
[[#movie_folders_named_incorrectly|anchor]] 
* Even if your movies are in folders already, the folders may not be named correctly. The folder name should be <code>Movie Title (Year)</code>, having the title and year in the folder’s name is critical right now.
* Examples that will work well:
** <code>/mnt/Movies/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** <code>/mnt/Kid Movies/Frozen (2013)/Frozen (2013) [Bluray-1080p].mkv</code>
* Examples that will work, but will require manual management:
** By letters: <code>/mnt/Movies/A-D/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By rating: <code>/mnt/Movies/R/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By genre: <code>/mnt/Movies/Crime, Drama, Sci-Fi/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** These examples will require manual management when the movie is added. Each of the examples will have many root directories, like <code>A-D</code> and <code>E-G</code> in the first letter example, <code>R</code> and <code>PG-13</code> in the rating example and you can guess at the variety of genre folders. When adding a new movie, the correct base folder will need to be selected for this format to work.
* Examples that won’t work:
** Single folder: <code>/mnt/Kid Movies/Frozen (2013) [Bluray-1080p].mkv</code>
*** At this time, movies simply have to be in a folder named after the movie. There is no way around this until development work is done to add this feature.
**'''Movie''' Folder Naming Formats from v0.2 that include '''File''' properties in the '''movie folder''' name such as <code>{Movie.Title}.{Release Year}.{Quality.Full}-{MediaInfo.Simple}{`Release.Group}</code> will not work in v3.
*** Folders are related to the movie and independent of the file. Additionally, this will break with the planned multiple files per movie support.
*** The other reason it was removed was it caused frequent confusion, database corruption, and generally was only half baked.
* The [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.

== How can I mass delete movies from the wanted list? ==
[[#how_can_i_mass_delete_movies_from_the_wanted_list|anchor]] 
* Use Movie Editor -> Select movies you want to delete -> Delete

== Why doesn't Radarr work behind a reverse proxy ==
[[#why_doesnt_radarr_work_behind_an_nginx_reverse_proxy|anchor]] 
* Starting with V3 Radarr has switched to .NET Core and a new webserver. In order for SignalR to work, the UI buttons to work, database changes to take, and other items. It requires the following addition to the location block for Radarr:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

* Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
* [https://github.com/aspnet/AspNetCore/issues/17081 See this ASP.NET Core issue]
* If you are using a CDN like Cloudflare ensure websockets are enabled to allow websocket connections.

== How do I update Radarr? ==
[[#how_do_i_update_my_radarr|anchor]] 
# Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
# Under the Development section change the branch name to <code>master</code> or <code>develop</code>
# Save
''This will not install the bits from that branch immediately, it will happen during the next update.''

* master (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. This is currently v3. This version will receive updates approximately monthly. On GitHub, this is the <code>master</code> branch.
* develop (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first. This is currently v3. This version will receive updates either weekly or biweekly depending on development. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is a snapshot of the <code>develop</code> branch at a point in time.
* nightly (Nightly): The bleeding edge. Released as soon as code is committed and passed all automated tests. '''''Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.''''' This is currently v3. This version is updated immediately. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is the <code>develop</code> branch.

* Note: If your install is through Docker append <code>:release</code>, <code>:latest</code>, or <code>:testing</code> to the end of your container tag depending on who makes your builds.
{| class="wikitable"
|+
!Current Versions
!master
!develop
!nightly
|-
|
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Frelease%2FVERSION.json Current Master/Latest]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Ftesting%2FVERSION.json Current Develop/Beta]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Fnightly%2FVERSION.json Current Nightly/Alpha]
|}
<center>
{| class="wikitable"
|-
! Release Channel Type !! Branch: master (stable) (v3.2) !! Branch: develop (beta) (v3.2) !! Branch: nightly (unstable) (v3.2)
|-
|[https://hub.docker.com/r/hotio/radarr hotio]||<code>hotio/radarr:release</code>||<code>hotio/radarr:testing</code>|| If you have to ask, you should not be on it.
|-
|[https://hub.docker.com/r/linuxserver/radarr LinuxServer.io]||<code>linuxserver/radarr:latest</code>||<code>linuxserver/radarr:develop</code>|| If you have to ask, you should not be on it.
|}
</center>

=== Installing a newer version ===
If Native:
# Go to System and then the Updates tab
# Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
If Docker:
# Repull your tag and update your container

== Can I switch from nightly back to develop? ==
[[#can_i_switch_from_nightly_back_to_develop|anchor]] 

[[Radarr_FAQ#Can I switch between branches?|See this related question]]

== Can I switch between branches? ==
[[#can_i_switch_between_branches|anchor]] 
* You can (almost) always increase your risk.
* <code>master</code> can go to <code>develop</code> or <code>nightly</code>
* <code>develop</code> can go to <code>nightly</code>
* Check with the development team to see if you can switch from <code>nightly</code> to <code>master</code>; <code>nightly</code> to <code>develop</code>; or <code>develop</code> to <code>master</code> for your given build.
* Failure to follow these instructions may result in your Radarr becoming unusable or throwing errors. You have been warned.
** The most common error is something like <code>Error parsing column 45 (Language=31 - Int64)</code> or other similar database errors around missing columns or tables.

* '''May 19 2021 Update'''
** <code>3.2.2</code> has been released as master/stable
** For those on nightly and are still on <code>3.2.2.5053</code> or lower you can safely downgrade to master or develop.
*** Develop can also downgrade to master as well.
*** Please note that if you're on nightly there will be no update to install given your build is higher than the current develop/master.

== How does radarr handle foreign movies or foreign titles? ==
[[#how_does_radarr_handle_foreign_movies_or_foreign_titles|anchor]] 
* Radarr uses both Alt Titles and Translations for parsing and searching. Search will use the Original Title, English Title, and Translated Title from whatever languages you have preferred (in profile and CFs). Parsing should look for a match in all Translations and Alt Titles.

* To get a movie in a foreign language set your Profile Language to Original (Movie's Original Language), a specific language for that profile, or any and use custom formats to determine which language to grab.
* Note that this does not include any indexer languages specified as multi.

== How does radarr handle "multi" in names? ==
[[#how_does_radarr_handle_multi_in_names|anchor]] 
* Radarr by default assumes multi is english and french unless specified in your indexer's advanced settings in Radarr.

* Note that multi definitions only help for release parsing and not for foreign titles or movies searches.

== Help, Movie Added, But Not Searched ==
[[#help_movie_added_but_not_searched|anchor]] 

* Neither Radarr nor Sonarr ''actively'' search for missing movies automatically. Instead, a periodic query of new posts is made to all indexers configured for RSS. When a wanted or cutoff unmet movie shows up in that list, it gets downloaded. This means that until a movie is posted (or reposted), it won’t get downloaded.
* If you’re adding a movie that you want now, the best option is to check the “Start search for missing movie” box, to the left of the ''Add Movie'' ('''1''') button. You can also go to the page for a movie you’ve added and click the magnifying glass “Search” ('''2''') button or use the Wanted view to search for Missing or Cutoff Unmet movies.

[[File:start search for missing movie.png|thumb|none|750px|alt=Add and Search for movie|Add and Search for movie]]
[[File:Search selected movie.png||thumb|none|750px|altt=Search selected movie|Search selected movie]]

== Root path for movies imported from lists becomes “C:” or other weird paths ==
[[#root_path_for_movies_imported_from_lists_become_c_or_other_weird_paths|anchor]] 
* Sometimes you can get a problem that movies that are imported from your lists, gets imported with the root path set to “C:” or other weird paths.

* This is a known issue for when the root path is either not setup during the creation of the list, or if the root path has been deleted after the list was created. Note that this problem can still occur even if the list is '''edited''' and the correct root path is set.

* Use the Movie Editor to fix paths of existing movies.

== Movie Imported, But Source File And Torrent Not Deleted ==
[[#movie_imported_but_source_file_and_torrent_not_deleted|anchor]] 
* Check if you have Completed Download Handling - Remove turned on. (This does not work if you are using rtorrent.)

[[File:Remove turned on.png|thumb|none|750px|alt=Settings|Settings > Download Clients]]

* If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.

== My Custom Script stopped working after upgrading from v0.2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v0.2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== I am using a Pi and Raspbian and Radarr will not launch ==
[[#i_am_using_a_pi_and_raspbian_and_radarr_will_not_launch|anchor]] Raspbian has a version of libseccomp2 that is too old to support running a docker container based on Ubuntu 20.04, which both hotio and LinuxServer use as their base for v3. You either need to use <code>--privileged</code>, update libseccomp2 from Ubuntu or get a better OS (We recommend Ubuntu 20.04 arm64)

'''Possible Solution:'''

Managed to fix the issue by installing the backport from debian repo. Generally not recommended to use backport in blanket upgrade mode. Installation of a single package may be ok but may also cause issues. So got to understand what you are doing.

Steps to fix:

First ensure you are running Raspbian buster e.g using <code>lsb_release -a</code>

Distributor ID: Raspbian

Description: Raspbian GNU/Linux 10 (buster)

Release: 10

Codename: buster

''If you are using buster:''
<code>Add the line `deb <nowiki>http://deb.debian.org/debian</nowiki> buster-backports` main to `/etc/apt/sources.list`
Run apt-get update
apt-get -t buster-backports install libseccomp2</code>

== Why are lists sync times so long and can I change it? ==
[[#why_are_lists_sync_times_so_long_and_can_i_change_it|anchor]]

Lists never were nor are intended to be <code>add it now</code> they are <code>hey i want this, add it eventually</code> tools

You can trigger a list refresh manually, script it and trigger it via the API, add the movies to radarr, use Ombi, or any similar app that adds them right away

This change was due to not have our server get killed by people updating lists every 10 minutes.

== Why doesn't Radarr work behind an nginx reverse proxy ==

[[Radarr_FAQ#Why_doesn.27t_Radarr_work_behind_a_reverse_proxy|See this section]]

== Can I disable the refresh movies task ==
[[#can_I_disable_the_refresh_movies_task|anchor]]

No, nor should you through any SQL hackery. The refresh movies task queries the upstream Servarr proxy and checks to see if the metadata for each movie (ids, cast, summary, rating, translations, alt titles, etc.) has updated compared to what is currently in Radarr. If necessary, it will then update the applicable movies.

A common complaint is the Refresh task causes heavy I/O usage. This is partly due to the setting "Analyze video files" which is advised to be enabled if you use tdarr or otherwise externally modify your files. If you don't you can safely disable "Analyze video files" to reduce some I/O. The other setting is "Rescan Movie Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to <code>Manual</code>. Do not change this to <code>Never</code> unless all changes to your library (new movies, upgrades, deletions etc) are done through Radarr. If you delete movie files manually or via Plex or another third party program, do not set this to <code>Never</code>.

{{FAQ|ARRNAME=Radarr|ARRDISCORD=https://radarr.video/discord|ARRPORT=7878}}

Radarr FAQ

2021-05-28T02:49:08Z

Bakerboy448: /* What is Minimum Availability? */

== How does Radarr work? ==
[[#how_does_radarr_work|anchor]] 
[[#How_does_Radarr_work|alt-anchor]] 
* Radarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Radarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Radarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Radarr's Release-Push API endpoint along with an IRC announce channel to push releases to Radarr for processing which can happen in near real time and with less overhead on the indexer and Radarr as Radarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== How does Radarr find movies? ==
[[#how_does_radarr_find_movies|anchor]] 
* Radarr does ''not'' regularly search for movie files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted movies, then compares that with its list of movies that are missing or need to be upgraded. Any matches are downloaded. This lets Radarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a movie, you'll need to set the correct path, profile and monitoring status then use the Start search for missing movie checkbox. If the movie hasn't been released yet, you don't need to initiate a search.
* Put another way, Radarr will only find movies that are newly uploaded to your indexers. It will not actively try to find movies you want that were uploaded in the past.
* If you've already added the movie, but now you want to search for it, you have a few choices. You can go to the movie's page and use the search button, which will do a search and then automatically pick one. You can use the Search tab and see ''all'' the results, hand picking the one you want. Or you can use the filters of <code>Missing</code>, <code>Wanted</code>, or <code>Cut-off Unmet</code>.
* If Radarr has been offline for an extended period of time, Radarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Radarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed movies.

## What is Minimum Availability?
== What is Minimum Availability? ==
[[#what_is_minimum_avalability|anchor]] 
- '''Announced''': Radarr shall consider movies available as soon as they are added to Radarr. This setting is recommended if you have good private trackers (or really good public ones, e.g. rarbg.to) that do not have fakes.

- '''In Cinemas''': Radarr shall consider movies available as soon as movies hit cinemas. This option is not recommended.

- '''Released''': Radarr shall consider movies available as soon as the blu-ray or streaming version is released. This option is recommended and likely should be combined with an Availability Delay of `-14` days.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Radarr/Radarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs can be found here].
'''''As of 5/27/2021 the logic is as follows'''''
# Quality
# Custom Format Score
# Protocol
# Indexer Priority
# Indexer Flags
# Seeds/Peers (If Torrent)
# Age (If Usenet)
# Size

== What are Lists and what can they do for me? ==
[[#what_are_lists_and_what_can_they_do_for_me|anchor]] 
* Lists are a part of Radarr that allow you to follow a given list creator.
* Let's say that you follow a given list creator on Trakt/TMDb and really like their Marvel Cinematic Universe film section and want to watch every movie on their list. You look in your Radarr and realize that you don't have those movies. Well instead of searching one by one and adding those lists and then searching your indexers for those movies. You can do this all at once with a List. The Lists can be set to import all the movies on that curators list as well as be set to automatically assign a quality profile, automatically add, and automatically monitor that movie.
* '''CAUTION:''' If lists are done improperly they will absolutely wreck your library with a bunch of trash you have no intention of watching. So make sure of what you're importing before you click save.
* ie. physically look at the list before you even go to Radarr.

== With the release of Radarr V3, what release should I download? ==
[[#with_the_release_of_radarr_v3_what_release_should_i_download|anchor]] 
Please see better information [[Radarr FAQ#How do I update Radarr?|here]]

== Why did the GUI / UI Change? Can it be changed back? ==
[[#why_did_the_gui_ui_change|anchor]] 
* Radarr is a fork of [[Sonarr]] which has the new UI.
* No it cannot be changed back. No it will not be changed back.
* You may, however, check out [https://github.com/gilbN/theme.park Theme Park]


== Where did Wanted and Cut-off Unmet go? ==
[[#where_did_wanted_and_cutoff_unmet_go|anchor]] 
* Movie Index (AKA 'Movies') -> Filter (top right corner) -> <code>Wanted</code> and <code>Cut-off Unmet</code>
[[File:radarr-where-did-wanted-and-cutoff-unmet-go.png|thumb|none|750px|alt=This is where wanted and Cut-off Unmet went|This is where wanted and Cut-off Unmet went]]

== Why can't I add a new movie to Radarr? ==
[[#why_cant_i_add_a_new_movie_to_radarr|anchor]] 
* Radarr uses [http://themoviedb.org The Movie Database (TMDb)] for movie information and images like fanart, banners and backgrounds. Generally, there are a few reasons why you may not be able to add a movie:
* TMDb doesn't like special characters to be used when searching for movies through the API (which Radarr uses), so try searching a translated name, and/or without special characters.
* You can also add by TMDb ID or, if TMDb has it, the IMDb ID
* The movie hasn't been added to TMDb yet, follow their [https://www.themoviedb.org/bible/new_content#59f7933c9251413e93000006 guide] to get it added.

== Can all my movie files be stored in one folder? ==
[[#can_all_my_movie_files_be_stored_in_one_folder|anchor]] 
* Not yet and the reason is that Radarr is a fork of [[Sonarr]], where every show has a folder. This limitation is a known pain point for many users and will maybe come in a future version.
:If you're looking to moving all your movies from one folder to individual folders check [[Radarr Tips and Tricks#Create a Folder for Each Movie|here]]

== Can I put all my movies in my library into one folder ==
[[Radarr FAQ#Can I put all my movies in my library into one folder|anchor]]

We get asked this a lot. There are no plans to support <code>\data\Movies\Movie1.mkv</code>, <code>\data\Movies\Movie2.mkv</code>, etc.

The [https://github.com/Radarr/Radarr/issues/153 Custom Folder GitHub Issue] technically covers this request, but it is no guarantee that all movie files in one folder will be implemented at that time.

A slight hack-ish solution is noted below. Please note that you mustn't trigger a rescan or it will show as missing and regardless the movie will never be upgraded.

* Use a Custom Script
** the script should be triggered on import
** it should be designed to move the file whenever you want it
** it then needs to call the Radarr API and change the movie to unmonitored.

== How can I rename my movie folders? ==
[[#how_can_i_rename_my_movie_folders|anchor]] 
# Movies
# Movie Editor
# Select what movies need their folder renamed
# Change Root Folder to the same Root Folder that the movies currently exist in
# Select "Yes move files"

== Movie File and Folder Naming ==
[[#movie_file_and_folder_naming|anchor]] 
* Currently, Radarr requires that each movie be in a folder with the format containing at minimum <code>Movie Title (Year)/</code>, optionally <code>_</code> or <code>.</code> are valid separators. To facilitate correct quality and resolution identification during import, a file name like <code>Movie Title (Year) [Quality-Resolution].ext</code> is best, again <code>_</code> or <code>.</code> are valid separators too.
* A useful tool for making these changes to your collection is [http://www.filebot.net/#download filebot] which has paid version in both the Apple and Windows stores, but can be found for free on their legacy [https://sourceforge.net/projects/filebot/files/latest/download SourceForge] site. It has both a GUI and CLI, so you can use whatever you’re comfortable with. For the above example, <code>{ny}</code> expands to <code>Name (Year)</code> and <code>{vf}</code> gives the resolution like <code>1080p</code>. There is nothing to infer quality, so you can fake it using <code>{ny}/{ny} [{dim[0] >= 1280 ? 'Bluray' : 'DVD'}-{vf}]</code> which will name anything lower than 720p to <code>[DVD-572p]</code> and greater or equal to 720p like <code>[Bluray-1080p]</code>.
See [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] for more details.

== Movie Folders Named Incorrectly ==
[[#movie_folders_named_incorrectly|anchor]] 
* Even if your movies are in folders already, the folders may not be named correctly. The folder name should be <code>Movie Title (Year)</code>, having the title and year in the folder’s name is critical right now.
* Examples that will work well:
** <code>/mnt/Movies/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** <code>/mnt/Kid Movies/Frozen (2013)/Frozen (2013) [Bluray-1080p].mkv</code>
* Examples that will work, but will require manual management:
** By letters: <code>/mnt/Movies/A-D/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By rating: <code>/mnt/Movies/R/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By genre: <code>/mnt/Movies/Crime, Drama, Sci-Fi/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** These examples will require manual management when the movie is added. Each of the examples will have many root directories, like <code>A-D</code> and <code>E-G</code> in the first letter example, <code>R</code> and <code>PG-13</code> in the rating example and you can guess at the variety of genre folders. When adding a new movie, the correct base folder will need to be selected for this format to work.
* Examples that won’t work:
** Single folder: <code>/mnt/Kid Movies/Frozen (2013) [Bluray-1080p].mkv</code>
*** At this time, movies simply have to be in a folder named after the movie. There is no way around this until development work is done to add this feature.
**'''Movie''' Folder Naming Formats from v0.2 that include '''File''' properties in the '''movie folder''' name such as <code>{Movie.Title}.{Release Year}.{Quality.Full}-{MediaInfo.Simple}{`Release.Group}</code> will not work in v3.
*** Folders are related to the movie and independent of the file. Additionally, this will break with the planned multiple files per movie support.
*** The other reason it was removed was it caused frequent confusion, database corruption, and generally was only half baked.
* The [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.

== How can I mass delete movies from the wanted list? ==
[[#how_can_i_mass_delete_movies_from_the_wanted_list|anchor]] 
* Use Movie Editor -> Select movies you want to delete -> Delete

== Why doesn't Radarr work behind a reverse proxy ==
[[#why_doesnt_radarr_work_behind_an_nginx_reverse_proxy|anchor]] 
* Starting with V3 Radarr has switched to .NET Core and a new webserver. In order for SignalR to work, the UI buttons to work, database changes to take, and other items. It requires the following addition to the location block for Radarr:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

* Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
* [https://github.com/aspnet/AspNetCore/issues/17081 See this ASP.NET Core issue]
* If you are using a CDN like Cloudflare ensure websockets are enabled to allow websocket connections.

== How do I update Radarr? ==
[[#how_do_i_update_my_radarr|anchor]] 
# Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
# Under the Development section change the branch name to <code>master</code> or <code>develop</code>
# Save
''This will not install the bits from that branch immediately, it will happen during the next update.''

* master (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. This is currently v3. This version will receive updates approximately monthly. On GitHub, this is the <code>master</code> branch.
* develop (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first. This is currently v3. This version will receive updates either weekly or biweekly depending on development. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is a snapshot of the <code>develop</code> branch at a point in time.
* nightly (Nightly): The bleeding edge. Released as soon as code is committed and passed all automated tests. '''''Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.''''' This is currently v3. This version is updated immediately. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is the <code>develop</code> branch.

* Note: If your install is through Docker append <code>:release</code>, <code>:latest</code>, or <code>:testing</code> to the end of your container tag depending on who makes your builds.
{| class="wikitable"
|+
!Current Versions
!master
!develop
!nightly
|-
|
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Frelease%2FVERSION.json Current Master/Latest]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Ftesting%2FVERSION.json Current Develop/Beta]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Fnightly%2FVERSION.json Current Nightly/Alpha]
|}
<center>
{| class="wikitable"
|-
! Release Channel Type !! Branch: master (stable) (v3.2) !! Branch: develop (beta) (v3.2) !! Branch: nightly (unstable) (v3.2)
|-
|[https://hub.docker.com/r/hotio/radarr hotio]||<code>hotio/radarr:release</code>||<code>hotio/radarr:testing</code>|| If you have to ask, you should not be on it.
|-
|[https://hub.docker.com/r/linuxserver/radarr LinuxServer.io]||<code>linuxserver/radarr:latest</code>||<code>linuxserver/radarr:develop</code>|| If you have to ask, you should not be on it.
|}
</center>

=== Installing a newer version ===
If Native:
# Go to System and then the Updates tab
# Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
If Docker:
# Repull your tag and update your container

== Can I switch from nightly back to develop? ==
[[#can_i_switch_from_nightly_back_to_develop|anchor]] 

[[Radarr_FAQ#Can I switch between branches?|See this related question]]

== Can I switch between branches? ==
[[#can_i_switch_between_branches|anchor]] 
* You can (almost) always increase your risk.
* <code>master</code> can go to <code>develop</code> or <code>nightly</code>
* <code>develop</code> can go to <code>nightly</code>
* Check with the development team to see if you can switch from <code>nightly</code> to <code>master</code>; <code>nightly</code> to <code>develop</code>; or <code>develop</code> to <code>master</code> for your given build.
* Failure to follow these instructions may result in your Radarr becoming unusable or throwing errors. You have been warned.
** The most common error is something like <code>Error parsing column 45 (Language=31 - Int64)</code> or other similar database errors around missing columns or tables.

* '''May 19 2021 Update'''
** <code>3.2.2</code> has been released as master/stable
** For those on nightly and are still on <code>3.2.2.5053</code> or lower you can safely downgrade to master or develop.
*** Develop can also downgrade to master as well.
*** Please note that if you're on nightly there will be no update to install given your build is higher than the current develop/master.

== How does radarr handle foreign movies or foreign titles? ==
[[#how_does_radarr_handle_foreign_movies_or_foreign_titles|anchor]] 
* Radarr uses both Alt Titles and Translations for parsing and searching. Search will use the Original Title, English Title, and Translated Title from whatever languages you have preferred (in profile and CFs). Parsing should look for a match in all Translations and Alt Titles.

* To get a movie in a foreign language set your Profile Language to Original (Movie's Original Language), a specific language for that profile, or any and use custom formats to determine which language to grab.
* Note that this does not include any indexer languages specified as multi.

== How does radarr handle "multi" in names? ==
[[#how_does_radarr_handle_multi_in_names|anchor]] 
* Radarr by default assumes multi is english and french unless specified in your indexer's advanced settings in Radarr.

* Note that multi definitions only help for release parsing and not for foreign titles or movies searches.

== Help, Movie Added, But Not Searched ==
[[#help_movie_added_but_not_searched|anchor]] 

* Neither Radarr nor Sonarr ''actively'' search for missing movies automatically. Instead, a periodic query of new posts is made to all indexers configured for RSS. When a wanted or cutoff unmet movie shows up in that list, it gets downloaded. This means that until a movie is posted (or reposted), it won’t get downloaded.
* If you’re adding a movie that you want now, the best option is to check the “Start search for missing movie” box, to the left of the ''Add Movie'' ('''1''') button. You can also go to the page for a movie you’ve added and click the magnifying glass “Search” ('''2''') button or use the Wanted view to search for Missing or Cutoff Unmet movies.

[[File:start search for missing movie.png|thumb|none|750px|alt=Add and Search for movie|Add and Search for movie]]
[[File:Search selected movie.png||thumb|none|750px|altt=Search selected movie|Search selected movie]]

== Root path for movies imported from lists becomes “C:” or other weird paths ==
[[#root_path_for_movies_imported_from_lists_become_c_or_other_weird_paths|anchor]] 
* Sometimes you can get a problem that movies that are imported from your lists, gets imported with the root path set to “C:” or other weird paths.

* This is a known issue for when the root path is either not setup during the creation of the list, or if the root path has been deleted after the list was created. Note that this problem can still occur even if the list is '''edited''' and the correct root path is set.

* Use the Movie Editor to fix paths of existing movies.

== Movie Imported, But Source File And Torrent Not Deleted ==
[[#movie_imported_but_source_file_and_torrent_not_deleted|anchor]] 
* Check if you have Completed Download Handling - Remove turned on. (This does not work if you are using rtorrent.)

[[File:Remove turned on.png|thumb|none|750px|alt=Settings|Settings > Download Clients]]

* If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.

== My Custom Script stopped working after upgrading from v0.2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v0.2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== I am using a Pi and Raspbian and Radarr will not launch ==
[[#i_am_using_a_pi_and_raspbian_and_radarr_will_not_launch|anchor]] Raspbian has a version of libseccomp2 that is too old to support running a docker container based on Ubuntu 20.04, which both hotio and LinuxServer use as their base for v3. You either need to use <code>--privileged</code>, update libseccomp2 from Ubuntu or get a better OS (We recommend Ubuntu 20.04 arm64)

'''Possible Solution:'''

Managed to fix the issue by installing the backport from debian repo. Generally not recommended to use backport in blanket upgrade mode. Installation of a single package may be ok but may also cause issues. So got to understand what you are doing.

Steps to fix:

First ensure you are running Raspbian buster e.g using <code>lsb_release -a</code>

Distributor ID: Raspbian

Description: Raspbian GNU/Linux 10 (buster)

Release: 10

Codename: buster

''If you are using buster:''
<code>Add the line `deb <nowiki>http://deb.debian.org/debian</nowiki> buster-backports` main to `/etc/apt/sources.list`
Run apt-get update
apt-get -t buster-backports install libseccomp2</code>

== Why are lists sync times so long and can I change it? ==
[[#why_are_lists_sync_times_so_long_and_can_i_change_it|anchor]]

Lists never were nor are intended to be <code>add it now</code> they are <code>hey i want this, add it eventually</code> tools

You can trigger a list refresh manually, script it and trigger it via the API, add the movies to radarr, use Ombi, or any similar app that adds them right away

This change was due to not have our server get killed by people updating lists every 10 minutes.

== Why doesn't Radarr work behind an nginx reverse proxy ==

[[Radarr_FAQ#Why_doesn.27t_Radarr_work_behind_a_reverse_proxy|See this section]]

== Can I disable the refresh movies task ==
[[#can_I_disable_the_refresh_movies_task|anchor]]

No, nor should you through any SQL hackery. The refresh movies task queries the upstream Servarr proxy and checks to see if the metadata for each movie (ids, cast, summary, rating, translations, alt titles, etc.) has updated compared to what is currently in Radarr. If necessary, it will then update the applicable movies.

A common complaint is the Refresh task causes heavy I/O usage. This is partly due to the setting "Analyze video files" which is advised to be enabled if you use tdarr or otherwise externally modify your files. If you don't you can safely disable "Analyze video files" to reduce some I/O. The other setting is "Rescan Movie Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to <code>Manual</code>. Do not change this to <code>Never</code> unless all changes to your library (new movies, upgrades, deletions etc) are done through Radarr. If you delete movie files manually or via Plex or another third party program, do not set this to <code>Never</code>.

{{FAQ|ARRNAME=Radarr|ARRDISCORD=https://radarr.video/discord|ARRPORT=7878}}

Radarr FAQ

2021-05-28T02:47:46Z

Bakerboy448: /* What is Minimum Availability? */

== How does Radarr work? ==
[[#how_does_radarr_work|anchor]] 
[[#How_does_Radarr_work|alt-anchor]] 
* Radarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Radarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Radarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Radarr's Release-Push API endpoint along with an IRC announce channel to push releases to Radarr for processing which can happen in near real time and with less overhead on the indexer and Radarr as Radarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== How does Radarr find movies? ==
[[#how_does_radarr_find_movies|anchor]] 
* Radarr does ''not'' regularly search for movie files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted movies, then compares that with its list of movies that are missing or need to be upgraded. Any matches are downloaded. This lets Radarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a movie, you'll need to set the correct path, profile and monitoring status then use the Start search for missing movie checkbox. If the movie hasn't been released yet, you don't need to initiate a search.
* Put another way, Radarr will only find movies that are newly uploaded to your indexers. It will not actively try to find movies you want that were uploaded in the past.
* If you've already added the movie, but now you want to search for it, you have a few choices. You can go to the movie's page and use the search button, which will do a search and then automatically pick one. You can use the Search tab and see ''all'' the results, hand picking the one you want. Or you can use the filters of <code>Missing</code>, <code>Wanted</code>, or <code>Cut-off Unmet</code>.
* If Radarr has been offline for an extended period of time, Radarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Radarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed movies.

## What is Minimum Availability?
== What is Minimum Availability? ==
[[#what_is_minimum_avalability|anchor]] 
- **Announced**: Radarr shall consider movies available as soon as they are added to Radarr. This setting is recommended if you have good private trackers (or really good public ones, e.g. rarbg.to) that do not have fakes.

- **In Cinemas**: Radarr shall consider movies available as soon as movies hit cinemas. This option is not recommended.

- **Released**: Radarr shall consider movies available as soon as the Blu-ray is released. This option is recommended and likely should be combined with an Availability Delay of `-14` days.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Radarr/Radarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs can be found here].
'''''As of 5/27/2021 the logic is as follows'''''
# Quality
# Custom Format Score
# Protocol
# Indexer Priority
# Indexer Flags
# Seeds/Peers (If Torrent)
# Age (If Usenet)
# Size

== What are Lists and what can they do for me? ==
[[#what_are_lists_and_what_can_they_do_for_me|anchor]] 
* Lists are a part of Radarr that allow you to follow a given list creator.
* Let's say that you follow a given list creator on Trakt/TMDb and really like their Marvel Cinematic Universe film section and want to watch every movie on their list. You look in your Radarr and realize that you don't have those movies. Well instead of searching one by one and adding those lists and then searching your indexers for those movies. You can do this all at once with a List. The Lists can be set to import all the movies on that curators list as well as be set to automatically assign a quality profile, automatically add, and automatically monitor that movie.
* '''CAUTION:''' If lists are done improperly they will absolutely wreck your library with a bunch of trash you have no intention of watching. So make sure of what you're importing before you click save.
* ie. physically look at the list before you even go to Radarr.

== With the release of Radarr V3, what release should I download? ==
[[#with_the_release_of_radarr_v3_what_release_should_i_download|anchor]] 
Please see better information [[Radarr FAQ#How do I update Radarr?|here]]

== Why did the GUI / UI Change? Can it be changed back? ==
[[#why_did_the_gui_ui_change|anchor]] 
* Radarr is a fork of [[Sonarr]] which has the new UI.
* No it cannot be changed back. No it will not be changed back.
* You may, however, check out [https://github.com/gilbN/theme.park Theme Park]


== Where did Wanted and Cut-off Unmet go? ==
[[#where_did_wanted_and_cutoff_unmet_go|anchor]] 
* Movie Index (AKA 'Movies') -> Filter (top right corner) -> <code>Wanted</code> and <code>Cut-off Unmet</code>
[[File:radarr-where-did-wanted-and-cutoff-unmet-go.png|thumb|none|750px|alt=This is where wanted and Cut-off Unmet went|This is where wanted and Cut-off Unmet went]]

== Why can't I add a new movie to Radarr? ==
[[#why_cant_i_add_a_new_movie_to_radarr|anchor]] 
* Radarr uses [http://themoviedb.org The Movie Database (TMDb)] for movie information and images like fanart, banners and backgrounds. Generally, there are a few reasons why you may not be able to add a movie:
* TMDb doesn't like special characters to be used when searching for movies through the API (which Radarr uses), so try searching a translated name, and/or without special characters.
* You can also add by TMDb ID or, if TMDb has it, the IMDb ID
* The movie hasn't been added to TMDb yet, follow their [https://www.themoviedb.org/bible/new_content#59f7933c9251413e93000006 guide] to get it added.

== Can all my movie files be stored in one folder? ==
[[#can_all_my_movie_files_be_stored_in_one_folder|anchor]] 
* Not yet and the reason is that Radarr is a fork of [[Sonarr]], where every show has a folder. This limitation is a known pain point for many users and will maybe come in a future version.
:If you're looking to moving all your movies from one folder to individual folders check [[Radarr Tips and Tricks#Create a Folder for Each Movie|here]]

== Can I put all my movies in my library into one folder ==
[[Radarr FAQ#Can I put all my movies in my library into one folder|anchor]]

We get asked this a lot. There are no plans to support <code>\data\Movies\Movie1.mkv</code>, <code>\data\Movies\Movie2.mkv</code>, etc.

The [https://github.com/Radarr/Radarr/issues/153 Custom Folder GitHub Issue] technically covers this request, but it is no guarantee that all movie files in one folder will be implemented at that time.

A slight hack-ish solution is noted below. Please note that you mustn't trigger a rescan or it will show as missing and regardless the movie will never be upgraded.

* Use a Custom Script
** the script should be triggered on import
** it should be designed to move the file whenever you want it
** it then needs to call the Radarr API and change the movie to unmonitored.

== How can I rename my movie folders? ==
[[#how_can_i_rename_my_movie_folders|anchor]] 
# Movies
# Movie Editor
# Select what movies need their folder renamed
# Change Root Folder to the same Root Folder that the movies currently exist in
# Select "Yes move files"

== Movie File and Folder Naming ==
[[#movie_file_and_folder_naming|anchor]] 
* Currently, Radarr requires that each movie be in a folder with the format containing at minimum <code>Movie Title (Year)/</code>, optionally <code>_</code> or <code>.</code> are valid separators. To facilitate correct quality and resolution identification during import, a file name like <code>Movie Title (Year) [Quality-Resolution].ext</code> is best, again <code>_</code> or <code>.</code> are valid separators too.
* A useful tool for making these changes to your collection is [http://www.filebot.net/#download filebot] which has paid version in both the Apple and Windows stores, but can be found for free on their legacy [https://sourceforge.net/projects/filebot/files/latest/download SourceForge] site. It has both a GUI and CLI, so you can use whatever you’re comfortable with. For the above example, <code>{ny}</code> expands to <code>Name (Year)</code> and <code>{vf}</code> gives the resolution like <code>1080p</code>. There is nothing to infer quality, so you can fake it using <code>{ny}/{ny} [{dim[0] >= 1280 ? 'Bluray' : 'DVD'}-{vf}]</code> which will name anything lower than 720p to <code>[DVD-572p]</code> and greater or equal to 720p like <code>[Bluray-1080p]</code>.
See [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] for more details.

== Movie Folders Named Incorrectly ==
[[#movie_folders_named_incorrectly|anchor]] 
* Even if your movies are in folders already, the folders may not be named correctly. The folder name should be <code>Movie Title (Year)</code>, having the title and year in the folder’s name is critical right now.
* Examples that will work well:
** <code>/mnt/Movies/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** <code>/mnt/Kid Movies/Frozen (2013)/Frozen (2013) [Bluray-1080p].mkv</code>
* Examples that will work, but will require manual management:
** By letters: <code>/mnt/Movies/A-D/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By rating: <code>/mnt/Movies/R/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By genre: <code>/mnt/Movies/Crime, Drama, Sci-Fi/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** These examples will require manual management when the movie is added. Each of the examples will have many root directories, like <code>A-D</code> and <code>E-G</code> in the first letter example, <code>R</code> and <code>PG-13</code> in the rating example and you can guess at the variety of genre folders. When adding a new movie, the correct base folder will need to be selected for this format to work.
* Examples that won’t work:
** Single folder: <code>/mnt/Kid Movies/Frozen (2013) [Bluray-1080p].mkv</code>
*** At this time, movies simply have to be in a folder named after the movie. There is no way around this until development work is done to add this feature.
**'''Movie''' Folder Naming Formats from v0.2 that include '''File''' properties in the '''movie folder''' name such as <code>{Movie.Title}.{Release Year}.{Quality.Full}-{MediaInfo.Simple}{`Release.Group}</code> will not work in v3.
*** Folders are related to the movie and independent of the file. Additionally, this will break with the planned multiple files per movie support.
*** The other reason it was removed was it caused frequent confusion, database corruption, and generally was only half baked.
* The [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.

== How can I mass delete movies from the wanted list? ==
[[#how_can_i_mass_delete_movies_from_the_wanted_list|anchor]] 
* Use Movie Editor -> Select movies you want to delete -> Delete

== Why doesn't Radarr work behind a reverse proxy ==
[[#why_doesnt_radarr_work_behind_an_nginx_reverse_proxy|anchor]] 
* Starting with V3 Radarr has switched to .NET Core and a new webserver. In order for SignalR to work, the UI buttons to work, database changes to take, and other items. It requires the following addition to the location block for Radarr:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

* Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
* [https://github.com/aspnet/AspNetCore/issues/17081 See this ASP.NET Core issue]
* If you are using a CDN like Cloudflare ensure websockets are enabled to allow websocket connections.

== How do I update Radarr? ==
[[#how_do_i_update_my_radarr|anchor]] 
# Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
# Under the Development section change the branch name to <code>master</code> or <code>develop</code>
# Save
''This will not install the bits from that branch immediately, it will happen during the next update.''

* master (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. This is currently v3. This version will receive updates approximately monthly. On GitHub, this is the <code>master</code> branch.
* develop (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first. This is currently v3. This version will receive updates either weekly or biweekly depending on development. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is a snapshot of the <code>develop</code> branch at a point in time.
* nightly (Nightly): The bleeding edge. Released as soon as code is committed and passed all automated tests. '''''Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.''''' This is currently v3. This version is updated immediately. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is the <code>develop</code> branch.

* Note: If your install is through Docker append <code>:release</code>, <code>:latest</code>, or <code>:testing</code> to the end of your container tag depending on who makes your builds.
{| class="wikitable"
|+
!Current Versions
!master
!develop
!nightly
|-
|
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Frelease%2FVERSION.json Current Master/Latest]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Ftesting%2FVERSION.json Current Develop/Beta]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Fnightly%2FVERSION.json Current Nightly/Alpha]
|}
<center>
{| class="wikitable"
|-
! Release Channel Type !! Branch: master (stable) (v3.2) !! Branch: develop (beta) (v3.2) !! Branch: nightly (unstable) (v3.2)
|-
|[https://hub.docker.com/r/hotio/radarr hotio]||<code>hotio/radarr:release</code>||<code>hotio/radarr:testing</code>|| If you have to ask, you should not be on it.
|-
|[https://hub.docker.com/r/linuxserver/radarr LinuxServer.io]||<code>linuxserver/radarr:latest</code>||<code>linuxserver/radarr:develop</code>|| If you have to ask, you should not be on it.
|}
</center>

=== Installing a newer version ===
If Native:
# Go to System and then the Updates tab
# Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
If Docker:
# Repull your tag and update your container

== Can I switch from nightly back to develop? ==
[[#can_i_switch_from_nightly_back_to_develop|anchor]] 

[[Radarr_FAQ#Can I switch between branches?|See this related question]]

== Can I switch between branches? ==
[[#can_i_switch_between_branches|anchor]] 
* You can (almost) always increase your risk.
* <code>master</code> can go to <code>develop</code> or <code>nightly</code>
* <code>develop</code> can go to <code>nightly</code>
* Check with the development team to see if you can switch from <code>nightly</code> to <code>master</code>; <code>nightly</code> to <code>develop</code>; or <code>develop</code> to <code>master</code> for your given build.
* Failure to follow these instructions may result in your Radarr becoming unusable or throwing errors. You have been warned.
** The most common error is something like <code>Error parsing column 45 (Language=31 - Int64)</code> or other similar database errors around missing columns or tables.

* '''May 19 2021 Update'''
** <code>3.2.2</code> has been released as master/stable
** For those on nightly and are still on <code>3.2.2.5053</code> or lower you can safely downgrade to master or develop.
*** Develop can also downgrade to master as well.
*** Please note that if you're on nightly there will be no update to install given your build is higher than the current develop/master.

== How does radarr handle foreign movies or foreign titles? ==
[[#how_does_radarr_handle_foreign_movies_or_foreign_titles|anchor]] 
* Radarr uses both Alt Titles and Translations for parsing and searching. Search will use the Original Title, English Title, and Translated Title from whatever languages you have preferred (in profile and CFs). Parsing should look for a match in all Translations and Alt Titles.

* To get a movie in a foreign language set your Profile Language to Original (Movie's Original Language), a specific language for that profile, or any and use custom formats to determine which language to grab.
* Note that this does not include any indexer languages specified as multi.

== How does radarr handle "multi" in names? ==
[[#how_does_radarr_handle_multi_in_names|anchor]] 
* Radarr by default assumes multi is english and french unless specified in your indexer's advanced settings in Radarr.

* Note that multi definitions only help for release parsing and not for foreign titles or movies searches.

== Help, Movie Added, But Not Searched ==
[[#help_movie_added_but_not_searched|anchor]] 

* Neither Radarr nor Sonarr ''actively'' search for missing movies automatically. Instead, a periodic query of new posts is made to all indexers configured for RSS. When a wanted or cutoff unmet movie shows up in that list, it gets downloaded. This means that until a movie is posted (or reposted), it won’t get downloaded.
* If you’re adding a movie that you want now, the best option is to check the “Start search for missing movie” box, to the left of the ''Add Movie'' ('''1''') button. You can also go to the page for a movie you’ve added and click the magnifying glass “Search” ('''2''') button or use the Wanted view to search for Missing or Cutoff Unmet movies.

[[File:start search for missing movie.png|thumb|none|750px|alt=Add and Search for movie|Add and Search for movie]]
[[File:Search selected movie.png||thumb|none|750px|altt=Search selected movie|Search selected movie]]

== Root path for movies imported from lists becomes “C:” or other weird paths ==
[[#root_path_for_movies_imported_from_lists_become_c_or_other_weird_paths|anchor]] 
* Sometimes you can get a problem that movies that are imported from your lists, gets imported with the root path set to “C:” or other weird paths.

* This is a known issue for when the root path is either not setup during the creation of the list, or if the root path has been deleted after the list was created. Note that this problem can still occur even if the list is '''edited''' and the correct root path is set.

* Use the Movie Editor to fix paths of existing movies.

== Movie Imported, But Source File And Torrent Not Deleted ==
[[#movie_imported_but_source_file_and_torrent_not_deleted|anchor]] 
* Check if you have Completed Download Handling - Remove turned on. (This does not work if you are using rtorrent.)

[[File:Remove turned on.png|thumb|none|750px|alt=Settings|Settings > Download Clients]]

* If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.

== My Custom Script stopped working after upgrading from v0.2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v0.2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== I am using a Pi and Raspbian and Radarr will not launch ==
[[#i_am_using_a_pi_and_raspbian_and_radarr_will_not_launch|anchor]] Raspbian has a version of libseccomp2 that is too old to support running a docker container based on Ubuntu 20.04, which both hotio and LinuxServer use as their base for v3. You either need to use <code>--privileged</code>, update libseccomp2 from Ubuntu or get a better OS (We recommend Ubuntu 20.04 arm64)

'''Possible Solution:'''

Managed to fix the issue by installing the backport from debian repo. Generally not recommended to use backport in blanket upgrade mode. Installation of a single package may be ok but may also cause issues. So got to understand what you are doing.

Steps to fix:

First ensure you are running Raspbian buster e.g using <code>lsb_release -a</code>

Distributor ID: Raspbian

Description: Raspbian GNU/Linux 10 (buster)

Release: 10

Codename: buster

''If you are using buster:''
<code>Add the line `deb <nowiki>http://deb.debian.org/debian</nowiki> buster-backports` main to `/etc/apt/sources.list`
Run apt-get update
apt-get -t buster-backports install libseccomp2</code>

== Why are lists sync times so long and can I change it? ==
[[#why_are_lists_sync_times_so_long_and_can_i_change_it|anchor]]

Lists never were nor are intended to be <code>add it now</code> they are <code>hey i want this, add it eventually</code> tools

You can trigger a list refresh manually, script it and trigger it via the API, add the movies to radarr, use Ombi, or any similar app that adds them right away

This change was due to not have our server get killed by people updating lists every 10 minutes.

== Why doesn't Radarr work behind an nginx reverse proxy ==

[[Radarr_FAQ#Why_doesn.27t_Radarr_work_behind_a_reverse_proxy|See this section]]

== Can I disable the refresh movies task ==
[[#can_I_disable_the_refresh_movies_task|anchor]]

No, nor should you through any SQL hackery. The refresh movies task queries the upstream Servarr proxy and checks to see if the metadata for each movie (ids, cast, summary, rating, translations, alt titles, etc.) has updated compared to what is currently in Radarr. If necessary, it will then update the applicable movies.

A common complaint is the Refresh task causes heavy I/O usage. This is partly due to the setting "Analyze video files" which is advised to be enabled if you use tdarr or otherwise externally modify your files. If you don't you can safely disable "Analyze video files" to reduce some I/O. The other setting is "Rescan Movie Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to <code>Manual</code>. Do not change this to <code>Never</code> unless all changes to your library (new movies, upgrades, deletions etc) are done through Radarr. If you delete movie files manually or via Plex or another third party program, do not set this to <code>Never</code>.

{{FAQ|ARRNAME=Radarr|ARRDISCORD=https://radarr.video/discord|ARRPORT=7878}}

Radarr FAQ

2021-05-28T02:47:34Z

Bakerboy448:

== How does Radarr work? ==
[[#how_does_radarr_work|anchor]] 
[[#How_does_Radarr_work|alt-anchor]] 
* Radarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Radarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Radarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Radarr's Release-Push API endpoint along with an IRC announce channel to push releases to Radarr for processing which can happen in near real time and with less overhead on the indexer and Radarr as Radarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== How does Radarr find movies? ==
[[#how_does_radarr_find_movies|anchor]] 
* Radarr does ''not'' regularly search for movie files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted movies, then compares that with its list of movies that are missing or need to be upgraded. Any matches are downloaded. This lets Radarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a movie, you'll need to set the correct path, profile and monitoring status then use the Start search for missing movie checkbox. If the movie hasn't been released yet, you don't need to initiate a search.
* Put another way, Radarr will only find movies that are newly uploaded to your indexers. It will not actively try to find movies you want that were uploaded in the past.
* If you've already added the movie, but now you want to search for it, you have a few choices. You can go to the movie's page and use the search button, which will do a search and then automatically pick one. You can use the Search tab and see ''all'' the results, hand picking the one you want. Or you can use the filters of <code>Missing</code>, <code>Wanted</code>, or <code>Cut-off Unmet</code>.
* If Radarr has been offline for an extended period of time, Radarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Radarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed movies.

## What is Minimum Availability?
== What is Minimum Availability? ==
[[#what_is_minimum_avalability|anchor]] 
- **Announced**: Radarr shall consider movies available as soon as they are added to Radarr. This setting is recommended if you have good private trackers (or really good public ones, e.g. rarbg.to) that do not have fakes.
- **In Cinemas**: Radarr shall consider movies available as soon as movies hit cinemas. This option is not recommended.
- **Released**: Radarr shall consider movies available as soon as the Blu-ray is released. This option is recommended and likely should be combined with an Availability Delay of `-14` days.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Radarr/Radarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs can be found here].
'''''As of 5/27/2021 the logic is as follows'''''
# Quality
# Custom Format Score
# Protocol
# Indexer Priority
# Indexer Flags
# Seeds/Peers (If Torrent)
# Age (If Usenet)
# Size

== What are Lists and what can they do for me? ==
[[#what_are_lists_and_what_can_they_do_for_me|anchor]] 
* Lists are a part of Radarr that allow you to follow a given list creator.
* Let's say that you follow a given list creator on Trakt/TMDb and really like their Marvel Cinematic Universe film section and want to watch every movie on their list. You look in your Radarr and realize that you don't have those movies. Well instead of searching one by one and adding those lists and then searching your indexers for those movies. You can do this all at once with a List. The Lists can be set to import all the movies on that curators list as well as be set to automatically assign a quality profile, automatically add, and automatically monitor that movie.
* '''CAUTION:''' If lists are done improperly they will absolutely wreck your library with a bunch of trash you have no intention of watching. So make sure of what you're importing before you click save.
* ie. physically look at the list before you even go to Radarr.

== With the release of Radarr V3, what release should I download? ==
[[#with_the_release_of_radarr_v3_what_release_should_i_download|anchor]] 
Please see better information [[Radarr FAQ#How do I update Radarr?|here]]

== Why did the GUI / UI Change? Can it be changed back? ==
[[#why_did_the_gui_ui_change|anchor]] 
* Radarr is a fork of [[Sonarr]] which has the new UI.
* No it cannot be changed back. No it will not be changed back.
* You may, however, check out [https://github.com/gilbN/theme.park Theme Park]


== Where did Wanted and Cut-off Unmet go? ==
[[#where_did_wanted_and_cutoff_unmet_go|anchor]] 
* Movie Index (AKA 'Movies') -> Filter (top right corner) -> <code>Wanted</code> and <code>Cut-off Unmet</code>
[[File:radarr-where-did-wanted-and-cutoff-unmet-go.png|thumb|none|750px|alt=This is where wanted and Cut-off Unmet went|This is where wanted and Cut-off Unmet went]]

== Why can't I add a new movie to Radarr? ==
[[#why_cant_i_add_a_new_movie_to_radarr|anchor]] 
* Radarr uses [http://themoviedb.org The Movie Database (TMDb)] for movie information and images like fanart, banners and backgrounds. Generally, there are a few reasons why you may not be able to add a movie:
* TMDb doesn't like special characters to be used when searching for movies through the API (which Radarr uses), so try searching a translated name, and/or without special characters.
* You can also add by TMDb ID or, if TMDb has it, the IMDb ID
* The movie hasn't been added to TMDb yet, follow their [https://www.themoviedb.org/bible/new_content#59f7933c9251413e93000006 guide] to get it added.

== Can all my movie files be stored in one folder? ==
[[#can_all_my_movie_files_be_stored_in_one_folder|anchor]] 
* Not yet and the reason is that Radarr is a fork of [[Sonarr]], where every show has a folder. This limitation is a known pain point for many users and will maybe come in a future version.
:If you're looking to moving all your movies from one folder to individual folders check [[Radarr Tips and Tricks#Create a Folder for Each Movie|here]]

== Can I put all my movies in my library into one folder ==
[[Radarr FAQ#Can I put all my movies in my library into one folder|anchor]]

We get asked this a lot. There are no plans to support <code>\data\Movies\Movie1.mkv</code>, <code>\data\Movies\Movie2.mkv</code>, etc.

The [https://github.com/Radarr/Radarr/issues/153 Custom Folder GitHub Issue] technically covers this request, but it is no guarantee that all movie files in one folder will be implemented at that time.

A slight hack-ish solution is noted below. Please note that you mustn't trigger a rescan or it will show as missing and regardless the movie will never be upgraded.

* Use a Custom Script
** the script should be triggered on import
** it should be designed to move the file whenever you want it
** it then needs to call the Radarr API and change the movie to unmonitored.

== How can I rename my movie folders? ==
[[#how_can_i_rename_my_movie_folders|anchor]] 
# Movies
# Movie Editor
# Select what movies need their folder renamed
# Change Root Folder to the same Root Folder that the movies currently exist in
# Select "Yes move files"

== Movie File and Folder Naming ==
[[#movie_file_and_folder_naming|anchor]] 
* Currently, Radarr requires that each movie be in a folder with the format containing at minimum <code>Movie Title (Year)/</code>, optionally <code>_</code> or <code>.</code> are valid separators. To facilitate correct quality and resolution identification during import, a file name like <code>Movie Title (Year) [Quality-Resolution].ext</code> is best, again <code>_</code> or <code>.</code> are valid separators too.
* A useful tool for making these changes to your collection is [http://www.filebot.net/#download filebot] which has paid version in both the Apple and Windows stores, but can be found for free on their legacy [https://sourceforge.net/projects/filebot/files/latest/download SourceForge] site. It has both a GUI and CLI, so you can use whatever you’re comfortable with. For the above example, <code>{ny}</code> expands to <code>Name (Year)</code> and <code>{vf}</code> gives the resolution like <code>1080p</code>. There is nothing to infer quality, so you can fake it using <code>{ny}/{ny} [{dim[0] >= 1280 ? 'Bluray' : 'DVD'}-{vf}]</code> which will name anything lower than 720p to <code>[DVD-572p]</code> and greater or equal to 720p like <code>[Bluray-1080p]</code>.
See [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] for more details.

== Movie Folders Named Incorrectly ==
[[#movie_folders_named_incorrectly|anchor]] 
* Even if your movies are in folders already, the folders may not be named correctly. The folder name should be <code>Movie Title (Year)</code>, having the title and year in the folder’s name is critical right now.
* Examples that will work well:
** <code>/mnt/Movies/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** <code>/mnt/Kid Movies/Frozen (2013)/Frozen (2013) [Bluray-1080p].mkv</code>
* Examples that will work, but will require manual management:
** By letters: <code>/mnt/Movies/A-D/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By rating: <code>/mnt/Movies/R/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By genre: <code>/mnt/Movies/Crime, Drama, Sci-Fi/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** These examples will require manual management when the movie is added. Each of the examples will have many root directories, like <code>A-D</code> and <code>E-G</code> in the first letter example, <code>R</code> and <code>PG-13</code> in the rating example and you can guess at the variety of genre folders. When adding a new movie, the correct base folder will need to be selected for this format to work.
* Examples that won’t work:
** Single folder: <code>/mnt/Kid Movies/Frozen (2013) [Bluray-1080p].mkv</code>
*** At this time, movies simply have to be in a folder named after the movie. There is no way around this until development work is done to add this feature.
**'''Movie''' Folder Naming Formats from v0.2 that include '''File''' properties in the '''movie folder''' name such as <code>{Movie.Title}.{Release Year}.{Quality.Full}-{MediaInfo.Simple}{`Release.Group}</code> will not work in v3.
*** Folders are related to the movie and independent of the file. Additionally, this will break with the planned multiple files per movie support.
*** The other reason it was removed was it caused frequent confusion, database corruption, and generally was only half baked.
* The [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.

== How can I mass delete movies from the wanted list? ==
[[#how_can_i_mass_delete_movies_from_the_wanted_list|anchor]] 
* Use Movie Editor -> Select movies you want to delete -> Delete

== Why doesn't Radarr work behind a reverse proxy ==
[[#why_doesnt_radarr_work_behind_an_nginx_reverse_proxy|anchor]] 
* Starting with V3 Radarr has switched to .NET Core and a new webserver. In order for SignalR to work, the UI buttons to work, database changes to take, and other items. It requires the following addition to the location block for Radarr:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

* Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
* [https://github.com/aspnet/AspNetCore/issues/17081 See this ASP.NET Core issue]
* If you are using a CDN like Cloudflare ensure websockets are enabled to allow websocket connections.

== How do I update Radarr? ==
[[#how_do_i_update_my_radarr|anchor]] 
# Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
# Under the Development section change the branch name to <code>master</code> or <code>develop</code>
# Save
''This will not install the bits from that branch immediately, it will happen during the next update.''

* master (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. This is currently v3. This version will receive updates approximately monthly. On GitHub, this is the <code>master</code> branch.
* develop (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first. This is currently v3. This version will receive updates either weekly or biweekly depending on development. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is a snapshot of the <code>develop</code> branch at a point in time.
* nightly (Nightly): The bleeding edge. Released as soon as code is committed and passed all automated tests. '''''Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.''''' This is currently v3. This version is updated immediately. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is the <code>develop</code> branch.

* Note: If your install is through Docker append <code>:release</code>, <code>:latest</code>, or <code>:testing</code> to the end of your container tag depending on who makes your builds.
{| class="wikitable"
|+
!Current Versions
!master
!develop
!nightly
|-
|
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Frelease%2FVERSION.json Current Master/Latest]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Ftesting%2FVERSION.json Current Develop/Beta]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Fnightly%2FVERSION.json Current Nightly/Alpha]
|}
<center>
{| class="wikitable"
|-
! Release Channel Type !! Branch: master (stable) (v3.2) !! Branch: develop (beta) (v3.2) !! Branch: nightly (unstable) (v3.2)
|-
|[https://hub.docker.com/r/hotio/radarr hotio]||<code>hotio/radarr:release</code>||<code>hotio/radarr:testing</code>|| If you have to ask, you should not be on it.
|-
|[https://hub.docker.com/r/linuxserver/radarr LinuxServer.io]||<code>linuxserver/radarr:latest</code>||<code>linuxserver/radarr:develop</code>|| If you have to ask, you should not be on it.
|}
</center>

=== Installing a newer version ===
If Native:
# Go to System and then the Updates tab
# Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
If Docker:
# Repull your tag and update your container

== Can I switch from nightly back to develop? ==
[[#can_i_switch_from_nightly_back_to_develop|anchor]] 

[[Radarr_FAQ#Can I switch between branches?|See this related question]]

== Can I switch between branches? ==
[[#can_i_switch_between_branches|anchor]] 
* You can (almost) always increase your risk.
* <code>master</code> can go to <code>develop</code> or <code>nightly</code>
* <code>develop</code> can go to <code>nightly</code>
* Check with the development team to see if you can switch from <code>nightly</code> to <code>master</code>; <code>nightly</code> to <code>develop</code>; or <code>develop</code> to <code>master</code> for your given build.
* Failure to follow these instructions may result in your Radarr becoming unusable or throwing errors. You have been warned.
** The most common error is something like <code>Error parsing column 45 (Language=31 - Int64)</code> or other similar database errors around missing columns or tables.

* '''May 19 2021 Update'''
** <code>3.2.2</code> has been released as master/stable
** For those on nightly and are still on <code>3.2.2.5053</code> or lower you can safely downgrade to master or develop.
*** Develop can also downgrade to master as well.
*** Please note that if you're on nightly there will be no update to install given your build is higher than the current develop/master.

== How does radarr handle foreign movies or foreign titles? ==
[[#how_does_radarr_handle_foreign_movies_or_foreign_titles|anchor]] 
* Radarr uses both Alt Titles and Translations for parsing and searching. Search will use the Original Title, English Title, and Translated Title from whatever languages you have preferred (in profile and CFs). Parsing should look for a match in all Translations and Alt Titles.

* To get a movie in a foreign language set your Profile Language to Original (Movie's Original Language), a specific language for that profile, or any and use custom formats to determine which language to grab.
* Note that this does not include any indexer languages specified as multi.

== How does radarr handle "multi" in names? ==
[[#how_does_radarr_handle_multi_in_names|anchor]] 
* Radarr by default assumes multi is english and french unless specified in your indexer's advanced settings in Radarr.

* Note that multi definitions only help for release parsing and not for foreign titles or movies searches.

== Help, Movie Added, But Not Searched ==
[[#help_movie_added_but_not_searched|anchor]] 

* Neither Radarr nor Sonarr ''actively'' search for missing movies automatically. Instead, a periodic query of new posts is made to all indexers configured for RSS. When a wanted or cutoff unmet movie shows up in that list, it gets downloaded. This means that until a movie is posted (or reposted), it won’t get downloaded.
* If you’re adding a movie that you want now, the best option is to check the “Start search for missing movie” box, to the left of the ''Add Movie'' ('''1''') button. You can also go to the page for a movie you’ve added and click the magnifying glass “Search” ('''2''') button or use the Wanted view to search for Missing or Cutoff Unmet movies.

[[File:start search for missing movie.png|thumb|none|750px|alt=Add and Search for movie|Add and Search for movie]]
[[File:Search selected movie.png||thumb|none|750px|altt=Search selected movie|Search selected movie]]

== Root path for movies imported from lists becomes “C:” or other weird paths ==
[[#root_path_for_movies_imported_from_lists_become_c_or_other_weird_paths|anchor]] 
* Sometimes you can get a problem that movies that are imported from your lists, gets imported with the root path set to “C:” or other weird paths.

* This is a known issue for when the root path is either not setup during the creation of the list, or if the root path has been deleted after the list was created. Note that this problem can still occur even if the list is '''edited''' and the correct root path is set.

* Use the Movie Editor to fix paths of existing movies.

== Movie Imported, But Source File And Torrent Not Deleted ==
[[#movie_imported_but_source_file_and_torrent_not_deleted|anchor]] 
* Check if you have Completed Download Handling - Remove turned on. (This does not work if you are using rtorrent.)

[[File:Remove turned on.png|thumb|none|750px|alt=Settings|Settings > Download Clients]]

* If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.

== My Custom Script stopped working after upgrading from v0.2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v0.2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== I am using a Pi and Raspbian and Radarr will not launch ==
[[#i_am_using_a_pi_and_raspbian_and_radarr_will_not_launch|anchor]] Raspbian has a version of libseccomp2 that is too old to support running a docker container based on Ubuntu 20.04, which both hotio and LinuxServer use as their base for v3. You either need to use <code>--privileged</code>, update libseccomp2 from Ubuntu or get a better OS (We recommend Ubuntu 20.04 arm64)

'''Possible Solution:'''

Managed to fix the issue by installing the backport from debian repo. Generally not recommended to use backport in blanket upgrade mode. Installation of a single package may be ok but may also cause issues. So got to understand what you are doing.

Steps to fix:

First ensure you are running Raspbian buster e.g using <code>lsb_release -a</code>

Distributor ID: Raspbian

Description: Raspbian GNU/Linux 10 (buster)

Release: 10

Codename: buster

''If you are using buster:''
<code>Add the line `deb <nowiki>http://deb.debian.org/debian</nowiki> buster-backports` main to `/etc/apt/sources.list`
Run apt-get update
apt-get -t buster-backports install libseccomp2</code>

== Why are lists sync times so long and can I change it? ==
[[#why_are_lists_sync_times_so_long_and_can_i_change_it|anchor]]

Lists never were nor are intended to be <code>add it now</code> they are <code>hey i want this, add it eventually</code> tools

You can trigger a list refresh manually, script it and trigger it via the API, add the movies to radarr, use Ombi, or any similar app that adds them right away

This change was due to not have our server get killed by people updating lists every 10 minutes.

== Why doesn't Radarr work behind an nginx reverse proxy ==

[[Radarr_FAQ#Why_doesn.27t_Radarr_work_behind_a_reverse_proxy|See this section]]

== Can I disable the refresh movies task ==
[[#can_I_disable_the_refresh_movies_task|anchor]]

No, nor should you through any SQL hackery. The refresh movies task queries the upstream Servarr proxy and checks to see if the metadata for each movie (ids, cast, summary, rating, translations, alt titles, etc.) has updated compared to what is currently in Radarr. If necessary, it will then update the applicable movies.

A common complaint is the Refresh task causes heavy I/O usage. This is partly due to the setting "Analyze video files" which is advised to be enabled if you use tdarr or otherwise externally modify your files. If you don't you can safely disable "Analyze video files" to reduce some I/O. The other setting is "Rescan Movie Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to <code>Manual</code>. Do not change this to <code>Never</code> unless all changes to your library (new movies, upgrades, deletions etc) are done through Radarr. If you delete movie files manually or via Plex or another third party program, do not set this to <code>Never</code>.

{{FAQ|ARRNAME=Radarr|ARRDISCORD=https://radarr.video/discord|ARRPORT=7878}}

Template:Troubleshooting

2021-05-24T21:18:36Z

Bakerboy448:

<noinclude>
<templatedata>
{
"params": {
"ARRNAME": {
"description": "Name of the Application",
"example": "Radarr",
"type": "string",
"required": true
},
"ARR_DISCORD": {
"description": "Link to the ARR #support Discord",
"type": "url",
"required": true
},
"ARR_WEBSITE": {
"description": "Link to the ARR Website",
"type": "url",
"required": true
},
"ARR_LATEST_RELEASE": {
"description": "Link to the ARR Download",
"type": "url",
"required": true
},
"VERSION": {
"description": "The current version of each of the ARRs",
"type": "string",
"required": true
},
"MEDIA": {
"description": "What type of media does the ARR use",
"example": "Radarr: movies, Sonarr: series, Lidarr: artist, Readarr: author",
"type": "string",
"required": true
},
"SEARCHSOURCE": {
"description": "What metadata provider does the ARR use",
"example": "Radarr: TMDb, Sonarr: TheTVDb, Lidarr: MusicBrainz, Readarr: GoodReads",
"type": "string",
"required": true
},
"QUERYSTRING": {},
"ARRNAME2": {
"description": "This string is used for lower cased ARR names for transclusion",
"example": "radarr, sonarr, lidarr, readarr",
"type": "string",
"required": true
}
},
"description": "This template is utilized for general troubleshooting steps that span across all the ARRs. Some Sections may be transcluded from a Troubleshooting Misc page when items are ARR specific."
}
</templatedata>
</noinclude>
== Troubleshooting ==
----
Please note that this information is only for {{{ARRNAME}}} {{{VERSION}}}.
=== Asking for Help ===
----
Do you need help? That's okay, everyone needs help sometimes. You can get real time help via chat on [{{{ARR_DISCORD}}} Discord] or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit].

But before you go there and post, be sure your request for help is the best it can be. Clearly describe the problem and briefly describe your setup, including things like your OS/distribution, version of Mono or .Net/.Netcore, version of {{{ARRNAME}}}, download client and its version. '''If you are using [https://www.docker.com/ Docker] please run through [[Docker Guide|the Docker Guide]] first as that will solve common and frequent path/permissions issues. Otherwise please have a [[Docker Guide#Docker-compose|docker compose]] handy''' Tell us about what you've tried already, what you've looked at. Use the Logging and Log Files to turn your logging up to trace, recreate the issue, paste the logs into a pastebin such as [https://0bin.net/ 0bin]: the relevant context and include a link to it in your post. Maybe even include some screen shots to highlight the issue.

The more we know, the easier it is to help you.

== Logging and Log Files ==

If you're linked here for support remember to get them the information from the actual trace log file, put the logs in a pastebin and show us context around what we need to see. If you're asked for debug logs your logs will contain <code>debug</code> and if you're asked for trace logs your logs will contain <code>trace</code>. If the logs you are providing do not contain either then they are not the logs requested.

What you need to do is:
# Turn Logging up to Trace
# Clear Logs
# Reproduce the Issue
# Open the trace log file ({{{ARRNAME}}}.trace.txt) and fine the relevant context
# Upload the context to [https://hastebin.com/ Hastebin], [https://pastebin.ubuntu.com/ Pastebin], [https://0bin.net/ 0bin], or any other pastebin type site a big chunk before the issue, the issue, and a big chunk after the issue.

* Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use N++. You can use the Notepad++ "Find in Files" function to search old log files as needed.
* '''Unix Only:''' Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use grep. For example if you want to find information about the movie or show "Shooter" you can run the following command <code>grep -inr -C 100 -e 'Shooter' /path/to/logs/*.trace*.txt</code> If your [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]] is in your home folder then you'd run: <code>grep -inr -C 100 -e 'Shooter' /home/$User/.config/logs/*.trace*.txt</code>
<div style="margin-left: 2em;"><pre>
* The flags have the following functions
* -i: ignore case
* -n: show line number
* -r: recursively check all files in the path
* -C: provide # of lines before and after the line it is found on
* -e: the pattern to search for
</pre></div>

==== Standard Logs Location ====
The log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the logs/ folder. You can also access the log files from the {{{ARRNAME}}} UI at System -> Logs -> Files.

Note: The Logs ("Events") Table in the UI is not the same as the log files and isn't as useful. If you're asked for logs, please copy/paste from the log files and not the table.

==== Update Logs Location ====
The update log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the UpdateLogs/ folder.

==== Sharing Logs ====
The logs can be long and hard to read as part of a forum or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit] post and they're spammy in [{{{ARR_DISCORD}}} Discord], so please use [https://pastebin.ubuntu.com/ Pastebin], [https://hastebin.com/ Hastebin], or any other similar pastebin site . The whole file typically isn't needed, just a good amount of context from before and after the issue/error. Don't forget to wait for spammy tasks like the RSS sync or library refresh to finish.

==== Trace/Debug Logs ====

You can change the log level at Settings -> General -> Logging. {{{ARRNAME}}} does not need to restarted for the change to take effect. This change only affects the log files, not the logging database. The latest debug/trace log files are named <code>{{{ARRNAME}}}.debug.txt</code> and <code>{{{ARRNAME}}}r.trace.txt</code> respectively.

If you're unable to access the {{{ARRNAME}}} UI to set the logging level you can do so by editing config.xml in the AppData directory by setting the LogLevel value to Debug or Trace instead of Info.
<div style="margin-left: 2em;"><pre>
<Config>
...
<LogLevel>debug</LogLevel>
...
</Config>
</pre></div>

==== Clearing Logs ====

You can clear log files and the logs database directly from the UI, under System -> Logs -> Files and System -> Logs -> Delete (Trash Can Icon)

==== Multiple Log Files ====

{{{ARRNAME}}} uses rolling log files limited to 1MB each. The current log file is always ,<code>{{{ARRNAME}}}.txt</code>, for the the other files <code>{{{ARRNAME}}}.0.txt</code> is the next newest (the higher the number the older it is). This log file contains fatal, error, warn, and info entries.

When Debug log level is enabled, additional <code>{{{ARRNAME}}}.debug.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, and debug entries. It usually covers a 40h period.

When Trace log level is enabled, additional <code>{{{ARRNAME}}}.trace.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, debug, and trace entries. Due to trace verbosity it only covers a couple of hours at most.

== Recovering from a Failed Update ==
----
==== Purpose ====
We do everything we can to prevent issues when upgrading, but they occur, this will walk you through the steps of recovering your installation.

==== Determine the issue ====
The best place to look when {{{ARRNAME}}} won't start after an update is your log files, before trying to start {{{ARRNAME}}} again, use [[{{{ARRNAME}}} Settings#Logging|Logging]] and [[{{{ARRNAME}}} System#Log_Files|Log Files]] to find them and increase the log level.

'''Migration Issue'''

Migration errors won't be identical, but here is an example:

<code>
14-2-4 18:56:49.5|Info|MigrationLogger|*** 36: update_with_quality_converters migrating ***

14-2-4 18:56:49.6|Error|MigrationLogger|SQL logic error or missing database duplicate column name: Items

While Processing: "ALTER TABLE "QualityProfiles" ADD COLUMN "Items" TEXT"

</code>

==== Resolving the issue ====
In the event of a migration issue there is not much you can do immediately, if the issue is specific to you (or there are not yet any posts), please create a post on [https://reddit.com/r/{{{ARRNAME}}} our subreddit] or swing by our discord, if there are others with the same issue, then rest assured we are working on it.

==== Manually upgrading ====
Grab the latest release from [{{{ARR_WEBSITE}}} our website]

Install the update (.exe) or extract (.zip) the contents over your existing installation and re-run {{{ARRNAME}}} as you normally would.

== Downloads and Importing ==

Downloading and importing is where ''most'' people experience issues. From a high level perspective, {{{ARRNAME}}} 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.

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

When you reach out for help, be sure to read [[#Asking for Help|asking for help]] so that you can provide us with the details we’ll need.

=== Testing the Download Client ===

Ensure your download client(s) are running. Start by testing the download client, if it doesn’t work you’ll be able to see details in the trace level logs. You should find a URL you can put into your browser and see if it works. It could be a connection problem, which could indicate a wrong ip, hostname, port or even a firewall blocking access. It might be obvious, like an authentication problem where you’ve gotten the username, password or apikey wrong.

=== Testing a Download ===

Now we’ll try a download, pick a {{{MEDIA}}} and do a manual search. Pick one of those files and attempt to download it. Does it get sent to the download client? Does it end up with the correct category? Does it show up in Activity? Does it end up in the trace level logs during the '''Check For Finished Download''' task which runs roughly every minute? Does it get correctly parsed during that task? Does the queued up download have a reasonable name? Since {{{ARRNAME}}} searches by '''{{{SEARCHSOURCE}}}''', on most indexers/trackers, it can queue one up with a name that it can’t recognize.

=== Testing an Import ===

Import issues should almost always manifest as an item in Activity with an orange icon you can hover to see the error. If they’re not showing up in Activity, this is the issue you need to focus on first so go back and figure that out. Most import errors are ''permissions'' issues, remember that {{{ARRNAME}}} needs to be able to read and write in the download folder. Sometimes, permissions in the library folder can be at fault too, so be sure to check both.

Incorrect path issues are possible too, though less common in normal setups. The key to understanding path issues is knowing that {{{ARRNAME}}} gets the path to the download ''from'' the download client, via its API. This becomes a problem in more unique use cases, like the download client running on a different system (maybe even OS!). It can also occur in a Docker setup, when volumes are not done well. A remote path map is a good solution where you don’t have control, like a seedbox setup. On a Docker setup, fixing the paths is a better option.

=== Common Problems ===

==== Download Client's WebUI is not enabled ====
{{{ARRNAME}}} talks to you download client via it's API and accesses it via the client's webui. You must ensure the client's webui is enabled and the port it is using does not conflict with any other client ports in use or ports in use on your system.

==== SSL in use and incorrectly configured ====
Ensure SSL encryption is not turned on if you're using both your {{{ARRNAME}}} instance and your download client on a local network. See [[{{{ARRNAME}}}_FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

==== Can’t see share on Windows ====

The default user for a Windows service is '''SYSTEM''' which typically doesn’t have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [[{{{ARRNAME}}} FAQ#Why can’t {{{ARRNAME}}} see my files on a remote server?|why can’t {{{ARRNAME}}} see my files on a remote server]] for details.

==== Mapped network drives are not reliable ====

While mapped network drives like <code>X:\</code> are convenient, they aren’t as reliable as UNC paths like <code>\\server\share</code> and they’re also not available before login. Setup {{{ARRNAME}}} and your download client(s) so that they use UNC paths as needed. If your library is on a share, you’d make sure your root folders are using UNC paths. If your download client sends to a share, that is where you’ll need to configure UNC paths since {{{ARRNAME}}} gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don’t use them for automation.

==== Docker and user, group, ownership, permissions and paths ====

Docker adds another layer of complexity that is easy to get wrong, but still end up with a setup that functions, but has various problems. Instead of going over them here, read this wiki article [[Docker Guide|for these automation software and Docker]] which is all about user, group, ownership, permissions and paths. It isn’t specific to any Docker system, instead it goes over things at a high level so that you can implement them in your own environment.

==== Permissions on the Library Folder ====
Don’t forget to check permissions and ownership of the ''destination''. It is easy to get fixated on the download’s ownership and permissions and that is ''usually'' the cause of permissions related issues, but it ''could'' be the destination as well. Check that the destination folder(s) exist. Check that a destination ''file'' doesn’t already exist or can’t be deleted or moved to recycle bin. Check that ownership and permissions allow the downloaded file to be copied, hard linked or moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the root folder.

==== Permissions on the Downloads Folder ====

Don’t forget to check permissions and ownership of the ''source''. It is easy to get fixated on the destination's ownership and permissions and that is a ''possible'' cause of permissions related issues, but it ''typically'' is the source. Check that the source folder(s) exist. Check that ownership and permissions allow the downloaded file to be copied/hardlinked or copy+delete/moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the downloads folder.

==== Download folder and library folder not different folders ====

The download client should download into a folder accessible by {{{ARRNAME}}} and that is not your root/library folder; {{{ARRNAME}}} should import from that separate download folder into your Library folder.

You should never download directly into your root folder. You also should not use your root folder as the download client's completed folder or incomplete folder.

If you download right into your library folder, you’ll end up with multiple copies of your media and when there are import issues, which there will be, you may not notice because your media server will see the download client copy.

The download folder will also be a hot mess of poorly named folders and files while your library folder will be nice and neat.

This frequently causes other random import issues as well.

==== Incorrect category ====

{{{ARRNAME}}} should be setup to use a category so that it only tries to process its own downloads. It is rare that a torrent submitted by {{{ARRNAME}}} gets added without the correct category, but it can happen. If you’re adding torrents manually and want {{{ARRNAME}}} to process them, they’ll need to have the correct category. It can be set at any time, since {{{ARRNAME}}} tries to process downloads every minute.

==== Packed torrents ====

If your torrent is packed in <code>.rar</code> files, you’ll need to setup extraction. We recommend [https://github.com/davidnewhall/unpackerr unpackerr]. One issue to look out for with packed torrents is that the video file will be copied or hard linked like normal, but it isn’t needed since the <code>.rar</code> files are seeding. That means if you’re using a ''copy'' setup, the torrent will be consuming double the space. And if you’re using a hard link setup, your torrent folder will be a little messier because of the unneeded file. This can be mitigated with a [https://gist.github.com/fryfrog/94716e7e27ba38dff57c7631d9f58bed cleanup script].

==== Repeated downloads ====

There are a few causes of repeated downloads, but a recent one is related to the Indexer restriction in Release Profiles. Because the indexer ''isn’t'' stored with the data, any preferred word scores are ''zero'' for media in your library, ''but'' during “RSS” and search, they’ll be applied. This gets you into a loop where you download the items again and again because it looks like an upgrade, then isn’t, then shows up again and looks like an upgrade, then isn’t. Don’t restrict your release profile to an indexer.

==== Usenet download misses import ====

{{{ARRNAME}}} only looks at the 60 most recent downloads in SABnzbd and NZBGet, so if you ''keep'' your history this means that during large queues with import issues, downloads can be silently missed and not imported. The best way to avoid that is to keep your history clear, so that any items that still appear need investigating. You can achieve this by enabling Remove under Completed and Failed Download Handler. In nzbget, this will move items to the ''hidden'' history which is great. Unfortunately, sabnzbd does not have a similar feature. The best you can achieve there is to use the nzb backup folder.

==== Download client clearing items ====

The download client should ''not'' be responsible for removing downloads. Usenet clients should be configured so they ''don’t'' remove downloads from history. Torrent clients should be setup so they ''don’t'' remove torrents when they’re finished seeding (pause or stop instead). This is because {{{ARRNAME}}} communicates with the download client to know what to import, so if they’re ''removed'' there is nothing to be imported… even if there is a folder full of files.

For Sabnzbd, this is handled with the History Retention setting.

==== Download cannot be matched to a library item====
For various reasons, releases cannot be parsed once's grabbed and sent to the download client. Activity -> Options -> Shown Unknown will display all items not otherwise ignored / already imported within {{{ARRNAME}}}'s download client category. These will typically need to be manually mapped and imported.

This can also occur if you have a release in your download client but that media item (movie/episode/book/song) does not exist in the application.

=== Problem Not Listed ===
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

== Searches Indexers and Trackers ==

=== Turn logging up to trace ===

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

=== Testing an Indexer or Tracker ===

When you test an indexer or tracker, in debug or trace logs you can find the URL used. An example of a successful test is below, you can see it query the indexer via a specific URL with specific parameters and then the response. You test this url in your browser like <code>{{{QUERYSTRING}}}</code> replacing the <code>apikey=(removed)</code> with the correct apikey like <code>apikey=123</code>. You can experiment with the parameters if you’re getting an error from the indexer or see if you have connectivity issues if it doesn’t even work. After you’ve tested in your own browser, you should test from the system {{{ARRNAME}}} is running on ''if'' you haven’t already.

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block}}

=== Testing a Search ===
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_testing_a_search}}

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers1.png|thumb|none|750px]]

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers2.png|thumb|none|750px]]

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block2}}

Here you can see the ''full'' trace log below
{{#lst:Troubleshooting Misc|{{{ARRNAME2}}}_trace_logs_example}}

=== Common Problems ===

==== Media is Unmonitored ====
The {{{MEDIA}}} is/are not monitored.

==== Wrong categories ====

Incorrect categories is probably the most common cause of results showing in manual searches of an indexer/tracker, but ''not'' in {{{ARRNAME}}}. The indexer/tracker ''should'' show the category in the search results, which should help you figure out what is missing. If you’re using Jackett, each tracker has a list of specifically supported categories. Make sure you’re using the correct ones for Categories. I find it helpful to have the list visible in one browser window while I edit the entry in {{{ARRNAME}}}.
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_type}}
==== Wrong results ====

Sometimes indexers will return completely unrelated results, {{{ARRNAME}}} will feed in parameters to limit the search to a {{{SEARCHSOURCE}}}, but the results returned are completely unrelated. Or sometimes, mostly related with a few incorrect results. The first is usually an indexer problem and you’ll be able to tell from the trace logs which is causing it. You can disable that indexer and report the problem. The other is usually categorized releases which should be reportable on the indexer/tracker.

==== Certificate validation ====

You’ll be connecting to most indexers/trackers via https, so you’ll need that to work properly on your system. That means your time zone and time both need to be set ''correctly''. It also means your system certificates need to be up to date.

==== Hitting rate limits ====

If you run your {{{ARRNAME}}} through a VPN or proxy, you may be competing with 10s or 100s or 1000s of other people all trying to use services like {{{SEARCHSOURCE}}}, theXEM ,and/or your indexers and trackers. Rate limiting and DDOS protection are often done by IP address and your VPN/proxy exit point is ''one'' IP address. Unless you’re in a repressive country like China, Australia or South Africa you don’t need to VPN/proxy {{{ARRNAME}}}.

Rarbg has a tendency to have some sort of rate limiting within their API and displays as responding with no results.

==== Using the Jackett /all endpoint ====

The Jackett <code>/all</code> endpoint is convenient, but that is its only benefit. Everything else is potential problems, so adding each tracker individually is recommended.

[https://github.com/Jackett/Jackett#aggregate-indexers Even Jackett says it should be avoided and should not be used.]

Using the all endpoint has no advantages (besides reduced management overhead), only disadvantages:
* you lose control over indexer specific settings (categories, search modes, etc.)
* mixing search modes (IMDB, query, etc.) might cause low-quality results
* indexer specific categories (>= 100000) can't be used.
* slow indexers will slow down the overall result
* total results are limited to 1000

Adding each indexer separately It allows for fine tuning of categories on a per indexer basis, which can be a problem with the <code>/all</code> end point if using the wrong category causes errors on some trackers. In {{{ARRNAME}}}, each indexer is limited to 1000 results if pagination is supported or 100 if not, which means as you add more and more trackers to Jackett, you’re more and more likely to clip results. Finally, if ''one'' of the trackers in <code>/all</code> returns an error, {{{ARRNAME}}} will disable it and now you don’t get any results.

==== Problem Not Listed ====
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

=== Errors ===

These are some of the common errors you may see when adding an indexer

==== The underlying connection was closed: An unexpected error occurred on a send. ====

This is caused by the indexer using a SSL protocol not supported by .net 4.5, to resolve this you will need to install .net 4.5, which is available on Vista/Server 2008 and above (if you’re on XP/Server 2003 its time to upgrade).

==== The request timed out ====

{{{ARRNAME}}} seems to have issues with certain TLS versions or configurations. If you get the following error messages in your log:
<pre>System.Net.WebException: The request timed out: ’https://example.org/api?t=caps&apikey=(removed) —> System.Net.WebException: The request timed out</pre>

And you can see the following in the trace log file:
<pre><DATE&TIME>|Trace|FallbackHttpDispatcher|Curl not available, using default WebClient. </pre>

You might fix it by installing libcurl3. On Ubuntu/Debian use;
<pre>apt install libcurl3</pre>

This can also be caused by:
* improperly configured or use of a VPN
* improperly configured or use of a proxy
* local DNS issues
* local IPv6 issues

MediaWiki:Sidebar

2021-05-21T23:31:21Z

Bakerboy448:

Installation Misc

2021-05-21T23:29:47Z

Bakerboy448:

== Installation ==
=== Radarr ===
==== OSX ====
<section begin=radarr_osx_installation />
Detailed instructions coming "soon"
For now please see our website for details:
https://radarr.video/#downloads-v3-macos
<section end=radarr_osx_installation />
<section begin=radarr_linux_installation />
==== Debian/Ubuntu ====
===== .NET Core Install =====
You'll need curl, mediainfo, and sqlite.
<code>sudo apt install curl mediainfo sqlite3</code>

====== Manual Install ======
Note: this assumes you created a user named <code>radarr</code>

[[File:ARR Download Link Example.png|thumb|right|Example of Radarr download options]]
In the example screenshot here, you can see multiple options. Choose the option that matches your OS and processor best. For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url.

For:
* ARM use <code>arch=arm</code>
* ARM64 use <code>arch=arm64</code>
* AMD64 use <code>arch=x64</code>

Download this file onto your system: (Note: The link below will target the Linux .NET Core x64 file. Replace if needed with the file you chose previously)
wget --content-disposition 'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'
* Alternatively: Go to the Radarr download page, and pick the appropriate file: https://github.com/Radarr/Radarr/releases
Uncompress:
tar -xvzf Radarr*.linux*.tar.gz
Move to your preferred install location (typically <code>/opt/Radarr/</code>
sudo mv Radarr/ /opt
Finally, make sure you grant the needed permission to your install directory:
sudo chown radarr:radarr /opt/Radarr

You can start Radarr with the following command:
/opt/Radarr/Radarr -nobrowser
<section end=radarr_linux_installation />

=== Sonarr ===
==== OSX ====
<section begin=sonarr_osx_installation />
<ol>
<li>After downloading Sonarr V3 from [https://services.sonarr.tv/v1/download/phantom-develop/latest?version=3&os=macos&installer=true here]. The <code>zip</code> file will be located in your downloads directory.</li>
<li>After the download has finished you'll need to unzip the file from there you'll have a '''Sonarr.app''' in your downloads folder simply move the '''Sonarr.app''' to your Applications directory.</li>
[[File:Move-sonarr-to-applications.gif|center|frameless|750x750px]]
<li> From there if you go to your launch pad you'll notice that Sonarr is now in there, double click on Sonarr</li>
<li> You'll probably get a pop up that says "Sonarr.app" cannot be opened because the developer cannot be verified.</li>
[[File:sonarr-developer-cannot-be-verified.png|center|frameless|250px]]
<li> Don't fret we can get this fixed.</li>
<ol>
<li>Click on System Preferences in your dock</li>
<li>Click Security and Privacy</li>
<li> Click '''Open Anyways'''</li>
<li> You'll get a pop up that looks something like this:</li>
[[File:sonarr-developer-cannot-be-verified2.png|none|framless|250px]]
<li> Click Open </li>
</ol>
<li> Now since Sonarr uses the Mono Framework Version 5.20 or later if you do not already have that installed you'll receive a pop up like this</li>
[[File:sonarr-cannot-launch-sonarr-mono.png|center|frameless|250px]]
<ul>
<li>Note: If Mono is already installed skip these steps</li>
</ul>
<ol>
<li> Click Download </li>
<li> Safari (or default browser) will now open up to [https://www.mono-project.com/download/stable/#download-mac the Mono Project] for macOS. Click '''Download mono (Stable channel)'''</li>
<li> Once the download is complete go to your downloads folder and click the new pkg file that was downloaded and install it</li>
<li> After installation is complete go back and reopen Sonarr </li>
</ol>
<li> Now browse to <code>http://localhost:8989</code></li>
</ol>
Now you're all set Sonarr is now up and running on your system.
<section end=sonarr_osx_installation />
<section begin=sonarr_linux_installation />

==== Debian/Ubuntu ====

[https://sonarr.tv/#downloads-v3-linux-ubuntu Please see our website]

Manual installs methods are unsupported and you'll need to determine the process yourself.

<section end="sonarr_linux_installation" />

=== Lidarr ===
==== OSX ====
<section begin=lidarr_osx_installation />
Detailed instructions coming "soon"
For now please see our website for details:
https://lidarr.audio/#downloads-v1-macos
<section end=lidarr_osx_installation />

<section begin=lidarr_linux_installation />
==== Debian/Ubuntu ====
===== .NET Core Install =====
You'll need curl, mediainfo, chromaprint, and sqlite.
<code>sudo apt install curl mediainfo sqlite3 libchromaprint-tools</code>

====== Manual Install ======
Note: this assumes you created a user named <code>lidarr</code>

[[File:ARR Download Link Example.png|thumb|right|Example of Lidarr download options]]
In the example screenshot here, you can see multiple options. Choose the option that matches your OS and processor best. For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url.

For:
* ARM use <code>arch=arm</code>
* ARM64 use <code>arch=arm64</code>
* AMD64 use <code>arch=x64</code>

Download this file onto your system: (Note: The link below will target the Linux .NET Core x64 file. Replace if needed with the file you chose previously)
wget --content-disposition 'http://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=x64'
* Alternatively: Go to the Lidarr download page, and pick the appropriate file: https://github.com/Lidarr/Lidarr/releases

Uncompress:
tar -xvzf Lidarr*.linux*.tar.gz
Move to your preferred install location (typically <code>/opt/Lidarr/</code>
sudo mv Lidarr/ /opt
Finally, make sure you grant the needed permission to your install directory:
sudo chown lidarr:lidarr /opt/Lidarr

You can start Lidarr with the following command:
/opt/Lidarr/Lidarr -nobrowser -data=path/to/app/data
<section end=lidarr_linux_installation />

=== Readarr ===
==== OSX ====
<section begin=readarr_osx_installation />
Readarr is in a pre-alpha state. Instructions will be built once Readarr is stable (i.e. alpha).
<section end=readarr_osx_installation />
==== Linux ====
<section begin=readarr_linux_installation />
==== Debian/Ubuntu ====

===== .NET Core Install =====
You'll need curl and sqlite.
<code>sudo apt install curl sqlite3</code>

====== Manual Install ======
Go to the Readarr discord and locate the binaries

Note: this assumes you created a user named <code>readarr</code>

Download this file onto your system:
wget --content-disposition '{Readarr is pre-alpha; link hidden from the public}'
Uncompress:
tar -xvzf Readarr*.linux-core-x64.tar.gz
Move to your preferred install location (typically <code>/opt/Readarr/</code>
sudo mv Readarr/ /opt
Finally, make sure you grant the needed permission to your install directory:
sudo chown readarr:readarr /opt/Readarr

You can start Readarr with the following command:
/opt/Readarr/Readarr -nobrowser
<section end=readarr_linux_ubuntu_NetCore_manual_installation />

=== Prowlarr ===
==== OSX ====
<section begin=prowlarr_osx_installation />
Detailed instructions coming "soon"
For now please see our website for details:
https://prowlarr.com/#downloads-v3-macos
<section end=prowlarr_osx_installation />
<section begin=prowlarr_linux_installation />
==== Debian/Ubuntu ====
===== .NET Core Install =====
You'll need curl and sqlite.
<code>sudo apt install curl sqlite3</code>

====== Manual Install ======
Note: this assumes you created a user named <code>prowlarr</code>
In the example screenshot here, you can see multiple options. Choose the option that matches your OS and processor best. For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url.

For:
* ARM use <code>arch=arm</code>
* ARM64 use <code>arch=arm64</code>
* AMD64 use <code>arch=x64</code>

Download this file onto your system: (Note: The link below will target the Linux .NET Core x64 file. Replace if needed with the file you chose previously)
wget --content-disposition 'https://prowlarr.servarr.com/v1/update/nightly/updatefile?os=linux&runtime=netcore&arch=x64'
Uncompress:
tar -xvzf Prowlarr*.linux*.tar.gz
Move to your preferred install location (typically <code>/opt/Prowlarr/</code>
sudo mv Prowlarr/ /opt
Finally, make sure you grant the needed permission to your install directory:
sudo chown prowlarr:prowlarr /opt/Prowlarr

You can start Prowlarr with the following command:
/opt/Prowlarr/Prowlarr -nobrowser
<section end=prowlarr_linux_installation />

== Code Blocks ==
=== Radarr ===
==== Preparing the Unit Service File ====
<section begin=radarr_installation_unit_service_file />
[Unit]
Description=Radarr Daemon
After=syslog.target network.target

[Service]
# Change the user and group variables here.
User=radarr
Group=radarr

Type=simple
#Update the data path
ExecStart=/opt/Radarr/Radarr -nobrowser -data=/path/to/appdata/for/Radarr/

TimeoutStopSec=20
KillMode=process
Restart=always

[Install]
WantedBy=multi-user.target
<section end=radarr_installation_unit_service_file />

=== Sonarr ===
==== Preparing the Unit Service File ====
<section begin=sonarr_installation_unit_service_file />
Manual installs methods are unsupported and you'll need to determine the process yourself.
<section end=sonarr_installation_unit_service_file />
=== Lidarr ===
==== Preparing the Unit Service File ====
<section begin=lidarr_installation_unit_service_file />
[Unit]
Description=Lidarr Daemon
After=syslog.target network.target

[Service]
# Change the user and group variables here.
User=lidarr
Group=lidarr

Type=simple

# NetCore install:
# Update the data path
ExecStart=/opt/Lidarr/Lidarr -nobrowser -data=/path/to/appdata/for/Lidarr/

TimeoutStopSec=20
KillMode=process
Restart=always

[Install]
WantedBy=multi-user.target
<section end=lidarr_installation_unit_service_file />
=== Readarr ===
==== Preparing the Unit Service File ====
<section begin=readarr_installation_unit_service_file />
[Unit]
Description=Readarr Daemon
After=syslog.target network.target

[Service]
# Change the user and group variables here.
User=readarr
Group=readarr

Type=simple

# NetCore install:
# Update the data path
ExecStart=/opt/Readarr/Readarr -nobrowser -data=/path/to/appdata/for/Readarr/

TimeoutStopSec=20
KillMode=process
Restart=always

[Install]
WantedBy=multi-user.target
<section end=readarr_installation_unit_service_file />

=== Prowlarr ===
==== Preparing the Unit Service File ====
<section begin=prowlarr_installation_unit_service_file />
[Unit]
Description=Prowlarr Daemon
After=syslog.target network.target

[Service]
# Change the user and group variables here.
User=prowlarr
Group=prowlarr

Type=simple
#Update the data path
ExecStart=/opt/Prowlarr/Prowlarr -nobrowser -data=/path/to/appdata/for/Prowlarr/

TimeoutStopSec=20
KillMode=process
Restart=always

[Install]
WantedBy=multi-user.target
<section end=prowlarr_installation_unit_service_file />

Installation Misc

2021-05-21T23:27:18Z

Bakerboy448: /* Prowlarr */

== Installation ==
=== Radarr ===
==== OSX ====
<section begin=radarr_osx_installation />
Detailed instructions coming "soon"
For now please see our website for details:
https://radarr.video/#downloads-v3-macos
<section end=radarr_osx_installation />
<section begin=radarr_linux_installation />
==== Debian/Ubuntu ====
===== .NET Core Install =====
You'll need curl, mediainfo, and sqlite.
<code>sudo apt install curl mediainfo sqlite3</code>

====== Manual Install ======
Note: this assumes you created a user named <code>radarr</code>

[[File:ARR Download Link Example.png|thumb|right|Example of Radarr download options]]
In the example screenshot here, you can see multiple options. Choose the option that matches your OS and processor best. For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url.

For:
* ARM use <code>arch=arm</code>
* ARM64 use <code>arch=arm64</code>

Download this file onto your system: (Note: The link below will target the Linux .NET Core x64 file. Replace if needed with the file you chose previously)
wget --content-disposition 'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'
* Alternatively: Go to the Radarr download page, and pick the appropriate file: https://github.com/Radarr/Radarr/releases
Uncompress:
tar -xvzf Radarr*.linux*.tar.gz
Move to your preferred install location (typically <code>/opt/Radarr/</code>
sudo mv Radarr/ /opt
Finally, make sure you grant the needed permission to your install directory:
sudo chown radarr:radarr /opt/Radarr

You can start Radarr with the following command:
/opt/Radarr/Radarr -nobrowser
<section end=radarr_linux_installation />

=== Sonarr ===
==== OSX ====
<section begin=sonarr_osx_installation />
<ol>
<li>After downloading Sonarr V3 from [https://services.sonarr.tv/v1/download/phantom-develop/latest?version=3&os=macos&installer=true here]. The <code>zip</code> file will be located in your downloads directory.</li>
<li>After the download has finished you'll need to unzip the file from there you'll have a '''Sonarr.app''' in your downloads folder simply move the '''Sonarr.app''' to your Applications directory.</li>
[[File:Move-sonarr-to-applications.gif|center|frameless|750x750px]]
<li> From there if you go to your launch pad you'll notice that Sonarr is now in there, double click on Sonarr</li>
<li> You'll probably get a pop up that says "Sonarr.app" cannot be opened because the developer cannot be verified.</li>
[[File:sonarr-developer-cannot-be-verified.png|center|frameless|250px]]
<li> Don't fret we can get this fixed.</li>
<ol>
<li>Click on System Preferences in your dock</li>
<li>Click Security and Privacy</li>
<li> Click '''Open Anyways'''</li>
<li> You'll get a pop up that looks something like this:</li>
[[File:sonarr-developer-cannot-be-verified2.png|none|framless|250px]]
<li> Click Open </li>
</ol>
<li> Now since Sonarr uses the Mono Framework Version 5.20 or later if you do not already have that installed you'll receive a pop up like this</li>
[[File:sonarr-cannot-launch-sonarr-mono.png|center|frameless|250px]]
<ul>
<li>Note: If Mono is already installed skip these steps</li>
</ul>
<ol>
<li> Click Download </li>
<li> Safari (or default browser) will now open up to [https://www.mono-project.com/download/stable/#download-mac the Mono Project] for macOS. Click '''Download mono (Stable channel)'''</li>
<li> Once the download is complete go to your downloads folder and click the new pkg file that was downloaded and install it</li>
<li> After installation is complete go back and reopen Sonarr </li>
</ol>
<li> Now browse to <code>http://localhost:8989</code></li>
</ol>
Now you're all set Sonarr is now up and running on your system.
<section end=sonarr_osx_installation />
<section begin=sonarr_linux_installation />

==== Debian/Ubuntu ====

[https://sonarr.tv/#downloads-v3-linux-ubuntu Please see our website]

Manual installs methods are unsupported and you'll need to determine the process yourself.

<section end="sonarr_linux_installation" />

=== Lidarr ===
==== OSX ====
<section begin=lidarr_osx_installation />
Detailed instructions coming "soon"
For now please see our website for details:
https://lidarr.audio/#downloads-v1-macos
<section end=lidarr_osx_installation />

<section begin=lidarr_linux_installation />
==== Debian/Ubuntu ====
===== .NET Core Install =====
You'll need curl, mediainfo, chromaprint, and sqlite.
<code>sudo apt install curl mediainfo sqlite3 libchromaprint-tools</code>

====== Manual Install ======
Note: this assumes you created a user named <code>lidarr</code>

[[File:ARR Download Link Example.png|thumb|right|Example of Lidarr download options]]
In the example screenshot here, you can see multiple options. Choose the option that matches your OS and processor best. For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url.

For:
* ARM use <code>arch=arm</code>
* ARM64 use <code>arch=arm64</code>

Download this file onto your system: (Note: The link below will target the Linux .NET Core x64 file. Replace if needed with the file you chose previously)
wget --content-disposition 'http://lidarr.servarr.com/v1/update/develop/updatefile?os=linux&runtime=netcore&arch=x64'
* Alternatively: Go to the Lidarr download page, and pick the appropriate file: https://github.com/Lidarr/Lidarr/releases

Uncompress:
tar -xvzf Lidarr*.linux*.tar.gz
Move to your preferred install location (typically <code>/opt/Lidarr/</code>
sudo mv Lidarr/ /opt
Finally, make sure you grant the needed permission to your install directory:
sudo chown lidarr:lidarr /opt/Lidarr

You can start Lidarr with the following command:
/opt/Lidarr/Lidarr -nobrowser -data=path/to/app/data
<section end=lidarr_linux_installation />

=== Readarr ===
==== OSX ====
<section begin=readarr_osx_installation />
Readarr is in a pre-alpha state. Instructions will be built once Readarr is stable (i.e. alpha).
<section end=readarr_osx_installation />
==== Linux ====
<section begin=readarr_linux_installation />
==== Debian/Ubuntu ====

===== .NET Core Install =====
You'll need curl and sqlite.
<code>sudo apt install curl sqlite3</code>

====== Manual Install ======
Go to the Readarr discord and locate the binaries

Note: this assumes you created a user named <code>readarr</code>

Download this file onto your system:
wget --content-disposition '{Readarr is pre-alpha; link hidden from the public}'
Uncompress:
tar -xvzf Readarr*.linux-core-x64.tar.gz
Move to your preferred install location (typically <code>/opt/Readarr/</code>
sudo mv Readarr/ /opt
Finally, make sure you grant the needed permission to your install directory:
sudo chown readarr:readarr /opt/Readarr

You can start Readarr with the following command:
/opt/Readarr/Readarr -nobrowser
<section end=readarr_linux_ubuntu_NetCore_manual_installation />

=== Prowlarr ===
==== OSX ====
<section begin=prowlarr_osx_installation />
Detailed instructions coming "soon"
For now please see our website for details:
https://prowlarr.com/#downloads-v3-macos
<section end=prowlarr_osx_installation />
<section begin=prowlarr_linux_installation />
==== Debian/Ubuntu ====
===== .NET Core Install =====
You'll need curl and sqlite.
<code>sudo apt install curl sqlite3</code>

====== Manual Install ======
Note: this assumes you created a user named <code>prowlarr</code>

Download this file onto your system:
wget --content-disposition 'https://prowlarr.servarr.com/v1/update/nightly/updatefile?os=linux&runtime=netcore&arch=x64'
Uncompress:
tar -xvzf Prowlarr*.linux*.tar.gz
Move to your preferred install location (typically <code>/opt/Prowlarr/</code>
sudo mv Prowlarr/ /opt
Finally, make sure you grant the needed permission to your install directory:
sudo chown prowlarr:prowlarr /opt/Prowlarr

You can start Prowlarr with the following command:
/opt/Prowlarr/Prowlarr -nobrowser
<section end=prowlarr_linux_installation />

== Code Blocks ==
=== Radarr ===
==== Preparing the Unit Service File ====
<section begin=radarr_installation_unit_service_file />
[Unit]
Description=Radarr Daemon
After=syslog.target network.target

[Service]
# Change the user and group variables here.
User=radarr
Group=radarr

Type=simple
#Update the data path
ExecStart=/opt/Radarr/Radarr -nobrowser -data=/path/to/appdata/for/Radarr/

TimeoutStopSec=20
KillMode=process
Restart=always

[Install]
WantedBy=multi-user.target
<section end=radarr_installation_unit_service_file />

=== Sonarr ===
==== Preparing the Unit Service File ====
<section begin=sonarr_installation_unit_service_file />
Manual installs methods are unsupported and you'll need to determine the process yourself.
<section end=sonarr_installation_unit_service_file />
=== Lidarr ===
==== Preparing the Unit Service File ====
<section begin=lidarr_installation_unit_service_file />
[Unit]
Description=Lidarr Daemon
After=syslog.target network.target

[Service]
# Change the user and group variables here.
User=lidarr
Group=lidarr

Type=simple

# NetCore install:
# Update the data path
ExecStart=/opt/Lidarr/Lidarr -nobrowser -data=/path/to/appdata/for/Lidarr/

TimeoutStopSec=20
KillMode=process
Restart=always

[Install]
WantedBy=multi-user.target
<section end=lidarr_installation_unit_service_file />
=== Readarr ===
==== Preparing the Unit Service File ====
<section begin=readarr_installation_unit_service_file />
[Unit]
Description=Readarr Daemon
After=syslog.target network.target

[Service]
# Change the user and group variables here.
User=readarr
Group=readarr

Type=simple

# NetCore install:
# Update the data path
ExecStart=/opt/Readarr/Readarr -nobrowser -data=/path/to/appdata/for/Readarr/

TimeoutStopSec=20
KillMode=process
Restart=always

[Install]
WantedBy=multi-user.target
<section end=readarr_installation_unit_service_file />

=== Prowlarr ===
==== Preparing the Unit Service File ====
<section begin=prowlarr_installation_unit_service_file />
[Unit]
Description=Prowlarr Daemon
After=syslog.target network.target

[Service]
# Change the user and group variables here.
User=prowlarr
Group=prowlarr

Type=simple
#Update the data path
ExecStart=/opt/Prowlarr/Prowlarr -nobrowser -data=/path/to/appdata/for/Prowlarr/

TimeoutStopSec=20
KillMode=process
Restart=always

[Install]
WantedBy=multi-user.target
<section end=prowlarr_installation_unit_service_file />

WikiMap

2021-05-21T23:22:02Z

Bakerboy448:

Please use https://github.com/Servarr/Wiki to track issues
Please use this page for easy access to templates

This page to act as an overall map of the wiki as many templates and sections are in use via transclusion.

== Stand Alone Templates ==

# [[Template:Appdata Directory]]
## [[Appdata Directory Misc]]
# [[Template:Installation]]
## [[Installation Misc]]
# [[Template:Troubleshooting]]
## [[Troubleshooting Misc]]
# [[Template:Contributing]]
# [[Template:FAQ]]

== Miscellaneous ==
# [[Sandbox]] <- Test code and do any testing here before sending it to live
# [[Useful Tools]]
# [[Cloud Setup|Rclone/Mergerfs/Gdrive setup & links]]
# [[Docker Guide]]
# [[Definitions]]
# [[Discord-Notifier-unRAID-Plex]]
# [[Discord-Notifier-unRAID-Network]]
# [[Clear Cache Cookies and Local Storage]]
# [[Docker on arm synology|Docker on ARM Synology]]

== * ARR UI Pages ==
Note: This is were most of the editing will take place

Note: All templates or sections are housed within their respective pages. To edit those templates click on the page then to the template page.
=== Movies/Series/Library ===
# [[Library]]
# [[Library Add New]]
# [[Library Import]]
# [[Library Discover]] <-- Radarr
# [[Library Mass Editor]] <-- Sonarr/Lidarr
# [[Library Bulk Monitoring Editor]] <--Season Pass/Album Studio/Bookshelf combined
# [[Library Unmapped Files]] <-- Lidarr/Readarr
# [[Filters]]
=== Calendar ===
# [[Calendar]]

=== Activity ===
# [[Activity]]
# [[Activity Queue]]
# [[Activity History]]
# [[Activity Blacklist]]

=== Wanted ===
# [[Wanted]]
# [[Wanted Cutoff Unmet]]

=== Settings ===
# [[Settings Media Management]]
## [[Template:Settings Media Management Root Folders]]
## [[Template:Settings Media Management Folders]]
## [[Template:Settings Media Management Permissions]]
# [[Settings Profiles]]
## [[Template:Settings Profiles Delay Profiles]]
# [[Template:Settings Quality Quality Table Meanings|Settings Quality Profiles (Template)]]
# [[Settings Custom Formats]]
# [[Settings Indexers]]
# [[Settings Download Clients]]
## [[Template:Settings Download Clients Download Clients]]
## [[Template:Settings Download Clients Failed Download Handling]]
# [[Settings Lists]]
# [[Settings Connect]]
# [[Settings Metadata]]
# [[Template:Settings Tags|Settings Tags (Template)]]
# [[Settings General]]
# [[Settings UI]]

=== System ===
# [[System status|System Status]]
# [[System tasks|System Tasks]]
# [[System backup|System Backup]]
# [[System updates|System Updates]]
# [[System events|System Events]]
# [[System log files|System Log Files]]

== Stand Alone Pages ==
* [[Radarr]]

* [[Sonarr]]

* [[Lidarr]]

* [[Readarr]]

== API Documentation ==
* [https://radarr.video/docs/api/ Radarr]

* Sonarr

* Lidarr

* Readarr

== *ARR Pages ==
Note: This is used on the *arr pages to display the links
<section begin=radarr_wiki_pages />
*[[Radarr]]
**[[Radarr Installation]]
**[[Radarr Quick Start Guide]]
**[[Radarr Library|Radarr Library (Movies)]]
**[[Radarr Calendar]]
**[[Radarr Activity]]
**[[Radarr Settings]]
**[[Radarr System]]
**[[Radarr Troubleshooting]]
**[[Radarr FAQ]]
**[[Radarr Tips and Tricks]]
**[[Radarr Contributing]]<section end=radarr_wiki_pages /><section begin=sonarr_wiki_pages />
*[[Sonarr]]
**[https://sonarr.tv/#downloads-v3 Sonarr Installation]
**[[Sonarr Installation|Sonarr Advanced Installation]]
**[[Sonarr Quick Start Guide]]
**[[Sonarr Library|Sonarr Library (Series)]]
**[[Sonarr Calendar]]
**[[Sonarr Activity]]
**[[Sonarr Wanted]]
**[[Sonarr Settings]]
**[[Sonarr System]]
**[[Sonarr Troubleshooting]]
**[[Sonarr FAQ]]
**[[Sonarr Tips and Tricks]]
**[[Sonarr Contributing]]<section end=sonarr_wiki_pages /><section begin=lidarr_wiki_pages />
*[[Lidarr]]
**[[Lidarr Installation]]
**[[Lidarr Quick Start Guide]]
**[[Lidarr Library|Lidarr Library (Artist)]]
**[[Lidarr Calendar]]
**[[Lidarr Activity]]
**[[Lidarr Wanted]]
**[[Lidarr Settings]]
**[[Lidarr System]]
**[[Lidarr Troubleshooting]]
**[[Lidarr FAQ]]
**[[Lidarr Tips and Tricks]]
**[[Lidarr Contributing]]<section end=lidarr_wiki_pages /><section begin=readarr_wiki_pages />
*[[Readarr]]
**[[Readarr Installation]]
**[[Readarr Quick Start Guide]]
**[[Readarr Library|Readarr Library]]
**[[Readarr Calendar]]
**[[Readarr Activity]]
**[[Readarr Wanted]]
**[[Readarr Settings]]
**[[Readarr System]]
**[[Readarr Troubleshooting]]
**[[Readarr FAQ]]
**[[Readarr Tips and Tricks]]
**[[Readarr Contributing]]<section end=readarr_wiki_pages /><section begin=prowlarr_wiki_pages />
*[[Prowlarr]]
**[[Prowlarr Installation]]
**[[Prowlarr Settings]]
**[[Prowlarr System]]
**[[Prowlarr Troubleshooting]]
**[[Prowlarr FAQ]]
**[[Prowlarr Tips and Tricks]]
**[[Prowlarr Contributing]]<section end=prowlarr_wiki_pages />

Sonarr FAQ

2021-05-21T17:21:06Z

Bakerboy448: /* How are possible downloads compared? */

== How does Sonarr find episodes? ==
[[#how_does_Sonarr_find_episodes|anchor]] 

* Sonarr does ''not'' regularly search for episode files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted episodes/newly uploaded releases, then compares that with its list of episodes that are missing or need to be upgraded. Any matches are downloaded. This lets Sonarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a show, you'll need to set the correct path, profile and monitoring status then use the Start search for missing checkbox. If the show has had no episodes and hasn't been released yet, you don't need to initiate a search.
* Put another way, Sonarr will only find releases that are newly uploaded to your indexers. It will not actively try to find releases uploaded in the past.
* If you've already added the show, but now you want to search for it, you have a few choices. You can go to the show's page and use the search button, which will do a search and then automatically pick episode(s). You can search individual episodes or seasons automatically or manually. Or you can use the filters of <code>Missing</code> and <code>Cut-off Unmet</code>.
* If Sonarr has been offline for an extended period of time, Sonarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Sonarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed episodes.

== Why didn’t Sonarr grab an episode I was expecting? ==
[[#Why_didnt_Sonarr_grab_an_episode_i_was_expecting|anchor]] 

First, make sure you read and understand the section above called ''“How does Sonarr find episodes?”'' Second, make sure at least one of your indexers has the episode you were expecting to be grabbed.
# Click the ‘Manual Search’ icon next to the episode listing in Sonarr. Are there any results? If no, then either Sonarr is having trouble communicating with your indexers, or your indexers do not have the episode, or the episode is improperly named/categorized on the indexer.
# '''If there are results from step 1''', check next to them for red exclamation point icon. Hover over the icon to see why that release is not a candidate for automatic downloads. If every result has the icon, then no automatic download will occur.
# '''If there is at least one valid manual search result from step 2''', then an automatic download should have happened. If it didn’t, the most likely reason is a temporary communication problem preventing an RSS Sync from your indexer. It is recommended to have several indexers set up for best results.
# '''If there is no manual result from a show, but you can find it when you browse your indexer’s website''' - This is a common problem that is most frequently caused by having an insufficient number of indexers. Different indexers index different content, and not all shows on your indexer may be tagged properly, which would cause Sonarr’s search to fail. Having several indexers active is the best solution to this problem.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Sonarr/Sonarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs#L31-L40s can be found here].
'''''As of 3/26/2021 the logic is as follows'''''
# Quality
# Language
# Preferred Word Score
# Protocol
# Episode Count
# Episode Number
# Indexer Priority
# Seeds/Peers (If Torrent)
# Age (If Usenet)
# Size

== Preferred Words FAQs ==
[[#Preferred_Words_FAQs|anchor]] 

For the score of the on disk file:
The existing name of the file and the "scene name" of the release are evaluated for preferred words. The higher score of the two is taken.

How are preferred words included in renaming?

For Sonarr you can make use of the `{Preferred Words}` token in your renaming scheme. and also check mark `Include Preferred when Renaming` in the release profile.
take a look [https://trash-guides.info/Sonarr/V3/Sonarr-recommended-naming-scheme/ HERE] for a recommended naming scheme examples for Sonarr.

Using the tokens in your renaming scheme could help with download loop issues.

Preferred Words always upgrade a release even if the quality and/or language cutoff has been met.
== How does Sonarr handle scene numbering issues (American Dad!, etc)? ==
[[#how_does_sonarr_handle_scene_numbering_issues|anchor]] 

* '''How Sonarr handles scene numbering issues'''
** Sonarr relies on [http://thexem.de/ TheXEM], a community driven site that lets users create mappings of shows that the scene (the people that post the files) and TheTVDB (which typically follows the network’s numbering). There are a number of shows on there already, but it is easy to add another and typically the changes are accepted within a couple days (if they’re correct). TheXEM is used to correct differences in episode numbering (disagreement whether an episode is a special or not) as well as season number differences, such as episodes being released as S10E01, but TheTVDB listing that same episode as S2017E01.
* '''Problematic Shows'''
** This by no means is an all inclusive list of shows that have known issues with scene mapping however, these are the big ones that come to mind while writing this.
** Typical Issue: Scene numbering does not match TVDb numbering so Sonarr doesn't work. Well enter XEM which creates a map for Sonarr to look at.
*** Scene releases double episodes in a single file since that is how they air but TVDb marks each episode individually.
*** Scene uses a year for the season S2010 and TVDb uses S01.
** [http://thexem.de XEM] works in most cases and keeps it running smooth without you ever knowing. However as with most things, there will always be a ''black sheep'' and in this case there is a list of them.
** This is an incomplete list of the known shows and how/why they're problematic:
*** American Dad
*** Arrested Development
*** Mythbusters
*** Paw Patrol
**** Double episode files vs single episode TVDb but also not all episodes are doubles so the map can get added wrong pointing to which ones are singles vs doubles
*** Pawn Stars
*** Pokémon
**** On TheXem, [http://thexem.de/xem/show/4638 pokemon] is tracking * dubbed* episodes. So if you want subbed episodes, you may be out of luck. If certain release groups are following TVDB and not XEM mapping, please contact us on our discord and bring the release name and group name as exceptions can be added for groups who follow TVDB.
* '''Possible resolutions:'''
# TVDb adds alternate ordering to the API (Current status: They say v4 but don't count on it to work or be stable based on the history of v3)
# XEM adds a map to allow for alternate orders that sonarr can use (Current status: Unlikely)
# Sonarr allows for disabling of XEM maps when doing manual searches (Current status: Unlikely)
* '''Sonarr side effects:'''
** On top of the issues with the shows already, Sonarr also has some odd behavior so you may just need to overlook this as well. Example:
** American Dad is currently on S17 based on TVDb or S16 based on Scene at the time of this writing. So searching in sonarr for season 17 will '''only''' return S16 results because of the XEM map. If you have a tracker with S17 episodes (because they use P2P and not Scene), please contact us on our discord and bring the release name and group name as exceptions can be added for groups who follow TVDB.

== Why can’t Sonarr import episode files for series X? / Why can’t Sonarr find releases for series X? ==
[[#why_cant_sonarr_import_episode_files_for_series_x_why_cant_sonarr_find_releases_for_series_x|anchor]] 

Sonarr relies on being able to match titles, often the scene posts episodes using different titles, eg ''CSI: Crime Scene Investigation'' as just ''CSI'' so Sonarr can’t match the names without some help. Sonarr maintains a list of problematic series which lets us solve this issue. '''For anime, it will need to be added to [https://thexem.de thexem.de]''', for other series to request a new mapping see the steps below.

# Make sure it hasn’t already been requested. [https://docs.google.com/spreadsheet/ccc?key=0Atcf2VZ47O8tdGdQN1ZTbjFRanhFSTBlU0xhbzhuMGc#gid=0 Requested Mappings]
# Make a new request here: [https://docs.google.com/forms/d/15S6FKZf5dDXOThH4Gkp3QCNtS9Q-AmxIiOpEBJJxi-o/viewform Scene Mapping Request Form]

''Typically these are added within 1-2 days.''

''Again, do not request a mapping for Anime; use XEM for that.'' Further information can be found with some of the XEM folks that hangout in our [https://discord.gg/an9rnEdWs5 <nowiki>#XEM</nowiki> discord channel].

The series "Helt Perfekt" with TVDB ids of <code>343189</code> and <code>252077</code> is difficult to automate due to TVDB having the same name for both shows, violating TVDB's own rules. The first entry for the series gets the name. Any future entries for the series must have the year as part of the series name. However, a scene exception as been added to map releases (case sensitive mapping) Helt Perfekt releases containing <code>NORWEGIAN</code> -> <code>252077</code> and containing <code>SWEDISH</code> -> <code>343189</code>

== TVDB is updated why isn't Sonarr? ==
[[#tvdb_is_updated_why_is_not_sonarr|anchor]] 

TVDB has a 24 hour cache on their API. Skyhook has a much smaller few hour cache on top of that. Sonarr only runs the Refresh Series task every 12 hours. Thus it typically takes 24 to 48 hours for a TVDB update to make it into Sonarr.

If you know a TVDB update was made more than 48 hours ago, then please come discuss on our [https://discord.gg/M6BvZn5 Discord].
== I see that feature/bug X was fixed, why can’t I see it? ==
[[#i_see_that_feature_bug_x_was_fixed_why_cant_i_see_it|anchor]] 

Sonarr consists of two main branches of code, <code>main</code> and <code>develop</code>, <code>main</code>is released periodically, when the <code>develop</code> branch is stable and <code>develop</code> is for pre-release testing and people willing to live on the edge, if you want to help out testing or want more information on the two branches, please see: [[Sonarr_Settings#Updates|Release Branches]]. When a feature is marked as in <code>develop</code> it will only be available to users running the <code>develop</code> branch, once it has been move to live (in <code>main</code>) it is officially released.

== Episode Progress - How is it calculated? ==
[[#episode_progress_-_how_is_it_calculated|anchor]] 

There are two parts to the episode count, one being the number of episodes (Episode Count) and the other being the number of episodes with files (Episode File Count), each one uses slightly different logic to give you the overall progress for a series or season.

* Episode Count
** Episode has already aired AND is monitored OR
** Episode has a file
* Episode File Count
** Episode has a file

If a series has 10 episodes that have all aired and you don’t have any files for them you would have 0/10 episodes, if you unmonitored all the episodes in that series you would have 0/0 and if you got all the episodes for that series, regardless of if the episodes are monitored or not, you would have 10/10 episodes.

== How do I access Sonarr from another computer? ==
[[#how_do_I_access_sonarr_from_another_computer|anchor]] 

By default Sonarr doesn’t listen to requests from all systems (when not run as administrator), it will only listen on localhost, this is due to how the Web Server Sonarr uses integrates with Windows (this also applies for current alternatives). If Sonarr is run as an administrator it will correctly register itself with Windows as well as open the Firewall port so it can be accessed from other systems on your network. Running as admin only needs to happen once (if you change the port it will need to be re-run).

== Why doesn’t Sonarr automatically search for missing episodes? ==
[[#why_doesnt_sonarr_automatically_search_for_missing_episodes|anchor]] 

There are two times when we would want to have missing episodes searched for, when a new series with existing aired episodes is added and when Sonarr has been offline and unable to find episodes as it normally would. Endlessly searching for episodes that have aired that are missing is a waste of resources, both in terms of local processing power and on the indexers and in our experience catches users off guard, wasting bandwidth.

In v1 of Sonarr we had an opt in backlog search option, often people would turn it on and then get a bunch of old episodes and ask us why, we also had indexers ask why they saw an increase in API calls, which was due to the backlog searching.

In v2 we sat back and thought about it and realized the benefit is not really there, we could try to throttle the searching, but that just draws it out and still does the same thing; hammer the indexer with useless requests. If the episode wasn’t there the last time the search was performed, why would it be there now? It would be if it was reposted, but if it was reposted, the automatic process that gets new episodes would see it was posted and act on it.

== Why does Sonarr refresh series information so frequently? ==
[[#why_does_sonarr_refresh_series_information_so_frequently|anchor]] 

* Sonarr refreshes series and episode information in addition to rescanning the disk for files every 12 hours. This might seem aggressive, but is a very important process. The data refresh from our TVDB proxy is important, because new episode information is synced down, air dates, number of episodes, status (continuing/ended). Even shows that aren’t airing are being updated with new information.
* The disk scan is less important, but is used to check for new files that weren’t sorted by Sonarr and detect deleted files.
* The most time consuming portion is the information refresh (assuming reasonable disk access speed), larger shows take longer due to the number of episodes to process.

== Why is there a number next to Activity? ==
[[#why_is_there_a_number_next_to_activity|anchor]] 

* This number shows the count of episodes in your download client’s queue and the last 30 items in its history that have not yet been imported. If the number is blue it is operating normally and should import episodes when they complete. Yellow means there is a warning on one of the episodes. Red means there has been an error. In the case of yellow (warning) and red (error), you will need to look at the queue under Activity to see what the issue is (hover over the icon to get more details).
* You need to remove the item from your download client’s queue or history to remove them from Sonarr’s queue.

== I see log messages for shows I don’t have/don’t want ==
[[#i_see_log_messages_for_shows_i_don_t_have_dont_want|anchor]] 

* These messages are completely normal and come from the RSS feeds that Sonarr checks to see if there are episodes you do want, usually these only appear in debug/trace logging, but in the event of an problem processing an item you may see a warning or error. It is safe to ignore the warnings/errors as well since they are for shows you don’t want, in the event it is for a show you want, open up a support thread on the forums.

== Seeding torrents aren’t deleted automatically ==
[[#seeding_torrents_arent_deleted_automatically|anchor]] 

* When a torrent that is still seeding is imported, it is copied or hard linked (if enabled and ''possible'') so that the torrent client can continue seeding. In an ideal setup, the torrent download folder and the library folder will be on the same file system and ''look like it'' (Docker and network shares make this easy to get wrong), which makes hard links possible and minimizes wasted space.
* In addition, you can configure your seed time/ratio goals in Sonarr or your download client, setup your download client to ''pause'' or ''stop'' when they’re met and enable Remove under Completed and Failed Download Handler. That way, torrents that finish seeding will be removed from the download client by Sonarr.

== Why can’t I add a new series? ==
[[#why_cant_i_add_a_new_series|anchor]] 

* In the event that TheTVDB is unavailable Sonarr is unable to get search results and you will be unable to add any new series by searching. You may be able to add a new series by the TVDBID if you know what it is, the UI explains how to add it by an ID.
* Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDB ID that does not have an English title. If no English title exist for that series on TheTVDB it will need to be added (if available).
* The show must be a TV Series, and not a movie. It must also exist on TVDB. If it is on IMDB, TMDB, or anywhere else, but not on TVDB you cannot add the show.
* The series must exist on TVDB

== Why can’t I add a new series when I know the TVDB ID? ==
[[#why_cant_i_add_a_new_series_when_i_know_the_tvdb_id|anchor]] 

* Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDB ID that does not have an English title. If no English title exist for that series on TheTVDB it will need to be added (if available).

== Sonarr won't work on Big Sur ==
[[#sonarr_wont_work_on_big_sur|anchor]] 

Run <code>chmod +x /Applications/Sonarr.app/Contents/MacOS/Sonarr</code>

== My Custom Script stopped working after upgrading from v2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== What's the different Series Types? ==
[[#whats_the_different_series_types|anchor]] 
Most shows should be <code>Standard</code>. For daily shows which are typically released with a date, <code>Daily</code> should be used. Finally, there is anime where using <code>Anime</code> is ''usually'' right, but sometimes <code>Standard</code> can work better, so try the ''other'' one if you’re having issues.

Please note that if the series type is set to anime and none of your enabled indexers have any anime categories configured then it effectively skips the indexer and may appear that it is not searching.

=== Show Type Examples ===
Below are some example release names for each show type. The specific differentiating piece is noted in bold.

'''Daily'''
* Some.Daily.Show.'''2021.03.04'''.1080p.HDTV.x264-DARKSPORT
* A.Daily.Show.with.Some.Guy.'''2021.03.03'''.1080p.CC.WEB-DL.AAC2.0.x264-null
* DailyShow.'''2021.03.08'''.720p.HDTV.x264-NTb
'''Standard'''
* The.Show.'''S20E03'''.Episode.Title.Part.3.1080p.HULU.WEB-DL.DDP5.1.H.264-NTb
* Another.Show.'''S03E08'''.1080p.WEB.H264-GGEZ
* GreatShow.'''S17E02'''.1080p.HDTV.x264-DARKFLiX
'''Anime'''
* Anime.Origins.'''E04'''.File.4_.Monkey.WEB-DL.H.264.1080p.AAC2.0.AC3.5.1.Srt.EngCC-Pikanet128.1272903A
* [Coalgirls] Human X Monkey '''148''' (1920x1080 Blu-ray FLAC) [63B8AC67]
* [KaiDubs] Series x Title (2011) - '''142''' [1080p] [English Dub] [CC] [AS-DL] [A24AB2E5]

== How can I rename my series folders? ==
[[#how_can_i_rename_my_series_folders|anchor]] 
# Series
# Mass Editor
# Select what series need their folder renamed
# Change Root Folder to the same Root Folder that the series currently exist in
# Select "Yes move files"

{{FAQ|ARRNAME=Sonarr|ARRDISCORD=https://discord.gg/M6BvZn5|ARRPORT=8989}}

Radarr FAQ

2021-05-21T17:20:54Z

Bakerboy448: /* How are possible downloads compared? */

== How does Radarr work? ==
[[#how_does_radarr_work|anchor]] 
[[#How_does_Radarr_work|alt-anchor]] 
* Radarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Radarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Radarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Radarr's Release-Push API endpoint along with an IRC announce channel to push releases to Radarr for processing which can happen in near real time and with less overhead on the indexer and Radarr as Radarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== How does Radarr find movies? ==
[[#how_does_radarr_find_movies|anchor]] 
* Radarr does ''not'' regularly search for movie files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted movies, then compares that with its list of movies that are missing or need to be upgraded. Any matches are downloaded. This lets Radarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a movie, you'll need to set the correct path, profile and monitoring status then use the Start search for missing movie checkbox. If the movie hasn't been released yet, you don't need to initiate a search.
* Put another way, Radarr will only find movies that are newly uploaded to your indexers. It will not actively try to find movies you want that were uploaded in the past.
* If you've already added the movie, but now you want to search for it, you have a few choices. You can go to the movie's page and use the search button, which will do a search and then automatically pick one. You can use the Search tab and see ''all'' the results, hand picking the one you want. Or you can use the filters of <code>Missing</code>, <code>Wanted</code>, or <code>Cut-off Unmet</code>.
* If Radarr has been offline for an extended period of time, Radarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Radarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed movies.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Radarr/Radarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs can be found here].
'''''As of 1/19/2021 the logic is as follows'''''
# Quality
# Custom Format Score
# Protocol
# Indexer Priority
# Indexer Flags
# Seeds/Peers (If Torrent)
# Age (If Usenet)
# Size

== What are Lists and what can they do for me? ==
[[#what_are_lists_and_what_can_they_do_for_me|anchor]] 
* Lists are a part of Radarr that allow you to follow a given list creator.
* Let's say that you follow a given list creator on Trakt/TMDb and really like their Marvel Cinematic Universe film section and want to watch every movie on their list. You look in your Radarr and realize that you don't have those movies. Well instead of searching one by one and adding those lists and then searching your indexers for those movies. You can do this all at once with a List. The Lists can be set to import all the movies on that curators list as well as be set to automatically assign a quality profile, automatically add, and automatically monitor that movie.
* '''CAUTION:''' If lists are done improperly they will absolutely wreck your library with a bunch of trash you have no intention of watching. So make sure of what you're importing before you click save.
* ie. physically look at the list before you even go to Radarr.

== With the release of Radarr V3, what release should I download? ==
[[#with_the_release_of_radarr_v3_what_release_should_i_download|anchor]] 
Please see better information [[Radarr FAQ#How do I update Radarr?|here]]

== Why did the GUI / UI Change? Can it be changed back? ==
[[#why_did_the_gui_ui_change|anchor]] 
* Radarr is a fork of [[Sonarr]] which has the new UI.
* No it cannot be changed back. No it will not be changed back.
* You may, however, check out [https://github.com/gilbN/theme.park Theme Park]


== Where did Wanted and Cut-off Unmet go? ==
[[#where_did_wanted_and_cutoff_unmet_go|anchor]] 
* Movie Index (AKA 'Movies') -> Filter (top right corner) -> <code>Wanted</code> and <code>Cut-off Unmet</code>
[[File:radarr-where-did-wanted-and-cutoff-unmet-go.png|thumb|none|750px|alt=This is where wanted and Cut-off Unmet went|This is where wanted and Cut-off Unmet went]]

== Why can't I add a new movie to Radarr? ==
[[#why_cant_i_add_a_new_movie_to_radarr|anchor]] 
* Radarr uses [http://themoviedb.org The Movie Database (TMDb)] for movie information and images like fanart, banners and backgrounds. Generally, there are a few reasons why you may not be able to add a movie:
* TMDb doesn't like special characters to be used when searching for movies through the API (which Radarr uses), so try searching a translated name, and/or without special characters.
* You can also add by TMDb ID or, if TMDb has it, the IMDb ID
* The movie hasn't been added to TMDb yet, follow their [https://www.themoviedb.org/bible/new_content#59f7933c9251413e93000006 guide] to get it added.

== Can all my movie files be stored in one folder? ==
[[#can_all_my_movie_files_be_stored_in_one_folder|anchor]] 
* Not yet and the reason is that Radarr is a fork of [[Sonarr]], where every show has a folder. This limitation is a known pain point for many users and will maybe come in a future version.
:If you're looking to moving all your movies from one folder to individual folders check [[Radarr Tips and Tricks#Create a Folder for Each Movie|here]]

== Can I put all my movies in my library into one folder ==
[[Radarr FAQ#Can I put all my movies in my library into one folder|anchor]]

We get asked this a lot. There are no plans to support <code>\data\Movies\Movie1.mkv</code>, <code>\data\Movies\Movie2.mkv</code>, etc.

The [https://github.com/Radarr/Radarr/issues/153 Custom Folder GitHub Issue] technically covers this request, but it is no guarantee that all movie files in one folder will be implemented at that time.

A slight hack-ish solution is noted below. Please note that you mustn't trigger a rescan or it will show as missing and regardless the movie will never be upgraded.

* Use a Custom Script
** the script should be triggered on import
** it should be designed to move the file whenever you want it
** it then needs to call the Radarr API and change the movie to unmonitored.

== How can I rename my movie folders? ==
[[#how_can_i_rename_my_movie_folders|anchor]] 
# Movies
# Movie Editor
# Select what movies need their folder renamed
# Change Root Folder to the same Root Folder that the movies currently exist in
# Select "Yes move files"

== Movie File and Folder Naming ==
[[#movie_file_and_folder_naming|anchor]] 
* Currently, Radarr requires that each movie be in a folder with the format containing at minimum <code>Movie Title (Year)/</code>, optionally <code>_</code> or <code>.</code> are valid separators. To facilitate correct quality and resolution identification during import, a file name like <code>Movie Title (Year) [Quality-Resolution].ext</code> is best, again <code>_</code> or <code>.</code> are valid separators too.
* A useful tool for making these changes to your collection is [http://www.filebot.net/#download filebot] which has paid version in both the Apple and Windows stores, but can be found for free on their legacy [https://sourceforge.net/projects/filebot/files/latest/download SourceForge] site. It has both a GUI and CLI, so you can use whatever you’re comfortable with. For the above example, <code>{ny}</code> expands to <code>Name (Year)</code> and <code>{vf}</code> gives the resolution like <code>1080p</code>. There is nothing to infer quality, so you can fake it using <code>{ny}/{ny} [{dim[0] >= 1280 ? 'Bluray' : 'DVD'}-{vf}]</code> which will name anything lower than 720p to <code>[DVD-572p]</code> and greater or equal to 720p like <code>[Bluray-1080p]</code>.
See [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] for more details.

== Movie Folders Named Incorrectly ==
[[#movie_folders_named_incorrectly|anchor]] 
* Even if your movies are in folders already, the folders may not be named correctly. The folder name should be <code>Movie Title (Year)</code>, having the title and year in the folder’s name is critical right now.
* Examples that will work well:
** <code>/mnt/Movies/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** <code>/mnt/Kid Movies/Frozen (2013)/Frozen (2013) [Bluray-1080p].mkv</code>
* Examples that will work, but will require manual management:
** By letters: <code>/mnt/Movies/A-D/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By rating: <code>/mnt/Movies/R/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By genre: <code>/mnt/Movies/Crime, Drama, Sci-Fi/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** These examples will require manual management when the movie is added. Each of the examples will have many root directories, like <code>A-D</code> and <code>E-G</code> in the first letter example, <code>R</code> and <code>PG-13</code> in the rating example and you can guess at the variety of genre folders. When adding a new movie, the correct base folder will need to be selected for this format to work.
* Examples that won’t work:
** Single folder: <code>/mnt/Kid Movies/Frozen (2013) [Bluray-1080p].mkv</code>
*** At this time, movies simply have to be in a folder named after the movie. There is no way around this until development work is done to add this feature.
**'''Movie''' Folder Naming Formats from v0.2 that include '''File''' properties in the '''movie folder''' name such as <code>{Movie.Title}.{Release Year}.{Quality.Full}-{MediaInfo.Simple}{`Release.Group}</code> will not work in v3.
*** Folders are related to the movie and independent of the file. Additionally, this will break with the planned multiple files per movie support.
*** The other reason it was removed was it caused frequent confusion, database corruption, and generally was only half baked.
* The [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.

== How can I mass delete movies from the wanted list? ==
[[#how_can_i_mass_delete_movies_from_the_wanted_list|anchor]] 
* Use Movie Editor -> Select movies you want to delete -> Delete

== Why doesn't Radarr work behind a reverse proxy ==
[[#why_doesnt_radarr_work_behind_an_nginx_reverse_proxy|anchor]] 
* Starting with V3 Radarr has switched to .NET Core and a new webserver. In order for SignalR to work, the UI buttons to work, database changes to take, and other items. It requires the following addition to the location block for Radarr:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

* Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
* [https://github.com/aspnet/AspNetCore/issues/17081 See this ASP.NET Core issue]
* If you are using a CDN like Cloudflare ensure websockets are enabled to allow websocket connections.

== How do I update Radarr? ==
[[#how_do_i_update_my_radarr|anchor]] 
# Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
# Under the Development section change the branch name to <code>master</code> or <code>develop</code>
# Save
''This will not install the bits from that branch immediately, it will happen during the next update.''

* master (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. This is currently v3. This version will receive updates approximately monthly. On GitHub, this is the <code>master</code> branch.
* develop (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first. This is currently v3. This version will receive updates either weekly or biweekly depending on development. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is a snapshot of the <code>develop</code> branch at a point in time.
* nightly (Nightly): The bleeding edge. Released as soon as code is committed and passed all automated tests. '''''Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.''''' This is currently v3. This version is updated immediately. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is the <code>develop</code> branch.

* Note: If your install is through Docker append <code>:release</code>, <code>:latest</code>, or <code>:testing</code> to the end of your container tag depending on who makes your builds.
{| class="wikitable"
|+
!Current Versions
!master
!develop
!nightly
|-
|
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Frelease%2FVERSION.json Current Master/Latest]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Ftesting%2FVERSION.json Current Develop/Beta]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Fnightly%2FVERSION.json Current Nightly/Alpha]
|}
<center>
{| class="wikitable"
|-
! Release Channel Type !! Branch: master (stable) (v3.2) !! Branch: develop (beta) (v3.2) !! Branch: nightly (unstable) (v3.2)
|-
|[https://hub.docker.com/r/hotio/radarr hotio]||<code>hotio/radarr:release</code>||<code>hotio/radarr:testing</code>|| If you have to ask, you should not be on it.
|-
|[https://hub.docker.com/r/linuxserver/radarr LinuxServer.io]||<code>linuxserver/radarr:latest</code>||<code>linuxserver/radarr:develop</code>|| If you have to ask, you should not be on it.
|}
</center>

=== Installing a newer version ===
If Native:
# Go to System and then the Updates tab
# Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
If Docker:
# Repull your tag and update your container

== Can I switch from nightly back to develop? ==
[[#can_i_switch_from_nightly_back_to_develop|anchor]] 

[[Radarr_FAQ#Can I switch between branches?|See this related question]]

== Can I switch between branches? ==
[[#can_i_switch_between_branches|anchor]] 
* You can (almost) always increase your risk.
* <code>master</code> can go to <code>develop</code> or <code>nightly</code>
* <code>develop</code> can go to <code>nightly</code>
* Check with the development team to see if you can switch from <code>nightly</code> to <code>master</code>; <code>nightly</code> to <code>develop</code>; or <code>develop</code> to <code>master</code> for your given build.
* Failure to follow these instructions may result in your Radarr becoming unusable or throwing errors. You have been warned.
** The most common error is something like <code>Error parsing column 45 (Language=31 - Int64)</code> or other similar database errors around missing columns or tables.

* '''May 19 2021 Update'''
** <code>3.2.2</code> has been released as master/stable
** For those on nightly and are still on <code>3.2.2.5053</code> or lower you can safely downgrade to master or develop.
*** Develop can also downgrade to master as well.
*** Please note that if you're on nightly there will be no update to install given your build is higher than the current develop/master.

== How does radarr handle foreign movies or foreign titles? ==
[[#how_does_radarr_handle_foreign_movies_or_foreign_titles|anchor]] 
* Radarr uses both Alt Titles and Translations for parsing and searching. Search will use the Original Title, English Title, and Translated Title from whatever languages you have preferred (in profile and CFs). Parsing should look for a match in all Translations and Alt Titles.

* To get a movie in a foreign language set your Profile Language to Original (Movie's Original Language), a specific language for that profile, or any and use custom formats to determine which language to grab.
* Note that this does not include any indexer languages specified as multi.

== How does radarr handle "multi" in names? ==
[[#how_does_radarr_handle_multi_in_names|anchor]] 
* Radarr by default assumes multi is english and french unless specified in your indexer's advanced settings in Radarr.

* Note that multi definitions only help for release parsing and not for foreign titles or movies searches.

== Help, Movie Added, But Not Searched ==
[[#help_movie_added_but_not_searched|anchor]] 

* Neither Radarr nor Sonarr ''actively'' search for missing movies automatically. Instead, a periodic query of new posts is made to all indexers configured for RSS. When a wanted or cutoff unmet movie shows up in that list, it gets downloaded. This means that until a movie is posted (or reposted), it won’t get downloaded.
* If you’re adding a movie that you want now, the best option is to check the “Start search for missing movie” box, to the left of the ''Add Movie'' ('''1''') button. You can also go to the page for a movie you’ve added and click the magnifying glass “Search” ('''2''') button or use the Wanted view to search for Missing or Cutoff Unmet movies.

[[File:start search for missing movie.png|thumb|none|750px|alt=Add and Search for movie|Add and Search for movie]]
[[File:Search selected movie.png||thumb|none|750px|altt=Search selected movie|Search selected movie]]

== Root path for movies imported from lists becomes “C:” or other weird paths ==
[[#root_path_for_movies_imported_from_lists_become_c_or_other_weird_paths|anchor]] 
* Sometimes you can get a problem that movies that are imported from your lists, gets imported with the root path set to “C:” or other weird paths.

* This is a known issue for when the root path is either not setup during the creation of the list, or if the root path has been deleted after the list was created. Note that this problem can still occur even if the list is '''edited''' and the correct root path is set.

* Use the Movie Editor to fix paths of existing movies.

== Movie Imported, But Source File And Torrent Not Deleted ==
[[#movie_imported_but_source_file_and_torrent_not_deleted|anchor]] 
* Check if you have Completed Download Handling - Remove turned on. (This does not work if you are using rtorrent.)

[[File:Remove turned on.png|thumb|none|750px|alt=Settings|Settings > Download Clients]]

* If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.

== My Custom Script stopped working after upgrading from v0.2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v0.2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== I am using a Pi and Raspbian and Radarr will not launch ==
[[#i_am_using_a_pi_and_raspbian_and_radarr_will_not_launch|anchor]] Raspbian has a version of libseccomp2 that is too old to support running a docker container based on Ubuntu 20.04, which both hotio and LinuxServer use as their base for v3. You either need to use <code>--privileged</code>, update libseccomp2 from Ubuntu or get a better OS (We recommend Ubuntu 20.04 arm64)

'''Possible Solution:'''

Managed to fix the issue by installing the backport from debian repo. Generally not recommended to use backport in blanket upgrade mode. Installation of a single package may be ok but may also cause issues. So got to understand what you are doing.

Steps to fix:

First ensure you are running Raspbian buster e.g using <code>lsb_release -a</code>

Distributor ID: Raspbian

Description: Raspbian GNU/Linux 10 (buster)

Release: 10

Codename: buster

''If you are using buster:''
<code>Add the line `deb <nowiki>http://deb.debian.org/debian</nowiki> buster-backports` main to `/etc/apt/sources.list`
Run apt-get update
apt-get -t buster-backports install libseccomp2</code>

== Why are lists sync times so long and can I change it? ==
[[#why_are_lists_sync_times_so_long_and_can_i_change_it|anchor]]

Lists never were nor are intended to be <code>add it now</code> they are <code>hey i want this, add it eventually</code> tools

You can trigger a list refresh manually, script it and trigger it via the API, add the movies to radarr, use Ombi, or any similar app that adds them right away

This change was due to not have our server get killed by people updating lists every 10 minutes.

== Why doesn't Radarr work behind an nginx reverse proxy ==

[[Radarr_FAQ#Why_doesn.27t_Radarr_work_behind_a_reverse_proxy|See this section]]

== Can I disable the refresh movies task ==
[[#can_I_disable_the_refresh_movies_task|anchor]]

No, nor should you through any SQL hackery. The refresh movies task queries the upstream Servarr proxy and checks to see if the metadata for each movie (ids, cast, summary, rating, translations, alt titles, etc.) has updated compared to what is currently in Radarr. If necessary, it will then update the applicable movies.

A common complaint is the Refresh task causes heavy I/O usage. This is partly due to the setting "Analyze video files" which is advised to be enabled if you use tdarr or otherwise externally modify your files. If you don't you can safely disable "Analyze video files" to reduce some I/O. The other setting is "Rescan Movie Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to <code>Manual</code>. Do not change this to <code>Never</code> unless all changes to your library (new movies, upgrades, deletions etc) are done through Radarr. If you delete movie files manually or via Plex or another third party program, do not set this to <code>Never</code>.

{{FAQ|ARRNAME=Radarr|ARRDISCORD=https://radarr.video/discord|ARRPORT=7878}}

Radarr FAQ

2021-05-20T00:01:31Z

Bakerboy448:

== How does Radarr work? ==
[[#how_does_radarr_work|anchor]] 
[[#How_does_Radarr_work|alt-anchor]] 
* Radarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Radarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Radarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Radarr's Release-Push API endpoint along with an IRC announce channel to push releases to Radarr for processing which can happen in near real time and with less overhead on the indexer and Radarr as Radarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== How does Radarr find movies? ==
[[#how_does_radarr_find_movies|anchor]] 
* Radarr does ''not'' regularly search for movie files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted movies, then compares that with its list of movies that are missing or need to be upgraded. Any matches are downloaded. This lets Radarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a movie, you'll need to set the correct path, profile and monitoring status then use the Start search for missing movie checkbox. If the movie hasn't been released yet, you don't need to initiate a search.
* Put another way, Radarr will only find movies that are newly uploaded to your indexers. It will not actively try to find movies you want that were uploaded in the past.
* If you've already added the movie, but now you want to search for it, you have a few choices. You can go to the movie's page and use the search button, which will do a search and then automatically pick one. You can use the Search tab and see ''all'' the results, hand picking the one you want. Or you can use the filters of <code>Missing</code>, <code>Wanted</code>, or <code>Cut-off Unmet</code>.
* If Radarr has been offline for an extended period of time, Radarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Radarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed movies.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Radarr/Radarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs can be found here].
'''''As of 1/19/2021 the logic is as follows'''''
# Quality
# Custom Format Score
# Protocol
# Indexer Priority
# Indexer Flags
# Peers (If Torrent)
# Age (If Usenet)
# Size

== What are Lists and what can they do for me? ==
[[#what_are_lists_and_what_can_they_do_for_me|anchor]] 
* Lists are a part of Radarr that allow you to follow a given list creator.
* Let's say that you follow a given list creator on Trakt/TMDb and really like their Marvel Cinematic Universe film section and want to watch every movie on their list. You look in your Radarr and realize that you don't have those movies. Well instead of searching one by one and adding those lists and then searching your indexers for those movies. You can do this all at once with a List. The Lists can be set to import all the movies on that curators list as well as be set to automatically assign a quality profile, automatically add, and automatically monitor that movie.
* '''CAUTION:''' If lists are done improperly they will absolutely wreck your library with a bunch of trash you have no intention of watching. So make sure of what you're importing before you click save.
* ie. physically look at the list before you even go to Radarr.

== With the release of Radarr V3, what release should I download? ==
[[#with_the_release_of_radarr_v3_what_release_should_i_download|anchor]] 
Please see better information [[Radarr FAQ#How do I update Radarr?|here]]

== Why did the GUI / UI Change? Can it be changed back? ==
[[#why_did_the_gui_ui_change|anchor]] 
* Radarr is a fork of [[Sonarr]] which has the new UI.
* No it cannot be changed back. No it will not be changed back.
* You may, however, check out [https://github.com/gilbN/theme.park Theme Park]


== Where did Wanted and Cut-off Unmet go? ==
[[#where_did_wanted_and_cutoff_unmet_go|anchor]] 
* Movie Index (AKA 'Movies') -> Filter (top right corner) -> <code>Wanted</code> and <code>Cut-off Unmet</code>
[[File:radarr-where-did-wanted-and-cutoff-unmet-go.png|thumb|none|750px|alt=This is where wanted and Cut-off Unmet went|This is where wanted and Cut-off Unmet went]]

== Why can't I add a new movie to Radarr? ==
[[#why_cant_i_add_a_new_movie_to_radarr|anchor]] 
* Radarr uses [http://themoviedb.org The Movie Database (TMDb)] for movie information and images like fanart, banners and backgrounds. Generally, there are a few reasons why you may not be able to add a movie:
* TMDb doesn't like special characters to be used when searching for movies through the API (which Radarr uses), so try searching a translated name, and/or without special characters.
* You can also add by TMDb ID or, if TMDb has it, the IMDb ID
* The movie hasn't been added to TMDb yet, follow their [https://www.themoviedb.org/bible/new_content#59f7933c9251413e93000006 guide] to get it added.

== Can all my movie files be stored in one folder? ==
[[#can_all_my_movie_files_be_stored_in_one_folder|anchor]] 
* Not yet and the reason is that Radarr is a fork of [[Sonarr]], where every show has a folder. This limitation is a known pain point for many users and will maybe come in a future version.
:If you're looking to moving all your movies from one folder to individual folders check [[Radarr Tips and Tricks#Create a Folder for Each Movie|here]]

== Can I put all my movies in my library into one folder ==
[[Radarr FAQ#Can I put all my movies in my library into one folder|anchor]]

We get asked this a lot. There are no plans to support <code>\data\Movies\Movie1.mkv</code>, <code>\data\Movies\Movie2.mkv</code>, etc.

The [https://github.com/Radarr/Radarr/issues/153 Custom Folder GitHub Issue] technically covers this request, but it is no guarantee that all movie files in one folder will be implemented at that time.

A slight hack-ish solution is noted below. Please note that you mustn't trigger a rescan or it will show as missing and regardless the movie will never be upgraded.

* Use a Custom Script
** the script should be triggered on import
** it should be designed to move the file whenever you want it
** it then needs to call the Radarr API and change the movie to unmonitored.

== How can I rename my movie folders? ==
[[#how_can_i_rename_my_movie_folders|anchor]] 
# Movies
# Movie Editor
# Select what movies need their folder renamed
# Change Root Folder to the same Root Folder that the movies currently exist in
# Select "Yes move files"

== Movie File and Folder Naming ==
[[#movie_file_and_folder_naming|anchor]] 
* Currently, Radarr requires that each movie be in a folder with the format containing at minimum <code>Movie Title (Year)/</code>, optionally <code>_</code> or <code>.</code> are valid separators. To facilitate correct quality and resolution identification during import, a file name like <code>Movie Title (Year) [Quality-Resolution].ext</code> is best, again <code>_</code> or <code>.</code> are valid separators too.
* A useful tool for making these changes to your collection is [http://www.filebot.net/#download filebot] which has paid version in both the Apple and Windows stores, but can be found for free on their legacy [https://sourceforge.net/projects/filebot/files/latest/download SourceForge] site. It has both a GUI and CLI, so you can use whatever you’re comfortable with. For the above example, <code>{ny}</code> expands to <code>Name (Year)</code> and <code>{vf}</code> gives the resolution like <code>1080p</code>. There is nothing to infer quality, so you can fake it using <code>{ny}/{ny} [{dim[0] >= 1280 ? 'Bluray' : 'DVD'}-{vf}]</code> which will name anything lower than 720p to <code>[DVD-572p]</code> and greater or equal to 720p like <code>[Bluray-1080p]</code>.
See [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] for more details.

== Movie Folders Named Incorrectly ==
[[#movie_folders_named_incorrectly|anchor]] 
* Even if your movies are in folders already, the folders may not be named correctly. The folder name should be <code>Movie Title (Year)</code>, having the title and year in the folder’s name is critical right now.
* Examples that will work well:
** <code>/mnt/Movies/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** <code>/mnt/Kid Movies/Frozen (2013)/Frozen (2013) [Bluray-1080p].mkv</code>
* Examples that will work, but will require manual management:
** By letters: <code>/mnt/Movies/A-D/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By rating: <code>/mnt/Movies/R/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By genre: <code>/mnt/Movies/Crime, Drama, Sci-Fi/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** These examples will require manual management when the movie is added. Each of the examples will have many root directories, like <code>A-D</code> and <code>E-G</code> in the first letter example, <code>R</code> and <code>PG-13</code> in the rating example and you can guess at the variety of genre folders. When adding a new movie, the correct base folder will need to be selected for this format to work.
* Examples that won’t work:
** Single folder: <code>/mnt/Kid Movies/Frozen (2013) [Bluray-1080p].mkv</code>
*** At this time, movies simply have to be in a folder named after the movie. There is no way around this until development work is done to add this feature.
**'''Movie''' Folder Naming Formats from v0.2 that include '''File''' properties in the '''movie folder''' name such as <code>{Movie.Title}.{Release Year}.{Quality.Full}-{MediaInfo.Simple}{`Release.Group}</code> will not work in v3.
*** Folders are related to the movie and independent of the file. Additionally, this will break with the planned multiple files per movie support.
*** The other reason it was removed was it caused frequent confusion, database corruption, and generally was only half baked.
* The [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.

== How can I mass delete movies from the wanted list? ==
[[#how_can_i_mass_delete_movies_from_the_wanted_list|anchor]] 
* Use Movie Editor -> Select movies you want to delete -> Delete

== Why doesn't Radarr work behind a reverse proxy ==
[[#why_doesnt_radarr_work_behind_an_nginx_reverse_proxy|anchor]] 
* Starting with V3 Radarr has switched to .NET Core and a new webserver. In order for SignalR to work, the UI buttons to work, database changes to take, and other items. It requires the following addition to the location block for Radarr:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

* Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
* [https://github.com/aspnet/AspNetCore/issues/17081 See this ASP.NET Core issue]
* If you are using a CDN like Cloudflare ensure websockets are enabled to allow websocket connections.

== How do I update Radarr? ==
[[#how_do_i_update_my_radarr|anchor]] 
# Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
# Under the Development section change the branch name to <code>master</code> or <code>develop</code>
# Save
''This will not install the bits from that branch immediately, it will happen during the next update.''

* master (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. This is currently v3. This version will receive updates approximately monthly. On GitHub, this is the <code>master</code> branch.
* develop (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first. This is currently v3. This version will receive updates either weekly or biweekly depending on development. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is a snapshot of the <code>develop</code> branch at a point in time.
* nightly (Nightly): The bleeding edge. Released as soon as code is committed and passed all automated tests. '''''Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.''''' This is currently v3. This version is updated immediately. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is the <code>develop</code> branch.

* Note: If your install is through Docker append <code>:release</code>, <code>:latest</code>, or <code>:testing</code> to the end of your container tag depending on who makes your builds.
{| class="wikitable"
|+
!Current Versions
!master
!develop
!nightly
|-
|
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Frelease%2FVERSION.json Current Master/Latest]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Ftesting%2FVERSION.json Current Develop/Beta]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Fnightly%2FVERSION.json Current Nightly/Alpha]
|}
<center>
{| class="wikitable"
|-
! Release Channel Type !! Branch: master (stable) (v3.2) !! Branch: develop (beta) (v3.2) !! Branch: nightly (unstable) (v3.2)
|-
|[https://hub.docker.com/r/hotio/radarr hotio]||<code>hotio/radarr:release</code>||<code>hotio/radarr:testing</code>|| If you have to ask, you should not be on it.
|-
|[https://hub.docker.com/r/linuxserver/radarr LinuxServer.io]||<code>linuxserver/radarr:latest</code>||<code>linuxserver/radarr:develop</code>|| If you have to ask, you should not be on it.
|}
</center>

=== Installing a newer version ===
If Native:
# Go to System and then the Updates tab
# Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
If Docker:
# Repull your tag and update your container

== Can I switch from nightly back to develop? ==
[[#can_i_switch_from_nightly_back_to_develop|anchor]] 

[[Radarr_FAQ#Can I switch between branches?|See this related question]]

== Can I switch between branches? ==
[[#can_i_switch_between_branches|anchor]] 
* You can (almost) always increase your risk.
* <code>master</code> can go to <code>develop</code> or <code>nightly</code>
* <code>develop</code> can go to <code>nightly</code>
* Check with the development team to see if you can switch from <code>nightly</code> to <code>master</code>; <code>nightly</code> to <code>develop</code>; or <code>develop</code> to <code>master</code> for your given build.
* Failure to follow these instructions may result in your Radarr becoming unusable or throwing errors. You have been warned.
** The most common error is something like <code>Error parsing column 45 (Language=31 - Int64)</code> or other similar database errors around missing columns or tables.

* '''May 19 2021 Update'''
** <code>3.2.2</code> has been released as master/stable
** For those on nightly and are still on <code>3.2.2.5053</code> or lower you can safely downgrade to master or develop.
*** Develop can also downgrade to master as well.
*** Please note that if you're on nightly there will be no update to install given your build is higher than the current develop/master.

== How does radarr handle foreign movies or foreign titles? ==
[[#how_does_radarr_handle_foreign_movies_or_foreign_titles|anchor]] 
* Radarr uses both Alt Titles and Translations for parsing and searching. Search will use the Original Title, English Title, and Translated Title from whatever languages you have preferred (in profile and CFs). Parsing should look for a match in all Translations and Alt Titles.

* To get a movie in a foreign language set your Profile Language to Original (Movie's Original Language), a specific language for that profile, or any and use custom formats to determine which language to grab.
* Note that this does not include any indexer languages specified as multi.

== How does radarr handle "multi" in names? ==
[[#how_does_radarr_handle_multi_in_names|anchor]] 
* Radarr by default assumes multi is english and french unless specified in your indexer's advanced settings in Radarr.

* Note that multi definitions only help for release parsing and not for foreign titles or movies searches.

== Help, Movie Added, But Not Searched ==
[[#help_movie_added_but_not_searched|anchor]] 

* Neither Radarr nor Sonarr ''actively'' search for missing movies automatically. Instead, a periodic query of new posts is made to all indexers configured for RSS. When a wanted or cutoff unmet movie shows up in that list, it gets downloaded. This means that until a movie is posted (or reposted), it won’t get downloaded.
* If you’re adding a movie that you want now, the best option is to check the “Start search for missing movie” box, to the left of the ''Add Movie'' ('''1''') button. You can also go to the page for a movie you’ve added and click the magnifying glass “Search” ('''2''') button or use the Wanted view to search for Missing or Cutoff Unmet movies.

[[File:start search for missing movie.png|thumb|none|750px|alt=Add and Search for movie|Add and Search for movie]]
[[File:Search selected movie.png||thumb|none|750px|altt=Search selected movie|Search selected movie]]

== Root path for movies imported from lists becomes “C:” or other weird paths ==
[[#root_path_for_movies_imported_from_lists_become_c_or_other_weird_paths|anchor]] 
* Sometimes you can get a problem that movies that are imported from your lists, gets imported with the root path set to “C:” or other weird paths.

* This is a known issue for when the root path is either not setup during the creation of the list, or if the root path has been deleted after the list was created. Note that this problem can still occur even if the list is '''edited''' and the correct root path is set.

* Use the Movie Editor to fix paths of existing movies.

== Movie Imported, But Source File And Torrent Not Deleted ==
[[#movie_imported_but_source_file_and_torrent_not_deleted|anchor]] 
* Check if you have Completed Download Handling - Remove turned on. (This does not work if you are using rtorrent.)

[[File:Remove turned on.png|thumb|none|750px|alt=Settings|Settings > Download Clients]]

* If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.

== My Custom Script stopped working after upgrading from v0.2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v0.2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== I am using a Pi and Raspbian and Radarr will not launch ==
[[#i_am_using_a_pi_and_raspbian_and_radarr_will_not_launch|anchor]] Raspbian has a version of libseccomp2 that is too old to support running a docker container based on Ubuntu 20.04, which both hotio and LinuxServer use as their base for v3. You either need to use <code>--privileged</code>, update libseccomp2 from Ubuntu or get a better OS (We recommend Ubuntu 20.04 arm64)

'''Possible Solution:'''

Managed to fix the issue by installing the backport from debian repo. Generally not recommended to use backport in blanket upgrade mode. Installation of a single package may be ok but may also cause issues. So got to understand what you are doing.

Steps to fix:

First ensure you are running Raspbian buster e.g using <code>lsb_release -a</code>

Distributor ID: Raspbian

Description: Raspbian GNU/Linux 10 (buster)

Release: 10

Codename: buster

''If you are using buster:''
<code>Add the line `deb <nowiki>http://deb.debian.org/debian</nowiki> buster-backports` main to `/etc/apt/sources.list`
Run apt-get update
apt-get -t buster-backports install libseccomp2</code>

== Why are lists sync times so long and can I change it? ==
[[#why_are_lists_sync_times_so_long_and_can_i_change_it|anchor]]

Lists never were nor are intended to be <code>add it now</code> they are <code>hey i want this, add it eventually</code> tools

You can trigger a list refresh manually, script it and trigger it via the API, add the movies to radarr, use Ombi, or any similar app that adds them right away

This change was due to not have our server get killed by people updating lists every 10 minutes.

== Why doesn't Radarr work behind an nginx reverse proxy ==

[[Radarr_FAQ#Why_doesn.27t_Radarr_work_behind_a_reverse_proxy|See this section]]

== Can I disable the refresh movies task ==
[[#can_I_disable_the_refresh_movies_task|anchor]]

No, nor should you through any SQL hackery. The refresh movies task queries the upstream Servarr proxy and checks to see if the metadata for each movie (ids, cast, summary, rating, translations, alt titles, etc.) has updated compared to what is currently in Radarr. If necessary, it will then update the applicable movies.

A common complaint is the Refresh task causes heavy I/O usage. This is partly due to the setting "Analyze video files" which is advised to be enabled if you use tdarr or otherwise externally modify your files. If you don't you can safely disable "Analyze video files" to reduce some I/O. The other setting is "Rescan Movie Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to <code>Manual</code>. Do not change this to <code>Never</code> unless all changes to your library (new movies, upgrades, deletions etc) are done through Radarr. If you delete movie files manually or via Plex or another third party program, do not set this to <code>Never</code>.

{{FAQ|ARRNAME=Radarr|ARRDISCORD=https://radarr.video/discord|ARRPORT=7878}}

System status

2021-05-14T00:32:01Z

Bakerboy448: root folder updates....

== System ==
=== Health ===
==== Overview ====
====== Radarr ======
<section begin=radarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=radarr_system_status_health_overview />
====== Sonarr ======
<section begin=sonarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=sonarr_system_status_health_overview />
====== Lidarr ======
<section begin=lidarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=lidarr_system_status_health_overview />
====== Readarr ======
<section begin=readarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=readarr_system_status_health_overview />
==== System Warnings ====
===== Radarr =====
<section begin=radarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Radarr are targeted for .NET. We will no longer be providing legacy mono builds after 3.2 is released. You are running one of these legacy builds but your platform supports .NET.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''[[Radarr_FAQ#how_do_i_backup_restore_my_Radarr| Back-Up your existing configuration]]''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>master</code> branch. If you are on <code>develop</code> or <code>nightly</code> you'll need to adjust <code>/master/</code> in the URL.
*** '''Delete your existing binaries (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''.
****<code>wget --content-disposition <nowiki>'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop radarr</code> Stop Radarr
****<code> sudo mv /opt/Radarr /opt/Radarr.old</code> Backup the old Binaries
**** <code> tar -xvzf Radarr*.linux-core-x64.tar.gz</code> Extract the Radarr Tarball
**** <code> sudo mv Radarr/ /opt</code> Move the new Radarr Binaries
**** <code> sudo chown -R radarr:radarr /opt/Radarr</code> Ensure Radarr has permissions to its directory, this assumes it runs as the user <code>radarr</code>
**** <code> sudo rm -rf /opt/Radarr.old</code> Remove the old binaries
**** <code> sudo rm -rf Radarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script in your systemd (<code> sudo nano -e /etc/systemd/system/radarr.service</code>) to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.
***** If Radarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start radarr.service</code> Restart Radarr

* '''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''
** Radarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.20 is the absolute minimum for Radarr.
** The upgrade procedure for Mono varies per platform.

*'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''
** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0. Note that Radarr uses <code>libsqlite3.so</code> which may or may not be contained in a sqlite3 upgrade package.

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.

*'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.
** Please look at System -> Info to see the current AppData & Startup directories.
** This means Radarr will be unable to update itself without risking data-loss.
** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081

** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:7878/$1 [P,L]
** For Caddy (V1) use this:
*** Note: you'll also need to add the websocket directive to your radarr configuration
proxy /radarr 127.0.0.1:7878 {
websocket
transparent
}

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#ptp_settings_old|PTP Indexer Settings Out of Date]]'''
** The following PassThePopcorn indexers have deprecated settings and should be updated.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

*'''[[#mono_support_end_of_life|Mono and x86 builds are ending]]'''
** Mono and x86 builds will no longer be supported in the next build of the application. If you are receiving this error then you are running the mono version of the application or the x86 version. Unfortunately, due to increasing difficulting in development support for these legacy versions we will be discontinuing their support and thus releases for them going forward. Thus it is advised you upgrade to a supported Operating System that does not require neither x86 nor mono. You may also be able to explore using Docker for your needs.

<section end=radarr_system_status_health_system_warnings />

===== Sonarr =====
<section begin=sonarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]'''
** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].

* '''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''
** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].

* '''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''
** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform. 
** Mono 5.8 is the absolute minimum for Sonarr, but Mono 5.20 is currently recommended.
** The upgrade procedure for Mono varies per platform.

* '''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''
** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** The upgrade procedure for Mono varies per platform.

* '''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.
** ''(This warning will not appear if your current version is less than 14 days old)''

* '''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.

* '''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''
** Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux. 
** Please look at System -> About to see the current AppData & Startup directories.
** This means Sonarr will be unable to update itself without risking data-loss.
** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.
* '''[[#package_maintainer_message|Package Maintainer Message]]'''
** Please refer to the specific message your package maintainer is indicating to you. This is not a Sonarr issue. For additional information, refer to your package maintainer. Your package maintainer can be found in System -> Status -> About. Note that this includes docker and your package maintainer is whomever maintains your docker image.

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=sonarr_system_status_health_system_warnings />

===== Lidarr =====
<section begin=lidarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Lidarr are targeted for .NET. We will soon no longer provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''Back-Up your existing configuration''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>develop</code> branch. If you are on <code>nightly</code> you'll need to adjust <code>/develop/</code> in the URL.
***'''Delete your existing binaries (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''
****<code>wget --content-disposition <nowiki>'http://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop lidarr.service</code> Stop Lidarr
****<code> sudo mv /opt/Lidarr /opt/Lidarr.old</code> Backup the old Binaries
****<code> tar -xvzf Lidarr*.linux-core-x64.tar.gz</code> Extract the Lidarr Tarball
****<code> sudo mv Lidarr/ /opt</code> Move the new Lidarr Binaries
****<code> sudo chown -R lidarr:lidarr /opt/Lidarr</code> Ensure Lidarr has permissions to its directory, this assumes it runs as the user <code>lidarr</code>
****<code> sudo rm -rf /opt/Lidarr.old</code> Remove the old binaries
****<code> sudo rm -rf Lidarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script (<code> sudo nano -e /etc/systemd/system/lidarr.service</code>) to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.
***** If Lidarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start lidarr.service</code> Restart Lidarr

*'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''
** Lidarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.20 is the absolute minimum for Lidarr.
** The upgrade procedure for Mono varies per platform..
** See "Update to .NET Core version above"

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081
** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:8686/$1 [P,L]

*'''[[#fpcalc_upgrade|Fpcalc Needs Upgrading]]'''
Lidarr can use chromaprint audio fingerprinting to identify tracks. This depends on an external binary, which is distributed with Lidarr for Windows and macOS, but must be provided independently on Linux.

To fix this on a native Linux instance, install the appropriate package using your package manager and make sure that fpcalc is on your PATH (this can be checked using which fpcalc and verifying that the correct location of fpcalc is returned):

{| class="wikitable"
|- style="font-weight:bold; text-align:center; vertical-align:middle;"
! Distribution
! Package
|-
| style="vertical-align:middle;" | Debian/Ubuntu
| <code>libchromaprint-tools</code>
|-
| style="vertical-align:middle;" | Fedora/CentOS
| <code>chromaprint-tools</code>
|-
| style="vertical-align:middle;" | Arch
| <code>chromaprint</code>
|-
| style="vertical-align:middle;" | OpenSUSE
|<code> chromaprint-fpcalc</code>
|-
| style="vertical-align:middle;" | Synology
| <code>chromaprint</code>
|}

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=lidarr_system_status_health_system_warnings />

===== Readarr =====
<section begin=readarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Readarr are targeted for .NET. We will soon no longer provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET Core.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''Back-Up your existing configuration''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>master</code> branch. If you are on <code>develop</code> or <code>nightly</code> you'll need to adjust <code>/master/</code> in the URL.
***'''Delete your existing binaries (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''.
****<code>wget --content-disposition <nowiki>'http://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop readarr</code> Stop Readarr
****<code> sudo mv /opt/Readarr /opt/Readarr.old</code> Backup the old Binaries
****<code> tar -xvzf Readarr*.linux-core-x64.tar.gz</code> Extract the Readarr Tarball
****<code> sudo mv Readarr/ /opt</code> Move the new Readarr Binaries
****<code> sudo chown -R readarr:readarr /opt/Readarr</code> Ensure Readarr has permissions to its directory, this assumes it runs as the user <code>readarr</code>
****<code> sudo rm -rf /opt/Readarr.old</code> Remove the old binaries
****<code> sudo rm -rf Readarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script (<code> sudo nano -e /etc/systemd/system/readarr.service</code>) to call <code>Readarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.
***** If Readarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start readarr.service</code> Restart Readarr

*'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''
** Readarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.20 is the absolute minimum for Readarr.
** The upgrade procedure for Mono varies per platform.
** See "Update to .NET Core version above"

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081
** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:8787/$1 [P,L]

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=readarr_system_status_health_system_warnings />

==== Download Clients ====
===== Radarr =====
<section begin=radarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.
*** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Radarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Radarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Radarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Radarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Radarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/hardlinks How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

[https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** Within the application, a root folder is defined as the configured media library folder. You're downloading directly into your root (library) folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Radarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#permissions_error|Permissions Error]]'''
** Radarr or the user radarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end=radarr_system_status_health_download_clients />

===== Sonarr =====
<section begin=sonarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Sonarr.
*** Ensure SSL encryption is not turned on if you're using both your Sonarr instance and your download client on a local network. See [[Sonarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Sonarr to prevent the errors.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** Within the application, a root folder is defined as the configured media library folder. You're downloading directly into your root (library) folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Sonarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Sonarr/V3/Sonarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#permissions_error|Permissions Error]]'''
** Sonarr or the user sonarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end="sonarr_system_status_health_download_clients" />

===== Lidarr =====
<section begin=lidarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.
*** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Lidarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Lidarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished song is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Lidarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Lidarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/audio</code> and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/audio</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** Within the application, a root folder is defined as the configured media library folder. You're downloading directly into your root (library) folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Lidarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* '''[[#permissions_error|Permissions Error]]'''
** Lidarr or the user lidarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=lidarr_system_status_health_download_clients />
===== Readarr =====
<section begin=readarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.
*** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Readarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Readarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Readarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished book is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Readarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Readarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/books</code> and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/books</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** Within the application, a root folder is defined as the configured media library folder. You're downloading directly into your root (library) folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Readarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* '''[[#permissions_error|Permissions Error]]'''
** Readarr or the user readarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=readarr_system_status_health_download_clients />

==== Completed/Failed Download Handling ====
===== Radarr =====
<section begin=radarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=radarr_system_status_health_complete_failed_download_handling />

===== Sonarr =====
<section begin=sonarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the
<section end=sonarr_system_status_health_complete_failed_download_handling />

===== Lidarr =====
<section begin=lidarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidrr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=lidarr_system_status_health_complete_failed_download_handling />

===== Readarr =====
<section begin=readarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=readarr_system_status_health_complete_failed_download_handling />

==== Indexers ====
===== Radarr =====
<section begin=radarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_radarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Radarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_radarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Radarr will not grab new releases automatically]]'''
** So Radarr uses the RSS feed to pick up new releases as they come along. More info on that [[Radarr FAQ#How does Radarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=radarr_system_status_health_indexers />

===== Sonarr =====
<section begin=sonarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_sonarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Sonarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_sonarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Sonarr will not grab new releases automatically]]'''
** So Sonarr uses the RSS feed to pick up new releases as they come along. More info on that [[Sonarr FAQ#How does Sonarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''
** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=sonarr_system_status_health_indexers />
===== Lidarr =====
<section begin=lidarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Lidarr will not grab new releases automatically]]'''
** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for music (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=lidarr_system_status_health_indexers />
===== Readarr =====
<section begin=readarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_readarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Readarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_readarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Readarr will not grab new releases automatically]]'''
** So Readarr uses the RSS feed to pick up new releases as they come along. More info on that [[Readarr FAQ#How does Readarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for books (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=readarr_system_status_health_indexers />

==== Folders ====
===== Radarr =====
<section begin=radarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder
***# Easiest way to find this is to go to the Movies (Library) Tab
***# Create a custom filter with the old root folder path
***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files
<section end=radarr_system_status_health_folders />
===== Sonarr =====
<section begin=sonarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder
***# Go to the Series > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these series to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files
* '''[[#import_list_missing_root_folder|Import List missing root folder]]'''
** This error is typically identified if a list is looking for a root folder but that root folder is no longer available.
**#Go to Settings > Import Lists
**#Edit the import lists that were mentioned in the health check
**#Save
<section end=sonarr_system_status_health_folders />
===== Lidarr =====
<section begin=lidarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these artists to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files
<section end=lidarr_system_status_health_folders />
===== Readarr =====
<section begin=readarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these authors to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files
<section end=readarr_system_status_health_folders />

==== Media ====
===== Radarr =====
<section begin=radarr_system_status_health_media />
* '''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''
** The movie is linked to a TMDb Id that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It. 
** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu

* '''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''
** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.
<section end=radarr_system_status_health_media />
===== Sonarr =====
<section begin=sonarr_system_status_health_media />
* '''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''
** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.
<section end=sonarr_system_status_health_media />
===== Lidarr =====
<section begin=lidarr_system_status_health_media />
Text
<section end=lidarr_system_status_health_media />
===== Readarr =====
<section begin=readarr_system_status_health_media />
Text
<section end=readarr_system_status_health_media />

=== Disk Space ===
==== Radarr ====
<section begin=radarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=radarr_system_status_disk_space />
==== Sonarr ====
<section begin=sonarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=sonarr_system_status_disk_space />
==== Lidarr ====
<section begin=lidarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=lidarr_system_status_disk_space />
==== Readarr ====
<section begin=readarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=readarr_system_status_disk_space />

=== About ===
==== Radarr ====
<section begin=radarr_system_status_about />
This will tell you about your current install of Radarr
<section end=radarr_system_status_about />
==== Sonarr ====
<section begin=sonarr_system_status_about />
This will tell you about your current install of Radarr
<section end=sonarr_system_status_about />
==== Lidarr ====
<section begin=lidarr_system_status_about />
This will tell you about your current install of Lidarr
<section end=lidarr_system_status_about />
==== Readarr ====
<section begin=readarr_system_status_about />
This will tell you about your current install of Readarr
<section end=readarr_system_status_about />

=== More Info ===
==== Radarr ====
<section begin=radarr_system_status_more_info />
* Home Page: [https://radarr.video Radarr's home page]
* Wiki: [https://wiki.servarr.com/Radarr You're here already]
* Reddit: [https://reddit.com/r/radarr r/radarr]
* Discord: [https://radarr.video/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/radarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Radarr/Radarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]
<section end=radarr_system_status_more_info />
==== Sonarr ====
<section begin=sonarr_system_status_more_info />
* Home page: [https://sonarr.tv Sonarr's home page]
* Forums: [https://forums.sonarr.tv Sonarr Forums]
* Discord: [https://discord.gg/M6BvZn5 Join our discord]
* Reddit: [https://reddit.com/r/sonarr r/sonarr]
* Twitter: [https://twitter.com/sonarrtv @sonarrtv]
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]
* Wiki: [https://wiki.servarr.com/sonarr You're here already]
* Donations: If you're feeling generous and would like to donate [https://sonarr.tv/donate click here]
* Source: https://github.com/Sonarr/Sonarr Github]
* Feature Requests: Got a great idea drop it on Github [https://github.com/Sonarr/Sonarr/issues here]
<section end=sonarr_system_status_more_info />
==== Lidarr ====
<section begin=lidarr_system_status_more_info />
* Home page: [https://lidarr.audio Lidarr's home page]
* Wiki: [https://wiki.servarr.com/Lidarr You're here already]
* Reddit: [https://reddit.com/r/lidarr r/lidarr]
* Discord: [https://lidarr.audio/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/lidarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/lidarr/Lidarr/ Github]
* Feature Requests: Got a great idea drop it on GitHub [https://github.com/Lidarr/Lidarr/issues here]
<section end=lidarr_system_status_more_info />
==== Readarr ====
<section begin=readarr_system_status_more_info />
* Home page: [https://readarr.com Readarr's home page]
* Wiki: [https://wiki.servarr.com/Readarr You're here already]
* Reddit: [https://reddit.com/r/readarr r/readarr]
* Discord: [https://readarr.com/discord Join our discord]
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Readarr/Readarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Readarr/Readarr/issues click here]
<section end=readarr_system_status_more_info />

=== Templates ===

Lidarr FAQ

2021-05-13T20:39:25Z

Bakerboy448:

== How does Lidarr work? ==
[[#how_does_lidarr_work|anchor]] 
* Lidarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Lidarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Lidarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Lidarr's Release-Push API endpoint along with an IRC announce channel to push releases to Lidarr for processing which can happen in near real time and with less overhead on the indexer and Lidarr as Lidarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== Why does Lidarr only show studio albums, How do I find singles or EPs? ==
[[#why_does_lidarr_only_show_studio_albums_how_do_i_find_singles_or_eps|anchor]] 
Lidarr defaults to only bringing in studio albums for each artist. However, you can expand the album types per an artist, or for your entire library by utilizing [[Lidarr Settings#Metadata Profiles|Metadata Profiles]].

== Why can't I add a various artists album? ==
[[#why_cant_i_add_a_various_artists_album|anchor]] 
Various Artists and other meta artists on Musicbrainz are due to the number of entries they provide.

== Can I add just an album? ==
[[#an_i_add_just_an_album|anchor]] 
Not at the moment.

== Can I download single tracks? ==
[[#can_i_download_single_tracks|anchor]] 
Lidarr works by searching for and downloading full releases, therefore individual tracks cannot be downloaded unless they were released as a single by the artist.

== Why doesn't artist X show up in search? ==
[[#why_doesnt_artist_x_show_up_in_search|anchor]] 
Search is still a work in progress. Artists that don't show up in search may be added by searching for `lidarr:mbid` where `mbid` is the Musicbrainz ID of the artist.

== Lidarr matched an album with too many tracks. How can I change the Album to the correct Release? ==
[[#lidarr_matched_an_album_with_too_many_tracks_how_can_i_change_thealbum_to_the_correct_release|anchor]] 
Open the Album details page and select the Edit Icon in the top nav. There you can find a dropdown of all releases tied to that Album.

== I'm having trouble importing my artists, what could it be? ==
[[#im_having_trouble_importing_my_artists_what_could_it_be|anchor]] 
The artist import process just imports the Artist names and path locations, which are then stored in the database so that a) metadata can be retrieved and b) downloaded content can be put in the same location in future. To this end, the user account that Lidarr runs under needs both read and write to your data directory.

== I can't find a release in Lidarr but it is on MusicBrainz ==
[[#cant_find_release_lidarr_on_mb|anchor]] 
This is likely due to the release having an <code>unknown</code> release status. Update MusicBrainz.

== How often do Lidarr's and MusicBrainz databases sync? ==
[[#lidarr_mb_db_sync|anchor]] 
Every hour at 5 after the hour

== How can I add missing artist images? ==
[[#missing_artist_images|anchor]] 
Add art to fanart.tv and wait ~7+ days for it to clear through the cache. Then refresh the metadata.

== How can I get missing album images? (Cover Art) ==
[[#missing_album_images|anchor]] 
Add coverart to musicbrainz and wait ~1hr+ for it to clear through the cache. Then refresh the metadata.

== I'm having trouble importing my artists, what could it be? ==
[[#im_having_trouble_importing_my_artists_what_could_it_be|anchor]] 
The artist import process just imports the Artist names and path locations, which are then stored in the database so that a) metadata can be retrieved and b) downloaded content can be put in the same location in future. To this end, the user account that Lidarr runs under needs both read and write to your data directory.
{{FAQ|ARRNAME=Lidarr|ARRDISCORD=https://lidarr.audio/discord|ARRPORT=8686}}

Sonarr FAQ

2021-05-13T04:50:47Z

Bakerboy448: /* How does Sonarr find episodes? */

== How does Sonarr find episodes? ==
[[#how_does_Sonarr_find_episodes|anchor]] 

* Sonarr does ''not'' regularly search for episode files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted episodes/newly uploaded releases, then compares that with its list of episodes that are missing or need to be upgraded. Any matches are downloaded. This lets Sonarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a show, you'll need to set the correct path, profile and monitoring status then use the Start search for missing checkbox. If the show has had no episodes and hasn't been released yet, you don't need to initiate a search.
* Put another way, Sonarr will only find releases that are newly uploaded to your indexers. It will not actively try to find releases uploaded in the past.
* If you've already added the show, but now you want to search for it, you have a few choices. You can go to the show's page and use the search button, which will do a search and then automatically pick episode(s). You can search individual episodes or seasons automatically or manually. Or you can use the filters of <code>Missing</code> and <code>Cut-off Unmet</code>.
* If Sonarr has been offline for an extended period of time, Sonarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Sonarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed episodes.

== Why didn’t Sonarr grab an episode I was expecting? ==
[[#Why_didnt_Sonarr_grab_an_episode_i_was_expecting|anchor]] 

First, make sure you read and understand the section above called ''“How does Sonarr find episodes?”'' Second, make sure at least one of your indexers has the episode you were expecting to be grabbed.
# Click the ‘Manual Search’ icon next to the episode listing in Sonarr. Are there any results? If no, then either Sonarr is having trouble communicating with your indexers, or your indexers do not have the episode, or the episode is improperly named/categorized on the indexer.
# '''If there are results from step 1''', check next to them for red exclamation point icon. Hover over the icon to see why that release is not a candidate for automatic downloads. If every result has the icon, then no automatic download will occur.
# '''If there is at least one valid manual search result from step 2''', then an automatic download should have happened. If it didn’t, the most likely reason is a temporary communication problem preventing an RSS Sync from your indexer. It is recommended to have several indexers set up for best results.
# '''If there is no manual result from a show, but you can find it when you browse your indexer’s website''' - This is a common problem that is most frequently caused by having an insufficient number of indexers. Different indexers index different content, and not all shows on your indexer may be tagged properly, which would cause Sonarr’s search to fail. Having several indexers active is the best solution to this problem.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Sonarr/Sonarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs#L31-L40s can be found here].
'''''As of 3/26/2021 the logic is as follows'''''
# Quality
# Language
# Preferred Word Score
# Protocol
# Episode Count
# Episode Number
# Indexer Priority
# Peers (If Torrent)
# Age (If Usenet)
# Size

== Preferred Words FAQs ==
[[#Preferred_Words_FAQs|anchor]] 

For the score of the on disk file:
The existing name of the file and the "scene name" of the release are evaluated for preferred words. The higher score of the two is taken.

How are preferred words included in renaming?

For Sonarr you can make use of the `{Preferred Words}` token in your renaming scheme. and also check mark `Include Preferred when Renaming` in the release profile.
take a look [https://trash-guides.info/Sonarr/V3/Sonarr-recommended-naming-scheme/ HERE] for a recommended naming scheme examples for Sonarr.

Using the tokens in your renaming scheme could help with download loop issues.

Preferred Words always upgrade a release even if the quality and/or language cutoff has been met.
== How does Sonarr handle scene numbering issues (American Dad!, etc)? ==
[[#how_does_sonarr_handle_scene_numbering_issues|anchor]] 

* '''How Sonarr handles scene numbering issues'''
** Sonarr relies on [http://thexem.de/ TheXEM], a community driven site that lets users create mappings of shows that the scene (the people that post the files) and TheTVDB (which typically follows the network’s numbering). There are a number of shows on there already, but it is easy to add another and typically the changes are accepted within a couple days (if they’re correct). TheXEM is used to correct differences in episode numbering (disagreement whether an episode is a special or not) as well as season number differences, such as episodes being released as S10E01, but TheTVDB listing that same episode as S2017E01.
* '''Problematic Shows'''
** This by no means is an all inclusive list of shows that have known issues with scene mapping however, these are the big ones that come to mind while writing this.
** Typical Issue: Scene numbering does not match TVDb numbering so Sonarr doesn't work. Well enter XEM which creates a map for Sonarr to look at.
*** Scene releases double episodes in a single file since that is how they air but TVDb marks each episode individually.
*** Scene uses a year for the season S2010 and TVDb uses S01.
** [http://thexem.de XEM] works in most cases and keeps it running smooth without you ever knowing. However as with most things, there will always be a ''black sheep'' and in this case there is a list of them.
** This is an incomplete list of the known shows and how/why they're problematic:
*** American Dad
*** Arrested Development
*** Mythbusters
*** Paw Patrol
**** Double episode files vs single episode TVDb but also not all episodes are doubles so the map can get added wrong pointing to which ones are singles vs doubles
*** Pawn Stars
*** Pokémon
**** On TheXem, [http://thexem.de/xem/show/4638 pokemon] is tracking * dubbed* episodes. So if you want subbed episodes, you may be out of luck. If certain release groups are following TVDB and not XEM mapping, please contact us on our discord and bring the release name and group name as exceptions can be added for groups who follow TVDB.
* '''Possible resolutions:'''
# TVDb adds alternate ordering to the API (Current status: They say v4 but don't count on it to work or be stable based on the history of v3)
# XEM adds a map to allow for alternate orders that sonarr can use (Current status: Unlikely)
# Sonarr allows for disabling of XEM maps when doing manual searches (Current status: Unlikely)
* '''Sonarr side effects:'''
** On top of the issues with the shows already, Sonarr also has some odd behavior so you may just need to overlook this as well. Example:
** American Dad is currently on S17 based on TVDb or S16 based on Scene at the time of this writing. So searching in sonarr for season 17 will '''only''' return S16 results because of the XEM map. If you have a tracker with S17 episodes (because they use P2P and not Scene), please contact us on our discord and bring the release name and group name as exceptions can be added for groups who follow TVDB.

== Why can’t Sonarr import episode files for series X? / Why can’t Sonarr find releases for series X? ==
[[#why_cant_sonarr_import_episode_files_for_series_x_why_cant_sonarr_find_releases_for_series_x|anchor]] 

Sonarr relies on being able to match titles, often the scene posts episodes using different titles, eg ''CSI: Crime Scene Investigation'' as just ''CSI'' so Sonarr can’t match the names without some help. Sonarr maintains a list of problematic series which lets us solve this issue. '''For anime, it will need to be added to [https://thexem.de thexem.de]''', for other series to request a new mapping see the steps below.

# Make sure it hasn’t already been requested. [https://docs.google.com/spreadsheet/ccc?key=0Atcf2VZ47O8tdGdQN1ZTbjFRanhFSTBlU0xhbzhuMGc#gid=0 Requested Mappings]
# Make a new request here: [https://docs.google.com/forms/d/15S6FKZf5dDXOThH4Gkp3QCNtS9Q-AmxIiOpEBJJxi-o/viewform Scene Mapping Request Form]

''Typically these are added within 1-2 days.''

''Again, do not request a mapping for Anime; use XEM for that.'' Further information can be found with some of the XEM folks that hangout in our [https://discord.gg/an9rnEdWs5 <nowiki>#XEM</nowiki> discord channel].

The series "Helt Perfekt" with TVDB ids of <code>343189</code> and <code>252077</code> is difficult to automate due to TVDB having the same name for both shows, violating TVDB's own rules. The first entry for the series gets the name. Any future entries for the series must have the year as part of the series name. However, a scene exception as been added to map releases (case sensitive mapping) Helt Perfekt releases containing <code>NORWEGIAN</code> -> <code>252077</code> and containing <code>SWEDISH</code> -> <code>343189</code>

== TVDB is updated why isn't Sonarr? ==
[[#tvdb_is_updated_why_is_not_sonarr|anchor]] 

TVDB has a 24 hour cache on their API. Skyhook has a much smaller few hour cache on top of that. Sonarr only runs the Refresh Series task every 12 hours. Thus it typically takes 24 to 48 hours for a TVDB update to make it into Sonarr.

If you know a TVDB update was made more than 48 hours ago, then please come discuss on our [https://discord.gg/M6BvZn5 Discord].
== I see that feature/bug X was fixed, why can’t I see it? ==
[[#i_see_that_feature_bug_x_was_fixed_why_cant_i_see_it|anchor]] 

Sonarr consists of two main branches of code, <code>main</code> and <code>develop</code>, <code>main</code>is released periodically, when the <code>develop</code> branch is stable and <code>develop</code> is for pre-release testing and people willing to live on the edge, if you want to help out testing or want more information on the two branches, please see: [[Sonarr_Settings#Updates|Release Branches]]. When a feature is marked as in <code>develop</code> it will only be available to users running the <code>develop</code> branch, once it has been move to live (in <code>main</code>) it is officially released.

== Episode Progress - How is it calculated? ==
[[#episode_progress_-_how_is_it_calculated|anchor]] 

There are two parts to the episode count, one being the number of episodes (Episode Count) and the other being the number of episodes with files (Episode File Count), each one uses slightly different logic to give you the overall progress for a series or season.

* Episode Count
** Episode has already aired AND is monitored OR
** Episode has a file
* Episode File Count
** Episode has a file

If a series has 10 episodes that have all aired and you don’t have any files for them you would have 0/10 episodes, if you unmonitored all the episodes in that series you would have 0/0 and if you got all the episodes for that series, regardless of if the episodes are monitored or not, you would have 10/10 episodes.

== How do I access Sonarr from another computer? ==
[[#how_do_I_access_sonarr_from_another_computer|anchor]] 

By default Sonarr doesn’t listen to requests from all systems (when not run as administrator), it will only listen on localhost, this is due to how the Web Server Sonarr uses integrates with Windows (this also applies for current alternatives). If Sonarr is run as an administrator it will correctly register itself with Windows as well as open the Firewall port so it can be accessed from other systems on your network. Running as admin only needs to happen once (if you change the port it will need to be re-run).

== Why doesn’t Sonarr automatically search for missing episodes? ==
[[#why_doesnt_sonarr_automatically_search_for_missing_episodes|anchor]] 

There are two times when we would want to have missing episodes searched for, when a new series with existing aired episodes is added and when Sonarr has been offline and unable to find episodes as it normally would. Endlessly searching for episodes that have aired that are missing is a waste of resources, both in terms of local processing power and on the indexers and in our experience catches users off guard, wasting bandwidth.

In v1 of Sonarr we had an opt in backlog search option, often people would turn it on and then get a bunch of old episodes and ask us why, we also had indexers ask why they saw an increase in API calls, which was due to the backlog searching.

In v2 we sat back and thought about it and realized the benefit is not really there, we could try to throttle the searching, but that just draws it out and still does the same thing; hammer the indexer with useless requests. If the episode wasn’t there the last time the search was performed, why would it be there now? It would be if it was reposted, but if it was reposted, the automatic process that gets new episodes would see it was posted and act on it.

== Why does Sonarr refresh series information so frequently? ==
[[#why_does_sonarr_refresh_series_information_so_frequently|anchor]] 

* Sonarr refreshes series and episode information in addition to rescanning the disk for files every 12 hours. This might seem aggressive, but is a very important process. The data refresh from our TVDB proxy is important, because new episode information is synced down, air dates, number of episodes, status (continuing/ended). Even shows that aren’t airing are being updated with new information.
* The disk scan is less important, but is used to check for new files that weren’t sorted by Sonarr and detect deleted files.
* The most time consuming portion is the information refresh (assuming reasonable disk access speed), larger shows take longer due to the number of episodes to process.

== Why is there a number next to Activity? ==
[[#why_is_there_a_number_next_to_activity|anchor]] 

* This number shows the count of episodes in your download client’s queue and the last 30 items in its history that have not yet been imported. If the number is blue it is operating normally and should import episodes when they complete. Yellow means there is a warning on one of the episodes. Red means there has been an error. In the case of yellow (warning) and red (error), you will need to look at the queue under Activity to see what the issue is (hover over the icon to get more details).
* You need to remove the item from your download client’s queue or history to remove them from Sonarr’s queue.

== I see log messages for shows I don’t have/don’t want ==
[[#i_see_log_messages_for_shows_i_don_t_have_dont_want|anchor]] 

* These messages are completely normal and come from the RSS feeds that Sonarr checks to see if there are episodes you do want, usually these only appear in debug/trace logging, but in the event of an problem processing an item you may see a warning or error. It is safe to ignore the warnings/errors as well since they are for shows you don’t want, in the event it is for a show you want, open up a support thread on the forums.

== Seeding torrents aren’t deleted automatically ==
[[#seeding_torrents_arent_deleted_automatically|anchor]] 

* When a torrent that is still seeding is imported, it is copied or hard linked (if enabled and ''possible'') so that the torrent client can continue seeding. In an ideal setup, the torrent download folder and the library folder will be on the same file system and ''look like it'' (Docker and network shares make this easy to get wrong), which makes hard links possible and minimizes wasted space.
* In addition, you can configure your seed time/ratio goals in Sonarr or your download client, setup your download client to ''pause'' or ''stop'' when they’re met and enable Remove under Completed and Failed Download Handler. That way, torrents that finish seeding will be removed from the download client by Sonarr.

== Why can’t I add a new series? ==
[[#why_cant_i_add_a_new_series|anchor]] 

* In the event that TheTVDB is unavailable Sonarr is unable to get search results and you will be unable to add any new series by searching. You may be able to add a new series by the TVDBID if you know what it is, the UI explains how to add it by an ID.
* Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDB ID that does not have an English title. If no English title exist for that series on TheTVDB it will need to be added (if available).
* The show must be a TV Series, and not a movie. It must also exist on TVDB. If it is on IMDB, TMDB, or anywhere else, but not on TVDB you cannot add the show.
* The series must exist on TVDB

== Why can’t I add a new series when I know the TVDB ID? ==
[[#why_cant_i_add_a_new_series_when_i_know_the_tvdb_id|anchor]] 

* Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDB ID that does not have an English title. If no English title exist for that series on TheTVDB it will need to be added (if available).

== Sonarr won't work on Big Sur ==
[[#sonarr_wont_work_on_big_sur|anchor]] 

Run <code>chmod +x /Applications/Sonarr.app/Contents/MacOS/Sonarr</code>

== My Custom Script stopped working after upgrading from v2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== What's the different Series Types? ==
[[#whats_the_different_series_types|anchor]] 
Most shows should be <code>Standard</code>. For daily shows which are typically released with a date, <code>Daily</code> should be used. Finally, there is anime where using <code>Anime</code> is ''usually'' right, but sometimes <code>Standard</code> can work better, so try the ''other'' one if you’re having issues.

Please note that if the series type is set to anime and none of your enabled indexers have any anime categories configured then it effectively skips the indexer and may appear that it is not searching.

=== Show Type Examples ===
Below are some example release names for each show type. The specific differentiating piece is noted in bold.

'''Daily'''
* Some.Daily.Show.'''2021.03.04'''.1080p.HDTV.x264-DARKSPORT
* A.Daily.Show.with.Some.Guy.'''2021.03.03'''.1080p.CC.WEB-DL.AAC2.0.x264-null
* DailyShow.'''2021.03.08'''.720p.HDTV.x264-NTb
'''Standard'''
* The.Show.'''S20E03'''.Episode.Title.Part.3.1080p.HULU.WEB-DL.DDP5.1.H.264-NTb
* Another.Show.'''S03E08'''.1080p.WEB.H264-GGEZ
* GreatShow.'''S17E02'''.1080p.HDTV.x264-DARKFLiX
'''Anime'''
* Anime.Origins.'''E04'''.File.4_.Monkey.WEB-DL.H.264.1080p.AAC2.0.AC3.5.1.Srt.EngCC-Pikanet128.1272903A
* [Coalgirls] Human X Monkey '''148''' (1920x1080 Blu-ray FLAC) [63B8AC67]
* [KaiDubs] Series x Title (2011) - '''142''' [1080p] [English Dub] [CC] [AS-DL] [A24AB2E5]

== How can I rename my series folders? ==
[[#how_can_i_rename_my_series_folders|anchor]] 
# Series
# Mass Editor
# Select what series need their folder renamed
# Change Root Folder to the same Root Folder that the series currently exist in
# Select "Yes move files"

{{FAQ|ARRNAME=Sonarr|ARRDISCORD=https://discord.gg/M6BvZn5|ARRPORT=8989}}

Sonarr FAQ

2021-05-13T04:49:40Z

Bakerboy448:

== How does Sonarr find episodes? ==
[[#how_does_Sonarr_find_episodes|anchor]] 

* Sonarr does ''not'' regularly search for episode files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted episodes/newly uploaded releases, then compares that with its list of episodes that are missing or need to be upgraded. Any matches are downloaded. This lets Sonarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a show, you'll need to set the correct path, profile and monitoring status then use the Start search for missing checkbox. If the show has had no episodes and hasn't been released yet, you don't need to initiate a search.
* Put another way, Sonarr will only find episodes that are newly uploaded to your indexers. It will not actively try to find episodes you want that uploaded in the past.
* If you've already added the show, but now you want to search for it, you have a few choices. You can go to the show's page and use the search button, which will do a search and then automatically pick episode(s). You can search individual episodes or seasons automatically or manually. Or you can use the filters of <code>Missing</code> and <code>Cut-off Unmet</code>.
* If Sonarr has been offline for an extended period of time, Sonarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Sonarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed episodes.

== Why didn’t Sonarr grab an episode I was expecting? ==
[[#Why_didnt_Sonarr_grab_an_episode_i_was_expecting|anchor]] 

First, make sure you read and understand the section above called ''“How does Sonarr find episodes?”'' Second, make sure at least one of your indexers has the episode you were expecting to be grabbed.
# Click the ‘Manual Search’ icon next to the episode listing in Sonarr. Are there any results? If no, then either Sonarr is having trouble communicating with your indexers, or your indexers do not have the episode, or the episode is improperly named/categorized on the indexer.
# '''If there are results from step 1''', check next to them for red exclamation point icon. Hover over the icon to see why that release is not a candidate for automatic downloads. If every result has the icon, then no automatic download will occur.
# '''If there is at least one valid manual search result from step 2''', then an automatic download should have happened. If it didn’t, the most likely reason is a temporary communication problem preventing an RSS Sync from your indexer. It is recommended to have several indexers set up for best results.
# '''If there is no manual result from a show, but you can find it when you browse your indexer’s website''' - This is a common problem that is most frequently caused by having an insufficient number of indexers. Different indexers index different content, and not all shows on your indexer may be tagged properly, which would cause Sonarr’s search to fail. Having several indexers active is the best solution to this problem.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Sonarr/Sonarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs#L31-L40s can be found here].
'''''As of 3/26/2021 the logic is as follows'''''
# Quality
# Language
# Preferred Word Score
# Protocol
# Episode Count
# Episode Number
# Indexer Priority
# Peers (If Torrent)
# Age (If Usenet)
# Size

== Preferred Words FAQs ==
[[#Preferred_Words_FAQs|anchor]] 

For the score of the on disk file:
The existing name of the file and the "scene name" of the release are evaluated for preferred words. The higher score of the two is taken.

How are preferred words included in renaming?

For Sonarr you can make use of the `{Preferred Words}` token in your renaming scheme. and also check mark `Include Preferred when Renaming` in the release profile.
take a look [https://trash-guides.info/Sonarr/V3/Sonarr-recommended-naming-scheme/ HERE] for a recommended naming scheme examples for Sonarr.

Using the tokens in your renaming scheme could help with download loop issues.

Preferred Words always upgrade a release even if the quality and/or language cutoff has been met.
== How does Sonarr handle scene numbering issues (American Dad!, etc)? ==
[[#how_does_sonarr_handle_scene_numbering_issues|anchor]] 

* '''How Sonarr handles scene numbering issues'''
** Sonarr relies on [http://thexem.de/ TheXEM], a community driven site that lets users create mappings of shows that the scene (the people that post the files) and TheTVDB (which typically follows the network’s numbering). There are a number of shows on there already, but it is easy to add another and typically the changes are accepted within a couple days (if they’re correct). TheXEM is used to correct differences in episode numbering (disagreement whether an episode is a special or not) as well as season number differences, such as episodes being released as S10E01, but TheTVDB listing that same episode as S2017E01.
* '''Problematic Shows'''
** This by no means is an all inclusive list of shows that have known issues with scene mapping however, these are the big ones that come to mind while writing this.
** Typical Issue: Scene numbering does not match TVDb numbering so Sonarr doesn't work. Well enter XEM which creates a map for Sonarr to look at.
*** Scene releases double episodes in a single file since that is how they air but TVDb marks each episode individually.
*** Scene uses a year for the season S2010 and TVDb uses S01.
** [http://thexem.de XEM] works in most cases and keeps it running smooth without you ever knowing. However as with most things, there will always be a ''black sheep'' and in this case there is a list of them.
** This is an incomplete list of the known shows and how/why they're problematic:
*** American Dad
*** Arrested Development
*** Mythbusters
*** Paw Patrol
**** Double episode files vs single episode TVDb but also not all episodes are doubles so the map can get added wrong pointing to which ones are singles vs doubles
*** Pawn Stars
*** Pokémon
**** On TheXem, [http://thexem.de/xem/show/4638 pokemon] is tracking * dubbed* episodes. So if you want subbed episodes, you may be out of luck. If certain release groups are following TVDB and not XEM mapping, please contact us on our discord and bring the release name and group name as exceptions can be added for groups who follow TVDB.
* '''Possible resolutions:'''
# TVDb adds alternate ordering to the API (Current status: They say v4 but don't count on it to work or be stable based on the history of v3)
# XEM adds a map to allow for alternate orders that sonarr can use (Current status: Unlikely)
# Sonarr allows for disabling of XEM maps when doing manual searches (Current status: Unlikely)
* '''Sonarr side effects:'''
** On top of the issues with the shows already, Sonarr also has some odd behavior so you may just need to overlook this as well. Example:
** American Dad is currently on S17 based on TVDb or S16 based on Scene at the time of this writing. So searching in sonarr for season 17 will '''only''' return S16 results because of the XEM map. If you have a tracker with S17 episodes (because they use P2P and not Scene), please contact us on our discord and bring the release name and group name as exceptions can be added for groups who follow TVDB.

== Why can’t Sonarr import episode files for series X? / Why can’t Sonarr find releases for series X? ==
[[#why_cant_sonarr_import_episode_files_for_series_x_why_cant_sonarr_find_releases_for_series_x|anchor]] 

Sonarr relies on being able to match titles, often the scene posts episodes using different titles, eg ''CSI: Crime Scene Investigation'' as just ''CSI'' so Sonarr can’t match the names without some help. Sonarr maintains a list of problematic series which lets us solve this issue. '''For anime, it will need to be added to [https://thexem.de thexem.de]''', for other series to request a new mapping see the steps below.

# Make sure it hasn’t already been requested. [https://docs.google.com/spreadsheet/ccc?key=0Atcf2VZ47O8tdGdQN1ZTbjFRanhFSTBlU0xhbzhuMGc#gid=0 Requested Mappings]
# Make a new request here: [https://docs.google.com/forms/d/15S6FKZf5dDXOThH4Gkp3QCNtS9Q-AmxIiOpEBJJxi-o/viewform Scene Mapping Request Form]

''Typically these are added within 1-2 days.''

''Again, do not request a mapping for Anime; use XEM for that.'' Further information can be found with some of the XEM folks that hangout in our [https://discord.gg/an9rnEdWs5 <nowiki>#XEM</nowiki> discord channel].

The series "Helt Perfekt" with TVDB ids of <code>343189</code> and <code>252077</code> is difficult to automate due to TVDB having the same name for both shows, violating TVDB's own rules. The first entry for the series gets the name. Any future entries for the series must have the year as part of the series name. However, a scene exception as been added to map releases (case sensitive mapping) Helt Perfekt releases containing <code>NORWEGIAN</code> -> <code>252077</code> and containing <code>SWEDISH</code> -> <code>343189</code>

== TVDB is updated why isn't Sonarr? ==
[[#tvdb_is_updated_why_is_not_sonarr|anchor]] 

TVDB has a 24 hour cache on their API. Skyhook has a much smaller few hour cache on top of that. Sonarr only runs the Refresh Series task every 12 hours. Thus it typically takes 24 to 48 hours for a TVDB update to make it into Sonarr.

If you know a TVDB update was made more than 48 hours ago, then please come discuss on our [https://discord.gg/M6BvZn5 Discord].
== I see that feature/bug X was fixed, why can’t I see it? ==
[[#i_see_that_feature_bug_x_was_fixed_why_cant_i_see_it|anchor]] 

Sonarr consists of two main branches of code, <code>main</code> and <code>develop</code>, <code>main</code>is released periodically, when the <code>develop</code> branch is stable and <code>develop</code> is for pre-release testing and people willing to live on the edge, if you want to help out testing or want more information on the two branches, please see: [[Sonarr_Settings#Updates|Release Branches]]. When a feature is marked as in <code>develop</code> it will only be available to users running the <code>develop</code> branch, once it has been move to live (in <code>main</code>) it is officially released.

== Episode Progress - How is it calculated? ==
[[#episode_progress_-_how_is_it_calculated|anchor]] 

There are two parts to the episode count, one being the number of episodes (Episode Count) and the other being the number of episodes with files (Episode File Count), each one uses slightly different logic to give you the overall progress for a series or season.

* Episode Count
** Episode has already aired AND is monitored OR
** Episode has a file
* Episode File Count
** Episode has a file

If a series has 10 episodes that have all aired and you don’t have any files for them you would have 0/10 episodes, if you unmonitored all the episodes in that series you would have 0/0 and if you got all the episodes for that series, regardless of if the episodes are monitored or not, you would have 10/10 episodes.

== How do I access Sonarr from another computer? ==
[[#how_do_I_access_sonarr_from_another_computer|anchor]] 

By default Sonarr doesn’t listen to requests from all systems (when not run as administrator), it will only listen on localhost, this is due to how the Web Server Sonarr uses integrates with Windows (this also applies for current alternatives). If Sonarr is run as an administrator it will correctly register itself with Windows as well as open the Firewall port so it can be accessed from other systems on your network. Running as admin only needs to happen once (if you change the port it will need to be re-run).

== Why doesn’t Sonarr automatically search for missing episodes? ==
[[#why_doesnt_sonarr_automatically_search_for_missing_episodes|anchor]] 

There are two times when we would want to have missing episodes searched for, when a new series with existing aired episodes is added and when Sonarr has been offline and unable to find episodes as it normally would. Endlessly searching for episodes that have aired that are missing is a waste of resources, both in terms of local processing power and on the indexers and in our experience catches users off guard, wasting bandwidth.

In v1 of Sonarr we had an opt in backlog search option, often people would turn it on and then get a bunch of old episodes and ask us why, we also had indexers ask why they saw an increase in API calls, which was due to the backlog searching.

In v2 we sat back and thought about it and realized the benefit is not really there, we could try to throttle the searching, but that just draws it out and still does the same thing; hammer the indexer with useless requests. If the episode wasn’t there the last time the search was performed, why would it be there now? It would be if it was reposted, but if it was reposted, the automatic process that gets new episodes would see it was posted and act on it.

== Why does Sonarr refresh series information so frequently? ==
[[#why_does_sonarr_refresh_series_information_so_frequently|anchor]] 

* Sonarr refreshes series and episode information in addition to rescanning the disk for files every 12 hours. This might seem aggressive, but is a very important process. The data refresh from our TVDB proxy is important, because new episode information is synced down, air dates, number of episodes, status (continuing/ended). Even shows that aren’t airing are being updated with new information.
* The disk scan is less important, but is used to check for new files that weren’t sorted by Sonarr and detect deleted files.
* The most time consuming portion is the information refresh (assuming reasonable disk access speed), larger shows take longer due to the number of episodes to process.

== Why is there a number next to Activity? ==
[[#why_is_there_a_number_next_to_activity|anchor]] 

* This number shows the count of episodes in your download client’s queue and the last 30 items in its history that have not yet been imported. If the number is blue it is operating normally and should import episodes when they complete. Yellow means there is a warning on one of the episodes. Red means there has been an error. In the case of yellow (warning) and red (error), you will need to look at the queue under Activity to see what the issue is (hover over the icon to get more details).
* You need to remove the item from your download client’s queue or history to remove them from Sonarr’s queue.

== I see log messages for shows I don’t have/don’t want ==
[[#i_see_log_messages_for_shows_i_don_t_have_dont_want|anchor]] 

* These messages are completely normal and come from the RSS feeds that Sonarr checks to see if there are episodes you do want, usually these only appear in debug/trace logging, but in the event of an problem processing an item you may see a warning or error. It is safe to ignore the warnings/errors as well since they are for shows you don’t want, in the event it is for a show you want, open up a support thread on the forums.

== Seeding torrents aren’t deleted automatically ==
[[#seeding_torrents_arent_deleted_automatically|anchor]] 

* When a torrent that is still seeding is imported, it is copied or hard linked (if enabled and ''possible'') so that the torrent client can continue seeding. In an ideal setup, the torrent download folder and the library folder will be on the same file system and ''look like it'' (Docker and network shares make this easy to get wrong), which makes hard links possible and minimizes wasted space.
* In addition, you can configure your seed time/ratio goals in Sonarr or your download client, setup your download client to ''pause'' or ''stop'' when they’re met and enable Remove under Completed and Failed Download Handler. That way, torrents that finish seeding will be removed from the download client by Sonarr.

== Why can’t I add a new series? ==
[[#why_cant_i_add_a_new_series|anchor]] 

* In the event that TheTVDB is unavailable Sonarr is unable to get search results and you will be unable to add any new series by searching. You may be able to add a new series by the TVDBID if you know what it is, the UI explains how to add it by an ID.
* Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDB ID that does not have an English title. If no English title exist for that series on TheTVDB it will need to be added (if available).
* The show must be a TV Series, and not a movie. It must also exist on TVDB. If it is on IMDB, TMDB, or anywhere else, but not on TVDB you cannot add the show.
* The series must exist on TVDB

== Why can’t I add a new series when I know the TVDB ID? ==
[[#why_cant_i_add_a_new_series_when_i_know_the_tvdb_id|anchor]] 

* Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDB ID that does not have an English title. If no English title exist for that series on TheTVDB it will need to be added (if available).

== Sonarr won't work on Big Sur ==
[[#sonarr_wont_work_on_big_sur|anchor]] 

Run <code>chmod +x /Applications/Sonarr.app/Contents/MacOS/Sonarr</code>

== My Custom Script stopped working after upgrading from v2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== What's the different Series Types? ==
[[#whats_the_different_series_types|anchor]] 
Most shows should be <code>Standard</code>. For daily shows which are typically released with a date, <code>Daily</code> should be used. Finally, there is anime where using <code>Anime</code> is ''usually'' right, but sometimes <code>Standard</code> can work better, so try the ''other'' one if you’re having issues.

Please note that if the series type is set to anime and none of your enabled indexers have any anime categories configured then it effectively skips the indexer and may appear that it is not searching.

=== Show Type Examples ===
Below are some example release names for each show type. The specific differentiating piece is noted in bold.

'''Daily'''
* Some.Daily.Show.'''2021.03.04'''.1080p.HDTV.x264-DARKSPORT
* A.Daily.Show.with.Some.Guy.'''2021.03.03'''.1080p.CC.WEB-DL.AAC2.0.x264-null
* DailyShow.'''2021.03.08'''.720p.HDTV.x264-NTb
'''Standard'''
* The.Show.'''S20E03'''.Episode.Title.Part.3.1080p.HULU.WEB-DL.DDP5.1.H.264-NTb
* Another.Show.'''S03E08'''.1080p.WEB.H264-GGEZ
* GreatShow.'''S17E02'''.1080p.HDTV.x264-DARKFLiX
'''Anime'''
* Anime.Origins.'''E04'''.File.4_.Monkey.WEB-DL.H.264.1080p.AAC2.0.AC3.5.1.Srt.EngCC-Pikanet128.1272903A
* [Coalgirls] Human X Monkey '''148''' (1920x1080 Blu-ray FLAC) [63B8AC67]
* [KaiDubs] Series x Title (2011) - '''142''' [1080p] [English Dub] [CC] [AS-DL] [A24AB2E5]

== How can I rename my series folders? ==
[[#how_can_i_rename_my_series_folders|anchor]] 
# Series
# Mass Editor
# Select what series need their folder renamed
# Change Root Folder to the same Root Folder that the series currently exist in
# Select "Yes move files"

{{FAQ|ARRNAME=Sonarr|ARRDISCORD=https://discord.gg/M6BvZn5|ARRPORT=8989}}

Template:Troubleshooting

2021-05-13T03:33:24Z

Bakerboy448: /* Common Problems */

<noinclude>
<templatedata>
{
"params": {
"ARRNAME": {
"description": "Name of the Application",
"example": "Radarr",
"type": "string",
"required": true
},
"ARR_DISCORD": {
"description": "Link to the ARR #support Discord",
"type": "url",
"required": true
},
"ARR_WEBSITE": {
"description": "Link to the ARR Website",
"type": "url",
"required": true
},
"ARR_LATEST_RELEASE": {
"description": "Link to the ARR Download",
"type": "url",
"required": true
},
"VERSION": {
"description": "The current version of each of the ARRs",
"type": "string",
"required": true
},
"MEDIA": {
"description": "What type of media does the ARR use",
"example": "Radarr: movies, Sonarr: series, Lidarr: artist, Readarr: author",
"type": "string",
"required": true
},
"SEARCHSOURCE": {
"description": "What metadata provider does the ARR use",
"example": "Radarr: TMDb, Sonarr: TheTVDb, Lidarr: MusicBrainz, Readarr: GoodReads",
"type": "string",
"required": true
},
"QUERYSTRING": {},
"ARRNAME2": {
"description": "This string is used for lower cased ARR names for transclusion",
"example": "radarr, sonarr, lidarr, readarr",
"type": "string",
"required": true
}
},
"description": "This template is utilized for general troubleshooting steps that span across all the ARRs. Some Sections may be transcluded from a Troubleshooting Misc page when items are ARR specific."
}
</templatedata>
</noinclude>
== Troubleshooting ==
----
Please note that this information is only for {{{ARRNAME}}} {{{VERSION}}}.
=== Asking for Help ===
----
Do you need help? That's okay, everyone needs help sometimes. You can get real time help via chat on [{{{ARR_DISCORD}}} Discord] or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit].

But before you go there and post, be sure your request for help is the best it can be. Clearly describe the problem and briefly describe your setup, including things like your OS/distribution, version of Mono or .Net/.Netcore, version of {{{ARRNAME}}}, download client and its version. '''If you are using [https://www.docker.com/ Docker] please run through [[Docker Guide|the Docker Guide]] first as that will solve common and frequent path/permissions issues. Otherwise please have a [[Docker Guide#Docker-compose|docker compose]] handy''' Tell us about what you've tried already, what you've looked at. Use the Logging and Log Files to turn your logging up to trace, recreate the issue, pastebin the relevant context and include a link to it in your post. Maybe even include some screen shots to highlight the issue.

The more we know, the easier it is to help you.

== Logging and Log Files ==

If you're linked here for support remember to get them the information from the actual trace log file, put the logs in a pastebin and show us context around what we need to see. If you're asked for debug logs your logs will contain <code>debug</code> and if you're asked for trace logs your logs will contain <code>trace</code>. If the logs you are providing do not contain either then they are not the logs requested.

What you need to do is:
# Turn Logging up to Trace
# Clear Logs
# Reproduce the Issue
# Open the trace log file ({{{ARRNAME}}}.trace.txt) and fine the relevant context
# [https://hastebin.com/ Hastebin], [https://pastebin.ubuntu.com/ Pastebin], [https://0bin.net/ 0bin], or any other pastebin type site a big chunk before the issue, the issue, and a big chunk after the issue.

* Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use N++. You can use the Notepad++ "Find in Files" function to search old log files as needed.
* '''Unix Only:''' Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use grep. For example if you want to find information about the movie or show "Shooter" you can run the following command <code>grep -inr -C 100 -e 'Shooter' /path/to/logs/*.trace*.txt</code> If your [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]] is in your home folder then you'd run: <code>grep -inr -C 100 -e 'Shooter' /home/$User/.config/logs/*.trace*.txt</code>
<div style="margin-left: 2em;"><pre>
* The flags have the following functions
* -i: ignore case
* -n: show line number
* -r: recursively check all files in the path
* -C: provide # of lines before and after the line it is found on
* -e: the pattern to search for
</pre></div>

==== Standard Logs Location ====
The log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the logs/ folder. You can also access the log files from the {{{ARRNAME}}} UI at System -> Logs -> Files.

Note: The Logs ("Events") Table in the UI is not the same as the log files and isn't as useful. If you're asked for logs, please copy/paste from the log files and not the table.

==== Update Logs Location ====
The update log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the UpdateLogs/ folder.

==== Sharing Logs ====
The logs can be long and hard to read as part of a forum or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit] post and they're spammy in [{{{ARR_DISCORD}}} Discord], so please use [https://pastebin.ubuntu.com/ Pastebin], [https://hastebin.com/ Hastebin], or any other similar pastebin site . The whole file typically isn't needed, just a good amount of context from before and after the issue/error. Don't forget to wait for spammy tasks like the RSS sync or library refresh to finish.

==== Trace/Debug Logs ====

You can change the log level at Settings -> General -> Logging. {{{ARRNAME}}} does not need to restarted for the change to take effect. This change only affects the log files, not the logging database. The latest debug/trace log files are named <code>{{{ARRNAME}}}.debug.txt</code> and <code>{{{ARRNAME}}}r.trace.txt</code> respectively.

If you're unable to access the {{{ARRNAME}}} UI to set the logging level you can do so by editing config.xml in the AppData directory by setting the LogLevel value to Debug or Trace instead of Info.
<div style="margin-left: 2em;"><pre>
<Config>
...
<LogLevel>debug</LogLevel>
...
</Config>
</pre></div>

==== Clearing Logs ====

You can clear log files and the logs database directly from the UI, under System -> Logs -> Files and System -> Logs -> Delete (Trash Can Icon)

==== Multiple Log Files ====

{{{ARRNAME}}} uses rolling log files limited to 1MB each. The current log file is always ,<code>{{{ARRNAME}}}.txt</code>, for the the other files <code>{{{ARRNAME}}}.0.txt</code> is the next newest (the higher the number the older it is). This log file contains fatal, error, warn, and info entries.

When Debug log level is enabled, additional <code>{{{ARRNAME}}}.debug.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, and debug entries. It usually covers a 40h period.

When Trace log level is enabled, additional <code>{{{ARRNAME}}}.trace.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, debug, and trace entries. Due to trace verbosity it only covers a couple of hours at most.

== Recovering from a Failed Update ==
----
==== Purpose ====
We do everything we can to prevent issues when upgrading, but they occur, this will walk you through the steps of recovering your installation.

==== Determine the issue ====
The best place to look when {{{ARRNAME}}} won't start after an update is your log files, before trying to start {{{ARRNAME}}} again, use [[{{{ARRNAME}}} Settings#Logging|Logging]] and [[{{{ARRNAME}}} System#Log_Files|Log Files]] to find them and increase the log level.

'''Migration Issue'''

Migration errors won't be identical, but here is an example:

<code>
14-2-4 18:56:49.5|Info|MigrationLogger|*** 36: update_with_quality_converters migrating ***

14-2-4 18:56:49.6|Error|MigrationLogger|SQL logic error or missing database duplicate column name: Items

While Processing: "ALTER TABLE "QualityProfiles" ADD COLUMN "Items" TEXT"

</code>

==== Resolving the issue ====
In the event of a migration issue there is not much you can do immediately, if the issue is specific to you (or there are not yet any posts), please create a post on [https://reddit.com/r/{{{ARRNAME}}} our subreddit] or swing by our discord, if there are others with the same issue, then rest assured we are working on it.

==== Manually upgrading ====
Grab the latest release from [{{{ARR_WEBSITE}}} our website]

Install the update (.exe) or extract (.zip) the contents over your existing installation and re-run {{{ARRNAME}}} as you normally would.

== Downloads and Importing ==

Downloading and importing is where ''most'' people experience issues. From a high level perspective, {{{ARRNAME}}} 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.

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

When you reach out for help, be sure to read [[#Asking for Help|asking for help]] so that you can provide us with the details we’ll need.

=== Testing the Download Client ===

Ensure your download client(s) are running. Start by testing the download client, if it doesn’t work you’ll be able to see details in the trace level logs. You should find a URL you can put into your browser and see if it works. It could be a connection problem, which could indicate a wrong ip, hostname, port or even a firewall blocking access. It might be obvious, like an authentication problem where you’ve gotten the username, password or apikey wrong.

=== Testing a Download ===

Now we’ll try a download, pick a {{{MEDIA}}} and do a manual search. Pick one of those files and attempt to download it. Does it get sent to the download client? Does it end up with the correct category? Does it show up in Activity? Does it end up in the trace level logs during the '''Check For Finished Download''' task which runs roughly every minute? Does it get correctly parsed during that task? Does the queued up download have a reasonable name? Since {{{ARRNAME}}} searches by '''{{{SEARCHSOURCE}}}''', on most indexers/trackers, it can queue one up with a name that it can’t recognize.

=== Testing an Import ===

Import issues should almost always manifest as an item in Activity with an orange icon you can hover to see the error. If they’re not showing up in Activity, this is the issue you need to focus on first so go back and figure that out. Most import errors are ''permissions'' issues, remember that {{{ARRNAME}}} needs to be able to read and write in the download folder. Sometimes, permissions in the library folder can be at fault too, so be sure to check both.

Incorrect path issues are possible too, though less common in normal setups. The key to understanding path issues is knowing that {{{ARRNAME}}} gets the path to the download ''from'' the download client, via its API. This becomes a problem in more unique use cases, like the download client running on a different system (maybe even OS!). It can also occur in a Docker setup, when volumes are not done well. A remote path map is a good solution where you don’t have control, like a seedbox setup. On a Docker setup, fixing the paths is a better option.

=== Common Problems ===

==== Download Client's WebUI is not enabled ====
{{{ARRNAME}}} talks to you download client via it's API and accesses it via the client's webui. You must ensure the client's webui is enabled and the port it is using does not conflict with any other client ports in use or ports in use on your system.

==== SSL in use and incorrectly configured ====
Ensure SSL encryption is not turned on if you're using both your {{{ARRNAME}}} instance and your download client on a local network. See [[{{{ARRNAME}}}_FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

==== Can’t see share on Windows ====

The default user for a Windows service is '''SYSTEM''' which typically doesn’t have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [[{{{ARRNAME}}} FAQ#Why can’t {{{ARRNAME}}} see my files on a remote server?|why can’t {{{ARRNAME}}} see my files on a remote server]] for details.

==== Mapped network drives are not reliable ====

While mapped network drives like <code>X:\</code> are convenient, they aren’t as reliable as UNC paths like <code>\\server\share</code> and they’re also not available before login. Setup {{{ARRNAME}}} and your download client(s) so that they use UNC paths as needed. If your library is on a share, you’d make sure your root folders are using UNC paths. If your download client sends to a share, that is where you’ll need to configure UNC paths since {{{ARRNAME}}} gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don’t use them for automation.

==== Docker and user, group, ownership, permissions and paths ====

Docker adds another layer of complexity that is easy to get wrong, but still end up with a setup that functions, but has various problems. Instead of going over them here, read this wiki article [[Docker Guide|for these automation software and Docker]] which is all about user, group, ownership, permissions and paths. It isn’t specific to any Docker system, instead it goes over things at a high level so that you can implement them in your own environment.

==== Permissions on the Library Folder ====
Don’t forget to check permissions and ownership of the ''destination''. It is easy to get fixated on the download’s ownership and permissions and that is ''usually'' the cause of permissions related issues, but it ''could'' be the destination as well. Check that the destination folder(s) exist. Check that a destination ''file'' doesn’t already exist or can’t be deleted or moved to recycle bin. Check that ownership and permissions allow the downloaded file to be copied, hard linked or moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the root folder.

==== Permissions on the Downloads Folder ====

Don’t forget to check permissions and ownership of the ''source''. It is easy to get fixated on the destination's ownership and permissions and that is a ''possible'' cause of permissions related issues, but it ''typically'' is the source. Check that the source folder(s) exist. Check that ownership and permissions allow the downloaded file to be copied/hardlinked or copy+delete/moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the downloads folder.

==== Download folder and library folder not different folders ====

The download client should download into a folder accessible by {{{ARRNAME}}} and that is not your root/library folder; {{{ARRNAME}}} should import from that separate download folder into your Library folder.

You should never download directly into your root folder. You also should not use your root folder as the download client's completed folder or incomplete folder.

If you download right into your library folder, you’ll end up with multiple copies of your media and when there are import issues, which there will be, you may not notice because your media server will see the download client copy.

The download folder will also be a hot mess of poorly named folders and files while your library folder will be nice and neat.

This frequently causes other random import issues as well.

==== Incorrect category ====

{{{ARRNAME}}} should be setup to use a category so that it only tries to process its own downloads. It is rare that a torrent submitted by {{{ARRNAME}}} gets added without the correct category, but it can happen. If you’re adding torrents manually and want {{{ARRNAME}}} to process them, they’ll need to have the correct category. It can be set at any time, since {{{ARRNAME}}} tries to process downloads every minute.

==== Packed torrents ====

If your torrent is packed in <code>.rar</code> files, you’ll need to setup extraction. We recommend [https://github.com/davidnewhall/unpackerr unpackerr]. One issue to look out for with packed torrents is that the video file will be copied or hard linked like normal, but it isn’t needed since the <code>.rar</code> files are seeding. That means if you’re using a ''copy'' setup, the torrent will be consuming double the space. And if you’re using a hard link setup, your torrent folder will be a little messier because of the unneeded file. This can be mitigated with a [https://gist.github.com/fryfrog/94716e7e27ba38dff57c7631d9f58bed cleanup script].

==== Repeated downloads ====

There are a few causes of repeated downloads, but a recent one is related to the Indexer restriction in Release Profiles. Because the indexer ''isn’t'' stored with the data, any preferred word scores are ''zero'' for media in your library, ''but'' during “RSS” and search, they’ll be applied. This gets you into a loop where you download the items again and again because it looks like an upgrade, then isn’t, then shows up again and looks like an upgrade, then isn’t. Don’t restrict your release profile to an indexer.

==== Usenet download misses import ====

{{{ARRNAME}}} only looks at the 60 most recent downloads in SABnzbd and NZBGet, so if you ''keep'' your history this means that during large queues with import issues, downloads can be silently missed and not imported. The best way to avoid that is to keep your history clear, so that any items that still appear need investigating. You can achieve this by enabling Remove under Completed and Failed Download Handler. In nzbget, this will move items to the ''hidden'' history which is great. Unfortunately, sabnzbd does not have a similar feature. The best you can achieve there is to use the nzb backup folder.

==== Download client clearing items ====

The download client should ''not'' be responsible for removing downloads. Usenet clients should be configured so they ''don’t'' remove downloads from history. Torrent clients should be setup so they ''don’t'' remove torrents when they’re finished seeding (pause or stop instead). This is because {{{ARRNAME}}} communicates with the download client to know what to import, so if they’re ''removed'' there is nothing to be imported… even if there is a folder full of files.

For Sabnzbd, this is handled with the History Retention setting.

==== Download cannot be matched to a library item====
For various reasons, releases cannot be parsed once's grabbed and sent to the download client. Activity -> Options -> Shown Unknown will display all items not otherwise ignored / already imported within {{{ARRNAME}}}'s download client category. These will typically need to be manually mapped and imported.

This can also occur if you have a release in your download client but that media item (movie/episode/book/song) does not exist in the application.

=== Problem Not Listed ===
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

== Searches Indexers and Trackers ==

=== Turn logging up to trace ===

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

=== Testing an Indexer or Tracker ===

When you test an indexer or tracker, in debug or trace logs you can find the URL used. An example of a successful test is below, you can see it query the indexer via a specific URL with specific parameters and then the response. You test this url in your browser like <code>{{{QUERYSTRING}}}</code> replacing the <code>apikey=(removed)</code> with the correct apikey like <code>apikey=123</code>. You can experiment with the parameters if you’re getting an error from the indexer or see if you have connectivity issues if it doesn’t even work. After you’ve tested in your own browser, you should test from the system {{{ARRNAME}}} is running on ''if'' you haven’t already.

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block}}

=== Testing a Search ===
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_testing_a_search}}

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers1.png|thumb|none|750px]]

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers2.png|thumb|none|750px]]

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block2}}

Here you can see the ''full'' trace log below
{{#lst:Troubleshooting Misc|{{{ARRNAME2}}}_trace_logs_example}}

=== Common Problems ===

==== Media is Unmonitored ====
The {{{MEDIA}}} is/are not monitored.

==== Wrong categories ====

Incorrect categories is probably the most common cause of results showing in manual searches of an indexer/tracker, but ''not'' in {{{ARRNAME}}}. The indexer/tracker ''should'' show the category in the search results, which should help you figure out what is missing. If you’re using Jackett, each tracker has a list of specifically supported categories. Make sure you’re using the correct ones for Categories. I find it helpful to have the list visible in one browser window while I edit the entry in {{{ARRNAME}}}.
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_type}}
==== Wrong results ====

Sometimes indexers will return completely unrelated results, {{{ARRNAME}}} will feed in parameters to limit the search to a {{{SEARCHSOURCE}}}, but the results returned are completely unrelated. Or sometimes, mostly related with a few incorrect results. The first is usually an indexer problem and you’ll be able to tell from the trace logs which is causing it. You can disable that indexer and report the problem. The other is usually categorized releases which should be reportable on the indexer/tracker.

==== Certificate validation ====

You’ll be connecting to most indexers/trackers via https, so you’ll need that to work properly on your system. That means your time zone and time both need to be set ''correctly''. It also means your system certificates need to be up to date.

==== Hitting rate limits ====

If you run your {{{ARRNAME}}} through a VPN or proxy, you may be competing with 10s or 100s or 1000s of other people all trying to use services like {{{SEARCHSOURCE}}}, theXEM ,and/or your indexers and trackers. Rate limiting and DDOS protection are often done by IP address and your VPN/proxy exit point is ''one'' IP address. Unless you’re in a repressive country like China, Australia or South Africa you don’t need to VPN/proxy {{{ARRNAME}}}.

Rarbg has a tendency to have some sort of rate limiting within their API and displays as responding with no results.

==== Using the Jackett /all endpoint ====

The Jackett <code>/all</code> endpoint is convenient, but that is its only benefit. Everything else is potential problems, so adding each tracker individually is recommended.

[https://github.com/Jackett/Jackett#aggregate-indexers Even Jackett says it should be avoided and should not be used.]

Using the all endpoint has no advantages (besides reduced management overhead), only disadvantages:
* you lose control over indexer specific settings (categories, search modes, etc.)
* mixing search modes (IMDB, query, etc.) might cause low-quality results
* indexer specific categories (>= 100000) can't be used.
* slow indexers will slow down the overall result
* total results are limited to 1000

Adding each indexer separately It allows for fine tuning of categories on a per indexer basis, which can be a problem with the <code>/all</code> end point if using the wrong category causes errors on some trackers. In {{{ARRNAME}}}, each indexer is limited to 1000 results if pagination is supported or 100 if not, which means as you add more and more trackers to Jackett, you’re more and more likely to clip results. Finally, if ''one'' of the trackers in <code>/all</code> returns an error, {{{ARRNAME}}} will disable it and now you don’t get any results.

==== Problem Not Listed ====
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

=== Errors ===

These are some of the common errors you may see when adding an indexer

==== The underlying connection was closed: An unexpected error occurred on a send. ====

This is caused by the indexer using a SSL protocol not supported by .net 4.5, to resolve this you will need to install .net 4.5, which is available on Vista/Server 2008 and above (if you’re on XP/Server 2003 its time to upgrade).

==== The request timed out ====

{{{ARRNAME}}} seems to have issues with certain TLS versions or configurations. If you get the following error messages in your log:
<pre>System.Net.WebException: The request timed out: ’https://example.org/api?t=caps&apikey=(removed) —> System.Net.WebException: The request timed out</pre>

And you can see the following in the trace log file:
<pre><DATE&TIME>|Trace|FallbackHttpDispatcher|Curl not available, using default WebClient. </pre>

You might fix it by installing libcurl3. On Ubuntu/Debian use;
<pre>apt install libcurl3</pre>

This can also be caused by:
* improperly configured or use of a VPN
* improperly configured or use of a proxy
* local DNS issues
* local IPv6 issues

Settings Indexers

2021-05-13T01:28:05Z

Bakerboy448: /* Lidarr */

== Settings Indexers ==
=== Overview ===
==== Radarr ====
<section begin=radarr_settings_indexers />
Once you're here you'll be adding the indexer/tracker that you'll be using to actually download any of your files.
If you're curious on how Radarr works with your indexer/tracker click [[Radarr FAQ |here]]
<section end=radarr_settings_indexers />
==== Sonarr ====
<section begin=sonarr_settings_indexers />
Once you're here you'll be adding the indexer/tracker that you'll be using to actually download any of your files.
If you're curious on how Sonarr works with your indexer/tracker click [[Sonarr FAQ |here]]
<section end=sonarr_settings_indexers />
==== Lidarr ====
<section begin=lidarr_settings_indexers />
Once you're here you'll be adding the indexer/tracker that you'll be using to actually download any of your files.
If you're curious on how Lidarr works with your indexer/tracker click [[Lidarr FAQ |here]]
<section end=lidarr_settings_indexers />
==== Readarr ====
<section begin=readarr_settings_indexers />
Once you're here you'll be adding the indexer/tracker that you'll be using to actually download any of your files.
If you're curious on how Readarr works with your indexer/tracker click [[Readarr FAQ |here]]
<section end=readarr_settings_indexers />

=== Indexer Settings===
==== Radarr ====
<section begin=radarr_settings_indexers_settings/>
Once you've clicked the <code>+</code> button to add a new indexer you'll be presented with a new window with many different options. For the purposes of this wiki Readarr considers both Usenet Indexers and Torrent Trackers as "Indexers".

There are two sections here: Usenet and Torrents. Based upon what download client you'll be using you'll want to select the type of indexer you'll be going with.

More information on Indexers and Trackers can be found [[Definitions#Indexers/Trackers|here]]

===== Usenet Indexer Configuration =====
* Newznab - Here you'll find presets of popular usenet indexers (that are pre-filled out, all you'll need is your API key which is provided by the usenet indexer of your choice) along with the ability to create a custom Indexer
* An excellent software that works with usenet and integrates quite well with Radarr is [https://github.com/theotherp/nzbhydra2 NZBHydra2]
** Regardless of if you select a pre filled out indexer or a custom indexer setup you'll be presented with a new window to input all your settings
** Choose from the presets or add a custom indexer (such as NZBHydra2)
** Name - The name of the indexer in Radarr
** Enable RSS - If enabled, use this indexer to watch for files that are wanted and missing or have not yet reached their cutoff.
** Enable Automatic Search - If enabled, use this indexer for automatic searches including Search on Add
** Enable Interactive Search - If enabled, use this indexer for manual interactive searches.
** URL - The indexer provided URL of the indexer such as <code>https://api.nzbgeek.info</code>.
** ''API Path'' - The indexer provided path to the api. This is typically <code>/api</code>
** ''Multiple Languages'' - Define what <code>MULTI</code> means for this indexer.
** API Key - The indexer provided key to access the API.
** ''Categories'' - Default categories will be used unless edited. It is likely these default categories are suboptimal. Upon editing this setting, Radarr queries the indexer for its available categories and displays them in a selectable a list. The stale defaults will clear as soon as a category is toggled.
** ''Additional Parameters'' - Additional Newznab parameters to add to the query link
** ''Remove year from search string'' - Should Radarr remove the year after the title when searching this indexer.
** ''Indexer Priority'' - Priority of this indexer to prefer one indexer over another in release tiebreaker scenarios. 1 is highest priority and 50 is lowest priority.

===== Torrent Tracker Configuration =====
* As with Usenet there are an assortment of prefilled out Torrent tracker information. If you are not a member of any of these these specific trackers they will not do you any good.
* One of the best and simplest ways to utilize Torrent trackers with Sonarr is to utilize a second program called [https://github.com/Jackett/Jackett Jackett]. This software pairs well with Sonarr as a search indexer that houses all your information and sends it to Sonarr.
* Torznab - This option will set you up with a Jackett preset, if you utilize multiple trackers you'll need to have each entry have a unique name
* Torznab Indexer
**Choose from the presets or add a custom indexer (such as Jackett)
** Name - The name of the indexer in Radarr
** Enable RSS - If enabled, use this indexer to watch for files that are wanted and missing or have not yet reached their cutoff.
** Enable Automatic Search - If enabled, use this indexer for automatic searches including Search on Add
** Enable Interactive Search - If enabled, use this indexer for manual interactive searches.
** URL - The indexer provided URL of the indexer such as <code>https://api.nzbgeek.info</code>.
** ''API Path'' - The indexer provided path to the api. This is typically <code>/api</code>
** ''Multiple Languages'' - Define what <code>MULTI</code> means for this indexer.
** API Key - The indexer provided key to access the API.
** ''Categories'' - Default categories will be used unless edited. It is likely these default categories are suboptimal. Upon editing this setting, Radarr queries the indexer for its available categories and displays them in a selectable a list. The stale defaults will clear as soon as a category is toggled.
** ''Additional Parameters'' - Additional Newznab parameters to add to the query link
** ''Remove year from search string'' - Should Radarr remove the year after the title when searching this indexer.
** ''Minimum Seeders'' - The minimum number of seeders required for a release from this tracker to be grabbed.
** ''Seed Ratio'' - If empty, use the download client default. Otherwise, the minimum seed ratio required for your download client to meet for releases from this indexer prior to it being paused by your client and removed by Sonarr (Requires Completed Download Handling - Remove enabled)
** ''Seed Time'' - If empty, use the download client default. Otherwise, the minimum seed time in minutes required for your download client to meet for releases from this indexer prior to it being paused by your client and removed by Sonarr (Requires Completed Download Handling - Remove enabled)
** ''Required Flags'' - What [[Definitions#Indexer_Flags| indexer flags]] are required for this indexer?
** ''Indexer Priority'' - Priority of this indexer to prefer one indexer over another in release tiebreaker scenarios. 1 is highest priority and 50 is lowest priority.
<section end=radarr_settings_indexers_settings/>
==== Sonarr ====
<section begin=sonarr_settings_indexers_settings/>
Once you've clicked the <code>+</code> button to add a new indexer you'll be presented with a new window with many different options. For the purposes of this wiki Readarr considers both Usenet Indexers and Torrent Trackers as "Indexers".

There are two sections here: Usenet and Torrents. Based upon what download client you'll be using you'll want to select the type of indexer you'll be going with.

More information on Indexers and Trackers can be found [[Definitions#Indexers/Trackers|here]]

===== Usenet Indexer Configuration =====
* Newznab - Here you'll find presets of popular usenet indexers (that are pre-filled out, all you'll need is your API key which is provided by the usenet indexer of your choice) along with the ability to create a custom Indexer
* An excellent software that works with usenet and integrates quite well with Sonarr is [https://github.com/theotherp/nzbhydra2 NZBHydra2]
** Regardless of if you select a pre filled out indexer or a custom indexer setup you'll be presented with a new window to input all your settings
** Choose from the presets or add a custom indexer (such as NZBHydra2)
** Name - The name of the indexer in Sonarr
** Enable RSS - If enabled, use this indexer to watch for files that are wanted and missing or have not yet reached their cutoff.
** Enable Automatic Search - If enabled, use this indexer for automatic searches including Search on Add
** Enable Interactive Search - If enabled, use this indexer for manual interactive searches.
** URL - The indexer provided URL of the indexer such as <code>https://api.nzbgeek.info</code>.
** ''API Path'' - The indexer provided path to the api. This is typically <code>/api</code>
** API Key - The indexer provided key to access the API.
** Categories - Default categories will be used unless edited. It is likely these default categories are suboptimal. Upon editing this setting, Sonarr queries the indexer for its available categories and displays them in a selectable a list. The stale defaults will clear as soon as a category is toggled.
** Anime Categories - The categories that Sonarr will use for Anime searches No categories will be used unless edited. Upon editing this setting, Sonarr queries the indexer for its available categories and displays them in a selectable a list. The stale defaults will clear as soon as a category is toggled.
** ''Additional Parameters'' - Additional Newznab parameters to add to the query link
** ''Indexer Priority'' - Priority of this indexer to prefer one indexer over another in release tiebreaker scenarios. 1 is highest priority and 50 is lowest priority.

===== Torrent Tracker Configuration =====
* As with Usenet there are an assortment of prefilled out Torrent tracker information. If you are not a member of any of these these specific trackers they will not do you any good.
* One of the best and simplest ways to utilize Torrent trackers with Sonarr is to utilize a second program called [https://github.com/Jackett/Jackett Jackett]. This software pairs well with Sonarr as a search indexer that houses all your information and sends it to Sonarr.
* Torznab - This option will set you up with a Jackett preset, if you utilize multiple trackers you'll need to have each entry have a unique name
* Torznab Indexer
**Choose from the presets or add a custom indexer (such as Jackett)
** Name - The name of the indexer in Sonarr
** Enable RSS - If enabled, use this indexer to watch for files that are wanted and missing or have not yet reached their cutoff.
** Enable Automatic Search - If enabled, use this indexer for automatic searches including Search on Add
** Enable Interactive Search - If enabled, use this indexer for manual interactive searches.
** URL - The indexer provided URL of the indexer such as <code>http://localhost:9117/jackett/api/v2.0/indexers/torrentdb/results/torznab/</code>.
** ''API Path'' - The indexer provided path to the api. This is typically <code>/api</code>
** API Key - The indexer provided key to access the API.
** Categories - Default categories will be used unless edited. It is likely these default categories are suboptimal. Upon editing this setting, Sonarr queries the indexer for its available categories and displays them in a selectable a list. The stale defaults will clear as soon as a category is toggled.
** Anime Categories - The categories that Sonarr will use for Anime searches No categories will be used unless edited. Upon editing this setting, Sonarr queries the indexer for its available categories and displays them in a selectable a list. The stale defaults will clear as soon as a category is toggled.
** ''Additional Parameters'' - Additional Torznab parameters to add to the query link
** ''Minimum Seeders'' - The minimum number of seeders required for a release from this tracker to be grabbed.
** ''Seed Ratio'' - If empty, use the download client default. Otherwise, the minimum seed ratio required for your download client to meet for releases from this indexer prior to it being paused by your client and removed by Sonarr (Requires Completed Download Handling - Remove enabled)
** ''Seed Time'' - If empty, use the download client default. Otherwise, the minimum seed time in minutes required for your download client to meet for releases from this indexer prior to it being paused by your client and removed by Sonarr (Requires Completed Download Handling - Remove enabled)
** ''Seed Time'' - If empty, use the download client default. Otherwise, the minimum seed time in minutes required for your download client to meet for season pack releases from this indexer prior to it being paused by your client and removed by Sonarr (Requires Completed Download Handling - Remove enabled)
** ''Indexer Priority'' - Priority of this indexer to prefer one indexer over another in release tiebreaker scenarios. 1 is highest priority and 50 is lowest priority.
<section end=sonarr_settings_indexers_settings/>
==== Lidarr ====
<section begin=lidarr_settings_indexers_settings/>
Once you've clicked the <code>+</code> button to add a new indexer you'll be presented with a new window with many different options. For the purposes of this wiki Readarr considers both Usenet Indexers and Torrent Trackers as "Indexers".

There are two sections here: Usenet and Torrents. Based upon what download client you'll be using you'll want to select the type of indexer you'll be going with.

More information on Indexers and Trackers can be found [[Definitions#Indexers/Trackers|here]]

===== Usenet Indexer Configuration =====
* Newznab - Here you'll find presets of popular usenet indexers (that are pre-filled out, all you'll need is your API key which is provided by the usenet indexer of your choice) along with the ability to create a custom Indexer
* An excellent software that works with usenet and integrates quite well with Lidarr is [https://github.com/theotherp/nzbhydra2 NZBHydra2]
** Regardless of if you select a pre filled out indexer or a custom indexer setup you'll be presented with a new window to input all your settings
** Choose from the presets or add a custom indexer (such as NZBHydra2)
** Name - The name of the indexer in Lidarr
** Enable RSS - If enabled, use this indexer to watch for files that are wanted and missing or have not yet reached their cutoff.
** Enable Automatic Search - If enabled, use this indexer for automatic searches including Search on Add
** Enable Interactive Search - If enabled, use this indexer for manual interactive searches.
** URL - The indexer provided URL of the indexer such as <code>https://api.nzbgeek.info</code>.
** ''API Path'' - The indexer provided path to the api. This is typically <code>/api</code>
** ''Multiple Languages'' - Define what <code>MULTI</code> means for this indexer.
** API Key - The indexer provided key to access the API.
** ''Categories'' - Default categories will be used unless edited. It is likely these default categories are suboptimal. Upon editing this setting, Lidarr queries the indexer for its available categories and displays them in a selectable a list. The stale defaults will clear as soon as a category is toggled.
** ''Additional Parameters'' - Additional Newznab parameters to add to the query link
** ''Remove year from search string'' - Should Lidarr remove the year after the title when searching this indexer.
** ''Indexer Priority'' - Priority of this indexer to prefer one indexer over another in release tiebreaker scenarios. 1 is highest priority and 50 is lowest priority.

===== Torrent Tracker Configuration =====
* As with Usenet there are an assortment of prefilled out Torrent tracker information. If you are not a member of any of these these specific trackers they will not do you any good.
* One of the best and simplest ways to utilize Torrent trackers with Sonarr is to utilize a second program called [https://github.com/Jackett/Jackett Jackett]. This software pairs well with Sonarr as a search indexer that houses all your information and sends it to Sonarr.
* Torznab - This option will set you up with a Jackett preset, if you utilize multiple trackers you'll need to have each entry have a unique name
* Torznab Indexer
**Choose from the presets or add a custom indexer (such as Jackett)
** Name - The name of the indexer in Lidarr
** Enable RSS - If enabled, use this indexer to watch for files that are wanted and missing or have not yet reached their cutoff.
** Enable Automatic Search - If enabled, use this indexer for automatic searches including Search on Add
** Enable Interactive Search - If enabled, use this indexer for manual interactive searches.
** URL - The indexer provided URL of the indexer such as <code>https://api.nzbgeek.info</code>.
** ''API Path'' - The indexer provided path to the api. This is typically <code>/api</code>
** ''Multiple Languages'' - Define what <code>MULTI</code> means for this indexer.
** API Key - The indexer provided key to access the API.
** ''Categories'' - Default categories will be used unless edited. It is likely these default categories are suboptimal. Upon editing this setting, Lidarr queries the indexer for its available categories and displays them in a selectable a list. The stale defaults will clear as soon as a category is toggled.
** ''Additional Parameters'' - Additional Newznab parameters to add to the query link
** ''Remove year from search string'' - Should Lidarr remove the year after the title when searching this indexer.
** ''Minimum Seeders'' - The minimum number of seeders required for a release from this tracker to be grabbed.
** ''Seed Ratio'' - If empty, use the download client default. Otherwise, the minimum seed ratio required for your download client to meet for releases from this indexer prior to it being paused by your client and removed by Sonarr (Requires Completed Download Handling - Remove enabled)
** ''Seed Time'' - If empty, use the download client default. Otherwise, the minimum seed time in minutes required for your download client to meet for releases from this indexer prior to it being paused by your client and removed by Sonarr (Requires Completed Download Handling - Remove enabled)
** ''Required Flags'' - What [[Definitions#Indexer_Flags| indexer flags]] are required for this indexer?
** ''Indexer Priority'' - Priority of this indexer to prefer one indexer over another in release tiebreaker scenarios. 1 is highest priority and 50 is lowest priority.
<section end=lidarr_settings_indexers_settings/>

==== Readarr ====
<section begin=readarr_settings_indexers_settings/>
Once you've clicked the <code>+</code> button to add a new indexer you'll be presented with a new window with many different options. For the purposes of this wiki Readarr considers both Usenet Indexers and Torrent Trackers as "Indexers".

There are two sections here: Usenet and Torrents. Based upon what download client you'll be using you'll want to select the type of indexer you'll be going with.

More information on Indexers and Trackers can be found [[Definitions#Indexers/Trackers|here]]

===== Usenet Indexer Configuration =====
* Newznab - Here you'll find presets of popular usenet indexers (that are pre-filled out, all you'll need is your API key which is provided by the usenet indexer of your choice) along with the ability to create a custom Indexer
* An excellent software that works with usenet and integrates quite well with Readarr is [https://github.com/theotherp/nzbhydra2 NZBHydra2]
** Regardless of if you select a pre filled out indexer or a custom indexer setup you'll be presented with a new window to input all your settings
** Choose from the presets or add a custom indexer (such as NZBHydra2)
** Name - The name of the indexer in Readarr
** Enable RSS - If enabled, use this indexer to watch for files that are wanted and missing or have not yet reached their cutoff.
** Enable Automatic Search - If enabled, use this indexer for automatic searches including Search on Add
** Enable Interactive Search - If enabled, use this indexer for manual interactive searches.
** URL - The indexer provided URL of the indexer such as <code>https://api.nzbgeek.info</code>.
** ''API Path'' - The indexer provided path to the api. This is typically <code>/api</code>
** API Key - The indexer provided key to access the API.
** ''Categories'' - Default categories will be used unless edited. It is likely these default categories are suboptimal. Upon editing this setting, Readarr queries the indexer for its available categories and displays them in a selectable a list. The stale defaults will clear as soon as a category is toggled.
** ''Early Download Limit'' - Number of days before the release date that Readarr will download from this indexer. If empty then no limit.
** ''Additional Parameters'' - Additional Newznab parameters to add to the query link
** ''Indexer Priority'' - Priority of this indexer to prefer one indexer over another in release tiebreaker scenarios. 1 is highest priority and 50 is lowest priority.

===== Torrent Tracker Configuration =====
* As with Usenet there are an assortment of prefilled out Torrent tracker information. If you are not a member of any of these these specific trackers they will not do you any good.
* One of the best and simplest ways to utilize Torrent trackers with Readarr is to utilize a second program called [https://github.com/Jackett/Jackett Jackett]. This software pairs well with Readarr as a search indexer that houses all your information and sends it to Readarr.
* Torznab - This option will set you up with a Jackett preset, if you utilize multiple trackers you'll need to have each entry have a unique name
* Torznab Indexer
**Choose from the presets or add a custom indexer (such as Jackett)
** Name - The name of the indexer in Readarr
** Enable RSS - If enabled, use this indexer to watch for files that are wanted and missing or have not yet reached their cutoff.
** Enable Automatic Search - If enabled, use this indexer for automatic searches including Search on Add
** Enable Interactive Search - If enabled, use this indexer for manual interactive searches.
** URL - The indexer provided URL of the indexer such as <code>http://localhost:9117/jackett/api/v2.0/indexers/torrentdb/results/torznab/</code>.
** ''API Path'' - The indexer provided path to the api. This is typically <code>/api</code>
** API Key - The indexer provided key to access the API.
** ''Categories'' - Default categories will be used unless edited. It is likely these default categories are suboptimal. Upon editing this setting, Readarr queries the indexer for its available categories and displays them in a selectable a list. The stale defaults will clear as soon as a category is toggled.
** ''Early Download Limit'' - Number of days before the release date that Readarr will download from this indexer. If empty then no limit.
** ''Additional Parameters'' - Additional Torznab parameters to add to the query link
** ''Minimum Seeders'' - The minimum number of seeders required for a release from this tracker to be grabbed.
** ''Seed Ratio'' - If empty, use the download client default. Otherwise, the minimum seed ratio required for your download client to meet for releases from this indexer prior to it being paused by your client and removed by Readarr (Requires Completed Download Handling - Remove enabled)
** ''Seed Time'' - If empty, use the download client default. Otherwise, the minimum seed time in minutes required for your download client to meet for releases from this indexer prior to it being paused by your client and removed by Readarr (Requires Completed Download Handling - Remove enabled)
** ''Indexer Priority'' - Priority of this indexer to prefer one indexer over another in release tiebreaker scenarios. 1 is highest priority and 50 is lowest priority.
<section end=readarr_settings_indexers_settings/>

=== Options ===
==== Radarr ====
<section begin=radarr_settings_indexers_options />
* Minimum Age - Usenet only: Minimum age in minutes of NZBs before they are grabbed. Use this to give new releases time to propagate to your usenet provider.
* Retention - Usenet only: Set to zero to set for unlimited retention
* Maximum Size - Maximum size for a release to be grabbed in MB. Set to zero to set to unlimited
* Prefer Indexer Flag - If enabled, prioritize releases with special flags
** See [[Definitions#Indexer Flags|Indexer Flags]] for more details
* Availability Delay - Amount of time before (-#) or after (#) the available date to search for Movie
** This is helpful to delay searching for a release to give the community time to perform the best encodes
* ''RSS Sync Interval'' - Interval in minutes. Set to zero to disable (this will stop all automatic release grabbing) Minimum: 10 minutes Maximum: 120 minutes
** Please see [[Radarr FAQ#How does Radarr work?|How does Radarr work?]] for a better understanding of how RSS Sync will help you
** Note: If Radarr has been offline for an extended period of time, Radarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn’t been too long will be able to process the releases it would have missed and avoid you needing to perform a search for the missed releases.
* ''Whitelisted Subtitle Tags'' - Subtitle tags set here will not be considered hardcoded
* ''Allow Hardcoded Subs'' - If enabled, detected hardcoded subs will be automatically downloaded
<section end=radarr_settings_indexers_options />

==== Sonarr ====
<section begin=sonarr_settings_indexers_options />
* Minimum Age - Usenet only: Minimum age in minutes of NZBs before they are grabbed. Use this to give new releases time to propagate to your usenet provider.
* Retention - Usenet only: Set to zero to set for unlimited retention
* Maximum Size - Maximum size for a release to be grabbed in MB. Set to zero to set to unlimited
* RSS Sync interval - Interval in minutes. Set to zero to disable (this will stop all automatic release grabbing) Minimum: 10 minutes Maximum: 120 minutes
** Please see [[Sonarr FAQ#How does Sonarr find episodes?|How does Sonarr find episodes?]] for a better understanding of how RSS Sync will help you
** Note: If Sonarr has been offline for an extended period of time, Sonarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn’t been too long will be able to process the releases it would have missed and avoid you needing to perform a search for the missed releases.
<section end=sonarr_settings_indexers_options />

==== Lidarr ====
<section begin=lidarr_settings_indexers_options />
* Minimum Age - Usenet only: Minimum age in minutes of NZBs before they are grabbed. Use this to give new releases time to propagate to your usenet provider.
* Maximum Size - Maximum size for a release to be grabbed in MB. Set to zero to set to unlimited
* Retention - Usenet only: Set to zero to set for unlimited retention
* RSS Sync interval - Interval in minutes. Set to zero to disable (this will stop all automatic release grabbing) Minimum: 10 minutes Maximum: 120 minutes
** Please see [[Lidarr FAQ#How does Lidarr work?|How does Lidarr work?]] for a better understanding of how RSS Sync will help you
** Note: If Lidarr has been offline for an extended period of time, Lidarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn’t been too long will be able to process the releases it would have missed and avoid you needing to perform a search for the missed releases.
<section end=lidarr_settings_indexers_options />

==== Readarr ====
<section begin=readarr_settings_indexers_options />
* Minimum Age - Usenet only: Minimum age in minutes of NZBs before they are grabbed. Use this to give new releases time to propagate to your usenet provider.
* Maximum Size - Maximum size for a release to be grabbed in MB. Set to zero to set to unlimited
* Retention - Usenet only: Set to zero to set for unlimited retention
* RSS Sync interval - Interval in minutes. Set to zero to disable (this will stop all automatic release grabbing) Minimum: 10 minutes Maximum: 120 minutes
** Please see [[Readarr FAQ#How does Readarr work?|How does Readarr work?]] for a better understanding of how RSS Sync will help you
** Note: If Readarr has been offline for an extended period of time, Readarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn’t been too long will be able to process the releases it would have missed and avoid you needing to perform a search for the missed releases.
<section end=readarr_settings_indexers_options />

=== Restrictions ===
==== Radarr ====
<section begin=radarr_settings_indexers_restrictions />
* Here you'll be able to set global restrictions based upon a couple of parameters
* Click the <code>+</code> and a new window will open
** Must Contain - Within this field you can tell Radarr that if a release does not contain a certain string then Radarr will not grab that release. This is case insensitive by default and regex can be used.
** Must Not Contain - Within this field you can tell Radarr that if a release does contain a certain string then Radarr will not grab that release. This is case insensitive by default and regex can be used.
** Tags - Here you can apply these settings to movies with at least one of the given tag
*** Please see [[#Tags|Tags]]
<section end=radarr_settings_indexers_restrictions />
==== Sonarr ====
<section begin=sonarr_settings_indexers_restrictions />
Not in Sonarr
<section end=sonarr_settings_indexers_restrictions />
==== Lidarr ====
<section begin=lidarr_settings_indexers_restrictions />
Not in Lidarr
<section end=lidarr_settings_indexers_restrictions />
==== Readarr ====
<section begin=readarr_settings_indexers_restrictions />
Not in Readarr
<section end=readarr_settings_indexers_restrictions />

=== Supported Indexers ===
==== Radarr ====
<section begin=radarr_settings_indexers_supported_indexers />
* Usenet
** Newznab
*** Newznab is a standardized API used by many usenet indexing sites.
*** Many presets are available, but all require an API key to be accessible.
** Omgwtfnzbs
*** This indexer ''also'' supports newznab and is available as one of the above presets.
*** Website: https://omgwtfnzbs.me/

Torrents
** filelist.io
*** Private Tracker
*** Website: https://filelist.io/
** HDBits
*** Private Tracker
*** Website: https://hdbits.org
** IP Torrents
*** Private Tracker
*** Website: https://iptorrents.com
** Nyaa
*** Website: http://www.nyaa.si/
*** Torrent Indexer for Japanese media (Anime) exclusively.
** Pass the Popcorn
*** Private Tracker
*** Website: https://passthepopcorn.me
** Rarbg
*** Website: https://rarbg.to/
** Torrent RSS Feed
*** Generic torrent RSS feed parser.
*** '''NOTE:''' The RSS feed must contain a pubdate. The release size is recommended as well.
** TorrentPotato
*** Website: [https://github.com/CouchPotato/CouchPotatoServer/wiki/Couchpotato-torrent-provider TorrentPotato]
** Torznab
*** Known indexers: Anime Tosho and Nyaa Pantsu as well as Jackett.
*** Torznab is a wordplay on Torrent and Newznab. It uses the same structure and syntax as the Newznab API specification, but exposing torrent-specific attributes and .torrent files. Thus supports a recent rss feed AND backlog searching capabilities. The specification is not maintained nor supported by the Newznab organization. (The same api specification is shared with nZEDb)
*** At this point it’s unlikely your favorite tracker supports this. Thus you can use [https://github.com/Jackett/Jackett Jackett]. It acts as a Torznab proxy adding Torznab support for more than 100 torrent trackers, but uses website scraping instead of APIs.
*** '''Important/Disclaimer:''' Many torrent trackers thrive on the community and may have rules in place that mandate site visits, karma, votes, comments and all. Please review your tracker rules and etiquette, keep your community alive. 
** We’re not responsible if your account is banned for disobeying rules or accruing HnRs/low-ratio.
<section end=radarr_settings_indexers_supported_indexers />

==== Sonarr ====
<section begin=sonarr_settings_indexers_supported_indexers />
* Usenet
** Newznab
*** Newznab is a standardized API used by many usenet indexing sites.
*** Many presets are available, but all require an API key to be accessible.
** Omgwtfnzbs
*** This indexer ''also'' supports newznab and is available as one of the above presets.
*** Website: https://omgwtfnzbs.me/
** Fanzub
*** Website: http://fanzub.com/
*** Indexer for Japanese media (Anime) exclusively.
* Torrents
** BroadcastheNet
*** Private Tracker
*** Website: https://broadcasthe.net/
** Filelist
*** Private Tracker
*** Website: https://filelist.io
** HDBits
*** Private tracker
*** Website: https://hdbits.org/
** IPTorrents
*** Private tracker, no search api.
*** Website: http://www.iptorrents.com/
** Nyaa
*** Website: http://www.nyaa.si/
*** Torrent Indexer for Japanese media (Anime) exclusively.
** Rarbg
*** Website: https://rarbg.to/
** Torrent RSS Feed
*** Generic torrent RSS feed parser.
*** '''NOTE:''' The RSS feed must contain a pubdate. The release size is recommended as well.
*** Private tracker
** Torrentleech
*** Private Indexer
*** Website: http://torrentleech.org/
** Torznab
*** Known indexers: Anime Tosho and Nyaa Pantsu as well as Jackett.
*** Torznab is a wordplay on Torrent and Newznab. It uses the same structure and syntax as the Newznab API specification, but exposing torrent-specific attributes and .torrent files. Thus supports a recent rss feed AND backlog searching capabilities. The specification is not maintained nor supported by the Newznab organization. (The same api specification is shared with nZEDb)
*** At this point it’s unlikely your favorite tracker supports this. We’ll update this post once we become aware of other trackers supporting it. Additionally you can use [https://github.com/Jackett/Jackett Jackett]. It acts as a Torznab proxy adding Torznab support for more than 100 torrent trackers, but uses website scraping instead of APIs.
*** '''Important/Disclaimer:''' Many torrent trackers thrive on the community and may have rules in place that mandate site visits, karma, votes, comments and all. Please review your tracker rules and etiquette, keep your community alive. 
*** We’re not responsible if your account is banned for disobeying rules or accruing HnRs/low-ratio.
** We’re not responsible if your account is banned for disobeying rules or accruing HnRs/low-ratio.
<section end=sonarr_settings_indexers_supported_indexers />

==== Lidarr ====
<section begin=lidarr_settings_indexers_supported_indexers />
* Usenet
** Headphones VIP
*** Website: https://headphones.codeshy.com/vip/
** Newznab
*** Newznab is a standardized API used by many usenet indexing sites.
*** Many presets are available, but most require an API key to be accessible.
** Omgwtfnzbs
*** This indexer ''also'' supports newznab and is available as one of the above presets.
*** Website: https://omgwtfnzbs.me/
* Torrents
** filelist.io
*** Private Tracker
*** Website: https://filelist.io/
** Gazelle API
*** Private Tracker
*** Website: https://gazellegames.net/login.php
** IP Torrents
*** Private Tracker
*** Website: https://iptorrents.com
** Rarbg
*** Website: https://rarbg.to/
** Redacted
*** Private Tracker - Considered one of the best Music Trackers on the net.
*** Website: https://redacted.ch/index.php
*** Interview: https://interviewfor.red/en/index.html
** Torrent RSS Feed
*** Generic torrent RSS feed parser.
*** '''NOTE:''' The RSS feed must contain a pubdate. The release size is recommended as well.
** Torrentleech
*** Private Indexer
*** Website: http://torrentleech.org/
** Torznab
*** Known indexers: Anime Tosho and Nyaa Pantsu as well as Jackett.
*** Torznab is a wordplay on Torrent and Newznab. It uses the same structure and syntax as the Newznab API specification, but exposing torrent-specific attributes and .torrent files. Thus supports a recent rss feed AND backlog searching capabilities. The specification is not maintained nor supported by the Newznab organization. (The same api specification is shared with nZEDb)
*** At this point it’s unlikely your favorite tracker supports this. We’ll update this post once we become aware of other trackers supporting it. Additionally you can use [https://github.com/Jackett/Jackett Jackett]. It acts as a Torznab proxy adding Torznab support for more than 100 torrent trackers, but uses website scraping instead of APIs.
*** '''Important/Disclaimer:''' Many torrent trackers thrive on the community and may have rules in place that mandate site visits, karma, votes, comments and all. Please review your tracker rules and etiquette, keep your community alive. 
** We’re not responsible if your account is banned for disobeying rules or accruing HnRs/low-ratio.
<section end=lidarr_settings_indexers_supported_indexers />
==== Readarr ====
<section begin=readarr_settings_indexers_supported_indexers />
* Usenet
** Newznab
*** Newznab is a standardized API used by many usenet indexing sites.
*** Many presets are available, but most require an API key to be accessible.
** Omgwtfnzbs
*** This indexer ''also'' supports newznab and is available as one of the above presets.
*** Website: https://omgwtfnzbs.me/
* Torrents
** filelist.io
*** Private Tracker
*** Website: https://filelist.io/
** Gazelle API
*** Private Tracker
*** Website: https://gazellegames.net/login.php
** IP Torrents
*** Private Tracker
*** Website: https://iptorrents.com
** Rarbg
*** Website: https://rarbg.to/
** Torrent RSS Feed
*** Generic torrent RSS feed parser.
*** '''NOTE:''' The RSS feed must contain a pubdate. The release size is recommended as well.
** Torrentleech
*** Private Indexer
*** Website: http://torrentleech.org/
** Torznab
*** Known indexers: Jackett.
*** Torznab is a wordplay on Torrent and Newznab. It uses the same structure and syntax as the Newznab API specification, but exposing torrent-specific attributes and .torrent files. Thus supports a recent rss feed AND backlog searching capabilities. The specification is not maintained nor supported by the Newznab organization. (The same api specification is shared with nZEDb)
*** At this point it’s unlikely your favorite tracker supports this. Additionally you can use [https://github.com/Jackett/Jackett Jackett]. It acts as a Torznab proxy adding Torznab support for more than 100 torrent trackers, but uses website scraping instead of APIs.
*** '''Important/Disclaimer:''' Many torrent trackers thrive on the community and may have rules in place that mandate site visits, karma, votes, comments and all. Please review your tracker rules and etiquette, keep your community alive. 
** We’re not responsible if your account is banned for disobeying rules or accruing HnRs/low-ratio.
<section end=readarr_settings_indexers_supported_indexers />

=== Templates ===
None.

System status

2021-05-12T20:15:03Z

Bakerboy448: /* Radarr */

== System ==
=== Health ===
==== Overview ====
====== Radarr ======
<section begin=radarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=radarr_system_status_health_overview />
====== Sonarr ======
<section begin=sonarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=sonarr_system_status_health_overview />
====== Lidarr ======
<section begin=lidarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=lidarr_system_status_health_overview />
====== Readarr ======
<section begin=readarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=readarr_system_status_health_overview />
==== System Warnings ====
===== Radarr =====
<section begin=radarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Radarr are targeted for .NET. We will no longer be providing legacy mono builds after 3.2 is released. You are running one of these legacy builds but your platform supports .NET.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''[[Radarr_FAQ#how_do_i_backup_restore_my_Radarr| Back-Up your existing configuration]]''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>master</code> branch. If you are on <code>develop</code> or <code>nightly</code> you'll need to adjust <code>/master/</code> in the URL.
*** '''Delete your existing binaries (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''.
****<code>wget --content-disposition <nowiki>'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop radarr</code> Stop Radarr
****<code> sudo mv /opt/Radarr /opt/Radarr.old</code> Backup the old Binaries
**** <code> tar -xvzf Radarr*.linux-core-x64.tar.gz</code> Extract the Radarr Tarball
**** <code> sudo mv Radarr/ /opt</code> Move the new Radarr Binaries
**** <code> sudo chown -R radarr:radarr /opt/Radarr</code> Ensure Radarr has permissions to its directory, this assumes it runs as the user <code>radarr</code>
**** <code> sudo rm -rf /opt/Radarr.old</code> Remove the old binaries
**** <code> sudo rm -rf Radarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script in your systemd (<code> sudo nano -e /etc/systemd/system/radarr.service</code>) to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.
***** If Radarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start radarr.service</code> Restart Radarr

* '''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''
** Radarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.20 is the absolute minimum for Radarr.
** The upgrade procedure for Mono varies per platform.

*'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''
** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0. Note that Radarr uses <code>libsqlite3.so</code> which may or may not be contained in a sqlite3 upgrade package.

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.

*'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.
** Please look at System -> Info to see the current AppData & Startup directories.
** This means Radarr will be unable to update itself without risking data-loss.
** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081

** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:7878/$1 [P,L]
** For Caddy (V1) use this:
*** Note: you'll also need to add the websocket directive to your radarr configuration
proxy /radarr 127.0.0.1:7878 {
websocket
transparent
}

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#ptp_settings_old|PTP Indexer Settings Out of Date]]'''
** The following PassThePopcorn indexers have deprecated settings and should be updated.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

*'''[[#mono_support_end_of_life|Mono and x86 builds are ending]]'''
** Mono and x86 builds will no longer be supported in the next build of the application. If you are receiving this error then you are running the mono version of the application or the x86 version. Unfortunately, due to increasing difficulting in development support for these legacy versions we will be discontinuing their support and thus releases for them going forward. Thus it is advised you upgrade to a supported Operating System that does not require neither x86 nor mono. You may also be able to explore using Docker for your needs.

<section end=radarr_system_status_health_system_warnings />

===== Sonarr =====
<section begin=sonarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]'''
** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].

* '''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''
** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].

* '''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''
** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform. 
** Mono 5.8 is the absolute minimum for Sonarr, but Mono 5.20 is currently recommended.
** The upgrade procedure for Mono varies per platform.

* '''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''
** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** The upgrade procedure for Mono varies per platform.

* '''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.
** ''(This warning will not appear if your current version is less than 14 days old)''

* '''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.

* '''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''
** Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux. 
** Please look at System -> About to see the current AppData & Startup directories.
** This means Sonarr will be unable to update itself without risking data-loss.
** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.
* '''[[#package_maintainer_message|Package Maintainer Message]]'''
** Please refer to the specific message your package maintainer is indicating to you. This is not a Sonarr issue. For additional information, refer to your package maintainer. Your package maintainer can be found in System -> Status -> About. Note that this includes docker and your package maintainer is whomever maintains your docker image.

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=sonarr_system_status_health_system_warnings />

===== Lidarr =====
<section begin=lidarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Lidarr are targeted for .NET. We will soon no longer provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''Back-Up your existing configuration''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>develop</code> branch. If you are on <code>nightly</code> you'll need to adjust <code>/develop/</code> in the URL.
***'''Delete your existing binaries (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''
****<code>wget --content-disposition <nowiki>'http://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop lidarr.service</code> Stop Lidarr
****<code> sudo mv /opt/Lidarr /opt/Lidarr.old</code> Backup the old Binaries
****<code> tar -xvzf Lidarr*.linux-core-x64.tar.gz</code> Extract the Lidarr Tarball
****<code> sudo mv Lidarr/ /opt</code> Move the new Lidarr Binaries
****<code> sudo chown -R lidarr:lidarr /opt/Lidarr</code> Ensure Lidarr has permissions to its directory, this assumes it runs as the user <code>lidarr</code>
****<code> sudo rm -rf /opt/Lidarr.old</code> Remove the old binaries
****<code> sudo rm -rf Lidarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script (<code> sudo nano -e /etc/systemd/system/lidarr.service</code>) to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.
***** If Lidarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start lidarr.service</code> Restart Lidarr

*'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''
** Lidarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.20 is the absolute minimum for Lidarr.
** The upgrade procedure for Mono varies per platform..
** See "Update to .NET Core version above"

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081
** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:8686/$1 [P,L]

*'''[[#fpcalc_upgrade|Fpcalc Needs Upgrading]]'''
Lidarr can use chromaprint audio fingerprinting to identify tracks. This depends on an external binary, which is distributed with Lidarr for Windows and macOS, but must be provided independently on Linux.

To fix this on a native Linux instance, install the appropriate package using your package manager and make sure that fpcalc is on your PATH (this can be checked using which fpcalc and verifying that the correct location of fpcalc is returned):

{| class="wikitable"
|- style="font-weight:bold; text-align:center; vertical-align:middle;"
! Distribution
! Package
|-
| style="vertical-align:middle;" | Debian/Ubuntu
| <code>libchromaprint-tools</code>
|-
| style="vertical-align:middle;" | Fedora/CentOS
| <code>chromaprint-tools</code>
|-
| style="vertical-align:middle;" | Arch
| <code>chromaprint</code>
|-
| style="vertical-align:middle;" | OpenSUSE
|<code> chromaprint-fpcalc</code>
|-
| style="vertical-align:middle;" | Synology
| <code>chromaprint</code>
|}

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=lidarr_system_status_health_system_warnings />

===== Readarr =====
<section begin=readarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Readarr are targeted for .NET. We will soon no longer provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET Core.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''Back-Up your existing configuration''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>master</code> branch. If you are on <code>develop</code> or <code>nightly</code> you'll need to adjust <code>/master/</code> in the URL.
***'''Delete your existing binaries (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''.
****<code>wget --content-disposition <nowiki>'http://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop readarr</code> Stop Readarr
****<code> sudo mv /opt/Readarr /opt/Readarr.old</code> Backup the old Binaries
****<code> tar -xvzf Readarr*.linux-core-x64.tar.gz</code> Extract the Readarr Tarball
****<code> sudo mv Readarr/ /opt</code> Move the new Readarr Binaries
****<code> sudo chown -R readarr:readarr /opt/Readarr</code> Ensure Readarr has permissions to its directory, this assumes it runs as the user <code>readarr</code>
****<code> sudo rm -rf /opt/Readarr.old</code> Remove the old binaries
****<code> sudo rm -rf Readarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script (<code> sudo nano -e /etc/systemd/system/readarr.service</code>) to call <code>Readarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.
***** If Readarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start readarr.service</code> Restart Readarr

*'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''
** Readarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.20 is the absolute minimum for Readarr.
** The upgrade procedure for Mono varies per platform.
** See "Update to .NET Core version above"

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081
** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:8787/$1 [P,L]

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=readarr_system_status_health_system_warnings />

==== Download Clients ====
===== Radarr =====
<section begin=radarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.
*** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Radarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Radarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Radarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Radarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Radarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/hardlinks How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

[https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Radarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#permissions_error|Permissions Error]]'''
** Radarr or the user radarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end=radarr_system_status_health_download_clients />

===== Sonarr =====
<section begin=sonarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Sonarr.
*** Ensure SSL encryption is not turned on if you're using both your Sonarr instance and your download client on a local network. See [[Sonarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Sonarr to prevent the errors.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Sonarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Sonarr/V3/Sonarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#permissions_error|Permissions Error]]'''
** Sonarr or the user sonarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end="sonarr_system_status_health_download_clients" />

===== Lidarr =====
<section begin=lidarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.
*** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Lidarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Lidarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished song is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Lidarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Lidarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/audio</code> and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/audio</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Lidarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* '''[[#permissions_error|Permissions Error]]'''
** Lidarr or the user lidarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=lidarr_system_status_health_download_clients />
===== Readarr =====
<section begin=readarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.
*** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Readarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Readarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Readarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished book is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Readarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Readarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/books</code> and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/books</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Readarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* '''[[#permissions_error|Permissions Error]]'''
** Readarr or the user readarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=readarr_system_status_health_download_clients />

==== Completed/Failed Download Handling ====
===== Radarr =====
<section begin=radarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=radarr_system_status_health_complete_failed_download_handling />

===== Sonarr =====
<section begin=sonarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the
<section end=sonarr_system_status_health_complete_failed_download_handling />

===== Lidarr =====
<section begin=lidarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidrr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=lidarr_system_status_health_complete_failed_download_handling />

===== Readarr =====
<section begin=readarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=readarr_system_status_health_complete_failed_download_handling />

==== Indexers ====
===== Radarr =====
<section begin=radarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_radarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Radarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_radarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Radarr will not grab new releases automatically]]'''
** So Radarr uses the RSS feed to pick up new releases as they come along. More info on that [[Radarr FAQ#How does Radarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=radarr_system_status_health_indexers />

===== Sonarr =====
<section begin=sonarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_sonarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Sonarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_sonarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Sonarr will not grab new releases automatically]]'''
** So Sonarr uses the RSS feed to pick up new releases as they come along. More info on that [[Sonarr FAQ#How does Sonarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''
** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=sonarr_system_status_health_indexers />
===== Lidarr =====
<section begin=lidarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Lidarr will not grab new releases automatically]]'''
** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for music (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=lidarr_system_status_health_indexers />
===== Readarr =====
<section begin=readarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_readarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Readarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_readarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Readarr will not grab new releases automatically]]'''
** So Readarr uses the RSS feed to pick up new releases as they come along. More info on that [[Readarr FAQ#How does Readarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for books (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=readarr_system_status_health_indexers />

==== Folders ====
===== Radarr =====
<section begin=radarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder
***# Easiest way to find this is to go to the Movies (Library) Tab
***# Create a custom filter with the old root folder path
***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files
<section end=radarr_system_status_health_folders />
===== Sonarr =====
<section begin=sonarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder
***# Go to the Series > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these series to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files
* '''[[#import_list_missing_root_folder|Import List missing root folder]]'''
** This error is typically identified if a list is looking for a root folder but that root folder is no longer available.
**#Go to Settings > Import Lists
**#Edit the import lists that were mentioned in the health check
**#Save
<section end=sonarr_system_status_health_folders />
===== Lidarr =====
<section begin=lidarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these artists to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files
<section end=lidarr_system_status_health_folders />
===== Readarr =====
<section begin=readarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these authors to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files
<section end=readarr_system_status_health_folders />

==== Media ====
===== Radarr =====
<section begin=radarr_system_status_health_media />
* '''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''
** The movie is linked to a TMDb Id that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It. 
** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu

* '''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''
** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.
<section end=radarr_system_status_health_media />
===== Sonarr =====
<section begin=sonarr_system_status_health_media />
* '''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''
** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.
<section end=sonarr_system_status_health_media />
===== Lidarr =====
<section begin=lidarr_system_status_health_media />
Text
<section end=lidarr_system_status_health_media />
===== Readarr =====
<section begin=readarr_system_status_health_media />
Text
<section end=readarr_system_status_health_media />

=== Disk Space ===
==== Radarr ====
<section begin=radarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=radarr_system_status_disk_space />
==== Sonarr ====
<section begin=sonarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=sonarr_system_status_disk_space />
==== Lidarr ====
<section begin=lidarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=lidarr_system_status_disk_space />
==== Readarr ====
<section begin=readarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=readarr_system_status_disk_space />

=== About ===
==== Radarr ====
<section begin=radarr_system_status_about />
This will tell you about your current install of Radarr
<section end=radarr_system_status_about />
==== Sonarr ====
<section begin=sonarr_system_status_about />
This will tell you about your current install of Radarr
<section end=sonarr_system_status_about />
==== Lidarr ====
<section begin=lidarr_system_status_about />
This will tell you about your current install of Lidarr
<section end=lidarr_system_status_about />
==== Readarr ====
<section begin=readarr_system_status_about />
This will tell you about your current install of Readarr
<section end=readarr_system_status_about />

=== More Info ===
==== Radarr ====
<section begin=radarr_system_status_more_info />
* Home Page: [https://radarr.video Radarr's home page]
* Wiki: [https://wiki.servarr.com/Radarr You're here already]
* Reddit: [https://reddit.com/r/radarr r/radarr]
* Discord: [https://radarr.video/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/radarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Radarr/Radarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]
<section end=radarr_system_status_more_info />
==== Sonarr ====
<section begin=sonarr_system_status_more_info />
* Home page: [https://sonarr.tv Sonarr's home page]
* Forums: [https://forums.sonarr.tv Sonarr Forums]
* Discord: [https://discord.gg/M6BvZn5 Join our discord]
* Reddit: [https://reddit.com/r/sonarr r/sonarr]
* Twitter: [https://twitter.com/sonarrtv @sonarrtv]
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]
* Wiki: [https://wiki.servarr.com/sonarr You're here already]
* Donations: If you're feeling generous and would like to donate [https://sonarr.tv/donate click here]
* Source: https://github.com/Sonarr/Sonarr Github]
* Feature Requests: Got a great idea drop it on Github [https://github.com/Sonarr/Sonarr/issues here]
<section end=sonarr_system_status_more_info />
==== Lidarr ====
<section begin=lidarr_system_status_more_info />
* Home page: [https://lidarr.audio Lidarr's home page]
* Wiki: [https://wiki.servarr.com/Lidarr You're here already]
* Reddit: [https://reddit.com/r/lidarr r/lidarr]
* Discord: [https://lidarr.audio/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/lidarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/lidarr/Lidarr/ Github]
* Feature Requests: Got a great idea drop it on GitHub [https://github.com/Lidarr/Lidarr/issues here]
<section end=lidarr_system_status_more_info />
==== Readarr ====
<section begin=readarr_system_status_more_info />
* Home page: [https://readarr.com Readarr's home page]
* Wiki: [https://wiki.servarr.com/Readarr You're here already]
* Reddit: [https://reddit.com/r/readarr r/readarr]
* Discord: [https://readarr.com/discord Join our discord]
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Readarr/Readarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Readarr/Readarr/issues click here]
<section end=readarr_system_status_more_info />

=== Templates ===

Readarr FAQ

2021-05-12T03:29:45Z

Bakerboy448:

Readarr Specific FAQ entries coming soon(tm) once it is out of pre-alpha testing.

{{FAQ|ARRNAME=Readarr|ARRDISCORD=http://readarr.com/discord|ARRPORT=8787}}

Readarr FAQ

2021-05-12T03:27:34Z

Bakerboy448:

Readarr Specific FAQ entries coming soon(tm) once it is out of pre-alpha testing.

{{FAQ|ARRNAME=Readarr|ARRDISCORD=http://readarr.com/discordARRPORT=8787}}

Lidarr FAQ

2021-05-12T03:27:05Z

Bakerboy448:

== How does Lidarr work? ==
[[#how_does_lidarr_work|anchor]] 
* Lidarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Lidarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Lidarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Lidarr's Release-Push API endpoint along with an IRC announce channel to push releases to Lidarr for processing which can happen in near real time and with less overhead on the indexer and Lidarr as Lidarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== Why does Lidarr only show studio albums, How do I find singles or EPs? ==
[[#why_does_lidarr_only_show_studio_albums_how_do_i_find_singles_or_eps|anchor]] 
Lidarr defaults to only bringing in studio albums for each artist. However, you can expand the album types per an artist, or for your entire library by utilizing [[Lidarr Settings#Metadata Profiles|Metadata Profiles]].

== Why can't I add a various artists album? ==
[[#why_cant_i_add_a_various_artists_album|anchor]] 
Various Artists and other meta artists on Musicbrainz are due to the number of entries they provide.

== Can I add just an album? ==
[[#an_i_add_just_an_album|anchor]] 
Not at the moment.

== Can I download single tracks? ==
[[#can_i_download_single_tracks|anchor]] 
Lidarr works by searching for and downloading full releases, therefore individual tracks cannot be downloaded unless they were released as a single by the artist.

== Why doesn't artist X show up in search? ==
[[#why_doesnt_artist_x_show_up_in_search|anchor]] 
Search is still a work in progress. Artists that don't show up in search may be added by searching for `lidarr:mbid` where `mbid` is the Musicbrainz ID of the artist.

== Lidarr matched an album with too many tracks. How can I change the Album to the correct Release? ==
[[#lidarr_matched_an_album_with_too_many_tracks_how_can_i_change_thealbum_to_the_correct_release|anchor]] 
Open the Album details page and select the Edit Icon in the top nav. There you can find a dropdown of all releases tied to that Album.

== I'm having trouble importing my artists, what could it be? ==
[[#im_having_trouble_importing_my_artists_what_could_it_be|anchor]] 
The artist import process just imports the Artist names and path locations, which are then stored in the database so that a) metadata can be retrieved and b) downloaded content can be put in the same location in future. To this end, the user account that Lidarr runs under needs both read and write to your data directory.

== I can't find a release in Lidarr but it is on MusicBrainz ==
[[#cant_find_release_lidarr_on_mb|anchor]] 
This is likely due to the release having an <code>unknown</code> release status. Update MusicBrainz.

== How often do Lidarr's and MusicBrainz databases sync? ==
[[#lidarr_mb_db_sync|anchor]] 
Every hour at 5 after the hour

== I'm having trouble importing my artists, what could it be? ==
[[#im_having_trouble_importing_my_artists_what_could_it_be|anchor]] 
The artist import process just imports the Artist names and path locations, which are then stored in the database so that a) metadata can be retrieved and b) downloaded content can be put in the same location in future. To this end, the user account that Lidarr runs under needs both read and write to your data directory.
{{FAQ|ARRNAME=Lidarr|ARRDISCORD=https://lidarr.audio/discord|ARRPORT=8686}}

Radarr FAQ

2021-05-12T03:26:43Z

Bakerboy448:

== How does Radarr work? ==
[[#how_does_radarr_work|anchor]] 
[[#How_does_Radarr_work|alt-anchor]] 
* Radarr relies on RSS feeds to automate grabbing of releases as they are posted, for both new releases as well as previously released releases being released or re-released. The RSS feed is the latest releases from a site, typically between 50 and 100 releases, though some sites provide more and some less. The RSS feed is comprised of all releases recently available, including releases for requested media you do not follow, if you look at debug logs you will see these releases being processed, which is completely normal.
* Radarr enforces a minimum of 10 minutes on the RSS Sync interval and a maximum of 2 hours. 15 minutes is the minimum recommended by most indexers, though some do allow lower intervals and 2 hours ensures Radarr is checking frequently enough to not miss a release (even though it can page through the RSS feed on many indexers to help with that). Some indexers allow clients to perform an RSS sync more frequently than 10 minutes, in those scenarios we recommend using Radarr's Release-Push API endpoint along with an IRC announce channel to push releases to Radarr for processing which can happen in near real time and with less overhead on the indexer and Radarr as Radarr doesn’t need to request the RSS feed too frequently and process the same releases over and over.

== How does Radarr find movies? ==
[[#how_does_radarr_find_movies|anchor]] 
* Radarr does ''not'' regularly search for movie files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted movies, then compares that with its list of movies that are missing or need to be upgraded. Any matches are downloaded. This lets Radarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a movie, you'll need to set the correct path, profile and monitoring status then use the Start search for missing movie checkbox. If the movie hasn't been released yet, you don't need to initiate a search.
* Put another way, Radarr will only find movies that are newly uploaded to your indexers. It will not actively try to find movies you want that were uploaded in the past.
* If you've already added the movie, but now you want to search for it, you have a few choices. You can go to the movie's page and use the search button, which will do a search and then automatically pick one. You can use the Search tab and see ''all'' the results, hand picking the one you want. Or you can use the filters of <code>Missing</code>, <code>Wanted</code>, or <code>Cut-off Unmet</code>.
* If Radarr has been offline for an extended period of time, Radarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Radarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed movies.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Radarr/Radarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs can be found here].
'''''As of 1/19/2021 the logic is as follows'''''
# Quality
# Custom Format Score
# Protocol
# Indexer Priority
# Indexer Flags
# Peers (If Torrent)
# Age (If Usenet)
# Size

== What are Lists and what can they do for me? ==
[[#what_are_lists_and_what_can_they_do_for_me|anchor]] 
* Lists are a part of Radarr that allow you to follow a given list creator.
* Let's say that you follow a given list creator on Trakt/TMDb and really like their Marvel Cinematic Universe film section and want to watch every movie on their list. You look in your Radarr and realize that you don't have those movies. Well instead of searching one by one and adding those lists and then searching your indexers for those movies. You can do this all at once with a List. The Lists can be set to import all the movies on that curators list as well as be set to automatically assign a quality profile, automatically add, and automatically monitor that movie.
* '''CAUTION:''' If lists are done improperly they will absolutely wreck your library with a bunch of trash you have no intention of watching. So make sure of what you're importing before you click save.
* ie. physically look at the list before you even go to Radarr.

== With the release of Radarr V3, what release should I download? ==
[[#with_the_release_of_radarr_v3_what_release_should_i_download|anchor]] 
Please see better information [[Radarr FAQ#How do I update Radarr?|here]]

== Why did the GUI / UI Change? Can it be changed back? ==
[[#why_did_the_gui_ui_change|anchor]] 
* Radarr is a fork of [[Sonarr]] which has the new UI.
* No it cannot be changed back. No it will not be changed back.
* You may, however, check out [https://github.com/gilbN/theme.park Theme Park]


== Where did Wanted and Cut-off Unmet go? ==
[[#where_did_wanted_and_cutoff_unmet_go|anchor]] 
* Movie Index (AKA 'Movies') -> Filter (top right corner) -> <code>Wanted</code> and <code>Cut-off Unmet</code>
[[File:radarr-where-did-wanted-and-cutoff-unmet-go.png|thumb|none|750px|alt=This is where wanted and Cut-off Unmet went|This is where wanted and Cut-off Unmet went]]

== Why can't I add a new movie to Radarr? ==
[[#why_cant_i_add_a_new_movie_to_radarr|anchor]] 
* Radarr uses [http://themoviedb.org The Movie Database (TMDb)] for movie information and images like fanart, banners and backgrounds. Generally, there are a few reasons why you may not be able to add a movie:
* TMDb doesn't like special characters to be used when searching for movies through the API (which Radarr uses), so try searching a translated name, and/or without special characters.
* You can also add by TMDb ID or, if TMDb has it, the IMDb ID
* The movie hasn't been added to TMDb yet, follow their [https://www.themoviedb.org/bible/new_content#59f7933c9251413e93000006 guide] to get it added.

== Can all my movie files be stored in one folder? ==
[[#can_all_my_movie_files_be_stored_in_one_folder|anchor]] 
* Not yet and the reason is that Radarr is a fork of [[Sonarr]], where every show has a folder. This limitation is a known pain point for many users and will maybe come in a future version.
:If you're looking to moving all your movies from one folder to individual folders check [[Radarr Tips and Tricks#Create a Folder for Each Movie|here]]

== Can I put all my movies in my library into one folder ==
[[Radarr FAQ#Can I put all my movies in my library into one folder|anchor]]

We get asked this a lot. There are no plans to support <code>\data\Movies\Movie1.mkv</code>, <code>\data\Movies\Movie2.mkv</code>, etc.

The [https://github.com/Radarr/Radarr/issues/153 Custom Folder GitHub Issue] technically covers this request, but it is no guarantee that all movie files in one folder will be implemented at that time.

A slight hack-ish solution is noted below. Please note that you mustn't trigger a rescan or it will show as missing and regardless the movie will never be upgraded.

* Use a Custom Script
** the script should be triggered on import
** it should be designed to move the file whenever you want it
** it then needs to call the Radarr API and change the movie to unmonitored.

== How can I rename my movie folders? ==
[[#how_can_i_rename_my_movie_folders|anchor]] 
# Movies
# Movie Editor
# Select what movies need their folder renamed
# Change Root Folder to the same Root Folder that the movies currently exist in
# Select "Yes move files"

== Movie File and Folder Naming ==
[[#movie_file_and_folder_naming|anchor]] 
* Currently, Radarr requires that each movie be in a folder with the format containing at minimum <code>Movie Title (Year)/</code>, optionally <code>_</code> or <code>.</code> are valid separators. To facilitate correct quality and resolution identification during import, a file name like <code>Movie Title (Year) [Quality-Resolution].ext</code> is best, again <code>_</code> or <code>.</code> are valid separators too.
* A useful tool for making these changes to your collection is [http://www.filebot.net/#download filebot] which has paid version in both the Apple and Windows stores, but can be found for free on their legacy [https://sourceforge.net/projects/filebot/files/latest/download SourceForge] site. It has both a GUI and CLI, so you can use whatever you’re comfortable with. For the above example, <code>{ny}</code> expands to <code>Name (Year)</code> and <code>{vf}</code> gives the resolution like <code>1080p</code>. There is nothing to infer quality, so you can fake it using <code>{ny}/{ny} [{dim[0] >= 1280 ? 'Bluray' : 'DVD'}-{vf}]</code> which will name anything lower than 720p to <code>[DVD-572p]</code> and greater or equal to 720p like <code>[Bluray-1080p]</code>.
See [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] for more details.

== Movie Folders Named Incorrectly ==
[[#movie_folders_named_incorrectly|anchor]] 
* Even if your movies are in folders already, the folders may not be named correctly. The folder name should be <code>Movie Title (Year)</code>, having the title and year in the folder’s name is critical right now.
* Examples that will work well:
** <code>/mnt/Movies/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** <code>/mnt/Kid Movies/Frozen (2013)/Frozen (2013) [Bluray-1080p].mkv</code>
* Examples that will work, but will require manual management:
** By letters: <code>/mnt/Movies/A-D/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By rating: <code>/mnt/Movies/R/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** By genre: <code>/mnt/Movies/Crime, Drama, Sci-Fi/A Clockwork Orange (1971)/A Clockwork Orange (1971) [Bluray-1080p].mkv</code>
** These examples will require manual management when the movie is added. Each of the examples will have many root directories, like <code>A-D</code> and <code>E-G</code> in the first letter example, <code>R</code> and <code>PG-13</code> in the rating example and you can guess at the variety of genre folders. When adding a new movie, the correct base folder will need to be selected for this format to work.
* Examples that won’t work:
** Single folder: <code>/mnt/Kid Movies/Frozen (2013) [Bluray-1080p].mkv</code>
*** At this time, movies simply have to be in a folder named after the movie. There is no way around this until development work is done to add this feature.
**'''Movie''' Folder Naming Formats from v0.2 that include '''File''' properties in the '''movie folder''' name such as <code>{Movie.Title}.{Release Year}.{Quality.Full}-{MediaInfo.Simple}{`Release.Group}</code> will not work in v3.
*** Folders are related to the movie and independent of the file. Additionally, this will break with the planned multiple files per movie support.
*** The other reason it was removed was it caused frequent confusion, database corruption, and generally was only half baked.
* The [[Radarr Tips and Tricks#Create a Folder for Each Movie|Create a Folder for Each Movie]] is a great source for making sure your file and folder structure will work great.

== How can I mass delete movies from the wanted list? ==
[[#how_can_i_mass_delete_movies_from_the_wanted_list|anchor]] 
* Use Movie Editor -> Select movies you want to delete -> Delete

== Why doesn't Radarr work behind a reverse proxy ==
[[#why_doesnt_radarr_work_behind_an_nginx_reverse_proxy|anchor]] 
* Starting with V3 Radarr has switched to .NET Core and a new webserver. In order for SignalR to work, the UI buttons to work, database changes to take, and other items. It requires the following addition to the location block for Radarr:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

* Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
* [https://github.com/aspnet/AspNetCore/issues/17081 See this ASP.NET Core issue]
* If you are using a CDN like Cloudflare ensure websockets are enabled to allow websocket connections.

== How do I update Radarr? ==
[[#how_do_i_update_my_radarr|anchor]] 
# Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).
# Under the Development section change the branch name to <code>master</code> or <code>develop</code>
# Save
''This will not install the bits from that branch immediately, it will happen during the next update.''

* master (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. This is currently v3. This version will receive updates approximately monthly. On GitHub, this is the <code>master</code> branch.
* develop (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first. This is currently v3. This version will receive updates either weekly or biweekly depending on development. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is a snapshot of the <code>develop</code> branch at a point in time.
* nightly (Nightly): The bleeding edge. Released as soon as code is committed and passed all automated tests. '''''Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.''''' This is currently v3. This version is updated immediately. '''Warning: You may not be able to go back to <code>master</code> after switching to this branch.''' On GitHub, this is the <code>develop</code> branch.

* Note: If your install is through Docker append <code>:release</code>, <code>:latest</code>, or <code>:testing</code> to the end of your container tag depending on who makes your builds.
{| class="wikitable"
|+
!Current Versions
!master
!develop
!nightly
|-
|
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Frelease%2FVERSION.json Current Master/Latest]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Ftesting%2FVERSION.json Current Develop/Beta]
|[https://img.shields.io/badge/dynamic/json?color=f5f5f5&style=flat-square&label=&query=%24.version&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhotio%2Fradarr%2Fnightly%2FVERSION.json Current Nightly/Alpha]
|}
<center>
{| class="wikitable"
|-
! Release Channel Type !! Branch: master (stable) (v3.1) !! Branch: develop (beta) (v3.1) !! Branch: nightly (unstable) (v3.2)
|-
|[https://hub.docker.com/r/hotio/radarr hotio]||<code>hotio/radarr:release</code>||<code>hotio/radarr:testing</code>|| If you have to ask, you should not be on it.
|-
|[https://hub.docker.com/r/linuxserver/radarr LinuxServer.io]||<code>linuxserver/radarr:latest</code>||<code>linuxserver/radarr:develop</code>|| If you have to ask, you should not be on it.
|}
</center>

=== Installing a newer version ===
If Native:
# Go to System and then the Updates tab
# Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.
If Docker:
# Repull your tag and update your container

== Can I switch from nightly back to develop? ==
[[#can_i_switch_from_nightly_back_to_develop|anchor]] 

[[Radarr_FAQ#Can I switch between branches?|See this related question]]

== Can I switch between branches? ==
[[#can_i_switch_between_branches|anchor]] 
* You can (almost) always increase your risk.
* <code>master</code> can go to <code>develop</code> or <code>nightly</code>
* <code>develop</code> can go to <code>nightly</code>
* Check with the development team to see if you can switch from <code>nightly</code> to <code>master</code>; <code>nightly</code> to <code>develop</code>; or <code>develop</code> to <code>master</code> for your given build.
* Failure to follow these instructions may result in your Radarr becoming unusable or throwing errors. You have been warned.
** The most common error is something like <code>Error parsing column 45 (Language=31 - Int64)</code> or other similar database errors around missing columns or tables.

* '''May 4 2021 Update'''
** <code>3.1.1</code> has been released as master/stable
** For those on nightly and are still on <code>3.1.1.4948</code> or lower you can safely downgrade to master
*** Same for develop.
** For those who are on nightly and are updated to <code>3.1.1.4957</code>, <code>3.2.0.4960</code>, or newer; you cannot downgrade as there was a DB migration in <code>3.1.1.4957</code> and you'd need to rollback your database to the backup prior to that update in order to jump to master

== How does radarr handle foreign movies or foreign titles? ==
[[#how_does_radarr_handle_foreign_movies_or_foreign_titles|anchor]] 
* Radarr uses both Alt Titles and Translations for parsing and searching. Search will use the Original Title, English Title, and Translated Title from whatever languages you have preferred (in profile and CFs). Parsing should look for a match in all Translations and Alt Titles.

* To get a movie in a foreign language set your Profile Language to Original (Movie's Original Language), a specific language for that profile, or any and use custom formats to determine which language to grab.
* Note that this does not include any indexer languages specified as multi.

== How does radarr handle "multi" in names? ==
[[#how_does_radarr_handle_multi_in_names|anchor]] 
* Radarr by default assumes multi is english and french unless specified in your indexer's advanced settings in Radarr.

* Note that multi definitions only help for release parsing and not for foreign titles or movies searches.

== Help, Movie Added, But Not Searched ==
[[#help_movie_added_but_not_searched|anchor]] 

* Neither Radarr nor Sonarr ''actively'' search for missing movies automatically. Instead, a periodic query of new posts is made to all indexers configured for RSS. When a wanted or cutoff unmet movie shows up in that list, it gets downloaded. This means that until a movie is posted (or reposted), it won’t get downloaded.
* If you’re adding a movie that you want now, the best option is to check the “Start search for missing movie” box, to the left of the ''Add Movie'' ('''1''') button. You can also go to the page for a movie you’ve added and click the magnifying glass “Search” ('''2''') button or use the Wanted view to search for Missing or Cutoff Unmet movies.

[[File:start search for missing movie.png|thumb|none|750px|alt=Add and Search for movie|Add and Search for movie]]
[[File:Search selected movie.png||thumb|none|750px|altt=Search selected movie|Search selected movie]]

== Root path for movies imported from lists becomes “C:” or other weird paths ==
[[#root_path_for_movies_imported_from_lists_become_c_or_other_weird_paths|anchor]] 
* Sometimes you can get a problem that movies that are imported from your lists, gets imported with the root path set to “C:” or other weird paths.

* This is a known issue for when the root path is either not setup during the creation of the list, or if the root path has been deleted after the list was created. Note that this problem can still occur even if the list is '''edited''' and the correct root path is set.

* Use the Movie Editor to fix paths of existing movies.

== Movie Imported, But Source File And Torrent Not Deleted ==
[[#movie_imported_but_source_file_and_torrent_not_deleted|anchor]] 
* Check if you have Completed Download Handling - Remove turned on. (This does not work if you are using rtorrent.)

[[File:Remove turned on.png|thumb|none|750px|alt=Settings|Settings > Download Clients]]

* If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.

== My Custom Script stopped working after upgrading from v0.2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v0.2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== I am using a Pi and Raspbian and Radarr will not launch ==
[[#i_am_using_a_pi_and_raspbian_and_radarr_will_not_launch|anchor]] Raspbian has a version of libseccomp2 that is too old to support running a docker container based on Ubuntu 20.04, which both hotio and LinuxServer use as their base for v3. You either need to use <code>--privileged</code>, update libseccomp2 from Ubuntu or get a better OS (We recommend Ubuntu 20.04 arm64)

'''Possible Solution:'''

Managed to fix the issue by installing the backport from debian repo. Generally not recommended to use backport in blanket upgrade mode. Installation of a single package may be ok but may also cause issues. So got to understand what you are doing.

Steps to fix:

First ensure you are running Raspbian buster e.g using <code>lsb_release -a</code>

Distributor ID: Raspbian

Description: Raspbian GNU/Linux 10 (buster)

Release: 10

Codename: buster

''If you are using buster:''
<code>Add the line `deb <nowiki>http://deb.debian.org/debian</nowiki> buster-backports` main to `/etc/apt/sources.list`
Run apt-get update
apt-get -t buster-backports install libseccomp2</code>

== Why are lists sync times so long and can I change it? ==
[[#why_are_lists_sync_times_so_long_and_can_i_change_it|anchor]]

Lists never were nor are intended to be <code>add it now</code> they are <code>hey i want this, add it eventually</code> tools

You can trigger a list refresh manually, script it and trigger it via the API, add the movies to radarr, use Ombi, or any similar app that adds them right away

This change was due to not have our server get killed by people updating lists every 10 minutes.

== Why doesn't Radarr work behind an nginx reverse proxy ==

[[Radarr_FAQ#Why_doesn.27t_Radarr_work_behind_a_reverse_proxy|See this section]]

== Can I disable the refresh movies task ==
[[#can_I_disable_the_refresh_movies_task|anchor]]

No, nor should you through any SQL hackery. The refresh movies task queries the upstream Servarr proxy and checks to see if the metadata for each movie (ids, cast, summary, rating, translations, alt titles, etc.) has updated compared to what is currently in Radarr. If necessary, it will then update the applicable movies.

A common complaint is the Refresh task causes heavy I/O usage. This is partly due to the setting "Analyze video files" which is advised to be enabled if you use tdarr or otherwise externally modify your files. If you don't you can safely disable "Analyze video files" to reduce some I/O. The other setting is "Rescan Movie Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to <code>Manual</code>. Do not change this to <code>Never</code> unless all changes to your library (new movies, upgrades, deletions etc) are done through Radarr. If you delete movie files manually or via Plex or another third party program, do not set this to <code>Never</code>.

{{FAQ|ARRNAME=Radarr|ARRDISCORD=https://radarr.video/discord|ARRPORT=7878}}

Template:Troubleshooting

2021-05-10T21:14:14Z

Bakerboy448: /* Download client clearing items */

<noinclude>
<templatedata>
{
"params": {
"ARRNAME": {
"description": "Name of the Application",
"example": "Radarr",
"type": "string",
"required": true
},
"ARR_DISCORD": {
"description": "Link to the ARR #support Discord",
"type": "url",
"required": true
},
"ARR_WEBSITE": {
"description": "Link to the ARR Website",
"type": "url",
"required": true
},
"ARR_LATEST_RELEASE": {
"description": "Link to the ARR Download",
"type": "url",
"required": true
},
"VERSION": {
"description": "The current version of each of the ARRs",
"type": "string",
"required": true
},
"MEDIA": {
"description": "What type of media does the ARR use",
"example": "Radarr: movies, Sonarr: series, Lidarr: artist, Readarr: author",
"type": "string",
"required": true
},
"SEARCHSOURCE": {
"description": "What metadata provider does the ARR use",
"example": "Radarr: TMDb, Sonarr: TheTVDb, Lidarr: MusicBrainz, Readarr: GoodReads",
"type": "string",
"required": true
},
"QUERYSTRING": {},
"ARRNAME2": {
"description": "This string is used for lower cased ARR names for transclusion",
"example": "radarr, sonarr, lidarr, readarr",
"type": "string",
"required": true
}
},
"description": "This template is utilized for general troubleshooting steps that span across all the ARRs. Some Sections may be transcluded from a Troubleshooting Misc page when items are ARR specific."
}
</templatedata>
</noinclude>
== Troubleshooting ==
----
Please note that this information is only for {{{ARRNAME}}} {{{VERSION}}}.
=== Asking for Help ===
----
Do you need help? That's okay, everyone needs help sometimes. You can get real time help via chat on [{{{ARR_DISCORD}}} Discord] or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit].

But before you go there and post, be sure your request for help is the best it can be. Clearly describe the problem and briefly describe your setup, including things like your OS/distribution, version of Mono or .Net/.Netcore, version of {{{ARRNAME}}}, download client and its version. '''If you are using [https://www.docker.com/ Docker] please run through [[Docker Guide|the Docker Guide]] first as that will solve common and frequent path/permissions issues. Otherwise please have a [[Docker Guide#Docker-compose|docker compose]] handy''' Tell us about what you've tried already, what you've looked at. Use the Logging and Log Files to turn your logging up to trace, recreate the issue, pastebin the relevant context and include a link to it in your post. Maybe even include some screen shots to highlight the issue.

The more we know, the easier it is to help you.

== Logging and Log Files ==

If you're linked here for support remember to get them the information from the actual trace log file, put the logs in a pastebin and show us context around what we need to see. If you're asked for debug logs your logs will contain <code>debug</code> and if you're asked for trace logs your logs will contain <code>trace</code>. If the logs you are providing do not contain either then they are not the logs requested.

What you need to do is:
# Turn Logging up to Trace
# Clear Logs
# Reproduce the Issue
# Open the trace log file ({{{ARRNAME}}}.trace.txt) and fine the relevant context
# [https://hastebin.com/ Hastebin], [https://pastebin.ubuntu.com/ Pastebin], [https://0bin.net/ 0bin], or any other pastebin type site a big chunk before the issue, the issue, and a big chunk after the issue.

* Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use N++. You can use the Notepad++ "Find in Files" function to search old log files as needed.
* '''Unix Only:''' Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use grep. For example if you want to find information about the movie or show "Shooter" you can run the following command <code>grep -inr -C 100 -e 'Shooter' /path/to/logs/*.trace*.txt</code> If your [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]] is in your home folder then you'd run: <code>grep -inr -C 100 -e 'Shooter' /home/$User/.config/logs/*.trace*.txt</code>
<div style="margin-left: 2em;"><pre>
* The flags have the following functions
* -i: ignore case
* -n: show line number
* -r: recursively check all files in the path
* -C: provide # of lines before and after the line it is found on
* -e: the pattern to search for
</pre></div>

==== Standard Logs Location ====
The log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the logs/ folder. You can also access the log files from the {{{ARRNAME}}} UI at System -> Logs -> Files.

Note: The Logs ("Events") Table in the UI is not the same as the log files and isn't as useful. If you're asked for logs, please copy/paste from the log files and not the table.

==== Update Logs Location ====
The update log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the UpdateLogs/ folder.

==== Sharing Logs ====
The logs can be long and hard to read as part of a forum or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit] post and they're spammy in [{{{ARR_DISCORD}}} Discord], so please use [https://pastebin.ubuntu.com/ Pastebin], [https://hastebin.com/ Hastebin], or any other similar pastebin site . The whole file typically isn't needed, just a good amount of context from before and after the issue/error. Don't forget to wait for spammy tasks like the RSS sync or library refresh to finish.

==== Trace/Debug Logs ====

You can change the log level at Settings -> General -> Logging. {{{ARRNAME}}} does not need to restarted for the change to take effect. This change only affects the log files, not the logging database. The latest debug/trace log files are named <code>{{{ARRNAME}}}.debug.txt</code> and <code>{{{ARRNAME}}}r.trace.txt</code> respectively.

If you're unable to access the {{{ARRNAME}}} UI to set the logging level you can do so by editing config.xml in the AppData directory by setting the LogLevel value to Debug or Trace instead of Info.
<div style="margin-left: 2em;"><pre>
<Config>
...
<LogLevel>debug</LogLevel>
...
</Config>
</pre></div>

==== Clearing Logs ====

You can clear log files and the logs database directly from the UI, under System -> Logs -> Files and System -> Logs -> Delete (Trash Can Icon)

==== Multiple Log Files ====

{{{ARRNAME}}} uses rolling log files limited to 1MB each. The current log file is always ,<code>{{{ARRNAME}}}.txt</code>, for the the other files <code>{{{ARRNAME}}}.0.txt</code> is the next newest (the higher the number the older it is). This log file contains fatal, error, warn, and info entries.

When Debug log level is enabled, additional <code>{{{ARRNAME}}}.debug.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, and debug entries. It usually covers a 40h period.

When Trace log level is enabled, additional <code>{{{ARRNAME}}}.trace.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, debug, and trace entries. Due to trace verbosity it only covers a couple of hours at most.

== Recovering from a Failed Update ==
----
==== Purpose ====
We do everything we can to prevent issues when upgrading, but they occur, this will walk you through the steps of recovering your installation.

==== Determine the issue ====
The best place to look when {{{ARRNAME}}} won't start after an update is your log files, before trying to start {{{ARRNAME}}} again, use [[{{{ARRNAME}}} Settings#Logging|Logging]] and [[{{{ARRNAME}}} System#Log_Files|Log Files]] to find them and increase the log level.

'''Migration Issue'''

Migration errors won't be identical, but here is an example:

<code>
14-2-4 18:56:49.5|Info|MigrationLogger|*** 36: update_with_quality_converters migrating ***

14-2-4 18:56:49.6|Error|MigrationLogger|SQL logic error or missing database duplicate column name: Items

While Processing: "ALTER TABLE "QualityProfiles" ADD COLUMN "Items" TEXT"

</code>

==== Resolving the issue ====
In the event of a migration issue there is not much you can do immediately, if the issue is specific to you (or there are not yet any posts), please create a post on [https://reddit.com/r/{{{ARRNAME}}} our subreddit] or swing by our discord, if there are others with the same issue, then rest assured we are working on it.

==== Manually upgrading ====
Grab the latest release from [{{{ARR_WEBSITE}}} our website]

Install the update (.exe) or extract (.zip) the contents over your existing installation and re-run {{{ARRNAME}}} as you normally would.

== Downloads and Importing ==

Downloading and importing is where ''most'' people experience issues. From a high level perspective, {{{ARRNAME}}} 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.

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

When you reach out for help, be sure to read [[#Asking for Help|asking for help]] so that you can provide us with the details we’ll need.

=== Testing the Download Client ===

Ensure your download client(s) are running. Start by testing the download client, if it doesn’t work you’ll be able to see details in the trace level logs. You should find a URL you can put into your browser and see if it works. It could be a connection problem, which could indicate a wrong ip, hostname, port or even a firewall blocking access. It might be obvious, like an authentication problem where you’ve gotten the username, password or apikey wrong.

=== Testing a Download ===

Now we’ll try a download, pick a {{{MEDIA}}} and do a manual search. Pick one of those files and attempt to download it. Does it get sent to the download client? Does it end up with the correct category? Does it show up in Activity? Does it end up in the trace level logs during the '''Check For Finished Download''' task which runs roughly every minute? Does it get correctly parsed during that task? Does the queued up download have a reasonable name? Since {{{ARRNAME}}} searches by '''{{{SEARCHSOURCE}}}''', on most indexers/trackers, it can queue one up with a name that it can’t recognize.

=== Testing an Import ===

Import issues should almost always manifest as an item in Activity with an orange icon you can hover to see the error. If they’re not showing up in Activity, this is the issue you need to focus on first so go back and figure that out. Most import errors are ''permissions'' issues, remember that {{{ARRNAME}}} needs to be able to read and write in the download folder. Sometimes, permissions in the library folder can be at fault too, so be sure to check both.

Incorrect path issues are possible too, though less common in normal setups. The key to understanding path issues is knowing that {{{ARRNAME}}} gets the path to the download ''from'' the download client, via its API. This becomes a problem in more unique use cases, like the download client running on a different system (maybe even OS!). It can also occur in a Docker setup, when volumes are not done well. A remote path map is a good solution where you don’t have control, like a seedbox setup. On a Docker setup, fixing the paths is a better option.

=== Common Problems ===

==== Download Client's WebUI is not enabled ====
{{{ARRNAME}}} talks to you download client via it's API and accesses it via the client's webui. You must ensure the client's webui is enabled and the port it is using does not conflict with any other client ports in use or ports in use on your system.

==== SSL in use and incorrectly configured ====
Ensure SSL encryption is not turned on if you're using both your {{{ARRNAME}}} instance and your download client on a local network. See [[{{{ARRNAME}}}_FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

==== Can’t see share on Windows ====

The default user for a Windows service is '''SYSTEM''' which typically doesn’t have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [[{{{ARRNAME}}} FAQ#Why can’t {{{ARRNAME}}} see my files on a remote server?|why can’t {{{ARRNAME}}} see my files on a remote server]] for details.

==== Mapped network drives are not reliable ====

While mapped network drives like <code>X:\</code> are convenient, they aren’t as reliable as UNC paths like <code>\\server\share</code> and they’re also not available before login. Setup {{{ARRNAME}}} and your download client(s) so that they use UNC paths as needed. If your library is on a share, you’d make sure your root folders are using UNC paths. If your download client sends to a share, that is where you’ll need to configure UNC paths since {{{ARRNAME}}} gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don’t use them for automation.

==== Docker and user, group, ownership, permissions and paths ====

Docker adds another layer of complexity that is easy to get wrong, but still end up with a setup that functions, but has various problems. Instead of going over them here, read this wiki article [[Docker Guide|for these automation software and Docker]] which is all about user, group, ownership, permissions and paths. It isn’t specific to any Docker system, instead it goes over things at a high level so that you can implement them in your own environment.

==== Permissions on the Library Folder ====
Don’t forget to check permissions and ownership of the ''destination''. It is easy to get fixated on the download’s ownership and permissions and that is ''usually'' the cause of permissions related issues, but it ''could'' be the destination as well. Check that the destination folder(s) exist. Check that a destination ''file'' doesn’t already exist or can’t be deleted or moved to recycle bin. Check that ownership and permissions allow the downloaded file to be copied, hard linked or moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the root folder.

==== Permissions on the Downloads Folder ====

Don’t forget to check permissions and ownership of the ''source''. It is easy to get fixated on the destination's ownership and permissions and that is a ''possible'' cause of permissions related issues, but it ''typically'' is the source. Check that the source folder(s) exist. Check that ownership and permissions allow the downloaded file to be copied/hardlinked or copy+delete/moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the downloads folder.

==== Download folder and library folder not different folders ====

The download client should download into a folder accessible by {{{ARRNAME}}} and that is not your root/library folder; {{{ARRNAME}}} should import from that separate download folder into your Library folder.

You should never download directly into your root folder. You also should not use your root folder as the download client's completed folder or incomplete folder.

If you download right into your library folder, you’ll end up with multiple copies of your media and when there are import issues, which there will be, you may not notice because your media server will see the download client copy.

The download folder will also be a hot mess of poorly named folders and files while your library folder will be nice and neat.

This frequently causes other random import issues as well.

==== Incorrect category ====

{{{ARRNAME}}} should be setup to use a category so that it only tries to process its own downloads. It is rare that a torrent submitted by {{{ARRNAME}}} gets added without the correct category, but it can happen. If you’re adding torrents manually and want {{{ARRNAME}}} to process them, they’ll need to have the correct category. It can be set at any time, since {{{ARRNAME}}} tries to process downloads every minute.

==== Packed torrents ====

If your torrent is packed in <code>.rar</code> files, you’ll need to setup extraction. We recommend [https://github.com/davidnewhall/unpackerr unpackerr]. One issue to look out for with packed torrents is that the video file will be copied or hard linked like normal, but it isn’t needed since the <code>.rar</code> files are seeding. That means if you’re using a ''copy'' setup, the torrent will be consuming double the space. And if you’re using a hard link setup, your torrent folder will be a little messier because of the unneeded file. This can be mitigated with a [https://gist.github.com/fryfrog/94716e7e27ba38dff57c7631d9f58bed cleanup script].

==== Repeated downloads ====

There are a few causes of repeated downloads, but a recent one is related to the Indexer restriction in Release Profiles. Because the indexer ''isn’t'' stored with the data, any preferred word scores are ''zero'' for media in your library, ''but'' during “RSS” and search, they’ll be applied. This gets you into a loop where you download the items again and again because it looks like an upgrade, then isn’t, then shows up again and looks like an upgrade, then isn’t. Don’t restrict your release profile to an indexer.

==== Usenet download misses import ====

{{{ARRNAME}}} only looks at the 60 most recent downloads in SABnzbd and NZBGet, so if you ''keep'' your history this means that during large queues with import issues, downloads can be silently missed and not imported. The best way to avoid that is to keep your history clear, so that any items that still appear need investigating. You can achieve this by enabling Remove under Completed and Failed Download Handler. In nzbget, this will move items to the ''hidden'' history which is great. Unfortunately, sabnzbd does not have a similar feature. The best you can achieve there is to use the nzb backup folder.

==== Download client clearing items ====

The download client should ''not'' be responsible for removing downloads. Usenet clients should be configured so they ''don’t'' remove downloads from history. Torrent clients should be setup so they ''don’t'' remove torrents when they’re finished seeding (pause or stop instead). This is because {{{ARRNAME}}} communicates with the download client to know what to import, so if they’re ''removed'' there is nothing to be imported… even if there is a folder full of files.

For Sabnzbd, this is handled with the History Retention setting.

=== Problem Not Listed ===
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

== Searches Indexers and Trackers ==

=== Turn logging up to trace ===

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

=== Testing an Indexer or Tracker ===

When you test an indexer or tracker, in debug or trace logs you can find the URL used. An example of a successful test is below, you can see it query the indexer via a specific URL with specific parameters and then the response. You test this url in your browser like <code>{{{QUERYSTRING}}}</code> replacing the <code>apikey=(removed)</code> with the correct apikey like <code>apikey=123</code>. You can experiment with the parameters if you’re getting an error from the indexer or see if you have connectivity issues if it doesn’t even work. After you’ve tested in your own browser, you should test from the system {{{ARRNAME}}} is running on ''if'' you haven’t already.

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block}}

=== Testing a Search ===
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_testing_a_search}}

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers1.png|thumb|none|750px]]

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers2.png|thumb|none|750px]]

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block2}}

Here you can see the ''full'' trace log below
{{#lst:Troubleshooting Misc|{{{ARRNAME2}}}_trace_logs_example}}

=== Common Problems ===

==== Media is Unmonitored ====
The {{{MEDIA}}} is/are not monitored.

==== Wrong categories ====

Incorrect categories is probably the most common cause of results showing in manual searches of an indexer/tracker, but ''not'' in {{{ARRNAME}}}. The indexer/tracker ''should'' show the category in the search results, which should help you figure out what is missing. If you’re using Jackett, each tracker has a list of specifically supported categories. Make sure you’re using the correct ones for Categories. I find it helpful to have the list visible in one browser window while I edit the entry in {{{ARRNAME}}}.
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_type}}
==== Wrong results ====

Sometimes indexers will return completely unrelated results, {{{ARRNAME}}} will feed in parameters to limit the search to a {{{SEARCHSOURCE}}}, but the results returned are completely unrelated. Or sometimes, mostly related with a few incorrect results. The first is usually an indexer problem and you’ll be able to tell from the trace logs which is causing it. You can disable that indexer and report the problem. The other is usually categorized releases which should be reportable on the indexer/tracker.

==== Certificate validation ====

You’ll be connecting to most indexers/trackers via https, so you’ll need that to work properly on your system. That means your time zone and time both need to be set ''correctly''. It also means your system certificates need to be up to date.

==== Hitting rate limits ====

If you run your {{{ARRNAME}}} through a VPN or proxy, you may be competing with 10s or 100s or 1000s of other people all trying to use services like {{{SEARCHSOURCE}}}, theXEM ,and/or your indexers and trackers. Rate limiting and DDOS protection are often done by IP address and your VPN/proxy exit point is ''one'' IP address. Unless you’re in a repressive country like China, Australia or South Africa you don’t need to VPN/proxy {{{ARRNAME}}}.

Rarbg has a tendency to have some sort of rate limiting within their API and displays as responding with no results.

==== Using the Jackett /all endpoint ====

The Jackett <code>/all</code> endpoint is convenient, but that is its only benefit. Everything else is potential problems, so adding each tracker individually is recommended.

[https://github.com/Jackett/Jackett#aggregate-indexers Even Jackett says it should be avoided and should not be used.]

Using the all endpoint has no advantages (besides reduced management overhead), only disadvantages:
* you lose control over indexer specific settings (categories, search modes, etc.)
* mixing search modes (IMDB, query, etc.) might cause low-quality results
* indexer specific categories (>= 100000) can't be used.
* slow indexers will slow down the overall result
* total results are limited to 1000

Adding each indexer separately It allows for fine tuning of categories on a per indexer basis, which can be a problem with the <code>/all</code> end point if using the wrong category causes errors on some trackers. In {{{ARRNAME}}}, each indexer is limited to 1000 results if pagination is supported or 100 if not, which means as you add more and more trackers to Jackett, you’re more and more likely to clip results. Finally, if ''one'' of the trackers in <code>/all</code> returns an error, {{{ARRNAME}}} will disable it and now you don’t get any results.

==== Problem Not Listed ====
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

=== Errors ===

These are some of the common errors you may see when adding an indexer

==== The underlying connection was closed: An unexpected error occurred on a send. ====

This is caused by the indexer using a SSL protocol not supported by .net 4.5, to resolve this you will need to install .net 4.5, which is available on Vista/Server 2008 and above (if you’re on XP/Server 2003 its time to upgrade).

==== The request timed out ====

{{{ARRNAME}}} seems to have issues with certain TLS versions or configurations. If you get the following error messages in your log:
<pre>System.Net.WebException: The request timed out: ’https://example.org/api?t=caps&apikey=(removed) —> System.Net.WebException: The request timed out</pre>

And you can see the following in the trace log file:
<pre><DATE&TIME>|Trace|FallbackHttpDispatcher|Curl not available, using default WebClient. </pre>

You might fix it by installing libcurl3. On Ubuntu/Debian use;
<pre>apt install libcurl3</pre>

This can also be caused by:
* improperly configured or use of a VPN
* improperly configured or use of a proxy
* local DNS issues
* local IPv6 issues

System status

2021-05-09T04:54:54Z

Bakerboy448:

== System ==
=== Health ===
==== Overview ====
====== Radarr ======
<section begin=radarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=radarr_system_status_health_overview />
====== Sonarr ======
<section begin=sonarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=sonarr_system_status_health_overview />
====== Lidarr ======
<section begin=lidarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=lidarr_system_status_health_overview />
====== Readarr ======
<section begin=readarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=readarr_system_status_health_overview />
==== System Warnings ====
===== Radarr =====
<section begin=radarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Radarr are targeted for .NET. We will no longer be providing legacy mono builds after 3.2 is released. You are running one of these legacy builds but your platform supports .NET.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''[[Radarr_FAQ#how_do_i_backup_restore_my_Radarr| Back-Up your existing configuration]]''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>master</code> branch. If you are on <code>develop</code> or <code>nightly</code> you'll need to adjust <code>/master/</code> in the URL.
*** '''Delete your existing binaries (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''.
****<code>wget --content-disposition <nowiki>'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop radarr</code> Stop Radarr
****<code> sudo mv /opt/Radarr /opt/Radarr.old</code> Backup the old Binaries
**** <code> tar -xvzf Radarr*.linux-core-x64.tar.gz</code> Extract the Radarr Tarball
**** <code> sudo mv Radarr/ /opt</code> Move the new Radarr Binaries
**** <code> sudo chown -R radarr:radarr /opt/Radarr</code> Ensure Radarr has permissions to its directory, this assumes it runs as the user <code>radarr</code>
**** <code> sudo rm -rf /opt/Radarr.old</code> Remove the old binaries
**** <code> sudo rm -rf Radarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script in your systemd (<code> sudo nano -e /etc/systemd/system/radarr.service</code>) to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.
***** If Radarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start radarr.service</code> Restart Radarr

* '''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''
** Radarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.20 is the absolute minimum for Radarr.
** The upgrade procedure for Mono varies per platform.

*'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''
** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0.

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.

*'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.
** Please look at System -> Info to see the current AppData & Startup directories.
** This means Radarr will be unable to update itself without risking data-loss.
** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081

** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:7878/$1 [P,L]
** For Caddy (V1) use this:
*** Note: you'll also need to add the websocket directive to your radarr configuration
proxy /radarr 127.0.0.1:7878 {
websocket
transparent
}

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#ptp_settings_old|PTP Indexer Settings Out of Date]]'''
** The following PassThePopcorn indexers have deprecated settings and should be updated.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

*'''[[#mono_support_end_of_life|Mono and x86 builds are ending]]'''
** Mono and x86 builds will no longer be supported in the next build of the application. If you are receiving this error then you are running the mono version of the application or the x86 version. Unfortunately, due to increasing difficulting in development support for these legacy versions we will be discontinuing their support and thus releases for them going forward. Thus it is advised you upgrade to a supported Operating System that does not require neither x86 nor mono. You may also be able to explore using Docker for your needs.

<section end=radarr_system_status_health_system_warnings />

===== Sonarr =====
<section begin=sonarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]'''
** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].

* '''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''
** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].

* '''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''
** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform. 
** Mono 5.8 is the absolute minimum for Sonarr, but Mono 5.20 is currently recommended.
** The upgrade procedure for Mono varies per platform.

* '''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''
** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** The upgrade procedure for Mono varies per platform.

* '''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.
** ''(This warning will not appear if your current version is less than 14 days old)''

* '''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.

* '''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''
** Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux. 
** Please look at System -> About to see the current AppData & Startup directories.
** This means Sonarr will be unable to update itself without risking data-loss.
** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.
* '''[[#package_maintainer_message|Package Maintainer Message]]'''
** Please refer to the specific message your package maintainer is indicating to you. This is not a Sonarr issue. For additional information, refer to your package maintainer. Your package maintainer can be found in System -> Status -> About. Note that this includes docker and your package maintainer is whomever maintains your docker image.

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=sonarr_system_status_health_system_warnings />

===== Lidarr =====
<section begin=lidarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Lidarr are targeted for .NET. We will soon no longer provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''Back-Up your existing configuration''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>develop</code> branch. If you are on <code>nightly</code> you'll need to adjust <code>/develop/</code> in the URL.
***'''Delete your existing binaries (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''
****<code>wget --content-disposition <nowiki>'http://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop lidarr.service</code> Stop Lidarr
****<code> sudo mv /opt/Lidarr /opt/Lidarr.old</code> Backup the old Binaries
****<code> tar -xvzf Lidarr*.linux-core-x64.tar.gz</code> Extract the Lidarr Tarball
****<code> sudo mv Lidarr/ /opt</code> Move the new Lidarr Binaries
****<code> sudo chown -R lidarr:lidarr /opt/Lidarr</code> Ensure Lidarr has permissions to its directory, this assumes it runs as the user <code>lidarr</code>
****<code> sudo rm -rf /opt/Lidarr.old</code> Remove the old binaries
****<code> sudo rm -rf Lidarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script (<code> sudo nano -e /etc/systemd/system/lidarr.service</code>) to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.
***** If Lidarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start lidarr.service</code> Restart Lidarr

*'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''
** Lidarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.20 is the absolute minimum for Lidarr.
** The upgrade procedure for Mono varies per platform..
** See "Update to .NET Core version above"

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081
** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:8686/$1 [P,L]

*'''[[#fpcalc_upgrade|Fpcalc Needs Upgrading]]'''
Lidarr can use chromaprint audio fingerprinting to identify tracks. This depends on an external binary, which is distributed with Lidarr for Windows and macOS, but must be provided independently on Linux.

To fix this on a native Linux instance, install the appropriate package using your package manager and make sure that fpcalc is on your PATH (this can be checked using which fpcalc and verifying that the correct location of fpcalc is returned):

{| class="wikitable"
|- style="font-weight:bold; text-align:center; vertical-align:middle;"
! Distribution
! Package
|-
| style="vertical-align:middle;" | Debian/Ubuntu
| <code>libchromaprint-tools</code>
|-
| style="vertical-align:middle;" | Fedora/CentOS
| <code>chromaprint-tools</code>
|-
| style="vertical-align:middle;" | Arch
| <code>chromaprint</code>
|-
| style="vertical-align:middle;" | OpenSUSE
|<code> chromaprint-fpcalc</code>
|-
| style="vertical-align:middle;" | Synology
| <code>chromaprint</code>
|}

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=lidarr_system_status_health_system_warnings />

===== Readarr =====
<section begin=readarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Readarr are targeted for .NET. We will soon no longer provide legacy mono builds for those platforms that cannot use .NET. You are running one of these legacy builds but your platform supports .NET Core.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''Back-Up your existing configuration''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>master</code> branch. If you are on <code>develop</code> or <code>nightly</code> you'll need to adjust <code>/master/</code> in the URL.
***'''Delete your existing binaries (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''.
****<code>wget --content-disposition <nowiki>'http://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop readarr</code> Stop Readarr
****<code> sudo mv /opt/Readarr /opt/Readarr.old</code> Backup the old Binaries
****<code> tar -xvzf Readarr*.linux-core-x64.tar.gz</code> Extract the Readarr Tarball
****<code> sudo mv Readarr/ /opt</code> Move the new Readarr Binaries
****<code> sudo chown -R readarr:readarr /opt/Readarr</code> Ensure Readarr has permissions to its directory, this assumes it runs as the user <code>readarr</code>
****<code> sudo rm -rf /opt/Readarr.old</code> Remove the old binaries
****<code> sudo rm -rf Readarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script (<code> sudo nano -e /etc/systemd/system/readarr.service</code>) to call <code>Readarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.
***** If Readarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start readarr.service</code> Restart Readarr

*'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''
** Readarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.20 is the absolute minimum for Readarr.
** The upgrade procedure for Mono varies per platform.
** See "Update to .NET Core version above"

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081
** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:8787/$1 [P,L]

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=readarr_system_status_health_system_warnings />

==== Download Clients ====
===== Radarr =====
<section begin=radarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.
*** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Radarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Radarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Radarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Radarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Radarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/hardlinks How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

[https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Radarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#permissions_error|Permissions Error]]'''
** Radarr or the user radarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end=radarr_system_status_health_download_clients />

===== Sonarr =====
<section begin=sonarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Sonarr.
*** Ensure SSL encryption is not turned on if you're using both your Sonarr instance and your download client on a local network. See [[Sonarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Sonarr to prevent the errors.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Sonarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Sonarr/V3/Sonarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#permissions_error|Permissions Error]]'''
** Sonarr or the user sonarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end="sonarr_system_status_health_download_clients" />

===== Lidarr =====
<section begin=lidarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.
*** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Lidarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Lidarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished song is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Lidarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Lidarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/audio</code> and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/audio</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Lidarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* '''[[#permissions_error|Permissions Error]]'''
** Lidarr or the user lidarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=lidarr_system_status_health_download_clients />
===== Readarr =====
<section begin=readarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.
*** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Readarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Readarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Readarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished book is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Readarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Readarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/books</code> and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/books</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Readarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* '''[[#permissions_error|Permissions Error]]'''
** Readarr or the user readarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=readarr_system_status_health_download_clients />

==== Completed/Failed Download Handling ====
===== Radarr =====
<section begin=radarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=radarr_system_status_health_complete_failed_download_handling />

===== Sonarr =====
<section begin=sonarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the
<section end=sonarr_system_status_health_complete_failed_download_handling />

===== Lidarr =====
<section begin=lidarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidrr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=lidarr_system_status_health_complete_failed_download_handling />

===== Readarr =====
<section begin=readarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=readarr_system_status_health_complete_failed_download_handling />

==== Indexers ====
===== Radarr =====
<section begin=radarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_radarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Radarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_radarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Radarr will not grab new releases automatically]]'''
** So Radarr uses the RSS feed to pick up new releases as they come along. More info on that [[Radarr FAQ#How does Radarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=radarr_system_status_health_indexers />

===== Sonarr =====
<section begin=sonarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_sonarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Sonarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_sonarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Sonarr will not grab new releases automatically]]'''
** So Sonarr uses the RSS feed to pick up new releases as they come along. More info on that [[Sonarr FAQ#How does Sonarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''
** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=sonarr_system_status_health_indexers />
===== Lidarr =====
<section begin=lidarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Lidarr will not grab new releases automatically]]'''
** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for music (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=lidarr_system_status_health_indexers />
===== Readarr =====
<section begin=readarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_readarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Readarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_readarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Readarr will not grab new releases automatically]]'''
** So Readarr uses the RSS feed to pick up new releases as they come along. More info on that [[Readarr FAQ#How does Readarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for books (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=readarr_system_status_health_indexers />

==== Folders ====
===== Radarr =====
<section begin=radarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder
***# Easiest way to find this is to go to the Movies (Library) Tab
***# Create a custom filter with the old root folder path
***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files
<section end=radarr_system_status_health_folders />
===== Sonarr =====
<section begin=sonarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder
***# Go to the Series > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these series to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files
* '''[[#import_list_missing_root_folder|Import List missing root folder]]'''
** This error is typically identified if a list is looking for a root folder but that root folder is no longer available.
**#Go to Settings > Import Lists
**#Edit the import lists that were mentioned in the health check
**#Save
<section end=sonarr_system_status_health_folders />
===== Lidarr =====
<section begin=lidarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these artists to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files
<section end=lidarr_system_status_health_folders />
===== Readarr =====
<section begin=readarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these authors to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files
<section end=readarr_system_status_health_folders />

==== Media ====
===== Radarr =====
<section begin=radarr_system_status_health_media />
* '''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''
** The movie is linked to a TMDb Id that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It. 
** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu

* '''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''
** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.
<section end=radarr_system_status_health_media />
===== Sonarr =====
<section begin=sonarr_system_status_health_media />
* '''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''
** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.
<section end=sonarr_system_status_health_media />
===== Lidarr =====
<section begin=lidarr_system_status_health_media />
Text
<section end=lidarr_system_status_health_media />
===== Readarr =====
<section begin=readarr_system_status_health_media />
Text
<section end=readarr_system_status_health_media />

=== Disk Space ===
==== Radarr ====
<section begin=radarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=radarr_system_status_disk_space />
==== Sonarr ====
<section begin=sonarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=sonarr_system_status_disk_space />
==== Lidarr ====
<section begin=lidarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=lidarr_system_status_disk_space />
==== Readarr ====
<section begin=readarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=readarr_system_status_disk_space />

=== About ===
==== Radarr ====
<section begin=radarr_system_status_about />
This will tell you about your current install of Radarr
<section end=radarr_system_status_about />
==== Sonarr ====
<section begin=sonarr_system_status_about />
This will tell you about your current install of Radarr
<section end=sonarr_system_status_about />
==== Lidarr ====
<section begin=lidarr_system_status_about />
This will tell you about your current install of Lidarr
<section end=lidarr_system_status_about />
==== Readarr ====
<section begin=readarr_system_status_about />
This will tell you about your current install of Readarr
<section end=readarr_system_status_about />

=== More Info ===
==== Radarr ====
<section begin=radarr_system_status_more_info />
* Home Page: [https://radarr.video Radarr's home page]
* Wiki: [https://wiki.servarr.com/Radarr You're here already]
* Reddit: [https://reddit.com/r/radarr r/radarr]
* Discord: [https://radarr.video/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/radarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Radarr/Radarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]
<section end=radarr_system_status_more_info />
==== Sonarr ====
<section begin=sonarr_system_status_more_info />
* Home page: [https://sonarr.tv Sonarr's home page]
* Forums: [https://forums.sonarr.tv Sonarr Forums]
* Discord: [https://discord.gg/M6BvZn5 Join our discord]
* Reddit: [https://reddit.com/r/sonarr r/sonarr]
* Twitter: [https://twitter.com/sonarrtv @sonarrtv]
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]
* Wiki: [https://wiki.servarr.com/sonarr You're here already]
* Donations: If you're feeling generous and would like to donate [https://sonarr.tv/donate click here]
* Source: https://github.com/Sonarr/Sonarr Github]
* Feature Requests: Got a great idea drop it on Github [https://github.com/Sonarr/Sonarr/issues here]
<section end=sonarr_system_status_more_info />
==== Lidarr ====
<section begin=lidarr_system_status_more_info />
* Home page: [https://lidarr.audio Lidarr's home page]
* Wiki: [https://wiki.servarr.com/Lidarr You're here already]
* Reddit: [https://reddit.com/r/lidarr r/lidarr]
* Discord: [https://lidarr.audio/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/lidarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/lidarr/Lidarr/ Github]
* Feature Requests: Got a great idea drop it on GitHub [https://github.com/Lidarr/Lidarr/issues here]
<section end=lidarr_system_status_more_info />
==== Readarr ====
<section begin=readarr_system_status_more_info />
* Home page: [https://readarr.com Readarr's home page]
* Wiki: [https://wiki.servarr.com/Readarr You're here already]
* Reddit: [https://reddit.com/r/readarr r/readarr]
* Discord: [https://readarr.com/discord Join our discord]
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Readarr/Readarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Readarr/Readarr/issues click here]
<section end=readarr_system_status_more_info />

=== Templates ===

Template:Troubleshooting

2021-05-08T23:34:11Z

Bakerboy448: /* Download folder and library folder not different folders */

<noinclude>
<templatedata>
{
"params": {
"ARRNAME": {
"description": "Name of the Application",
"example": "Radarr",
"type": "string",
"required": true
},
"ARR_DISCORD": {
"description": "Link to the ARR #support Discord",
"type": "url",
"required": true
},
"ARR_WEBSITE": {
"description": "Link to the ARR Website",
"type": "url",
"required": true
},
"ARR_LATEST_RELEASE": {
"description": "Link to the ARR Download",
"type": "url",
"required": true
},
"VERSION": {
"description": "The current version of each of the ARRs",
"type": "string",
"required": true
},
"MEDIA": {
"description": "What type of media does the ARR use",
"example": "Radarr: movies, Sonarr: series, Lidarr: artist, Readarr: author",
"type": "string",
"required": true
},
"SEARCHSOURCE": {
"description": "What metadata provider does the ARR use",
"example": "Radarr: TMDb, Sonarr: TheTVDb, Lidarr: MusicBrainz, Readarr: GoodReads",
"type": "string",
"required": true
},
"QUERYSTRING": {},
"ARRNAME2": {
"description": "This string is used for lower cased ARR names for transclusion",
"example": "radarr, sonarr, lidarr, readarr",
"type": "string",
"required": true
}
},
"description": "This template is utilized for general troubleshooting steps that span across all the ARRs. Some Sections may be transcluded from a Troubleshooting Misc page when items are ARR specific."
}
</templatedata>
</noinclude>
== Troubleshooting ==
----
Please note that this information is only for {{{ARRNAME}}} {{{VERSION}}}.
=== Asking for Help ===
----
Do you need help? That's okay, everyone needs help sometimes. You can get real time help via chat on [{{{ARR_DISCORD}}} Discord] or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit].

But before you go there and post, be sure your request for help is the best it can be. Clearly describe the problem and briefly describe your setup, including things like your OS/distribution, version of Mono or .Net/.Netcore, version of {{{ARRNAME}}}, download client and its version. '''If you are using [https://www.docker.com/ Docker] please run through [[Docker Guide|the Docker Guide]] first as that will solve common and frequent path/permissions issues. Otherwise please have a [[Docker Guide#Docker-compose|docker compose]] handy''' Tell us about what you've tried already, what you've looked at. Use the Logging and Log Files to turn your logging up to trace, recreate the issue, pastebin the relevant context and include a link to it in your post. Maybe even include some screen shots to highlight the issue.

The more we know, the easier it is to help you.

== Logging and Log Files ==

If you're linked here for support remember to get them the information from the actual trace log file, put the logs in a pastebin and show us context around what we need to see. If you're asked for debug logs your logs will contain <code>debug</code> and if you're asked for trace logs your logs will contain <code>trace</code>. If the logs you are providing do not contain either then they are not the logs requested.

What you need to do is:
# Turn Logging up to Trace
# Clear Logs
# Reproduce the Issue
# Open the trace log file ({{{ARRNAME}}}.trace.txt) and fine the relevant context
# [https://hastebin.com/ Hastebin], [https://pastebin.ubuntu.com/ Pastebin], [https://0bin.net/ 0bin], or any other pastebin type site a big chunk before the issue, the issue, and a big chunk after the issue.

* Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use N++. You can use the Notepad++ "Find in Files" function to search old log files as needed.
* '''Unix Only:''' Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use grep. For example if you want to find information about the movie or show "Shooter" you can run the following command <code>grep -inr -C 100 -e 'Shooter' /path/to/logs/*.trace*.txt</code> If your [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]] is in your home folder then you'd run: <code>grep -inr -C 100 -e 'Shooter' /home/$User/.config/logs/*.trace*.txt</code>
<div style="margin-left: 2em;"><pre>
* The flags have the following functions
* -i: ignore case
* -n: show line number
* -r: recursively check all files in the path
* -C: provide # of lines before and after the line it is found on
* -e: the pattern to search for
</pre></div>

==== Standard Logs Location ====
The log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the logs/ folder. You can also access the log files from the {{{ARRNAME}}} UI at System -> Logs -> Files.

Note: The Logs ("Events") Table in the UI is not the same as the log files and isn't as useful. If you're asked for logs, please copy/paste from the log files and not the table.

==== Update Logs Location ====
The update log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the UpdateLogs/ folder.

==== Sharing Logs ====
The logs can be long and hard to read as part of a forum or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit] post and they're spammy in [{{{ARR_DISCORD}}} Discord], so please use [https://pastebin.ubuntu.com/ Pastebin], [https://hastebin.com/ Hastebin], or any other similar pastebin site . The whole file typically isn't needed, just a good amount of context from before and after the issue/error. Don't forget to wait for spammy tasks like the RSS sync or library refresh to finish.

==== Trace/Debug Logs ====

You can change the log level at Settings -> General -> Logging. {{{ARRNAME}}} does not need to restarted for the change to take effect. This change only affects the log files, not the logging database. The latest debug/trace log files are named <code>{{{ARRNAME}}}.debug.txt</code> and <code>{{{ARRNAME}}}r.trace.txt</code> respectively.

If you're unable to access the {{{ARRNAME}}} UI to set the logging level you can do so by editing config.xml in the AppData directory by setting the LogLevel value to Debug or Trace instead of Info.
<div style="margin-left: 2em;"><pre>
<Config>
...
<LogLevel>debug</LogLevel>
...
</Config>
</pre></div>

==== Clearing Logs ====

You can clear log files and the logs database directly from the UI, under System -> Logs -> Files and System -> Logs -> Delete (Trash Can Icon)

==== Multiple Log Files ====

{{{ARRNAME}}} uses rolling log files limited to 1MB each. The current log file is always ,<code>{{{ARRNAME}}}.txt</code>, for the the other files <code>{{{ARRNAME}}}.0.txt</code> is the next newest (the higher the number the older it is). This log file contains fatal, error, warn, and info entries.

When Debug log level is enabled, additional <code>{{{ARRNAME}}}.debug.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, and debug entries. It usually covers a 40h period.

When Trace log level is enabled, additional <code>{{{ARRNAME}}}.trace.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, debug, and trace entries. Due to trace verbosity it only covers a couple of hours at most.

== Recovering from a Failed Update ==
----
==== Purpose ====
We do everything we can to prevent issues when upgrading, but they occur, this will walk you through the steps of recovering your installation.

==== Determine the issue ====
The best place to look when {{{ARRNAME}}} won't start after an update is your log files, before trying to start {{{ARRNAME}}} again, use [[{{{ARRNAME}}} Settings#Logging|Logging]] and [[{{{ARRNAME}}} System#Log_Files|Log Files]] to find them and increase the log level.

'''Migration Issue'''

Migration errors won't be identical, but here is an example:

<code>
14-2-4 18:56:49.5|Info|MigrationLogger|*** 36: update_with_quality_converters migrating ***

14-2-4 18:56:49.6|Error|MigrationLogger|SQL logic error or missing database duplicate column name: Items

While Processing: "ALTER TABLE "QualityProfiles" ADD COLUMN "Items" TEXT"

</code>

==== Resolving the issue ====
In the event of a migration issue there is not much you can do immediately, if the issue is specific to you (or there are not yet any posts), please create a post on [https://reddit.com/r/{{{ARRNAME}}} our subreddit] or swing by our discord, if there are others with the same issue, then rest assured we are working on it.

==== Manually upgrading ====
Grab the latest release from [{{{ARR_WEBSITE}}} our website]

Install the update (.exe) or extract (.zip) the contents over your existing installation and re-run {{{ARRNAME}}} as you normally would.

== Downloads and Importing ==

Downloading and importing is where ''most'' people experience issues. From a high level perspective, {{{ARRNAME}}} 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.

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

When you reach out for help, be sure to read [[#Asking for Help|asking for help]] so that you can provide us with the details we’ll need.

=== Testing the Download Client ===

Ensure your download client(s) are running. Start by testing the download client, if it doesn’t work you’ll be able to see details in the trace level logs. You should find a URL you can put into your browser and see if it works. It could be a connection problem, which could indicate a wrong ip, hostname, port or even a firewall blocking access. It might be obvious, like an authentication problem where you’ve gotten the username, password or apikey wrong.

=== Testing a Download ===

Now we’ll try a download, pick a {{{MEDIA}}} and do a manual search. Pick one of those files and attempt to download it. Does it get sent to the download client? Does it end up with the correct category? Does it show up in Activity? Does it end up in the trace level logs during the '''Check For Finished Download''' task which runs roughly every minute? Does it get correctly parsed during that task? Does the queued up download have a reasonable name? Since {{{ARRNAME}}} searches by '''{{{SEARCHSOURCE}}}''', on most indexers/trackers, it can queue one up with a name that it can’t recognize.

=== Testing an Import ===

Import issues should almost always manifest as an item in Activity with an orange icon you can hover to see the error. If they’re not showing up in Activity, this is the issue you need to focus on first so go back and figure that out. Most import errors are ''permissions'' issues, remember that {{{ARRNAME}}} needs to be able to read and write in the download folder. Sometimes, permissions in the library folder can be at fault too, so be sure to check both.

Incorrect path issues are possible too, though less common in normal setups. The key to understanding path issues is knowing that {{{ARRNAME}}} gets the path to the download ''from'' the download client, via its API. This becomes a problem in more unique use cases, like the download client running on a different system (maybe even OS!). It can also occur in a Docker setup, when volumes are not done well. A remote path map is a good solution where you don’t have control, like a seedbox setup. On a Docker setup, fixing the paths is a better option.

=== Common Problems ===

==== Download Client's WebUI is not enabled ====
{{{ARRNAME}}} talks to you download client via it's API and accesses it via the client's webui. You must ensure the client's webui is enabled and the port it is using does not conflict with any other client ports in use or ports in use on your system.

==== SSL in use and incorrectly configured ====
Ensure SSL encryption is not turned on if you're using both your {{{ARRNAME}}} instance and your download client on a local network. See [[{{{ARRNAME}}}_FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

==== Can’t see share on Windows ====

The default user for a Windows service is '''SYSTEM''' which typically doesn’t have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [[{{{ARRNAME}}} FAQ#Why can’t {{{ARRNAME}}} see my files on a remote server?|why can’t {{{ARRNAME}}} see my files on a remote server]] for details.

==== Mapped network drives are not reliable ====

While mapped network drives like <code>X:\</code> are convenient, they aren’t as reliable as UNC paths like <code>\\server\share</code> and they’re also not available before login. Setup {{{ARRNAME}}} and your download client(s) so that they use UNC paths as needed. If your library is on a share, you’d make sure your root folders are using UNC paths. If your download client sends to a share, that is where you’ll need to configure UNC paths since {{{ARRNAME}}} gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don’t use them for automation.

==== Docker and user, group, ownership, permissions and paths ====

Docker adds another layer of complexity that is easy to get wrong, but still end up with a setup that functions, but has various problems. Instead of going over them here, read this wiki article [[Docker Guide|for these automation software and Docker]] which is all about user, group, ownership, permissions and paths. It isn’t specific to any Docker system, instead it goes over things at a high level so that you can implement them in your own environment.

==== Permissions on the Library Folder ====
Don’t forget to check permissions and ownership of the ''destination''. It is easy to get fixated on the download’s ownership and permissions and that is ''usually'' the cause of permissions related issues, but it ''could'' be the destination as well. Check that the destination folder(s) exist. Check that a destination ''file'' doesn’t already exist or can’t be deleted or moved to recycle bin. Check that ownership and permissions allow the downloaded file to be copied, hard linked or moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the root folder.

==== Permissions on the Downloads Folder ====

Don’t forget to check permissions and ownership of the ''source''. It is easy to get fixated on the destination's ownership and permissions and that is a ''possible'' cause of permissions related issues, but it ''typically'' is the source. Check that the source folder(s) exist. Check that ownership and permissions allow the downloaded file to be copied/hardlinked or copy+delete/moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the downloads folder.

==== Download folder and library folder not different folders ====

The download client should download into a folder accessible by {{{ARRNAME}}} and that is not your root/library folder; {{{ARRNAME}}} should import from that separate download folder into your Library folder.

You should never download directly into your root folder. You also should not use your root folder as the download client's completed folder or incomplete folder.

If you download right into your library folder, you’ll end up with multiple copies of your media and when there are import issues, which there will be, you may not notice because your media server will see the download client copy.

The download folder will also be a hot mess of poorly named folders and files while your library folder will be nice and neat.

This frequently causes other random import issues as well.

==== Incorrect category ====

{{{ARRNAME}}} should be setup to use a category so that it only tries to process its own downloads. It is rare that a torrent submitted by {{{ARRNAME}}} gets added without the correct category, but it can happen. If you’re adding torrents manually and want {{{ARRNAME}}} to process them, they’ll need to have the correct category. It can be set at any time, since {{{ARRNAME}}} tries to process downloads every minute.

==== Packed torrents ====

If your torrent is packed in <code>.rar</code> files, you’ll need to setup extraction. We recommend [https://github.com/davidnewhall/unpackerr unpackerr]. One issue to look out for with packed torrents is that the video file will be copied or hard linked like normal, but it isn’t needed since the <code>.rar</code> files are seeding. That means if you’re using a ''copy'' setup, the torrent will be consuming double the space. And if you’re using a hard link setup, your torrent folder will be a little messier because of the unneeded file. This can be mitigated with a [https://gist.github.com/fryfrog/94716e7e27ba38dff57c7631d9f58bed cleanup script].

==== Repeated downloads ====

There are a few causes of repeated downloads, but a recent one is related to the Indexer restriction in Release Profiles. Because the indexer ''isn’t'' stored with the data, any preferred word scores are ''zero'' for media in your library, ''but'' during “RSS” and search, they’ll be applied. This gets you into a loop where you download the items again and again because it looks like an upgrade, then isn’t, then shows up again and looks like an upgrade, then isn’t. Don’t restrict your release profile to an indexer.

==== Usenet download misses import ====

{{{ARRNAME}}} only looks at the 60 most recent downloads in SABnzbd and NZBGet, so if you ''keep'' your history this means that during large queues with import issues, downloads can be silently missed and not imported. The best way to avoid that is to keep your history clear, so that any items that still appear need investigating. You can achieve this by enabling Remove under Completed and Failed Download Handler. In nzbget, this will move items to the ''hidden'' history which is great. Unfortunately, sabnzbd does not have a similar feature. The best you can achieve there is to use the nzb backup folder.

==== Download client clearing items ====

The download client should ''not'' be responsible for removing downloads. Usenet clients should be configured so they ''don’t'' remove downloads from history. Torrent clients should be setup so they ''don’t'' remove torrents when they’re finished seeding (pause or stop instead). This is because {{{ARRNAME}}} communicates with the download client to know what to import, so if they’re ''removed'' there is nothing to be imported… even if there is a folder full of files.

=== Problem Not Listed ===
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

== Searches Indexers and Trackers ==

=== Turn logging up to trace ===

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

=== Testing an Indexer or Tracker ===

When you test an indexer or tracker, in debug or trace logs you can find the URL used. An example of a successful test is below, you can see it query the indexer via a specific URL with specific parameters and then the response. You test this url in your browser like <code>{{{QUERYSTRING}}}</code> replacing the <code>apikey=(removed)</code> with the correct apikey like <code>apikey=123</code>. You can experiment with the parameters if you’re getting an error from the indexer or see if you have connectivity issues if it doesn’t even work. After you’ve tested in your own browser, you should test from the system {{{ARRNAME}}} is running on ''if'' you haven’t already.

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block}}

=== Testing a Search ===
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_testing_a_search}}

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers1.png|thumb|none|750px]]

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers2.png|thumb|none|750px]]

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block2}}

Here you can see the ''full'' trace log below
{{#lst:Troubleshooting Misc|{{{ARRNAME2}}}_trace_logs_example}}

=== Common Problems ===

==== Media is Unmonitored ====
The {{{MEDIA}}} is/are not monitored.

==== Wrong categories ====

Incorrect categories is probably the most common cause of results showing in manual searches of an indexer/tracker, but ''not'' in {{{ARRNAME}}}. The indexer/tracker ''should'' show the category in the search results, which should help you figure out what is missing. If you’re using Jackett, each tracker has a list of specifically supported categories. Make sure you’re using the correct ones for Categories. I find it helpful to have the list visible in one browser window while I edit the entry in {{{ARRNAME}}}.
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_type}}
==== Wrong results ====

Sometimes indexers will return completely unrelated results, {{{ARRNAME}}} will feed in parameters to limit the search to a {{{SEARCHSOURCE}}}, but the results returned are completely unrelated. Or sometimes, mostly related with a few incorrect results. The first is usually an indexer problem and you’ll be able to tell from the trace logs which is causing it. You can disable that indexer and report the problem. The other is usually categorized releases which should be reportable on the indexer/tracker.

==== Certificate validation ====

You’ll be connecting to most indexers/trackers via https, so you’ll need that to work properly on your system. That means your time zone and time both need to be set ''correctly''. It also means your system certificates need to be up to date.

==== Hitting rate limits ====

If you run your {{{ARRNAME}}} through a VPN or proxy, you may be competing with 10s or 100s or 1000s of other people all trying to use services like {{{SEARCHSOURCE}}}, theXEM ,and/or your indexers and trackers. Rate limiting and DDOS protection are often done by IP address and your VPN/proxy exit point is ''one'' IP address. Unless you’re in a repressive country like China, Australia or South Africa you don’t need to VPN/proxy {{{ARRNAME}}}.

Rarbg has a tendency to have some sort of rate limiting within their API and displays as responding with no results.

==== Using the Jackett /all endpoint ====

The Jackett <code>/all</code> endpoint is convenient, but that is its only benefit. Everything else is potential problems, so adding each tracker individually is recommended.

[https://github.com/Jackett/Jackett#aggregate-indexers Even Jackett says it should be avoided and should not be used.]

Using the all endpoint has no advantages (besides reduced management overhead), only disadvantages:
* you lose control over indexer specific settings (categories, search modes, etc.)
* mixing search modes (IMDB, query, etc.) might cause low-quality results
* indexer specific categories (>= 100000) can't be used.
* slow indexers will slow down the overall result
* total results are limited to 1000

Adding each indexer separately It allows for fine tuning of categories on a per indexer basis, which can be a problem with the <code>/all</code> end point if using the wrong category causes errors on some trackers. In {{{ARRNAME}}}, each indexer is limited to 1000 results if pagination is supported or 100 if not, which means as you add more and more trackers to Jackett, you’re more and more likely to clip results. Finally, if ''one'' of the trackers in <code>/all</code> returns an error, {{{ARRNAME}}} will disable it and now you don’t get any results.

==== Problem Not Listed ====
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

=== Errors ===

These are some of the common errors you may see when adding an indexer

==== The underlying connection was closed: An unexpected error occurred on a send. ====

This is caused by the indexer using a SSL protocol not supported by .net 4.5, to resolve this you will need to install .net 4.5, which is available on Vista/Server 2008 and above (if you’re on XP/Server 2003 its time to upgrade).

==== The request timed out ====

{{{ARRNAME}}} seems to have issues with certain TLS versions or configurations. If you get the following error messages in your log:
<pre>System.Net.WebException: The request timed out: ’https://example.org/api?t=caps&apikey=(removed) —> System.Net.WebException: The request timed out</pre>

And you can see the following in the trace log file:
<pre><DATE&TIME>|Trace|FallbackHttpDispatcher|Curl not available, using default WebClient. </pre>

You might fix it by installing libcurl3. On Ubuntu/Debian use;
<pre>apt install libcurl3</pre>

This can also be caused by:
* improperly configured or use of a VPN
* improperly configured or use of a proxy
* local DNS issues
* local IPv6 issues

Template:Troubleshooting

2021-05-08T23:29:30Z

Bakerboy448: /* Download folder and library folder not different folders */

<noinclude>
<templatedata>
{
"params": {
"ARRNAME": {
"description": "Name of the Application",
"example": "Radarr",
"type": "string",
"required": true
},
"ARR_DISCORD": {
"description": "Link to the ARR #support Discord",
"type": "url",
"required": true
},
"ARR_WEBSITE": {
"description": "Link to the ARR Website",
"type": "url",
"required": true
},
"ARR_LATEST_RELEASE": {
"description": "Link to the ARR Download",
"type": "url",
"required": true
},
"VERSION": {
"description": "The current version of each of the ARRs",
"type": "string",
"required": true
},
"MEDIA": {
"description": "What type of media does the ARR use",
"example": "Radarr: movies, Sonarr: series, Lidarr: artist, Readarr: author",
"type": "string",
"required": true
},
"SEARCHSOURCE": {
"description": "What metadata provider does the ARR use",
"example": "Radarr: TMDb, Sonarr: TheTVDb, Lidarr: MusicBrainz, Readarr: GoodReads",
"type": "string",
"required": true
},
"QUERYSTRING": {},
"ARRNAME2": {
"description": "This string is used for lower cased ARR names for transclusion",
"example": "radarr, sonarr, lidarr, readarr",
"type": "string",
"required": true
}
},
"description": "This template is utilized for general troubleshooting steps that span across all the ARRs. Some Sections may be transcluded from a Troubleshooting Misc page when items are ARR specific."
}
</templatedata>
</noinclude>
== Troubleshooting ==
----
Please note that this information is only for {{{ARRNAME}}} {{{VERSION}}}.
=== Asking for Help ===
----
Do you need help? That's okay, everyone needs help sometimes. You can get real time help via chat on [{{{ARR_DISCORD}}} Discord] or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit].

But before you go there and post, be sure your request for help is the best it can be. Clearly describe the problem and briefly describe your setup, including things like your OS/distribution, version of Mono or .Net/.Netcore, version of {{{ARRNAME}}}, download client and its version. '''If you are using [https://www.docker.com/ Docker] please run through [[Docker Guide|the Docker Guide]] first as that will solve common and frequent path/permissions issues. Otherwise please have a [[Docker Guide#Docker-compose|docker compose]] handy''' Tell us about what you've tried already, what you've looked at. Use the Logging and Log Files to turn your logging up to trace, recreate the issue, pastebin the relevant context and include a link to it in your post. Maybe even include some screen shots to highlight the issue.

The more we know, the easier it is to help you.

== Logging and Log Files ==

If you're linked here for support remember to get them the information from the actual trace log file, put the logs in a pastebin and show us context around what we need to see. If you're asked for debug logs your logs will contain <code>debug</code> and if you're asked for trace logs your logs will contain <code>trace</code>. If the logs you are providing do not contain either then they are not the logs requested.

What you need to do is:
# Turn Logging up to Trace
# Clear Logs
# Reproduce the Issue
# Open the trace log file ({{{ARRNAME}}}.trace.txt) and fine the relevant context
# [https://hastebin.com/ Hastebin], [https://pastebin.ubuntu.com/ Pastebin], [https://0bin.net/ 0bin], or any other pastebin type site a big chunk before the issue, the issue, and a big chunk after the issue.

* Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use N++. You can use the Notepad++ "Find in Files" function to search old log files as needed.
* '''Unix Only:''' Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use grep. For example if you want to find information about the movie or show "Shooter" you can run the following command <code>grep -inr -C 100 -e 'Shooter' /path/to/logs/*.trace*.txt</code> If your [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]] is in your home folder then you'd run: <code>grep -inr -C 100 -e 'Shooter' /home/$User/.config/logs/*.trace*.txt</code>
<div style="margin-left: 2em;"><pre>
* The flags have the following functions
* -i: ignore case
* -n: show line number
* -r: recursively check all files in the path
* -C: provide # of lines before and after the line it is found on
* -e: the pattern to search for
</pre></div>

==== Standard Logs Location ====
The log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the logs/ folder. You can also access the log files from the {{{ARRNAME}}} UI at System -> Logs -> Files.

Note: The Logs ("Events") Table in the UI is not the same as the log files and isn't as useful. If you're asked for logs, please copy/paste from the log files and not the table.

==== Update Logs Location ====
The update log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the UpdateLogs/ folder.

==== Sharing Logs ====
The logs can be long and hard to read as part of a forum or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit] post and they're spammy in [{{{ARR_DISCORD}}} Discord], so please use [https://pastebin.ubuntu.com/ Pastebin], [https://hastebin.com/ Hastebin], or any other similar pastebin site . The whole file typically isn't needed, just a good amount of context from before and after the issue/error. Don't forget to wait for spammy tasks like the RSS sync or library refresh to finish.

==== Trace/Debug Logs ====

You can change the log level at Settings -> General -> Logging. {{{ARRNAME}}} does not need to restarted for the change to take effect. This change only affects the log files, not the logging database. The latest debug/trace log files are named <code>{{{ARRNAME}}}.debug.txt</code> and <code>{{{ARRNAME}}}r.trace.txt</code> respectively.

If you're unable to access the {{{ARRNAME}}} UI to set the logging level you can do so by editing config.xml in the AppData directory by setting the LogLevel value to Debug or Trace instead of Info.
<div style="margin-left: 2em;"><pre>
<Config>
...
<LogLevel>debug</LogLevel>
...
</Config>
</pre></div>

==== Clearing Logs ====

You can clear log files and the logs database directly from the UI, under System -> Logs -> Files and System -> Logs -> Delete (Trash Can Icon)

==== Multiple Log Files ====

{{{ARRNAME}}} uses rolling log files limited to 1MB each. The current log file is always ,<code>{{{ARRNAME}}}.txt</code>, for the the other files <code>{{{ARRNAME}}}.0.txt</code> is the next newest (the higher the number the older it is). This log file contains fatal, error, warn, and info entries.

When Debug log level is enabled, additional <code>{{{ARRNAME}}}.debug.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, and debug entries. It usually covers a 40h period.

When Trace log level is enabled, additional <code>{{{ARRNAME}}}.trace.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, debug, and trace entries. Due to trace verbosity it only covers a couple of hours at most.

== Recovering from a Failed Update ==
----
==== Purpose ====
We do everything we can to prevent issues when upgrading, but they occur, this will walk you through the steps of recovering your installation.

==== Determine the issue ====
The best place to look when {{{ARRNAME}}} won't start after an update is your log files, before trying to start {{{ARRNAME}}} again, use [[{{{ARRNAME}}} Settings#Logging|Logging]] and [[{{{ARRNAME}}} System#Log_Files|Log Files]] to find them and increase the log level.

'''Migration Issue'''

Migration errors won't be identical, but here is an example:

<code>
14-2-4 18:56:49.5|Info|MigrationLogger|*** 36: update_with_quality_converters migrating ***

14-2-4 18:56:49.6|Error|MigrationLogger|SQL logic error or missing database duplicate column name: Items

While Processing: "ALTER TABLE "QualityProfiles" ADD COLUMN "Items" TEXT"

</code>

==== Resolving the issue ====
In the event of a migration issue there is not much you can do immediately, if the issue is specific to you (or there are not yet any posts), please create a post on [https://reddit.com/r/{{{ARRNAME}}} our subreddit] or swing by our discord, if there are others with the same issue, then rest assured we are working on it.

==== Manually upgrading ====
Grab the latest release from [{{{ARR_WEBSITE}}} our website]

Install the update (.exe) or extract (.zip) the contents over your existing installation and re-run {{{ARRNAME}}} as you normally would.

== Downloads and Importing ==

Downloading and importing is where ''most'' people experience issues. From a high level perspective, {{{ARRNAME}}} 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.

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

When you reach out for help, be sure to read [[#Asking for Help|asking for help]] so that you can provide us with the details we’ll need.

=== Testing the Download Client ===

Ensure your download client(s) are running. Start by testing the download client, if it doesn’t work you’ll be able to see details in the trace level logs. You should find a URL you can put into your browser and see if it works. It could be a connection problem, which could indicate a wrong ip, hostname, port or even a firewall blocking access. It might be obvious, like an authentication problem where you’ve gotten the username, password or apikey wrong.

=== Testing a Download ===

Now we’ll try a download, pick a {{{MEDIA}}} and do a manual search. Pick one of those files and attempt to download it. Does it get sent to the download client? Does it end up with the correct category? Does it show up in Activity? Does it end up in the trace level logs during the '''Check For Finished Download''' task which runs roughly every minute? Does it get correctly parsed during that task? Does the queued up download have a reasonable name? Since {{{ARRNAME}}} searches by '''{{{SEARCHSOURCE}}}''', on most indexers/trackers, it can queue one up with a name that it can’t recognize.

=== Testing an Import ===

Import issues should almost always manifest as an item in Activity with an orange icon you can hover to see the error. If they’re not showing up in Activity, this is the issue you need to focus on first so go back and figure that out. Most import errors are ''permissions'' issues, remember that {{{ARRNAME}}} needs to be able to read and write in the download folder. Sometimes, permissions in the library folder can be at fault too, so be sure to check both.

Incorrect path issues are possible too, though less common in normal setups. The key to understanding path issues is knowing that {{{ARRNAME}}} gets the path to the download ''from'' the download client, via its API. This becomes a problem in more unique use cases, like the download client running on a different system (maybe even OS!). It can also occur in a Docker setup, when volumes are not done well. A remote path map is a good solution where you don’t have control, like a seedbox setup. On a Docker setup, fixing the paths is a better option.

=== Common Problems ===

==== Download Client's WebUI is not enabled ====
{{{ARRNAME}}} talks to you download client via it's API and accesses it via the client's webui. You must ensure the client's webui is enabled and the port it is using does not conflict with any other client ports in use or ports in use on your system.

==== SSL in use and incorrectly configured ====
Ensure SSL encryption is not turned on if you're using both your {{{ARRNAME}}} instance and your download client on a local network. See [[{{{ARRNAME}}}_FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

==== Can’t see share on Windows ====

The default user for a Windows service is '''SYSTEM''' which typically doesn’t have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [[{{{ARRNAME}}} FAQ#Why can’t {{{ARRNAME}}} see my files on a remote server?|why can’t {{{ARRNAME}}} see my files on a remote server]] for details.

==== Mapped network drives are not reliable ====

While mapped network drives like <code>X:\</code> are convenient, they aren’t as reliable as UNC paths like <code>\\server\share</code> and they’re also not available before login. Setup {{{ARRNAME}}} and your download client(s) so that they use UNC paths as needed. If your library is on a share, you’d make sure your root folders are using UNC paths. If your download client sends to a share, that is where you’ll need to configure UNC paths since {{{ARRNAME}}} gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don’t use them for automation.

==== Docker and user, group, ownership, permissions and paths ====

Docker adds another layer of complexity that is easy to get wrong, but still end up with a setup that functions, but has various problems. Instead of going over them here, read this wiki article [[Docker Guide|for these automation software and Docker]] which is all about user, group, ownership, permissions and paths. It isn’t specific to any Docker system, instead it goes over things at a high level so that you can implement them in your own environment.

==== Permissions on the Library Folder ====
Don’t forget to check permissions and ownership of the ''destination''. It is easy to get fixated on the download’s ownership and permissions and that is ''usually'' the cause of permissions related issues, but it ''could'' be the destination as well. Check that the destination folder(s) exist. Check that a destination ''file'' doesn’t already exist or can’t be deleted or moved to recycle bin. Check that ownership and permissions allow the downloaded file to be copied, hard linked or moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the root folder.

==== Permissions on the Downloads Folder ====

Don’t forget to check permissions and ownership of the ''source''. It is easy to get fixated on the destination's ownership and permissions and that is a ''possible'' cause of permissions related issues, but it ''typically'' is the source. Check that the source folder(s) exist. Check that ownership and permissions allow the downloaded file to be copied/hardlinked or copy+delete/moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the downloads folder.

==== Download folder and library folder not different folders ====

The download client should download into a temporary folder and {{{ARRNAME}}} should import from that into your Library folder.

You should never download directly into your root folder nor use your root folder as the download client's completed folder.

If you download right into your library folder, you’ll end up with multiple copies of your media and when there are import issues, which there will be, you may not notice because your media server will see the download client copy.

The download folder will also be a hot mess of poorly named folders and files while your library folder will be nice and neat.

This frequently causes other random import issues as well.

==== Incorrect category ====

{{{ARRNAME}}} should be setup to use a category so that it only tries to process its own downloads. It is rare that a torrent submitted by {{{ARRNAME}}} gets added without the correct category, but it can happen. If you’re adding torrents manually and want {{{ARRNAME}}} to process them, they’ll need to have the correct category. It can be set at any time, since {{{ARRNAME}}} tries to process downloads every minute.

==== Packed torrents ====

If your torrent is packed in <code>.rar</code> files, you’ll need to setup extraction. We recommend [https://github.com/davidnewhall/unpackerr unpackerr]. One issue to look out for with packed torrents is that the video file will be copied or hard linked like normal, but it isn’t needed since the <code>.rar</code> files are seeding. That means if you’re using a ''copy'' setup, the torrent will be consuming double the space. And if you’re using a hard link setup, your torrent folder will be a little messier because of the unneeded file. This can be mitigated with a [https://gist.github.com/fryfrog/94716e7e27ba38dff57c7631d9f58bed cleanup script].

==== Repeated downloads ====

There are a few causes of repeated downloads, but a recent one is related to the Indexer restriction in Release Profiles. Because the indexer ''isn’t'' stored with the data, any preferred word scores are ''zero'' for media in your library, ''but'' during “RSS” and search, they’ll be applied. This gets you into a loop where you download the items again and again because it looks like an upgrade, then isn’t, then shows up again and looks like an upgrade, then isn’t. Don’t restrict your release profile to an indexer.

==== Usenet download misses import ====

{{{ARRNAME}}} only looks at the 60 most recent downloads in SABnzbd and NZBGet, so if you ''keep'' your history this means that during large queues with import issues, downloads can be silently missed and not imported. The best way to avoid that is to keep your history clear, so that any items that still appear need investigating. You can achieve this by enabling Remove under Completed and Failed Download Handler. In nzbget, this will move items to the ''hidden'' history which is great. Unfortunately, sabnzbd does not have a similar feature. The best you can achieve there is to use the nzb backup folder.

==== Download client clearing items ====

The download client should ''not'' be responsible for removing downloads. Usenet clients should be configured so they ''don’t'' remove downloads from history. Torrent clients should be setup so they ''don’t'' remove torrents when they’re finished seeding (pause or stop instead). This is because {{{ARRNAME}}} communicates with the download client to know what to import, so if they’re ''removed'' there is nothing to be imported… even if there is a folder full of files.

=== Problem Not Listed ===
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

== Searches Indexers and Trackers ==

=== Turn logging up to trace ===

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

=== Testing an Indexer or Tracker ===

When you test an indexer or tracker, in debug or trace logs you can find the URL used. An example of a successful test is below, you can see it query the indexer via a specific URL with specific parameters and then the response. You test this url in your browser like <code>{{{QUERYSTRING}}}</code> replacing the <code>apikey=(removed)</code> with the correct apikey like <code>apikey=123</code>. You can experiment with the parameters if you’re getting an error from the indexer or see if you have connectivity issues if it doesn’t even work. After you’ve tested in your own browser, you should test from the system {{{ARRNAME}}} is running on ''if'' you haven’t already.

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block}}

=== Testing a Search ===
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_testing_a_search}}

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers1.png|thumb|none|750px]]

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers2.png|thumb|none|750px]]

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block2}}

Here you can see the ''full'' trace log below
{{#lst:Troubleshooting Misc|{{{ARRNAME2}}}_trace_logs_example}}

=== Common Problems ===

==== Media is Unmonitored ====
The {{{MEDIA}}} is/are not monitored.

==== Wrong categories ====

Incorrect categories is probably the most common cause of results showing in manual searches of an indexer/tracker, but ''not'' in {{{ARRNAME}}}. The indexer/tracker ''should'' show the category in the search results, which should help you figure out what is missing. If you’re using Jackett, each tracker has a list of specifically supported categories. Make sure you’re using the correct ones for Categories. I find it helpful to have the list visible in one browser window while I edit the entry in {{{ARRNAME}}}.
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_type}}
==== Wrong results ====

Sometimes indexers will return completely unrelated results, {{{ARRNAME}}} will feed in parameters to limit the search to a {{{SEARCHSOURCE}}}, but the results returned are completely unrelated. Or sometimes, mostly related with a few incorrect results. The first is usually an indexer problem and you’ll be able to tell from the trace logs which is causing it. You can disable that indexer and report the problem. The other is usually categorized releases which should be reportable on the indexer/tracker.

==== Certificate validation ====

You’ll be connecting to most indexers/trackers via https, so you’ll need that to work properly on your system. That means your time zone and time both need to be set ''correctly''. It also means your system certificates need to be up to date.

==== Hitting rate limits ====

If you run your {{{ARRNAME}}} through a VPN or proxy, you may be competing with 10s or 100s or 1000s of other people all trying to use services like {{{SEARCHSOURCE}}}, theXEM ,and/or your indexers and trackers. Rate limiting and DDOS protection are often done by IP address and your VPN/proxy exit point is ''one'' IP address. Unless you’re in a repressive country like China, Australia or South Africa you don’t need to VPN/proxy {{{ARRNAME}}}.

Rarbg has a tendency to have some sort of rate limiting within their API and displays as responding with no results.

==== Using the Jackett /all endpoint ====

The Jackett <code>/all</code> endpoint is convenient, but that is its only benefit. Everything else is potential problems, so adding each tracker individually is recommended.

[https://github.com/Jackett/Jackett#aggregate-indexers Even Jackett says it should be avoided and should not be used.]

Using the all endpoint has no advantages (besides reduced management overhead), only disadvantages:
* you lose control over indexer specific settings (categories, search modes, etc.)
* mixing search modes (IMDB, query, etc.) might cause low-quality results
* indexer specific categories (>= 100000) can't be used.
* slow indexers will slow down the overall result
* total results are limited to 1000

Adding each indexer separately It allows for fine tuning of categories on a per indexer basis, which can be a problem with the <code>/all</code> end point if using the wrong category causes errors on some trackers. In {{{ARRNAME}}}, each indexer is limited to 1000 results if pagination is supported or 100 if not, which means as you add more and more trackers to Jackett, you’re more and more likely to clip results. Finally, if ''one'' of the trackers in <code>/all</code> returns an error, {{{ARRNAME}}} will disable it and now you don’t get any results.

==== Problem Not Listed ====
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

=== Errors ===

These are some of the common errors you may see when adding an indexer

==== The underlying connection was closed: An unexpected error occurred on a send. ====

This is caused by the indexer using a SSL protocol not supported by .net 4.5, to resolve this you will need to install .net 4.5, which is available on Vista/Server 2008 and above (if you’re on XP/Server 2003 its time to upgrade).

==== The request timed out ====

{{{ARRNAME}}} seems to have issues with certain TLS versions or configurations. If you get the following error messages in your log:
<pre>System.Net.WebException: The request timed out: ’https://example.org/api?t=caps&apikey=(removed) —> System.Net.WebException: The request timed out</pre>

And you can see the following in the trace log file:
<pre><DATE&TIME>|Trace|FallbackHttpDispatcher|Curl not available, using default WebClient. </pre>

You might fix it by installing libcurl3. On Ubuntu/Debian use;
<pre>apt install libcurl3</pre>

This can also be caused by:
* improperly configured or use of a VPN
* improperly configured or use of a proxy
* local DNS issues
* local IPv6 issues

Template:Troubleshooting

2021-05-08T23:29:05Z

Bakerboy448: /* Download folder and library folder not different folders */

<noinclude>
<templatedata>
{
"params": {
"ARRNAME": {
"description": "Name of the Application",
"example": "Radarr",
"type": "string",
"required": true
},
"ARR_DISCORD": {
"description": "Link to the ARR #support Discord",
"type": "url",
"required": true
},
"ARR_WEBSITE": {
"description": "Link to the ARR Website",
"type": "url",
"required": true
},
"ARR_LATEST_RELEASE": {
"description": "Link to the ARR Download",
"type": "url",
"required": true
},
"VERSION": {
"description": "The current version of each of the ARRs",
"type": "string",
"required": true
},
"MEDIA": {
"description": "What type of media does the ARR use",
"example": "Radarr: movies, Sonarr: series, Lidarr: artist, Readarr: author",
"type": "string",
"required": true
},
"SEARCHSOURCE": {
"description": "What metadata provider does the ARR use",
"example": "Radarr: TMDb, Sonarr: TheTVDb, Lidarr: MusicBrainz, Readarr: GoodReads",
"type": "string",
"required": true
},
"QUERYSTRING": {},
"ARRNAME2": {
"description": "This string is used for lower cased ARR names for transclusion",
"example": "radarr, sonarr, lidarr, readarr",
"type": "string",
"required": true
}
},
"description": "This template is utilized for general troubleshooting steps that span across all the ARRs. Some Sections may be transcluded from a Troubleshooting Misc page when items are ARR specific."
}
</templatedata>
</noinclude>
== Troubleshooting ==
----
Please note that this information is only for {{{ARRNAME}}} {{{VERSION}}}.
=== Asking for Help ===
----
Do you need help? That's okay, everyone needs help sometimes. You can get real time help via chat on [{{{ARR_DISCORD}}} Discord] or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit].

But before you go there and post, be sure your request for help is the best it can be. Clearly describe the problem and briefly describe your setup, including things like your OS/distribution, version of Mono or .Net/.Netcore, version of {{{ARRNAME}}}, download client and its version. '''If you are using [https://www.docker.com/ Docker] please run through [[Docker Guide|the Docker Guide]] first as that will solve common and frequent path/permissions issues. Otherwise please have a [[Docker Guide#Docker-compose|docker compose]] handy''' Tell us about what you've tried already, what you've looked at. Use the Logging and Log Files to turn your logging up to trace, recreate the issue, pastebin the relevant context and include a link to it in your post. Maybe even include some screen shots to highlight the issue.

The more we know, the easier it is to help you.

== Logging and Log Files ==

If you're linked here for support remember to get them the information from the actual trace log file, put the logs in a pastebin and show us context around what we need to see. If you're asked for debug logs your logs will contain <code>debug</code> and if you're asked for trace logs your logs will contain <code>trace</code>. If the logs you are providing do not contain either then they are not the logs requested.

What you need to do is:
# Turn Logging up to Trace
# Clear Logs
# Reproduce the Issue
# Open the trace log file ({{{ARRNAME}}}.trace.txt) and fine the relevant context
# [https://hastebin.com/ Hastebin], [https://pastebin.ubuntu.com/ Pastebin], [https://0bin.net/ 0bin], or any other pastebin type site a big chunk before the issue, the issue, and a big chunk after the issue.

* Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use N++. You can use the Notepad++ "Find in Files" function to search old log files as needed.
* '''Unix Only:''' Alternatively If you're looking for a specific entry in an old log file but aren't sure which one you can use grep. For example if you want to find information about the movie or show "Shooter" you can run the following command <code>grep -inr -C 100 -e 'Shooter' /path/to/logs/*.trace*.txt</code> If your [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]] is in your home folder then you'd run: <code>grep -inr -C 100 -e 'Shooter' /home/$User/.config/logs/*.trace*.txt</code>
<div style="margin-left: 2em;"><pre>
* The flags have the following functions
* -i: ignore case
* -n: show line number
* -r: recursively check all files in the path
* -C: provide # of lines before and after the line it is found on
* -e: the pattern to search for
</pre></div>

==== Standard Logs Location ====
The log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the logs/ folder. You can also access the log files from the {{{ARRNAME}}} UI at System -> Logs -> Files.

Note: The Logs ("Events") Table in the UI is not the same as the log files and isn't as useful. If you're asked for logs, please copy/paste from the log files and not the table.

==== Update Logs Location ====
The update log files are located in {{{ARRNAME}}}'s [[{{{ARRNAME}}} Appdata Directory|Appdata Directory]], inside the UpdateLogs/ folder.

==== Sharing Logs ====
The logs can be long and hard to read as part of a forum or [https://www.reddit.com/r/{{{ARRNAME}}} Reddit] post and they're spammy in [{{{ARR_DISCORD}}} Discord], so please use [https://pastebin.ubuntu.com/ Pastebin], [https://hastebin.com/ Hastebin], or any other similar pastebin site . The whole file typically isn't needed, just a good amount of context from before and after the issue/error. Don't forget to wait for spammy tasks like the RSS sync or library refresh to finish.

==== Trace/Debug Logs ====

You can change the log level at Settings -> General -> Logging. {{{ARRNAME}}} does not need to restarted for the change to take effect. This change only affects the log files, not the logging database. The latest debug/trace log files are named <code>{{{ARRNAME}}}.debug.txt</code> and <code>{{{ARRNAME}}}r.trace.txt</code> respectively.

If you're unable to access the {{{ARRNAME}}} UI to set the logging level you can do so by editing config.xml in the AppData directory by setting the LogLevel value to Debug or Trace instead of Info.
<div style="margin-left: 2em;"><pre>
<Config>
...
<LogLevel>debug</LogLevel>
...
</Config>
</pre></div>

==== Clearing Logs ====

You can clear log files and the logs database directly from the UI, under System -> Logs -> Files and System -> Logs -> Delete (Trash Can Icon)

==== Multiple Log Files ====

{{{ARRNAME}}} uses rolling log files limited to 1MB each. The current log file is always ,<code>{{{ARRNAME}}}.txt</code>, for the the other files <code>{{{ARRNAME}}}.0.txt</code> is the next newest (the higher the number the older it is). This log file contains fatal, error, warn, and info entries.

When Debug log level is enabled, additional <code>{{{ARRNAME}}}.debug.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, and debug entries. It usually covers a 40h period.

When Trace log level is enabled, additional <code>{{{ARRNAME}}}.trace.txt</code> rolling log files will be present. This log files contains fatal, error, warn, info, debug, and trace entries. Due to trace verbosity it only covers a couple of hours at most.

== Recovering from a Failed Update ==
----
==== Purpose ====
We do everything we can to prevent issues when upgrading, but they occur, this will walk you through the steps of recovering your installation.

==== Determine the issue ====
The best place to look when {{{ARRNAME}}} won't start after an update is your log files, before trying to start {{{ARRNAME}}} again, use [[{{{ARRNAME}}} Settings#Logging|Logging]] and [[{{{ARRNAME}}} System#Log_Files|Log Files]] to find them and increase the log level.

'''Migration Issue'''

Migration errors won't be identical, but here is an example:

<code>
14-2-4 18:56:49.5|Info|MigrationLogger|*** 36: update_with_quality_converters migrating ***

14-2-4 18:56:49.6|Error|MigrationLogger|SQL logic error or missing database duplicate column name: Items

While Processing: "ALTER TABLE "QualityProfiles" ADD COLUMN "Items" TEXT"

</code>

==== Resolving the issue ====
In the event of a migration issue there is not much you can do immediately, if the issue is specific to you (or there are not yet any posts), please create a post on [https://reddit.com/r/{{{ARRNAME}}} our subreddit] or swing by our discord, if there are others with the same issue, then rest assured we are working on it.

==== Manually upgrading ====
Grab the latest release from [{{{ARR_WEBSITE}}} our website]

Install the update (.exe) or extract (.zip) the contents over your existing installation and re-run {{{ARRNAME}}} as you normally would.

== Downloads and Importing ==

Downloading and importing is where ''most'' people experience issues. From a high level perspective, {{{ARRNAME}}} 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.

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

When you reach out for help, be sure to read [[#Asking for Help|asking for help]] so that you can provide us with the details we’ll need.

=== Testing the Download Client ===

Ensure your download client(s) are running. Start by testing the download client, if it doesn’t work you’ll be able to see details in the trace level logs. You should find a URL you can put into your browser and see if it works. It could be a connection problem, which could indicate a wrong ip, hostname, port or even a firewall blocking access. It might be obvious, like an authentication problem where you’ve gotten the username, password or apikey wrong.

=== Testing a Download ===

Now we’ll try a download, pick a {{{MEDIA}}} and do a manual search. Pick one of those files and attempt to download it. Does it get sent to the download client? Does it end up with the correct category? Does it show up in Activity? Does it end up in the trace level logs during the '''Check For Finished Download''' task which runs roughly every minute? Does it get correctly parsed during that task? Does the queued up download have a reasonable name? Since {{{ARRNAME}}} searches by '''{{{SEARCHSOURCE}}}''', on most indexers/trackers, it can queue one up with a name that it can’t recognize.

=== Testing an Import ===

Import issues should almost always manifest as an item in Activity with an orange icon you can hover to see the error. If they’re not showing up in Activity, this is the issue you need to focus on first so go back and figure that out. Most import errors are ''permissions'' issues, remember that {{{ARRNAME}}} needs to be able to read and write in the download folder. Sometimes, permissions in the library folder can be at fault too, so be sure to check both.

Incorrect path issues are possible too, though less common in normal setups. The key to understanding path issues is knowing that {{{ARRNAME}}} gets the path to the download ''from'' the download client, via its API. This becomes a problem in more unique use cases, like the download client running on a different system (maybe even OS!). It can also occur in a Docker setup, when volumes are not done well. A remote path map is a good solution where you don’t have control, like a seedbox setup. On a Docker setup, fixing the paths is a better option.

=== Common Problems ===

==== Download Client's WebUI is not enabled ====
{{{ARRNAME}}} talks to you download client via it's API and accesses it via the client's webui. You must ensure the client's webui is enabled and the port it is using does not conflict with any other client ports in use or ports in use on your system.

==== SSL in use and incorrectly configured ====
Ensure SSL encryption is not turned on if you're using both your {{{ARRNAME}}} instance and your download client on a local network. See [[{{{ARRNAME}}}_FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

==== Can’t see share on Windows ====

The default user for a Windows service is '''SYSTEM''' which typically doesn’t have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [[{{{ARRNAME}}} FAQ#Why can’t {{{ARRNAME}}} see my files on a remote server?|why can’t {{{ARRNAME}}} see my files on a remote server]] for details.

==== Mapped network drives are not reliable ====

While mapped network drives like <code>X:\</code> are convenient, they aren’t as reliable as UNC paths like <code>\\server\share</code> and they’re also not available before login. Setup {{{ARRNAME}}} and your download client(s) so that they use UNC paths as needed. If your library is on a share, you’d make sure your root folders are using UNC paths. If your download client sends to a share, that is where you’ll need to configure UNC paths since {{{ARRNAME}}} gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don’t use them for automation.

==== Docker and user, group, ownership, permissions and paths ====

Docker adds another layer of complexity that is easy to get wrong, but still end up with a setup that functions, but has various problems. Instead of going over them here, read this wiki article [[Docker Guide|for these automation software and Docker]] which is all about user, group, ownership, permissions and paths. It isn’t specific to any Docker system, instead it goes over things at a high level so that you can implement them in your own environment.

==== Permissions on the Library Folder ====
Don’t forget to check permissions and ownership of the ''destination''. It is easy to get fixated on the download’s ownership and permissions and that is ''usually'' the cause of permissions related issues, but it ''could'' be the destination as well. Check that the destination folder(s) exist. Check that a destination ''file'' doesn’t already exist or can’t be deleted or moved to recycle bin. Check that ownership and permissions allow the downloaded file to be copied, hard linked or moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the root folder.

==== Permissions on the Downloads Folder ====

Don’t forget to check permissions and ownership of the ''source''. It is easy to get fixated on the destination's ownership and permissions and that is a ''possible'' cause of permissions related issues, but it ''typically'' is the source. Check that the source folder(s) exist. Check that ownership and permissions allow the downloaded file to be copied/hardlinked or copy+delete/moved.
The user or group that {{{ARRNAME}}} runs as needs to be able to read and write the downloads folder.

==== Download folder and library folder not different folders ====

The download client should download into a temporary folder and {{{ARRNAME}}} should import from that into your Library folder.

You should never download directly into your root folder nor use your root folder as the download client's completed folder.

If you download right into your library folder, you’ll end up with multiple copies of your media and when there are import issues, which there will be, you may not notice because your media server will see the download client copy.

The download folder will also be a hot mess of poorly named folders and files while your library folder will be nice and neat.

This frequently causes other random import issues as well.

==== Incorrect category ====

{{{ARRNAME}}} should be setup to use a category so that it only tries to process its own downloads. It is rare that a torrent submitted by {{{ARRNAME}}} gets added without the correct category, but it can happen. If you’re adding torrents manually and want {{{ARRNAME}}} to process them, they’ll need to have the correct category. It can be set at any time, since {{{ARRNAME}}} tries to process downloads every minute.

==== Packed torrents ====

If your torrent is packed in <code>.rar</code> files, you’ll need to setup extraction. We recommend [https://github.com/davidnewhall/unpackerr unpackerr]. One issue to look out for with packed torrents is that the video file will be copied or hard linked like normal, but it isn’t needed since the <code>.rar</code> files are seeding. That means if you’re using a ''copy'' setup, the torrent will be consuming double the space. And if you’re using a hard link setup, your torrent folder will be a little messier because of the unneeded file. This can be mitigated with a [https://gist.github.com/fryfrog/94716e7e27ba38dff57c7631d9f58bed cleanup script].

==== Repeated downloads ====

There are a few causes of repeated downloads, but a recent one is related to the Indexer restriction in Release Profiles. Because the indexer ''isn’t'' stored with the data, any preferred word scores are ''zero'' for media in your library, ''but'' during “RSS” and search, they’ll be applied. This gets you into a loop where you download the items again and again because it looks like an upgrade, then isn’t, then shows up again and looks like an upgrade, then isn’t. Don’t restrict your release profile to an indexer.

==== Usenet download misses import ====

{{{ARRNAME}}} only looks at the 60 most recent downloads in SABnzbd and NZBGet, so if you ''keep'' your history this means that during large queues with import issues, downloads can be silently missed and not imported. The best way to avoid that is to keep your history clear, so that any items that still appear need investigating. You can achieve this by enabling Remove under Completed and Failed Download Handler. In nzbget, this will move items to the ''hidden'' history which is great. Unfortunately, sabnzbd does not have a similar feature. The best you can achieve there is to use the nzb backup folder.

==== Download client clearing items ====

The download client should ''not'' be responsible for removing downloads. Usenet clients should be configured so they ''don’t'' remove downloads from history. Torrent clients should be setup so they ''don’t'' remove torrents when they’re finished seeding (pause or stop instead). This is because {{{ARRNAME}}} communicates with the download client to know what to import, so if they’re ''removed'' there is nothing to be imported… even if there is a folder full of files.

=== Problem Not Listed ===
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

== Searches Indexers and Trackers ==

=== Turn logging up to trace ===

'''The first step is to turn logging up to Trace, see [[#Logging and Log Files|Logging and Log Files]] for details on adjusting logging and searching logs. You’ll then reproduce the issue and use the trace level logs from that time frame to examine the issue.''' If someone is helping you, put context from before/after in a [https://paste.ubuntu.com pastebin] to show them. It doesn’t need to be the whole file and it shouldn’t ''just'' be the error. You should also reproduce the issue while tasks that spam the log file aren’t running.

=== Testing an Indexer or Tracker ===

When you test an indexer or tracker, in debug or trace logs you can find the URL used. An example of a successful test is below, you can see it query the indexer via a specific URL with specific parameters and then the response. You test this url in your browser like <code>{{{QUERYSTRING}}}</code> replacing the <code>apikey=(removed)</code> with the correct apikey like <code>apikey=123</code>. You can experiment with the parameters if you’re getting an error from the indexer or see if you have connectivity issues if it doesn’t even work. After you’ve tested in your own browser, you should test from the system {{{ARRNAME}}} is running on ''if'' you haven’t already.

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block}}

=== Testing a Search ===
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_testing_a_search}}

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers1.png|thumb|none|750px]]

[[File:{{{ARRNAME}}}-searches-indexers-and-trackers2.png|thumb|none|750px]]

{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_code_block2}}

Here you can see the ''full'' trace log below
{{#lst:Troubleshooting Misc|{{{ARRNAME2}}}_trace_logs_example}}

=== Common Problems ===

==== Media is Unmonitored ====
The {{{MEDIA}}} is/are not monitored.

==== Wrong categories ====

Incorrect categories is probably the most common cause of results showing in manual searches of an indexer/tracker, but ''not'' in {{{ARRNAME}}}. The indexer/tracker ''should'' show the category in the search results, which should help you figure out what is missing. If you’re using Jackett, each tracker has a list of specifically supported categories. Make sure you’re using the correct ones for Categories. I find it helpful to have the list visible in one browser window while I edit the entry in {{{ARRNAME}}}.
{{#lst::Troubleshooting Misc|{{{ARRNAME2}}}_indexers_and_trackers_type}}
==== Wrong results ====

Sometimes indexers will return completely unrelated results, {{{ARRNAME}}} will feed in parameters to limit the search to a {{{SEARCHSOURCE}}}, but the results returned are completely unrelated. Or sometimes, mostly related with a few incorrect results. The first is usually an indexer problem and you’ll be able to tell from the trace logs which is causing it. You can disable that indexer and report the problem. The other is usually categorized releases which should be reportable on the indexer/tracker.

==== Certificate validation ====

You’ll be connecting to most indexers/trackers via https, so you’ll need that to work properly on your system. That means your time zone and time both need to be set ''correctly''. It also means your system certificates need to be up to date.

==== Hitting rate limits ====

If you run your {{{ARRNAME}}} through a VPN or proxy, you may be competing with 10s or 100s or 1000s of other people all trying to use services like {{{SEARCHSOURCE}}}, theXEM ,and/or your indexers and trackers. Rate limiting and DDOS protection are often done by IP address and your VPN/proxy exit point is ''one'' IP address. Unless you’re in a repressive country like China, Australia or South Africa you don’t need to VPN/proxy {{{ARRNAME}}}.

Rarbg has a tendency to have some sort of rate limiting within their API and displays as responding with no results.

==== Using the Jackett /all endpoint ====

The Jackett <code>/all</code> endpoint is convenient, but that is its only benefit. Everything else is potential problems, so adding each tracker individually is recommended.

[https://github.com/Jackett/Jackett#aggregate-indexers Even Jackett says it should be avoided and should not be used.]

Using the all endpoint has no advantages (besides reduced management overhead), only disadvantages:
* you lose control over indexer specific settings (categories, search modes, etc.)
* mixing search modes (IMDB, query, etc.) might cause low-quality results
* indexer specific categories (>= 100000) can't be used.
* slow indexers will slow down the overall result
* total results are limited to 1000

Adding each indexer separately It allows for fine tuning of categories on a per indexer basis, which can be a problem with the <code>/all</code> end point if using the wrong category causes errors on some trackers. In {{{ARRNAME}}}, each indexer is limited to 1000 results if pagination is supported or 100 if not, which means as you add more and more trackers to Jackett, you’re more and more likely to clip results. Finally, if ''one'' of the trackers in <code>/all</code> returns an error, {{{ARRNAME}}} will disable it and now you don’t get any results.

==== Problem Not Listed ====
Please discuss with the support team on discord. If this is something that may be a common problem, please suggest adding it to the wiki.

=== Errors ===

These are some of the common errors you may see when adding an indexer

==== The underlying connection was closed: An unexpected error occurred on a send. ====

This is caused by the indexer using a SSL protocol not supported by .net 4.5, to resolve this you will need to install .net 4.5, which is available on Vista/Server 2008 and above (if you’re on XP/Server 2003 its time to upgrade).

==== The request timed out ====

{{{ARRNAME}}} seems to have issues with certain TLS versions or configurations. If you get the following error messages in your log:
<pre>System.Net.WebException: The request timed out: ’https://example.org/api?t=caps&apikey=(removed) —> System.Net.WebException: The request timed out</pre>

And you can see the following in the trace log file:
<pre><DATE&TIME>|Trace|FallbackHttpDispatcher|Curl not available, using default WebClient. </pre>

You might fix it by installing libcurl3. On Ubuntu/Debian use;
<pre>apt install libcurl3</pre>

This can also be caused by:
* improperly configured or use of a VPN
* improperly configured or use of a proxy
* local DNS issues
* local IPv6 issues

Docker Guide

2021-05-08T14:35:37Z

Bakerboy448: /* Interesting docker images */

=== The Best Docker Setup ===

'''TL; DR''': An [https://www.lexico.com/en/definition/eponymous eponymous] user per daemon and a shared group with a umask of <code>002</code>. Consistent path definitions between ''all'' containers that maintains the folder structure. Using one volume for Sonarr, Radarr and Lidarr so the download folder and library folder are on the same file system which makes hard links and instant moves possible. And most of all, ignore ''most'' of the Docker image’s path documentation!

'''Note: Many folks find [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ TRaSH's Hardlink Tutorial] helpful and easier to understand than this guide. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.'''

==== Introduction ====

This article will not show you specifics about the best Docker setup, but it describes an overview that you can use to make your own setup the best that it can be. The idea is that you run each docker container as its own user, with a shared group and consistent volumes so every container sees the same path layout. This is easy to say, but difficult to understand and explain.

==== Multiple users and a shared group ====

===== Permissions =====

Ideally, each software runs as its own user user and they’re all part of a shared group with folder permissions set to <code>775</code> (<code>drwxrwxr-x</code>) and files set to <code>664</code> (<code>-rw-rw-r--</code>), which is a umask of <code>002</code>. A sane alternative to this is a single shared user, which would use <code>755</code> and <code>644</code> which is a umask of <code>022</code>. You can restrict permissions even more by denying read from “other”, which would be a umask of <code>007</code> for a user per daemon or <code>077</code> for a single shared user. For a deeper explanation, try the Arch Linux wiki articles about [https://wiki.archlinux.org/index.php/File_permissions_and_attributes File permissions and attributes] and [https://wiki.archlinux.org/index.php/Umask Umask].

===== UMASK =====

Many docker images accept a <code>-e UMASK=002</code> environment variable and some software inside can be configured with a user, group and umask (NZBGet) or folder/file permission (Sonarr/Radarr). This will ensure that files and folders created by ''one'' can be read and written by the others. If you’re using existing folders and files, you’ll need to fix their current ownership and permissions too, but going forward they’ll be correct because you set each software up right.

===== PUID and PGID =====

Many docker images also take a <code>-e PUID=123</code> and <code>-e PGID=321</code> that lets you change the UID/GID used inside to that of an account on the outside. If you ever peak in, you’ll find that username is something like <code>abc</code>, <code>nobody</code> or <code>hotio</code>, but because it uses the UID/GID you pass in, on the outside it looks like the expected user. If you’re using storage from another system via NFS or CIFS, it will make your life easier if ''that'' system also has matching users and group. Perhaps let one system pick the UID/GIDs, then re-use those on the other system, assuming they don’t conflict.

===== Example =====

You run [https://github.com/Sonarr/Sonarr/releases Sonarr] using [https://github.com/hotio/docker-sonarr hotio/sonarr], you’ve created a <code>sonarr</code> user with uid <code>123</code> and a shared group <code>media</code> with gid <code>321</code> which the <code>sonarr</code> user is a member of. You configure the Docker image to run with <code>-e PUID=123 -e PGID=321 -e UMASK=002</code>. Sonarr also lets you configured user, group as well as folder and file permissions. The previous settings should negate these, but you could configure them if you wanted. Folders would be <code>775</code>, files <code>664</code> and the user/group are a little tricky because ''inside'' the container, they have a different name. Maybe <code>abc</code> or <code>nobody</code>. I’d leave all these blank unless you find you need them for some reason.

==== Single user and optional shared group ====

Another popular and arguably easier option is a single, shared user. Perhaps even ''your'' user. It isn’t as secure and doesn’t follow best practices, but in the end it is easier to understand and implement. The UMASK for this is <code>022</code> which results in <code>755</code> (<code>drwxr-xr-x</code>) for folders and <code>644</code> (<code>-rw-r--r--</code>) for files. The group no longer really matters, so you’ll probably just use the group named after the user. This does make it harder to share with ''other'' users, so you may still end up wanting a UMASK of <code>002</code> even with this setup.

==== Ownership and permissions of /config ====

Don’t forget that your <code>/config</code> volume will ''also'' need to have correct ownership and permissions, usually the daemon’s user and that user’s group like <code>sonarr:sonarr</code> and a umask of <code>022</code> or <code>077</code> so ''only'' that user has access. In a single user setup, this would of course be the one user you’ve chosen.

==== Consistent and well planned paths ====

'''Note: Many folks find [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ TRaSH's Hardlink Tutorial] helpful and easier to understand than this guide. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.'''

The easiest and most important detail is to create unified path definitions across all the containers.

If you’re wondering why hard links aren’t working or why a simple move is taking far longer than it should, this section explains it. The paths you use on the ''inside'' matter. Because of how Docker’s volumes work, passing in two volumes such as the commonly suggested <code>/tv</code> and <code>/downloads</code> makes them look like two file systems, even if they aren’t. This means hard links won’t work ''and'' instead of an instant move, a slower and more io intensive copy + delete is used. If you have multiple download clients because you’re using torrents and usenet, having a single <code>/downloads</code> path means they’ll be mixed up. Because the Radarr in one container will ask the NZBGet in its own container where files are, using the same path in both means it will all just work. If you don’t, you’d need to fix it with a remote path map.

So pick ''one'' path layout and use it for all of them. I’m a fan of <code>/data</code>, but there are other great names like <code>/shared</code>, <code>/media</code> or <code>/dvr</code>. If this can be the same on the outside ''and'' inside, your setup will be simpler: one path to remember or if integrating docker and native software. But if not, that’s fine too. For example, Synology might use <code>/Volume1/data</code> and unRAID might use <code>/mnt/user/data</code> on the outside, but <code>/data</code> on the inside is fine.

It is also important to remember that you’ll need to setup or re-configure paths in the software running ''inside'' these Docker containers. If you change the paths for your download client, you’ll need to edit its settings to match. If you change your library path, you’ll need to change those settings in Sonarr, Radarr, Lidarr and/or Plex.

===== Examples =====

What matters here is the general structure, not the names. You are free to pick folder names that make sense to you. And there are other ways of arranging things too. For example, you’re not likely to download and run into conflicts of identical releases between usenet and torrents, so you ''could'' put both in <code>/data/downloads/{movies|music|tv}</code> folders. Downloads don’t even have to be sorted into subfolders either, since movies, music and tv will rarely conflict.

This example <code>data</code> folder has subfolders for torrents and usenet and each of these have subfolders for tv, movie and music downloads to keep things neat. The <code>media</code> folder has nicely named <code>tv</code>, <code>movies</code> and <code>music</code> subfolders, this is your library and what you’d pass to Plex, Kodi, or Emby.

<pre>data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv</pre>
The path for each Docker container can be as specific as needed while still maintaining the correct structure:

====== Torrents ======

<pre>data
└── torrents
├── movies
├── music
└── tv</pre>
Torrents only needs access to torrent files, so pass it <code>-v /host/data/torrents:/data/torrents</code>. In the torrent software settings, you’ll need to reconfigure paths and you can sort into subfolders like<code>/data/torrents/{tv|movies|music}</code>.

====== Usenet ======

<pre>data
└── usenet
├── movies
├── music
└── tv</pre>
Usenet only needs access to usenet files, so pass it <code>-v /host/data/usenet:/data/usenet</code>. In the usenet software settings, you’ll need to reconfigure paths and you can sort into subfolders like<code>/data/usenet/{tv|movies|music}</code>.

====== Media Server ======

<pre>data
└── media
├── movies
├── music
└── tv</pre>
Plex/Emby only needs access to your media library, so pass <code>-v /host/data/media:/data/media</code>, which can have any number of subfolders like <code>movies</code>, <code>kids movies</code>, <code>tv</code>, <code>documentary tv</code> and/or <code>music</code> as sub folders.

====== Sonarr, Radarr and Lidarr ======

<pre>data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv</pre>
Sonarr, Radarr and Lidarr get everything using <code>-v /host/data:/data</code> because the ''download'' folder(s) and ''media'' folder will look like and ''be'' one file system. Hard links will work and moves will be atomic, instead of copy + delete.

===== Issues =====

There are a couple minor issues with not following the Docker image’s suggested paths.

The biggest is that volumes defined in the <code>Dockerfile</code> will get created if they’re not specified, this means they’ll pile up as you delete and re-create the containers. If they end up with data in them, they can consume space unexpectedly and likely in an unsuitable place. You can find a [https://old.reddit.com/r/usenet/wiki/docker#wiki_prune_docker cleanup command] in the helpful commands section below. This could also be mitigated by passing in an empty folder for all the volumes you don’t want to use, like <code>/data/empty:/movies</code> and <code>/data/empty:/downloads</code>. Maybe even put a file named <code>DO NOT USE THIS FOLDER</code> inside, to remind yourself.

Another problem is that some images are pre-configured to use the documented volumes, so you’ll need to change settings in the software inside the Docker container. Thankfully, since configuration persists outside the container this is a one time issue. You might also pick a path like <code>/data</code> or <code>/media</code> which some images already define for a specific use. It shouldn’t be a problem, but will be a little more confusing when combined with the previous issues. In the end, it is worth it for working hard links and fast moves. The consistency and simplicity are welcome side effects as well.

If you use the latest version of the abandoned [https://github.com/Sperryfreak01/RadarrSync RadarrSync] to synchronize two Radarr instances, it ''depends'' on mapping the ''same'' path inside to a different path on the outside, for example <code>/movies</code> for one instance would point at <code>/data/media/Movies</code> and the other at <code>/data/media/Movies 4k</code>. This breaks ''everything'' you’ve read above. There is no good solution, you either use the old version which isn’t as good, do your mapping in a way that is ugly and breaks hard links or just don’t use it at all.

==== Running containers using ====

===== Docker-compose =====

This is the best option for most users, it lets you control and configure many containers and their interdependence in one file. A good starting place is docker’s own [https://docs.docker.com/compose/gettingstarted/ Get started with Docker Compose]. You can use [https://composerize.com composerize] or [https://old.reddit.com/r/usenet/wiki/docker#wiki_get_docker-compose red5d/docker-autocompose]to convert <code>docker run</code> commands into a single <code>docker-compose.yml</code> file.

The below is ''not'' a complete working example! The containers only have PID, UID, UMASK and example paths defined to keep it simple.

<pre># sonarr
Sonarr:
image: "hotio/sonarr"
volumes:
- /path/to/config/sonarr:/config
- /host/data:/data
environment:
- PUID=111
- PGID=321
- UMASK=002

# deluge
Deluge:
image: binhex/arch-delugevpn
volumes:
- /path/to/config/deluge:/config
- /host/data/torrents:/data/torrents
environment:
- PUID=222
- PGID=321
- UMASK=002

# sabnzbd
SABnzbd:
image: binhex/arch-sabnzbd
volumes:
- /path/to/config/sabnzbd:/config
- /host/data/usenet:/data/usenet
environment:
- PUID=333
- PGID=321
- UMASK=002

# plex
Plex:
image: binhex/arch-plex
volumes:
- /path/to/config/plex:/config
- /host/data/media:/data/media

environment:
- PUID=444
- PGID=321
- UMASK=002</pre>
====== Update all images and containers ======

<pre>docker-compose pull
docker-compose up -d</pre>
====== Update individual image and container ======

<pre>docker-compose pull NAME
docker-compose up -d NAME</pre>
===== Docker Run =====

Like the Docker Compose example above, the following <code>docker run</code> commands are stripped down to ''only'' the PUID, PGID, UMASK and volumes in order to act as an obvious example.

<pre># sonarr
docker run -v /path/to/config/sonarr:/config \
-v /host/data:/data \
-e PUID=111 -e PGID=321 -e UMASK=002 \
hotio/sonarr

# deluge
docker run -v /path/to/config/deluge:/config \
-v /host/data/torrents:/data/torrents \
-e PUID=222 -e PGID=321 -e UMASK=002 \
binhex/arch-delugevpn

# sabnzbd
docker run -v /path/to/config/sabnzbd:/config \
-v /host/data/usenet:/data/usenet \
-e PUID=333 -e PGID=321 -e UMASK=002 \
binhex/arch-sabnzbd

# plex
docker run -v /path/to/config/plex:/config \
-v /host/data/media:/data/media \
-e PUID=444 -e PGID=321 -e UMASK=002 \
binhex/arch-plex</pre>
===== Systemd =====

I don’t run a full Docker setup, so I manage my few Docker containers with individual systemd service files. It standardizes control and makes dependencies simpler for both native and docker services. The generic example below can be adapted to any container by adjusting or adding the various values and options.

<pre># /etc/systemd/system/thing.service
[Unit]
Description=Thing
Requires=docker.service
After=network.target docker.service

[Service]
ExecStart=/usr/bin/docker run --rm \
--name=thing \
-v /path/to/config/thing:/config \
-v /host/data:/data
-e PUID=111 -e PGID=321 -e UMASK=002 \
nobody/thing

ExecStop=/usr/bin/docker stop -t 30 thing

[Install]
WantedBy=default.target</pre>
==== Helpful commands ====

===== List running containers =====

<pre>docker ps</pre>
===== Shell ''inside'' a container =====

<pre>docker exec -it CONTAINER_NAME /bin/bash</pre>
For more information, see the [https://docs.docker.com/engine/reference/commandline/exec/ docker exec] documentation.

===== Prune docker =====

<pre>docker system prune --all --volumes</pre>
Remove unused containers, networks, volumes, images and build cache. As the WARNING this command gives says, this will remove all of the previously mentioned items for anything not in use by a running container. In a correctly configured environment, this is fine. But be aware and proceed cautiously the first time. See the [https://docs.docker.com/engine/reference/commandline/system_prune/ docker system prune] documentation for more details.

===== Get docker run command =====

Getting the <code>docker run</code> command from GUI managers can be hard, this docker image makes it easy for a running container ([https://stackoverflow.com/questions/32758793/how-to-show-the-run-command-of-a-docker-container source]).

<pre>docker run --rm -v /var/run/docker.sock:/var/run/docker.sock assaflavie/runlike CONTAINER_NAME</pre>
===== Get docker-compose =====
Additionally, you may check out [https://trash-guides.info/Misc/how-to-provide-a-docker-compose/ TRaSH's Guide for docker-compose]

Getting a <code>docker-compose.yml</code> from running instances is possible with [https://hub.docker.com/r/red5d/docker-autocompose red5d/docker-autocompose], in case you’ve already started your containers with <code>docker run</code> or <code>docker create</code> and want to change to <code>docker-compose</code> style. It is also great for sharing your settings with others, since it doesn’t matter what management software you’re using. The last argument(s) are your container names and you can pass in as many as needed at the same time. The first container name is required, more are optional. You can see container names in the '''NAMES''' column of `docker ps`, they're usually set by you or might be generated based on the image like <code>binhex-qbittorrent</code>. It is ''not'' the image name, like <code>binhex/arch-qbittorrentvpn</code>.

<pre>docker run --rm -v /var/run/docker.sock:/var/run/docker.sock red5d/docker-autocompose CONTAINER_NAME [ANOTHER_CONTAINER_NAME] ... [ONE_MORE_CONTAINER_NAME]</pre>

===== Troubleshoot networking =====

Most Docker images don’t have many useful tools in them for troubleshooting, but you can [https://success.docker.com/article/troubleshooting-container-networking attach a network troubleshooting type image] to an existing container to help with that.

<pre>docker run -it --rm --network container:CONTAINER_NAME nicolaka/netshoot</pre>
===== Recursively chown user and group =====

<pre>chown -R user:group /some/path/here</pre>
===== Recursively chmod to 775/664 =====

<pre>chmod -R a=,a+rX,u+w,g+w /some/path/here
^ ^ ^ ^ adds write to group
| | | adds write to user
| | adds read to all and execute to all folders (which controls access)
| sets all to `000`</pre>
===== Find UID/GID for user =====

<pre>id <username></pre>

===== Examine files for hard links =====
<pre>ls -alhi
42207934 -rw-r--r-- 2 user group 0 Sep 11 11:55 hardlink
42207936 -rw-r--r-- 1 user group 0 Sep 11 11:55 nohardlinks
42207934 -rw-r--r-- 2 user group 0 Sep 11 11:55 original
</pre>

<pre>stat original
File: original
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 803h/2051d Inode: 42207934 Links: 2
Access: (0644/-rw-r--r--) Uid: ( 1000/ user) Gid: ( 1001/ group)
Access: 2020-09-11 11:55:43.803327144 -0500
Modify: 2020-09-11 11:55:43.803327144 -0500
Change: 2020-09-11 11:55:49.706660476 -0500
Birth: 2020-09-11 11:55:43.803327144 -0500
</pre>

==== Interesting docker images ====

* [https://hub.docker.com/r/rasmunk/sshfs rasmunk/sshfs] let you create an sshfs volume, ''perfect'' for a seedbox setup using a remote mount instead of sync. Better documentation, including examples can be found at the github [https://github.com/rasmunk/docker-volume-sshfs rasmunk/docker-volume-sshfs] repository. This is a more recently maintained fork of [https://hub.docker.com/p/vieux/sshfs vieux/sshfs].
* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/sonarr sonarr], [https://hub.docker.com/r/hotio/radarr radarr] and [https://hub.docker.com/r/hotio/lidarr lidarr] images let you run the built in version ''or'' specify an alternative via environment variable. The documentation and Dockerfile also don’t make any poor path suggestions. Images are automatically updated 2x in 1 hour if upstream changes are found. Hotio also builds our Pull Requests which may be useful for testing.
* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/ombi ombi], [https://hub.docker.com/r/hotio/jackett jackett], [https://hub.docker.com/r/hotio/nzbhydra2 nzbhydra2] and [https://hub.docker.com/r/hotio/bazarr bazarr] are useful too, but don’t really require any special permissions or paths.
* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/unpackerr unpackerr] is useful for packed torrent extraction across a variety of torrent clients where unpacking is lacking or missing entirely.
* [https://hub.docker.com/u/binhex binhex’s] [https://hub.docker.com/r/binhex/arch-qbittorrentvpn/ qbittorrent], [https://hub.docker.com/r/binhex/arch-delugevpn/ deluge] and [https://hub.docker.com/r/binhex/arch-rtorrentvpn/ rtorrent] are popular torrent clients with built in VPN support. For usenet, there is [https://hub.docker.com/r/binhex/arch-sabnzbd/ sabnzbd] and [https://hub.docker.com/r/binhex/arch-nzbget/ nzbget].
* [https://hub.docker.com/u/binhex binhex’s] [https://hub.docker.com/r/binhex/arch-sonarr/ sonarr], [https://hub.docker.com/r/binhex/arch-radarr/ radarr] and [https://hub.docker.com/r/binhex/arch-lidarr/ lidarr] images suggest default paths that don’t allow for hard linking, instead follow the process described above and pass in a single volume.
* [https://hub.docker.com/u/linuxserver linuxserver.io’s] images have images for a ''lot'' of software and they’re well maintained.
* [https://hub.docker.com/r/pyouroboros/ouroboros pyouroboros/ouroboros] or [https://hub.docker.com/r/containrrr/watchtower containrrr/watchtower] automatically update your running Docker containers to the latest available image. These are not recommended if you use Docker Compose.

==== Custom Docker Network and DNS ====

One interesting feature of a [https://docs.docker.com/network/network-tutorial-standalone/#use-user-defined-bridge-networks custom Docker network] is that it gets its own DNS server. If you create a bridge network for your containers, you can use their hostnames in your configuration. For example, if you <code>docker run --network=isolated --hostname=deluge binhex/arch-deluge</code> and <code>docker run --network=isolated --hostname=radarr binhex/arch-radarr</code>, you can then configure the Download Client in Radarr to point at just <code>deluge</code> and it’ll work ''and'' communicate on its own private network. Which means if you wanted to be even more secure, you could ''stop'' forwarding that port too. If you put your reverse proxy container on the same network, you can even stop forwarding the web interface ports and make them even more secure.

==== Common Problems ====

===== Correct ''outside'' paths, incorrect ''inside'' paths =====

Many people read this and think they understand, but they end up seeing the outside path correctly to something like <code>/data/usenet</code>, but then they miss the point and set the ''inside'' path to <code>/downloads</code> still.

===== Running Docker containers as root or changing users around =====

If you find yourself running your containers as <code>root:root</code>, you’re doing something wrong. If you’re not passing in a UID and GID, you’ll be using whatever the default is for the image and ''that'' will be unlikely to line up with a reasonable user on your system. And if you’re changing the user and group your Docker containers are running as, you’ll probably end up with permissions issues on folders like the <code>/config</code> folder which will likely have files and folders in them that got created the first time with the UID/GID you used the first time.

===== Running Docker containers with umask 000 =====

If you find yourself setting a UMASK of <code>000</code> (which is 777 for folders and 666 for files), you’re ''also'' doing something wrong. It leaves your files and folders read/write to ''everyone'', which is poor Linux hygiene.

==== Getting Help ====

Need some help? For real time, chat style support try the [https://discord.gg/xyRwnyB Sonarr] or [https://radarr.video/discord Radarr] Discord servers. If you prefer forum style support, make a post in [http://reddit.com/r/sonarr /r/sonarr] or [http://reddit.com/r/radarr /r/radarr].

Docker Guide

2021-05-08T14:11:00Z

Bakerboy448: Drop LSIO and fix radarr discord

=== The Best Docker Setup ===

'''TL; DR''': An [https://www.lexico.com/en/definition/eponymous eponymous] user per daemon and a shared group with a umask of <code>002</code>. Consistent path definitions between ''all'' containers that maintains the folder structure. Using one volume for Sonarr, Radarr and Lidarr so the download folder and library folder are on the same file system which makes hard links and instant moves possible. And most of all, ignore ''most'' of the Docker image’s path documentation!

'''Note: Many folks find [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ TRaSH's Hardlink Tutorial] helpful and easier to understand than this guide. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.'''

==== Introduction ====

This article will not show you specifics about the best Docker setup, but it describes an overview that you can use to make your own setup the best that it can be. The idea is that you run each docker container as its own user, with a shared group and consistent volumes so every container sees the same path layout. This is easy to say, but difficult to understand and explain.

==== Multiple users and a shared group ====

===== Permissions =====

Ideally, each software runs as its own user user and they’re all part of a shared group with folder permissions set to <code>775</code> (<code>drwxrwxr-x</code>) and files set to <code>664</code> (<code>-rw-rw-r--</code>), which is a umask of <code>002</code>. A sane alternative to this is a single shared user, which would use <code>755</code> and <code>644</code> which is a umask of <code>022</code>. You can restrict permissions even more by denying read from “other”, which would be a umask of <code>007</code> for a user per daemon or <code>077</code> for a single shared user. For a deeper explanation, try the Arch Linux wiki articles about [https://wiki.archlinux.org/index.php/File_permissions_and_attributes File permissions and attributes] and [https://wiki.archlinux.org/index.php/Umask Umask].

===== UMASK =====

Many docker images accept a <code>-e UMASK=002</code> environment variable and some software inside can be configured with a user, group and umask (NZBGet) or folder/file permission (Sonarr/Radarr). This will ensure that files and folders created by ''one'' can be read and written by the others. If you’re using existing folders and files, you’ll need to fix their current ownership and permissions too, but going forward they’ll be correct because you set each software up right.

===== PUID and PGID =====

Many docker images also take a <code>-e PUID=123</code> and <code>-e PGID=321</code> that lets you change the UID/GID used inside to that of an account on the outside. If you ever peak in, you’ll find that username is something like <code>abc</code>, <code>nobody</code> or <code>hotio</code>, but because it uses the UID/GID you pass in, on the outside it looks like the expected user. If you’re using storage from another system via NFS or CIFS, it will make your life easier if ''that'' system also has matching users and group. Perhaps let one system pick the UID/GIDs, then re-use those on the other system, assuming they don’t conflict.

===== Example =====

You run [https://github.com/Sonarr/Sonarr/releases Sonarr] using [https://github.com/hotio/docker-sonarr hotio/sonarr], you’ve created a <code>sonarr</code> user with uid <code>123</code> and a shared group <code>media</code> with gid <code>321</code> which the <code>sonarr</code> user is a member of. You configure the Docker image to run with <code>-e PUID=123 -e PGID=321 -e UMASK=002</code>. Sonarr also lets you configured user, group as well as folder and file permissions. The previous settings should negate these, but you could configure them if you wanted. Folders would be <code>775</code>, files <code>664</code> and the user/group are a little tricky because ''inside'' the container, they have a different name. Maybe <code>abc</code> or <code>nobody</code>. I’d leave all these blank unless you find you need them for some reason.

==== Single user and optional shared group ====

Another popular and arguably easier option is a single, shared user. Perhaps even ''your'' user. It isn’t as secure and doesn’t follow best practices, but in the end it is easier to understand and implement. The UMASK for this is <code>022</code> which results in <code>755</code> (<code>drwxr-xr-x</code>) for folders and <code>644</code> (<code>-rw-r--r--</code>) for files. The group no longer really matters, so you’ll probably just use the group named after the user. This does make it harder to share with ''other'' users, so you may still end up wanting a UMASK of <code>002</code> even with this setup.

==== Ownership and permissions of /config ====

Don’t forget that your <code>/config</code> volume will ''also'' need to have correct ownership and permissions, usually the daemon’s user and that user’s group like <code>sonarr:sonarr</code> and a umask of <code>022</code> or <code>077</code> so ''only'' that user has access. In a single user setup, this would of course be the one user you’ve chosen.

==== Consistent and well planned paths ====

'''Note: Many folks find [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ TRaSH's Hardlink Tutorial] helpful and easier to understand than this guide. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.'''

The easiest and most important detail is to create unified path definitions across all the containers.

If you’re wondering why hard links aren’t working or why a simple move is taking far longer than it should, this section explains it. The paths you use on the ''inside'' matter. Because of how Docker’s volumes work, passing in two volumes such as the commonly suggested <code>/tv</code> and <code>/downloads</code> makes them look like two file systems, even if they aren’t. This means hard links won’t work ''and'' instead of an instant move, a slower and more io intensive copy + delete is used. If you have multiple download clients because you’re using torrents and usenet, having a single <code>/downloads</code> path means they’ll be mixed up. Because the Radarr in one container will ask the NZBGet in its own container where files are, using the same path in both means it will all just work. If you don’t, you’d need to fix it with a remote path map.

So pick ''one'' path layout and use it for all of them. I’m a fan of <code>/data</code>, but there are other great names like <code>/shared</code>, <code>/media</code> or <code>/dvr</code>. If this can be the same on the outside ''and'' inside, your setup will be simpler: one path to remember or if integrating docker and native software. But if not, that’s fine too. For example, Synology might use <code>/Volume1/data</code> and unRAID might use <code>/mnt/user/data</code> on the outside, but <code>/data</code> on the inside is fine.

It is also important to remember that you’ll need to setup or re-configure paths in the software running ''inside'' these Docker containers. If you change the paths for your download client, you’ll need to edit its settings to match. If you change your library path, you’ll need to change those settings in Sonarr, Radarr, Lidarr and/or Plex.

===== Examples =====

What matters here is the general structure, not the names. You are free to pick folder names that make sense to you. And there are other ways of arranging things too. For example, you’re not likely to download and run into conflicts of identical releases between usenet and torrents, so you ''could'' put both in <code>/data/downloads/{movies|music|tv}</code> folders. Downloads don’t even have to be sorted into subfolders either, since movies, music and tv will rarely conflict.

This example <code>data</code> folder has subfolders for torrents and usenet and each of these have subfolders for tv, movie and music downloads to keep things neat. The <code>media</code> folder has nicely named <code>tv</code>, <code>movies</code> and <code>music</code> subfolders, this is your library and what you’d pass to Plex, Kodi, or Emby.

<pre>data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv</pre>
The path for each Docker container can be as specific as needed while still maintaining the correct structure:

====== Torrents ======

<pre>data
└── torrents
├── movies
├── music
└── tv</pre>
Torrents only needs access to torrent files, so pass it <code>-v /host/data/torrents:/data/torrents</code>. In the torrent software settings, you’ll need to reconfigure paths and you can sort into subfolders like<code>/data/torrents/{tv|movies|music}</code>.

====== Usenet ======

<pre>data
└── usenet
├── movies
├── music
└── tv</pre>
Usenet only needs access to usenet files, so pass it <code>-v /host/data/usenet:/data/usenet</code>. In the usenet software settings, you’ll need to reconfigure paths and you can sort into subfolders like<code>/data/usenet/{tv|movies|music}</code>.

====== Media Server ======

<pre>data
└── media
├── movies
├── music
└── tv</pre>
Plex/Emby only needs access to your media library, so pass <code>-v /host/data/media:/data/media</code>, which can have any number of subfolders like <code>movies</code>, <code>kids movies</code>, <code>tv</code>, <code>documentary tv</code> and/or <code>music</code> as sub folders.

====== Sonarr, Radarr and Lidarr ======

<pre>data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv</pre>
Sonarr, Radarr and Lidarr get everything using <code>-v /host/data:/data</code> because the ''download'' folder(s) and ''media'' folder will look like and ''be'' one file system. Hard links will work and moves will be atomic, instead of copy + delete.

===== Issues =====

There are a couple minor issues with not following the Docker image’s suggested paths.

The biggest is that volumes defined in the <code>Dockerfile</code> will get created if they’re not specified, this means they’ll pile up as you delete and re-create the containers. If they end up with data in them, they can consume space unexpectedly and likely in an unsuitable place. You can find a [https://old.reddit.com/r/usenet/wiki/docker#wiki_prune_docker cleanup command] in the helpful commands section below. This could also be mitigated by passing in an empty folder for all the volumes you don’t want to use, like <code>/data/empty:/movies</code> and <code>/data/empty:/downloads</code>. Maybe even put a file named <code>DO NOT USE THIS FOLDER</code> inside, to remind yourself.

Another problem is that some images are pre-configured to use the documented volumes, so you’ll need to change settings in the software inside the Docker container. Thankfully, since configuration persists outside the container this is a one time issue. You might also pick a path like <code>/data</code> or <code>/media</code> which some images already define for a specific use. It shouldn’t be a problem, but will be a little more confusing when combined with the previous issues. In the end, it is worth it for working hard links and fast moves. The consistency and simplicity are welcome side effects as well.

If you use the latest version of the abandoned [https://github.com/Sperryfreak01/RadarrSync RadarrSync] to synchronize two Radarr instances, it ''depends'' on mapping the ''same'' path inside to a different path on the outside, for example <code>/movies</code> for one instance would point at <code>/data/media/Movies</code> and the other at <code>/data/media/Movies 4k</code>. This breaks ''everything'' you’ve read above. There is no good solution, you either use the old version which isn’t as good, do your mapping in a way that is ugly and breaks hard links or just don’t use it at all.

==== Running containers using ====

===== Docker-compose =====

This is the best option for most users, it lets you control and configure many containers and their interdependence in one file. A good starting place is docker’s own [https://docs.docker.com/compose/gettingstarted/ Get started with Docker Compose]. You can use [https://composerize.com composerize] or [https://old.reddit.com/r/usenet/wiki/docker#wiki_get_docker-compose red5d/docker-autocompose]to convert <code>docker run</code> commands into a single <code>docker-compose.yml</code> file.

The below is ''not'' a complete working example! The containers only have PID, UID, UMASK and example paths defined to keep it simple.

<pre># sonarr
Sonarr:
image: "hotio/sonarr"
volumes:
- /path/to/config/sonarr:/config
- /host/data:/data
environment:
- PUID=111
- PGID=321
- UMASK=002

# deluge
Deluge:
image: binhex/arch-delugevpn
volumes:
- /path/to/config/deluge:/config
- /host/data/torrents:/data/torrents
environment:
- PUID=222
- PGID=321
- UMASK=002

# sabnzbd
SABnzbd:
image: binhex/arch-sabnzbd
volumes:
- /path/to/config/sabnzbd:/config
- /host/data/usenet:/data/usenet
environment:
- PUID=333
- PGID=321
- UMASK=002

# plex
Plex:
image: binhex/arch-plex
volumes:
- /path/to/config/plex:/config
- /host/data/media:/data/media

environment:
- PUID=444
- PGID=321
- UMASK=002</pre>
====== Update all images and containers ======

<pre>docker-compose pull
docker-compose up -d</pre>
====== Update individual image and container ======

<pre>docker-compose pull NAME
docker-compose up -d NAME</pre>
===== Docker Run =====

Like the Docker Compose example above, the following <code>docker run</code> commands are stripped down to ''only'' the PUID, PGID, UMASK and volumes in order to act as an obvious example.

<pre># sonarr
docker run -v /path/to/config/sonarr:/config \
-v /host/data:/data \
-e PUID=111 -e PGID=321 -e UMASK=002 \
hotio/sonarr

# deluge
docker run -v /path/to/config/deluge:/config \
-v /host/data/torrents:/data/torrents \
-e PUID=222 -e PGID=321 -e UMASK=002 \
binhex/arch-delugevpn

# sabnzbd
docker run -v /path/to/config/sabnzbd:/config \
-v /host/data/usenet:/data/usenet \
-e PUID=333 -e PGID=321 -e UMASK=002 \
binhex/arch-sabnzbd

# plex
docker run -v /path/to/config/plex:/config \
-v /host/data/media:/data/media \
-e PUID=444 -e PGID=321 -e UMASK=002 \
binhex/arch-plex</pre>
===== Systemd =====

I don’t run a full Docker setup, so I manage my few Docker containers with individual systemd service files. It standardizes control and makes dependencies simpler for both native and docker services. The generic example below can be adapted to any container by adjusting or adding the various values and options.

<pre># /etc/systemd/system/thing.service
[Unit]
Description=Thing
Requires=docker.service
After=network.target docker.service

[Service]
ExecStart=/usr/bin/docker run --rm \
--name=thing \
-v /path/to/config/thing:/config \
-v /host/data:/data
-e PUID=111 -e PGID=321 -e UMASK=002 \
nobody/thing

ExecStop=/usr/bin/docker stop -t 30 thing

[Install]
WantedBy=default.target</pre>
==== Helpful commands ====

===== List running containers =====

<pre>docker ps</pre>
===== Shell ''inside'' a container =====

<pre>docker exec -it CONTAINER_NAME /bin/bash</pre>
For more information, see the [https://docs.docker.com/engine/reference/commandline/exec/ docker exec] documentation.

===== Prune docker =====

<pre>docker system prune --all --volumes</pre>
Remove unused containers, networks, volumes, images and build cache. As the WARNING this command gives says, this will remove all of the previously mentioned items for anything not in use by a running container. In a correctly configured environment, this is fine. But be aware and proceed cautiously the first time. See the [https://docs.docker.com/engine/reference/commandline/system_prune/ docker system prune] documentation for more details.

===== Get docker run command =====

Getting the <code>docker run</code> command from GUI managers can be hard, this docker image makes it easy for a running container ([https://stackoverflow.com/questions/32758793/how-to-show-the-run-command-of-a-docker-container source]).

<pre>docker run --rm -v /var/run/docker.sock:/var/run/docker.sock assaflavie/runlike CONTAINER_NAME</pre>
===== Get docker-compose =====
Additionally, you may check out [https://trash-guides.info/Misc/how-to-provide-a-docker-compose/ TRaSH's Guide for docker-compose]

Getting a <code>docker-compose.yml</code> from running instances is possible with [https://hub.docker.com/r/red5d/docker-autocompose red5d/docker-autocompose], in case you’ve already started your containers with <code>docker run</code> or <code>docker create</code> and want to change to <code>docker-compose</code> style. It is also great for sharing your settings with others, since it doesn’t matter what management software you’re using. The last argument(s) are your container names and you can pass in as many as needed at the same time. The first container name is required, more are optional. You can see container names in the '''NAMES''' column of `docker ps`, they're usually set by you or might be generated based on the image like <code>binhex-qbittorrent</code>. It is ''not'' the image name, like <code>binhex/arch-qbittorrentvpn</code>.

<pre>docker run --rm -v /var/run/docker.sock:/var/run/docker.sock red5d/docker-autocompose CONTAINER_NAME [ANOTHER_CONTAINER_NAME] ... [ONE_MORE_CONTAINER_NAME]</pre>

===== Troubleshoot networking =====

Most Docker images don’t have many useful tools in them for troubleshooting, but you can [https://success.docker.com/article/troubleshooting-container-networking attach a network troubleshooting type image] to an existing container to help with that.

<pre>docker run -it --rm --network container:CONTAINER_NAME nicolaka/netshoot</pre>
===== Recursively chown user and group =====

<pre>chown -R user:group /some/path/here</pre>
===== Recursively chmod to 775/664 =====

<pre>chmod -R a=,a+rX,u+w,g+w /some/path/here
^ ^ ^ ^ adds write to group
| | | adds write to user
| | adds read to all and execute to all folders (which controls access)
| sets all to `000`</pre>
===== Find UID/GID for user =====

<pre>id <username></pre>

===== Examine files for hard links =====
<pre>ls -alhi
42207934 -rw-r--r-- 2 user group 0 Sep 11 11:55 hardlink
42207936 -rw-r--r-- 1 user group 0 Sep 11 11:55 nohardlinks
42207934 -rw-r--r-- 2 user group 0 Sep 11 11:55 original
</pre>

<pre>stat original
File: original
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 803h/2051d Inode: 42207934 Links: 2
Access: (0644/-rw-r--r--) Uid: ( 1000/ user) Gid: ( 1001/ group)
Access: 2020-09-11 11:55:43.803327144 -0500
Modify: 2020-09-11 11:55:43.803327144 -0500
Change: 2020-09-11 11:55:49.706660476 -0500
Birth: 2020-09-11 11:55:43.803327144 -0500
</pre>

==== Interesting docker images ====

* [https://hub.docker.com/r/rasmunk/sshfs rasmunk/sshfs] let you create an sshfs volume, ''perfect'' for a seedbox setup using a remote mount instead of sync. Better documentation, including examples can be found at the github [https://github.com/rasmunk/docker-volume-sshfs rasmunk/docker-volume-sshfs] repository. This is a more recently maintained fork of [https://hub.docker.com/p/vieux/sshfs vieux/sshfs].
* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/sonarr sonarr], [https://hub.docker.com/r/hotio/radarr radarr] and [https://hub.docker.com/r/hotio/lidarr lidarr] images let you run the built in version ''or'' specify an alternative via environment variable. The documentation and Dockerfile also don’t make any poor path suggestions.
* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/ombi ombi], [https://hub.docker.com/r/hotio/jackett jackett], [https://hub.docker.com/r/hotio/nzbhydra2 nzbhydra2] and [https://hub.docker.com/r/hotio/bazarr bazarr] are useful too, but don’t really require any special permissions or paths.
* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/unpackerr unpackerr] is useful for packed torrent extraction across a variety of torrent clients where unpacking is lacking or missing entirely.
* [https://hub.docker.com/u/binhex binhex’s] [https://hub.docker.com/r/binhex/arch-qbittorrentvpn/ qbittorrent], [https://hub.docker.com/r/binhex/arch-delugevpn/ deluge] and [https://hub.docker.com/r/binhex/arch-rtorrentvpn/ rtorrent] are popular torrent clients with built in VPN support. For usenet, there is [https://hub.docker.com/r/binhex/arch-sabnzbd/ sabnzbd] and [https://hub.docker.com/r/binhex/arch-nzbget/ nzbget].
* [https://hub.docker.com/u/binhex binhex’s] [https://hub.docker.com/r/binhex/arch-sonarr/ sonarr], [https://hub.docker.com/r/binhex/arch-radarr/ radarr] and [https://hub.docker.com/r/binhex/arch-lidarr/ lidarr] images suggest default paths that don’t allow for hard linking, instead follow the process described above and pass in a single volume.
* [https://hub.docker.com/u/linuxserver linuxserver.io’s] images also suggest default paths that don’t allow for hard linking, instead follow the process described above and pass in a single volume. But they do have images for a ''lot'' of software and they’re well maintained.
* [https://hub.docker.com/r/pyouroboros/ouroboros pyouroboros/ouroboros] or [https://hub.docker.com/r/containrrr/watchtower containrrr/watchtower] automatically update your running Docker containers to the latest available image. These are not recommended if you use Docker Compose.

==== Custom Docker Network and DNS ====

One interesting feature of a [https://docs.docker.com/network/network-tutorial-standalone/#use-user-defined-bridge-networks custom Docker network] is that it gets its own DNS server. If you create a bridge network for your containers, you can use their hostnames in your configuration. For example, if you <code>docker run --network=isolated --hostname=deluge binhex/arch-deluge</code> and <code>docker run --network=isolated --hostname=radarr binhex/arch-radarr</code>, you can then configure the Download Client in Radarr to point at just <code>deluge</code> and it’ll work ''and'' communicate on its own private network. Which means if you wanted to be even more secure, you could ''stop'' forwarding that port too. If you put your reverse proxy container on the same network, you can even stop forwarding the web interface ports and make them even more secure.

==== Common Problems ====

===== Correct ''outside'' paths, incorrect ''inside'' paths =====

Many people read this and think they understand, but they end up seeing the outside path correctly to something like <code>/data/usenet</code>, but then they miss the point and set the ''inside'' path to <code>/downloads</code> still.

===== Running Docker containers as root or changing users around =====

If you find yourself running your containers as <code>root:root</code>, you’re doing something wrong. If you’re not passing in a UID and GID, you’ll be using whatever the default is for the image and ''that'' will be unlikely to line up with a reasonable user on your system. And if you’re changing the user and group your Docker containers are running as, you’ll probably end up with permissions issues on folders like the <code>/config</code> folder which will likely have files and folders in them that got created the first time with the UID/GID you used the first time.

===== Running Docker containers with umask 000 =====

If you find yourself setting a UMASK of <code>000</code> (which is 777 for folders and 666 for files), you’re ''also'' doing something wrong. It leaves your files and folders read/write to ''everyone'', which is poor Linux hygiene.

==== Getting Help ====

Need some help? For real time, chat style support try the [https://discord.gg/xyRwnyB Sonarr] or [https://radarr.video/discord Radarr] Discord servers. If you prefer forum style support, make a post in [http://reddit.com/r/sonarr /r/sonarr] or [http://reddit.com/r/radarr /r/radarr].

Sonarr FAQ

2021-05-08T04:38:39Z

Bakerboy448:

== How does Sonarr find episodes? ==
[[#how_does_Sonarr_find_episodes|anchor]] 

* Sonarr does ''not'' regularly search for episode files that are missing or have not met their quality goals. Instead, it fairly frequently queries your indexers and trackers for ''all'' the newly posted episodes, then compares that with its list of episodes that are missing or need to be upgraded. Any matches are downloaded. This lets Sonarr cover a library of ''any size'' with just 24-100 queries per day (RSS interval of 15-60 minutes). If you understand this, you'll realize that it only covers the ''future'' though.
* So how do you deal with the present and past? When you're adding a show, you'll need to set the correct path, profile and monitoring status then use the Start search for missing checkbox. If the show has had no episodes and hasn't been released yet, you don't need to initiate a search.
* Put another way, Sonarr will only find episodes that are newly uploaded to your indexers. It will not actively try to find episodes you want that uploaded in the past.
* If you've already added the show, but now you want to search for it, you have a few choices. You can go to the show's page and use the search button, which will do a search and then automatically pick episode(s). You can search individual episodes or seasons automatically or manually. Or you can use the filters of <code>Missing</code> and <code>Cut-off Unmet</code>.
* If Sonarr has been offline for an extended period of time, Sonarr will attempt to page back to find the last release it processed in an attempt to avoid missing a release. As long as your indexer supports paging and it hasn't been too long Sonarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed episodes.

== Why didn’t Sonarr grab an episode I was expecting? ==
[[#Why_didnt_Sonarr_grab_an_episode_i_was_expecting|anchor]] 

First, make sure you read and understand the section above called ''“How does Sonarr find episodes?”'' Second, make sure at least one of your indexers has the episode you were expecting to be grabbed.
# Click the ‘Manual Search’ icon next to the episode listing in Sonarr. Are there any results? If no, then either Sonarr is having trouble communicating with your indexers, or your indexers do not have the episode, or the episode is improperly named/categorized on the indexer.
# '''If there are results from step 1''', check next to them for red exclamation point icon. Hover over the icon to see why that release is not a candidate for automatic downloads. If every result has the icon, then no automatic download will occur.
# '''If there is at least one valid manual search result from step 2''', then an automatic download should have happened. If it didn’t, the most likely reason is a temporary communication problem preventing an RSS Sync from your indexer. It is recommended to have several indexers set up for best results.
# '''If there is no manual result from a show, but you can find it when you browse your indexer’s website''' - This is a common problem that is most frequently caused by having an insufficient number of indexers. Different indexers index different content, and not all shows on your indexer may be tagged properly, which would cause Sonarr’s search to fail. Having several indexers active is the best solution to this problem.

== How are possible downloads compared? ==
[[#how_are_possible_downloads_compared|anchor]] 
'''Generally Quality Trumps All'''

The current logic [https://github.com/Sonarr/Sonarr/blob/develop/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs#L31-L40s can be found here].
'''''As of 3/26/2021 the logic is as follows'''''
# Quality
# Language
# Preferred Word Score
# Protocol
# Episode Count
# Episode Number
# Indexer Priority
# Peers (If Torrent)
# Age (If Usenet)
# Size

== Preferred Words FAQs ==
[[#Preferred_Words_FAQs|anchor]] 

For the score of the on disk file:
The existing name of the file and the "scene name" of the release are evaluated for preferred words. The higher score of the two is taken.

How are preferred words included in renaming?

For Sonarr you can make use of the `{Preferred Words}` token in your renaming scheme. and also check mark `Include Preferred when Renaming` in the release profile.
take a look [https://trash-guides.info/Sonarr/V3/Sonarr-recommended-naming-scheme/ HERE] for a recommended naming scheme examples for Sonarr.

Using the tokens in your renaming scheme could help with download loop issues.

Preferred Words always upgrade a release even if the quality and/or language cutoff has been met.
== How does Sonarr handle scene numbering issues (American Dad!, etc)? ==
[[#how_does_sonarr_handle_scene_numbering_issues|anchor]] 

* '''How Sonarr handles scene numbering issues'''
** Sonarr relies on [http://thexem.de/ TheXEM], a community driven site that lets users create mappings of shows that the scene (the people that post the files) and TheTVDB (which typically follows the network’s numbering). There are a number of shows on there already, but it is easy to add another and typically the changes are accepted within a couple days (if they’re correct). TheXEM is used to correct differences in episode numbering (disagreement whether an episode is a special or not) as well as season number differences, such as episodes being released as S10E01, but TheTVDB listing that same episode as S2017E01.
* '''Problematic Shows'''
** This by no means is an all inclusive list of shows that have known issues with scene mapping however, these are the big ones that come to mind while writing this.
** Typical Issue: Scene numbering does not match TVDb numbering so Sonarr doesn't work. Well enter XEM which creates a map for Sonarr to look at.
*** Scene releases double episodes in a single file since that is how they air but TVDb marks each episode individually.
*** Scene uses a year for the season S2010 and TVDb uses S01.
** [http://thexem.de XEM] works in most cases and keeps it running smooth without you ever knowing. However as with most things, there will always be a ''black sheep'' and in this case there is a list of them.
** This is an incomplete list of the known shows and how/why they're problematic:
*** American Dad
*** Arrested Development
*** Mythbusters
*** Paw Patrol
**** Double episode files vs single episode TVDb but also not all episodes are doubles so the map can get added wrong pointing to which ones are singles vs doubles
*** Pawn Stars
*** Pokémon
**** On TheXem, [http://thexem.de/xem/show/4638 pokemon] is tracking * dubbed* episodes. So if you want subbed episodes, you may be out of luck. If certain release groups are following TVDB and not XEM mapping, please contact us on our discord and bring the release name and group name as exceptions can be added for groups who follow TVDB.
* '''Possible resolutions:'''
# TVDb adds alternate ordering to the API (Current status: They say v4 but don't count on it to work or be stable based on the history of v3)
# XEM adds a map to allow for alternate orders that sonarr can use (Current status: Unlikely)
# Sonarr allows for disabling of XEM maps when doing manual searches (Current status: Unlikely)
* '''Sonarr side effects:'''
** On top of the issues with the shows already, Sonarr also has some odd behavior so you may just need to overlook this as well. Example:
** American Dad is currently on S17 based on TVDb or S16 based on Scene at the time of this writing. So searching in sonarr for season 17 will '''only''' return S16 results because of the XEM map. If you have a tracker with S17 episodes (because they use P2P and not Scene), please contact us on our discord and bring the release name and group name as exceptions can be added for groups who follow TVDB.

== Why can’t Sonarr import episode files for series X? / Why can’t Sonarr find releases for series X? ==
[[#why_cant_sonarr_import_episode_files_for_series_x_why_cant_sonarr_find_releases_for_series_x|anchor]] 

Sonarr relies on being able to match titles, often the scene posts episodes using different titles, eg ''CSI: Crime Scene Investigation'' as just ''CSI'' so Sonarr can’t match the names without some help. Sonarr maintains a list of problematic series which lets us solve this issue. '''For anime, it will need to be added to [https://thexem.de thexem.de]''', for other series to request a new mapping see the steps below.

# Make sure it hasn’t already been requested. [https://docs.google.com/spreadsheet/ccc?key=0Atcf2VZ47O8tdGdQN1ZTbjFRanhFSTBlU0xhbzhuMGc#gid=0 Requested Mappings]
# Make a new request here: [https://docs.google.com/forms/d/15S6FKZf5dDXOThH4Gkp3QCNtS9Q-AmxIiOpEBJJxi-o/viewform Scene Mapping Request Form]

''Typically these are added within 1-2 days.''

''Again, do not request a mapping for Anime; use XEM for that.'' Further information can be found with some of the XEM folks that hangout in our [https://discord.gg/an9rnEdWs5 <nowiki>#XEM</nowiki> discord channel].

The series "Helt Perfekt" with TVDB ids of <code>343189</code> and <code>252077</code> is difficult to automate due to TVDB having the same name for both shows, violating TVDB's own rules. The first entry for the series gets the name. Any future entries for the series must have the year as part of the series name. However, a scene exception as been added to map releases (case sensitive mapping) Helt Perfekt releases containing <code>NORWEGIAN</code> -> <code>252077</code> and containing <code>SWEDISH</code> -> <code>343189</code>

== TVDB is updated why isn't Sonarr? ==
[[#tvdb_is_updated_why_is_not_sonarr|anchor]] 

TVDB has a 24 hour cache on their API. Skyhook has a much smaller few hour cache on top of that. Sonarr only runs the Refresh Series task every 12 hours. Thus it typically takes 24 to 48 hours for a TVDB update to make it into Sonarr.

If you know a TVDB update was made more than 48 hours ago, then please come discuss on our [https://discord.gg/M6BvZn5 Discord].
== I see that feature/bug X was fixed, why can’t I see it? ==
[[#i_see_that_feature_bug_x_was_fixed_why_cant_i_see_it|anchor]] 

Sonarr consists of two main branches of code, <code>main</code> and <code>develop</code>, <code>main</code>is released periodically, when the <code>develop</code> branch is stable and <code>develop</code> is for pre-release testing and people willing to live on the edge, if you want to help out testing or want more information on the two branches, please see: [[Sonarr_Settings#Updates|Release Branches]]. When a feature is marked as in <code>develop</code> it will only be available to users running the <code>develop</code> branch, once it has been move to live (in <code>main</code>) it is officially released.

== Episode Progress - How is it calculated? ==
[[#episode_progress_-_how_is_it_calculated|anchor]] 

There are two parts to the episode count, one being the number of episodes (Episode Count) and the other being the number of episodes with files (Episode File Count), each one uses slightly different logic to give you the overall progress for a series or season.

* Episode Count
** Episode has already aired AND is monitored OR
** Episode has a file
* Episode File Count
** Episode has a file

If a series has 10 episodes that have all aired and you don’t have any files for them you would have 0/10 episodes, if you unmonitored all the episodes in that series you would have 0/0 and if you got all the episodes for that series, regardless of if the episodes are monitored or not, you would have 10/10 episodes.

== How do I access Sonarr from another computer? ==
[[#how_do_I_access_sonarr_from_another_computer|anchor]] 

By default Sonarr doesn’t listen to requests from all systems (when not run as administrator), it will only listen on localhost, this is due to how the Web Server Sonarr uses integrates with Windows (this also applies for current alternatives). If Sonarr is run as an administrator it will correctly register itself with Windows as well as open the Firewall port so it can be accessed from other systems on your network. Running as admin only needs to happen once (if you change the port it will need to be re-run).

== Why doesn’t Sonarr automatically search for missing episodes? ==
[[#why_doesnt_sonarr_automatically_search_for_missing_episodes|anchor]] 

There are two times when we would want to have missing episodes searched for, when a new series with existing aired episodes is added and when Sonarr has been offline and unable to find episodes as it normally would. Endlessly searching for episodes that have aired that are missing is a waste of resources, both in terms of local processing power and on the indexers and in our experience catches users off guard, wasting bandwidth.

In v1 of Sonarr we had an opt in backlog search option, often people would turn it on and then get a bunch of old episodes and ask us why, we also had indexers ask why they saw an increase in API calls, which was due to the backlog searching.

In v2 we sat back and thought about it and realized the benefit is not really there, we could try to throttle the searching, but that just draws it out and still does the same thing; hammer the indexer with useless requests. If the episode wasn’t there the last time the search was performed, why would it be there now? It would be if it was reposted, but if it was reposted, the automatic process that gets new episodes would see it was posted and act on it.

== Why does Sonarr refresh series information so frequently? ==
[[#why_does_sonarr_refresh_series_information_so_frequently|anchor]] 

* Sonarr refreshes series and episode information in addition to rescanning the disk for files every 12 hours. This might seem aggressive, but is a very important process. The data refresh from our TVDB proxy is important, because new episode information is synced down, air dates, number of episodes, status (continuing/ended). Even shows that aren’t airing are being updated with new information.
* The disk scan is less important, but is used to check for new files that weren’t sorted by Sonarr and detect deleted files.
* The most time consuming portion is the information refresh (assuming reasonable disk access speed), larger shows take longer due to the number of episodes to process.

== Why is there a number next to Activity? ==
[[#why_is_there_a_number_next_to_activity|anchor]] 

* This number shows the count of episodes in your download client’s queue and the last 30 items in its history that have not yet been imported. If the number is blue it is operating normally and should import episodes when they complete. Yellow means there is a warning on one of the episodes. Red means there has been an error. In the case of yellow (warning) and red (error), you will need to look at the queue under Activity to see what the issue is (hover over the icon to get more details).
* You need to remove the item from your download client’s queue or history to remove them from Sonarr’s queue.

== I see log messages for shows I don’t have/don’t want ==
[[#i_see_log_messages_for_shows_i_don_t_have_dont_want|anchor]] 

* These messages are completely normal and come from the RSS feeds that Sonarr checks to see if there are episodes you do want, usually these only appear in debug/trace logging, but in the event of an problem processing an item you may see a warning or error. It is safe to ignore the warnings/errors as well since they are for shows you don’t want, in the event it is for a show you want, open up a support thread on the forums.

== Seeding torrents aren’t deleted automatically ==
[[#seeding_torrents_arent_deleted_automatically|anchor]] 

* When a torrent that is still seeding is imported, it is copied or hard linked (if enabled and ''possible'') so that the torrent client can continue seeding. In an ideal setup, the torrent download folder and the library folder will be on the same file system and ''look like it'' (Docker and network shares make this easy to get wrong), which makes hard links possible and minimizes wasted space.
* In addition, you can configure your seed time/ratio goals in Sonarr or your download client, setup your download client to ''pause'' or ''stop'' when they’re met and enable Remove under Completed and Failed Download Handler. That way, torrents that finish seeding will be removed from the download client by Sonarr.

== Why can’t I add a new series? ==
[[#why_cant_i_add_a_new_series|anchor]] 

* In the event that TheTVDB is unavailable Sonarr is unable to get search results and you will be unable to add any new series by searching. You may be able to add a new series by the TVDBID if you know what it is, the UI explains how to add it by an ID.
* Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDB ID that does not have an English title. If no English title exist for that series on TheTVDB it will need to be added (if available).
* The show must be a TV Series, and not a movie. It must also exist on TVDB. If it is on IMDB, TMDB, or anywhere else, but not on TVDB you cannot add the show.
* The series must exist on TVDB

== Why can’t I add a new series when I know the TVDB ID? ==
[[#why_cant_i_add_a_new_series_when_i_know_the_tvdb_id|anchor]] 

* Sonarr cannot add any series that does not have an English language title. If you try to add a series via TVDB ID that does not have an English title. If no English title exist for that series on TheTVDB it will need to be added (if available).

== Sonarr won't work on Big Sur ==
[[#sonarr_wont_work_on_big_sur|anchor]] 

Run <code>chmod +x /Applications/Sonarr.app/Contents/MacOS/Sonarr</code>

== My Custom Script stopped working after upgrading from v2 ==
[[#my_custom_script_stopped_working_after_upgrading_from_v2|anchor]] 

You were likely passing arguments in your connection...that is not supported.
# Change your argument to be your path
# Make sure the shebang in your script maps to your pwsh path (if you don't have a shebang definition in there, add it)
# Make sure the pwsh script is executable

== What's the different Series Types? ==
[[#whats_the_different_series_types|anchor]] 
Most shows should be <code>Standard</code>. For daily shows which are typically released with a date, <code>Daily</code> should be used. Finally, there is anime where using <code>Anime</code> is ''usually'' right, but sometimes <code>Standard</code> can work better, so try the ''other'' one if you’re having issues.

Please note that if the series type is set to anime and none of your enabled indexers have any anime categories configured then it effectively skips the indexer and may appear that it is not searching.

=== Show Type Examples ===
Below are some example release names for each show type. The specific differentiating piece is noted in bold.

'''Daily'''
* Some.Daily.Show.'''2021.03.04'''.1080p.HDTV.x264-DARKSPORT
* A.Daily.Show.with.Some.Guy.'''2021.03.03'''.1080p.CC.WEB-DL.AAC2.0.x264-null
* DailyShow.'''2021.03.08'''.720p.HDTV.x264-NTb
'''Standard'''
* The.Show.'''S20E03'''.Episode.Title.Part.3.1080p.HULU.WEB-DL.DDP5.1.H.264-NTb
* Another.Show.'''S03E08'''.1080p.WEB.H264-GGEZ
* GreatShow.'''S17E02'''.1080p.HDTV.x264-DARKFLiX
'''Anime'''
* Anime.Origins.'''E04'''.File.4_.Monkey.WEB-DL.H.264.1080p.AAC2.0.AC3.5.1.Srt.EngCC-Pikanet128.1272903A
* [Coalgirls] Human X Monkey '''148''' (1920x1080 Blu-ray FLAC) [63B8AC67]
* [KaiDubs] Series x Title (2011) - '''142''' [1080p] [English Dub] [CC] [AS-DL] [A24AB2E5]

== How can I rename my series folders? ==
[[#how_can_i_rename_my_series_folders|anchor]] 
# Series
# Mass Editor
# Select what series need their folder renamed
# Change Root Folder to the same Root Folder that the series currently exist in
# Select "Yes move files"

{{FAQ|ARRNAME=Sonarr|ARRDISCORD=https://discord.gg/M6BvZn5|ARRPORT=8989}}

System status

2021-05-08T01:20:42Z

Bakerboy448: /* Radarr */

== System ==
=== Health ===
==== Overview ====
====== Radarr ======
<section begin=radarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=radarr_system_status_health_overview />
====== Sonarr ======
<section begin=sonarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=sonarr_system_status_health_overview />
====== Lidarr ======
<section begin=lidarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=lidarr_system_status_health_overview />
====== Readarr ======
<section begin=readarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=readarr_system_status_health_overview />
==== System Warnings ====
===== Radarr =====
<section begin=radarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Radarr are targeted for .NET. We will no longer be providing legacy mono builds after 3.2 is released. You are running one of these legacy builds but your platform supports .NET.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''[[Radarr_FAQ#how_do_i_backup_restore_my_Radarr| Back-Up your existing configuration]]''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>master</code> branch. If you are on <code>develop</code> or <code>nightly</code> you'll need to adjust <code>/master/</code> in the URL.
*** '''Delete your existing binaries (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''.
****<code>wget --content-disposition <nowiki>'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop radarr</code> Stop Radarr
****<code> sudo mv /opt/Radarr /opt/Radarr.old</code> Backup the old Binaries
**** <code> tar -xvzf Radarr*.linux-core-x64.tar.gz</code> Extract the Radarr Tarball
**** <code> sudo mv Radarr/ /opt</code> Move the new Radarr Binaries
**** <code> sudo chown -R radarr:radarr /opt/Radarr</code> Ensure Radarr has permissions to its directory, this assumes it runs as the user <code>radarr</code>
**** <code> sudo rm -rf /opt/Radarr.old</code> Remove the old binaries
**** <code> sudo rm -rf Radarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script in your systemd (<code> sudo nano -e /etc/systemd/system/radarr.service</code>) to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.
***** If Radarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start radarr.service</code> Restart Radarr

* '''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''
** Radarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.8 is the absolute minimum for Radarr but Mono 5.20 is currently recommended and is the minimum requirement on nightly builds.
** The upgrade procedure for Mono varies per platform.

*'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''
** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0.

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.

*'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.
** Please look at System -> Info to see the current AppData & Startup directories.
** This means Radarr will be unable to update itself without risking data-loss.
** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081

** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:7878/$1 [P,L]
** For Caddy (V1) use this:
*** Note: you'll also need to add the websocket directive to your radarr configuration
proxy /radarr 127.0.0.1:7878 {
websocket
transparent
}

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#ptp_settings_old|PTP Indexer Settings Out of Date]]'''
** The following PassThePopcorn indexers have deprecated settings and should be updated.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

*'''[[#mono_support_end_of_life|Mono and x86 builds are ending]]'''
** Mono and x86 builds will no longer be supported in the next build of the application. If you are receiving this error then you are running the mono version of the application or the x86 version. Unfortunately, due to increasing difficulting in development support for these legacy versions we will be discontinuing their support and thus releases for them going forward. Thus it is advised you upgrade to a supported Operating System that does not require neither x86 nor mono. You may also be able to explore using Docker for your needs.

<section end=radarr_system_status_health_system_warnings />

===== Sonarr =====
<section begin=sonarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]'''
** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].

* '''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''
** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].

* '''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''
** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform. 
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.
** The upgrade procedure for Mono varies per platform.

* '''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''
** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** The upgrade procedure for Mono varies per platform.

* '''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.
** ''(This warning will not appear if your current version is less than 14 days old)''

* '''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.

* '''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''
** Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux. 
** Please look at System -> About to see the current AppData & Startup directories.
** This means Sonarr will be unable to update itself without risking data-loss.
** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.
* '''[[#package_maintainer_message|Package Maintainer Message]]'''
** Please refer to the specific message your package maintainer is indicating to you. This is not a Sonarr issue. For additional information, refer to your package maintainer. Your package maintainer can be found in System -> Status -> About. Note that this includes docker and your package maintainer is whomever maintains your docker image.

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=sonarr_system_status_health_system_warnings />

===== Lidarr =====
<section begin=lidarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Lidarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''Back-Up your existing configuration''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>develop</code> branch. If you are on <code>nightly</code> you'll need to adjust <code>/develop/</code> in the URL.
***'''Delete your existing binaries (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''
****<code>wget --content-disposition <nowiki>'http://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop lidarr.service</code> Stop Lidarr
****<code> sudo mv /opt/Lidarr /opt/Lidarr.old</code> Backup the old Binaries
****<code> tar -xvzf Lidarr*.linux-core-x64.tar.gz</code> Extract the Lidarr Tarball
****<code> sudo mv Lidarr/ /opt</code> Move the new Lidarr Binaries
****<code> sudo chown -R lidarr:lidarr /opt/Lidarr</code> Ensure Lidarr has permissions to its directory, this assumes it runs as the user <code>lidarr</code>
****<code> sudo rm -rf /opt/Lidarr.old</code> Remove the old binaries
****<code> sudo rm -rf Lidarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script (<code> sudo nano -e /etc/systemd/system/lidarr.service</code>) to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.
***** If Lidarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start lidarr.service</code> Restart Lidarr

*'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''
** Lidarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.
** See "Update to .NET Core version above"

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081
** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:8686/$1 [P,L]

*'''[[#fpcalc_upgrade|Fpcalc Needs Upgrading]]'''
Lidarr can use chromaprint audio fingerprinting to identify tracks. This depends on an external binary, which is distributed with Lidarr for Windows and macOS, but must be provided independently on Linux.

To fix this on a native Linux instance, install the appropriate package using your package manager and make sure that fpcalc is on your PATH (this can be checked using which fpcalc and verifying that the correct location of fpcalc is returned):

{| class="wikitable"
|- style="font-weight:bold; text-align:center; vertical-align:middle;"
! Distribution
! Package
|-
| style="vertical-align:middle;" | Debian/Ubuntu
| <code>libchromaprint-tools</code>
|-
| style="vertical-align:middle;" | Fedora/CentOS
| <code>chromaprint-tools</code>
|-
| style="vertical-align:middle;" | Arch
| <code>chromaprint</code>
|-
| style="vertical-align:middle;" | OpenSUSE
|<code> chromaprint-fpcalc</code>
|-
| style="vertical-align:middle;" | Synology
| <code>chromaprint</code>
|}

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=lidarr_system_status_health_system_warnings />

===== Readarr =====
<section begin=readarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Readarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''Back-Up your existing configuration''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>master</code> branch. If you are on <code>develop</code> or <code>nightly</code> you'll need to adjust <code>/master/</code> in the URL.
***'''Delete your existing binaries (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''.
****<code>wget --content-disposition <nowiki>'http://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop readarr</code> Stop Readarr
****<code> sudo mv /opt/Readarr /opt/Readarr.old</code> Backup the old Binaries
****<code> tar -xvzf Readarr*.linux-core-x64.tar.gz</code> Extract the Readarr Tarball
****<code> sudo mv Readarr/ /opt</code> Move the new Readarr Binaries
****<code> sudo chown -R readarr:readarr /opt/Readarr</code> Ensure Readarr has permissions to its directory, this assumes it runs as the user <code>readarr</code>
****<code> sudo rm -rf /opt/Readarr.old</code> Remove the old binaries
****<code> sudo rm -rf Readarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script (<code> sudo nano -e /etc/systemd/system/readarr.service</code>) to call <code>Readarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.
***** If Readarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start readarr.service</code> Restart Readarr

*'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''
** Readarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.
** See "Update to .NET Core version above"

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081
** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:8787/$1 [P,L]

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=readarr_system_status_health_system_warnings />

==== Download Clients ====
===== Radarr =====
<section begin=radarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.
*** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Radarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Radarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Radarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Radarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Radarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

[https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Radarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#permissions_error|Permissions Error]]'''
** Radarr or the user radarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end=radarr_system_status_health_download_clients />

===== Sonarr =====
<section begin=sonarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Sonarr.
*** Ensure SSL encryption is not turned on if you're using both your Sonarr instance and your download client on a local network. See [[Sonarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Sonarr to prevent the errors.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Sonarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Sonarr/V3/Sonarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#permissions_error|Permissions Error]]'''
** Sonarr or the user sonarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end="sonarr_system_status_health_download_clients" />

===== Lidarr =====
<section begin=lidarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.
*** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Lidarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Lidarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished song is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Lidarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Lidarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/audio</code> and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/audio</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Lidarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* '''[[#permissions_error|Permissions Error]]'''
** Lidarr or the user lidarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=lidarr_system_status_health_download_clients />
===== Readarr =====
<section begin=readarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.
*** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Readarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Readarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Readarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished book is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Readarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Readarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/books</code> and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/books</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Readarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* '''[[#permissions_error|Permissions Error]]'''
** Readarr or the user readarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=readarr_system_status_health_download_clients />

==== Completed/Failed Download Handling ====
===== Radarr =====
<section begin=radarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=radarr_system_status_health_complete_failed_download_handling />

===== Sonarr =====
<section begin=sonarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the
<section end=sonarr_system_status_health_complete_failed_download_handling />

===== Lidarr =====
<section begin=lidarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidrr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=lidarr_system_status_health_complete_failed_download_handling />

===== Readarr =====
<section begin=readarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=readarr_system_status_health_complete_failed_download_handling />

==== Indexers ====
===== Radarr =====
<section begin=radarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_radarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Radarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_radarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Radarr will not grab new releases automatically]]'''
** So Radarr uses the RSS feed to pick up new releases as they come along. More info on that [[Radarr FAQ#How does Radarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=radarr_system_status_health_indexers />

===== Sonarr =====
<section begin=sonarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_sonarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Sonarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_sonarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Sonarr will not grab new releases automatically]]'''
** So Sonarr uses the RSS feed to pick up new releases as they come along. More info on that [[Sonarr FAQ#How does Sonarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''
** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=sonarr_system_status_health_indexers />
===== Lidarr =====
<section begin=lidarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Lidarr will not grab new releases automatically]]'''
** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for music (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=lidarr_system_status_health_indexers />
===== Readarr =====
<section begin=readarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_readarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Readarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_readarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Readarr will not grab new releases automatically]]'''
** So Readarr uses the RSS feed to pick up new releases as they come along. More info on that [[Readarr FAQ#How does Readarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for books (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=readarr_system_status_health_indexers />

==== Folders ====
===== Radarr =====
<section begin=radarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder
***# Easiest way to find this is to go to the Movies (Library) Tab
***# Create a custom filter with the old root folder path
***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files
<section end=radarr_system_status_health_folders />
===== Sonarr =====
<section begin=sonarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder
***# Go to the Series > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these series to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files
* '''[[#import_list_missing_root_folder|Import List missing root folder]]'''
** This error is typically identified if a list is looking for a root folder but that root folder is no longer available.
**#Go to Settings > Import Lists
**#Edit the import lists that were mentioned in the health check
**#Save
<section end=sonarr_system_status_health_folders />
===== Lidarr =====
<section begin=lidarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these artists to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files
<section end=lidarr_system_status_health_folders />
===== Readarr =====
<section begin=readarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these authors to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files
<section end=readarr_system_status_health_folders />

==== Media ====
===== Radarr =====
<section begin=radarr_system_status_health_media />
* '''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''
** The movie is linked to a TMDb Id that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It. 
** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu

* '''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''
** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.
<section end=radarr_system_status_health_media />
===== Sonarr =====
<section begin=sonarr_system_status_health_media />
* '''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''
** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.
<section end=sonarr_system_status_health_media />
===== Lidarr =====
<section begin=lidarr_system_status_health_media />
Text
<section end=lidarr_system_status_health_media />
===== Readarr =====
<section begin=readarr_system_status_health_media />
Text
<section end=readarr_system_status_health_media />

=== Disk Space ===
==== Radarr ====
<section begin=radarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=radarr_system_status_disk_space />
==== Sonarr ====
<section begin=sonarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=sonarr_system_status_disk_space />
==== Lidarr ====
<section begin=lidarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=lidarr_system_status_disk_space />
==== Readarr ====
<section begin=readarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=readarr_system_status_disk_space />

=== About ===
==== Radarr ====
<section begin=radarr_system_status_about />
This will tell you about your current install of Radarr
<section end=radarr_system_status_about />
==== Sonarr ====
<section begin=sonarr_system_status_about />
This will tell you about your current install of Radarr
<section end=sonarr_system_status_about />
==== Lidarr ====
<section begin=lidarr_system_status_about />
This will tell you about your current install of Lidarr
<section end=lidarr_system_status_about />
==== Readarr ====
<section begin=readarr_system_status_about />
This will tell you about your current install of Readarr
<section end=readarr_system_status_about />

=== More Info ===
==== Radarr ====
<section begin=radarr_system_status_more_info />
* Home Page: [https://radarr.video Radarr's home page]
* Wiki: [https://wiki.servarr.com/Radarr You're here already]
* Reddit: [https://reddit.com/r/radarr r/radarr]
* Discord: [https://radarr.video/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/radarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Radarr/Radarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]
<section end=radarr_system_status_more_info />
==== Sonarr ====
<section begin=sonarr_system_status_more_info />
* Home page: [https://sonarr.tv Sonarr's home page]
* Forums: [https://forums.sonarr.tv Sonarr Forums]
* Discord: [https://discord.gg/M6BvZn5 Join our discord]
* Reddit: [https://reddit.com/r/sonarr r/sonarr]
* Twitter: [https://twitter.com/sonarrtv @sonarrtv]
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]
* Wiki: [https://wiki.servarr.com/sonarr You're here already]
* Donations: If you're feeling generous and would like to donate [https://sonarr.tv/donate click here]
* Source: https://github.com/Sonarr/Sonarr Github]
* Feature Requests: Got a great idea drop it on Github [https://github.com/Sonarr/Sonarr/issues here]
<section end=sonarr_system_status_more_info />
==== Lidarr ====
<section begin=lidarr_system_status_more_info />
* Home page: [https://lidarr.audio Lidarr's home page]
* Wiki: [https://wiki.servarr.com/Lidarr You're here already]
* Reddit: [https://reddit.com/r/lidarr r/lidarr]
* Discord: [https://lidarr.audio/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/lidarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/lidarr/Lidarr/ Github]
* Feature Requests: Got a great idea drop it on GitHub [https://github.com/Lidarr/Lidarr/issues here]
<section end=lidarr_system_status_more_info />
==== Readarr ====
<section begin=readarr_system_status_more_info />
* Home page: [https://readarr.com Readarr's home page]
* Wiki: [https://wiki.servarr.com/Readarr You're here already]
* Reddit: [https://reddit.com/r/readarr r/readarr]
* Discord: [https://readarr.com/discord Join our discord]
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Readarr/Readarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Readarr/Readarr/issues click here]
<section end=readarr_system_status_more_info />

=== Templates ===

Cloud Setup

2021-05-06T23:26:35Z

Bakerboy448:

== Rclone, Mergerfs, and Google Drive ==

'''Please note that this guide is maintained and developed by the community and not the *Arr Teams'''

With many options for storing 'unlimited' data in the cloud, configuring your system to allow your Arr's and media serving apps to access the data securely is possible. For this guide we will use [https://gsuite.google.com/products/drive/ Google Suite Unlimited Storage] or a similar [https://rclone.org/ Rclone] compatible storage service. We will also use a utility called Mergerfs to help keep our uploads organized.

Please note that this guide is for information only and you should only store legally obtained media.

Please Note: To get "unlimited" storage with Google Drive, you require an Enterprise Workspace Plan. It appears very likely that unlimited storage is going away.

== Application Overview ==

Recommendations:
* '''Don't download into your Gdrive''' - Download to a local disk and move the data later with Rclone
* '''Don't import to your Gdrive''' - Set up a merged local cache disk and move the data later with Rclone
* '''Do all large writes locally'''
* '''Move to cloud on a schedule''' - Easily scriptable
* '''Absolutely do not write (large files) directly to the rclone mount'''

To connect with your Gdrive, you will need to use three applications:
# Rclone - https://rclone.org/install/
# mergerfs - https://github.com/trapexit/mergerfs
# fuse - https://manpages.ubuntu.com/manpages/eoan/man8/mount.fuse.8.html

Once you have set up these applications, it is highly recommended to set up a cron job to automatically move files from your local drive to the cloud using Rclone. Animosity22 has [https://github.com/animosity22/homescripts a terrific Github page] with a sample script, or [[Cloud_Setup#Nightly_Cloud_Upload_Example|see the example below.]]

=== Rclone ===
Rclone's core purpose for the Arr's is to allow access to your data depository that is located in Gdrive. Rclone will mount and serve your file automatically, with your apps not knowing they are accessing data in the cloud. More Rclone information can be found on [https://github.com/animosity22/homescripts animosity22's Github page.]

To install Rclone, run the following command:
<pre>curl https://rclone.org/install.sh | sudo bash </pre>

==== Setting up Rclone ====
Before we can run Rclone's config tool, we must create a Google API Client ID for your system. The default Rclone config will use the Rclone client ID, which is not recommended: Everyone should create a personal client ID.

# Log into the Google API Console with your Google account. It doesn't matter what Google account you use. (It need not be the same account as the Google Drive you want to access) https://console.developers.google.com/apis/dashboard
# Select a project or create a new project.
# Under "ENABLE APIS AND SERVICES" search for "Google Drive", and <code>enable</code> the "Google Drive API". [[File:ENABLE APIS AND SERVICES.png|thumb|ENABLE APIS AND SERVICES]]
# Click "Credentials" in the left-side panel, then "Create Credentials" in the upper right. [[File:Google Drive Credentials Screenshot.png|thumb|Create New Credentials]]
# If you already configured an "Oauth Consent Screen", then skip to the next step; if not, click on "CONFIGURE CONSENT SCREEN" button (near the top right corner of the right panel), then select "External" and click on "CREATE"; on the next screen, enter an "Application name" ("rclone" is OK) then click on "Save" (all other data is optional). Click again on "Credentials" on the left panel to go back to the "Credentials" screen.
# Click on the "+ CREATE CREDENTIALS" button at the top of the screen, then select "OAuth client ID".
# Choose an application type of "Desktop app" if you using a Google account or "Other" if you using a GSuite account and click "Create". (the default name is fine)
# It will show you a client ID and client secret. Write or copy these values down. Use these values in rclone config to add a new remote or edit an existing remote.

Setup your Google Service Account (SA) file this allows it to not be tied to a single user account.
# go to the Google Developer Console.
# go to "IAM & admin" -> "Service Accounts".
# Use the "Create Credentials" button. Fill in "Service account name" with something that identifies your client. e.g. <code>mount</code>Leave "Role" Empty
# Tick "Furnish a new private key" - select "Key type JSON".
# Tick "Enable G Suite Domain-wide Delegation". These credentials are what rclone will use for authentication. If you ever need to remove access, press the "Delete service account key" button.

Allow API access to Google Drive
# go to admin console
# Go into "Security" (or use the search bar)
# Select "Show more" and then "Advanced settings"
# Select "Manage API client access" in the "Authentication" section
# In the "Client Name" field enter the service account's "Client ID" - this can be found in the Developer Console under "IAM & Admin" -> "Service Accounts", then "View Client ID" for the newly created service account. It is a ~21 character numerical string.
# In the next field, "One or More API Scopes", enter https://www.googleapis.com/auth/drive to grant access to Google Drive specifically.

Now that you have the API access squared away, you can run the rclone <code>config</code> utility to create your rclone.conf file.

<code>rclone config</code>
# <code>n</code> - New Remote
# <code>cloud</code> - Name of your new remote
# <code>13</code> - Google Drive
# <code>abunchofnumbersandletters.apps.googleusercontent.com</code> Enter your Google Application Client Id
# <code>yourgoogleapplicationclientsecret</code>Enter your Google Application Client Secret
# <code>1</code> - Full Access
# Leave Blank ID of the root folder
# Enter the path and filename to your Google Drive SA Json
# <code>n</code> - Do Not Use Auto Config
# <code>y</code> - Use Team Drive
# Review for Accuracy

You can now mount your newly created remote to access your cloud storage:
rclone mount --daemon --daemon-timeout=5m --allow-non-empty --buffer-size=128M --use-mmap --dir-cache-time=48h --cache-info-age=48h --vfs-cache-mode=full --vfs-cache-max-age=6h --log-file=~/.config/rclone/logs/rclone.log --log-level INFO cloud: /mnt/cloud

When you executed <code>rclone config</code> above, it created a file <code>rclone.conf</code> and placed it at <code>~/.config/rclone.conf</code>. If you intend to have your OS auto-mount your new rclone mount using systemd, ensure this file is accessible by the user you have in your .conf file.

==== Encrypting your Cloud Storage ====
If you followed the previous steps, you created an unencrypted Google Drive mount. If you would like to encrypt your storage so that Google can not scan your files, then follow these optional steps:

Start by running Rclone's config tool again, as you did previously:
<code>rclone config</code>
# <code>n</code> - New Remote
# <code>cloudcrypt</code> - Name of your new encrypted remote
# <code>crypt</code> - Encrypt/Decrypt a remote
# <code>cloud:crypt</code> - Remote to encrypt/decrypt, followed by a semicolon and a name indicating the function.
# <code>standard</code> - How to encrypt the filenames.
# <code>true</code> - Encrypt directory names

The next few questions will ask you to create two passwords, one for the encryption and one for the salt. It is recommended to choose two different passwords, and for the best protection, allow them to be generated for you and document them somewhere safe.

Once the password section is finished, it should present you with the new config, which should look similar to this:
[cloudcrypt]
type = crypt
remote = cloud:crypt
filename_encryption = standard
directory_name_encryption = true
password = **Encrypted PW1**
password2 = **Encrypted PW2**

Finally, make sure when you run rclone (either manually or via autostart script), you mount <code>cloudcrypt</code> rather than calling <code>cloud</code>.

==== Rclone Linux Autostart using Systemd ====
Most modern Linux distributions have switched to systemd, which involves a simple unit service file which gets enabled and started. It is important to remember that in Linux, capitalization matters. <code>User</code> account names and <code>Group</code> names are typically all lowercase, as are the directory structures mapped to them as part of the home directory.
===== Preparing the Unit Service File =====
Several items may need to be changed to match your installation:

# <code>User</code> should match the service account that Rclone will run as.
# <code>Group</code> should match the service account group that Rclone will run as.

The unit service file should be named <code>Rclone.service</code> and the best place for it is <code>/etc/systemd/system/</code>. Alternative locations like <code>/usr/lib/systemd/system/</code> and <code>/lib/systemd/system/</code> may depend on the distribution used.

This example unit assumes that the <code>User</code> and <code>Group</code> are both <code>plex</code>, Rclone's executable is placed in <code>/usr/bin/</code>, your cloud storage is being mounted to <code>/cloud</code>, and you have previously ran Rclone and set up a config file, which is located at <code>~/.config/rclone/rclone.conf</code> Feel free to remove the <code># comment</code> lines, they are there for those who want to know what those flags are doing and were taken from the rclone documentation.

[Unit]
Description=Google Drive Encrypted (rclone)
Wants=network-online.target
After=network-online.target

[Service]
Type=notify
ExecStart=/usr/bin/rclone mount cloud: /mnt/cloud \
# Allow mounting over a non-empty directory (not Windows).
--allow-non-empty \
# In memory buffer size when reading files for each --transfer. (default 16M)
--buffer-size=128M \
# Use mmap allocator (see docs).
--use-mmap \
# Time to cache directory entries for. (default 5m0s)
--dir-cache-time=48h \
# How long to cache file structure information (directory listings, file size, times etc). (default 6h0m0s)
--cache-info-age=48h \
# Cache mode off|minimal|writes|full (default off)
--vfs-cache-mode=full \
# Max age of objects in the cache. (default 1h0m0s)
--vfs-cache-max-age=6h \
# Override the permission bits set by the filesystem.
--umask 002 \
# Location where rclone logs will be stored
--log-file=~/.config/rclone/logs/rclone.log \
# Logging level for rclone logs
--log-level INFO \
# Location where the rclone.conf file is located
--config ~/.config/rclone/rclone.conf
ExecStop=/bin/fusermount -uz /mnt/cloud
Restart=on-abort
User=plex
KillMode=none
RestartSec=5

[Install]
WantedBy=default.target
===== Verify Directory Permissions =====
Ensure the <code>User</code> that will be running Rclone has access to both the executable directory and data directory.
Running the command <code>ls -lad /directory/</code> will show the permissions for that folder. In the example below, the user and group are both <code>plex</code>.
Example:
$ ls -lad /cloud
drwxr-xr-x 6 plex plex 24576 Nov 28 21:30 /cloud
$ ls -lad /home/plex/.config/rclone/
drwxr-xr-x 6 plex plex 24576 Nov 28 21:30 /home/plex/.config/rclone/

===== Enabling and starting the Unit Service File =====
Once you have created <code>Rclone.service</code>, you will want to enable the service:
sudo systemctl enable Rclone.service

You are now ready to start Rclone. You can do so with the <code>start</code> command:
sudo systemctl start Rclone.service

If you want to verify Rclone is running, you can run the <code>status</code> command:
$ sudo systemctl status rclone.service
● rclone.service - Google Drive Encrypted (rclone)
Loaded: loaded (/etc/systemd/system/rclone.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-11-15 16:28:26 MST; 2 weeks 4 days ago
Main PID: 2392484 (rclone)
Tasks: 31 (limit: 76935)
Memory: 21.9G
CGroup: /system.slice/rclone.service
└─2392484 /usr/bin/rclone mount cloud: /cloud --allow-non-empty --buffer-size=128M --use-mmap --dir-cache-time=48h >
Nov 15 16:28:25 systemname systemd[1]: Starting Google Drive Encrypted (rclone)...
Nov 15 16:28:26 systemname systemd[1]: Started Google Drive Encrypted (rclone).

=== Mergerfs ===
Mergerfs core purpose for the Arr's is to allow you to have a single merged directory structure, based on two different directories. For example, if you used rclone to mount a directory named <code>/mnt/cloud</code> and you have a locally mounted directory named <code>/mnt/local</code>, <code>mergerfs</code> would create a single merged directory of those two, which you could call <code>/mnt/merge</code>. Your media server and Arrs would access <code>/mnt/merge</code> and see the combination of local + cloud storage.

Example:
You have the first 4 episodes of 'Popular TV Show' located on your cloud drive, and Sonarr just downloaded and imported episode 5. If you looked in your cloud drive (/mnt/cloud), you would see:
/mnt/cloud/TV Shows/Popular TV Show/S01E01.mkv
/mnt/cloud/TV Shows/Popular TV Show/S01E02.mkv
/mnt/cloud/TV Shows/Popular TV Show/S01E02.mkv
/mnt/cloud/TV Shows/Popular TV Show/S01E04.mkv
If you looked in your local storage (/local) you would see:
/mnt/local/TV Shows/Popular TV Show/S01E05.mkv
And if you looked in the merged directory thanks to mergerfs (/merge) you would see:
/mnt/merge/TV Shows/Popular TV Show/S01E01.mkv
/mnt/merge/TV Shows/Popular TV Show/S01E02.mkv
/mnt/merge/TV Shows/Popular TV Show/S01E02.mkv
/mnt/merge/TV Shows/Popular TV Show/S01E04.mkv
/mnt/merge/TV Shows/Popular TV Show/S01E05.mkv
None of your applications know that these files have two different real file paths. All new files would always be written to your local HD, then you can use Rclone to sync them to the cloud later. When that sync is completed, its invisible to your apps so you do not need to worry about missing episodes or movies.

==== Setting up Mergerfs ====
Mergefs has a dependency on Fuse, so we will start by installing that:
sudo apt install fuse
Next, we must modify the <code>fuse.conf</code> file to enable the <code>allow_other</code> funtion:
sudo nano /etc/fuse.conf
Modify the last line by removing the # before <code>user_allow_other</code>. It should look like this:
# Allow non-root users to specify the allow_other or allow_root mount options.
user_allow_other
Now we can install Mergerfs. Go to the [https://github.com/trapexit/mergerfs/releases Mergerfs github page] and download the newest release that matches your install.
<pre>wget https://github.com/trapexit/mergerfs/releases/download/2.32.0/mergerfs_2.32.0.ubuntu-focal_amd64.deb</pre>
And then install it:
dpkg -i mergefs*.deb

To execute Mergerfs, run the following command. This assumes your local storage is mounted at <code>/mnt/local</code>, your cloud storage is mounted at <code>/mnt/cloud</code>, and your merged mount is <code>/mnt/merge</code>. ''Note:'' There are no spaces in the variables passed to the <code>-o</code> flag, so it looks like a giant run on list and should be a single line.
/usr/bin/mergerfs /mnt/local:/mnt/cloud /mnt/merge -o rw,use_ino,allow_other,func.getattr=newest,category.action=all,category.create=ff,cache.files=auto-full,statfs_ignore=nc,func.getattr=newest,dropcacheonclose=true,nonempty

Once you verify that everything is working, it is recommended to use an autostart file configured to start after Rclone.

==== Mergerfs Linux Autostart using Systemd ====
Most modern Linux distributions have switched to systemd, which involves a simple unit service file which gets enabled and started. It is important to remember that in Linux, capitalization matters. <code>User</code> account names and <code>Group</code> names are typically all lowercase, as are the directory structures mapped to them as part of the home directory.

===== Preparing the Unit Service File =====
Several items may need to be changed to match your installation:

# <code>User</code> should match the service account that Mergerfs will run as.
# <code>Group</code> should match the service account group that Mergerfs will run as.

The unit service file should be named to match your merged folder name. If you have followed along with this wiki, that name would be <code>merge</code> so your service file would be named<code>merge.service</code>, and the best place for it is <code>/etc/systemd/system/</code>. Alternative locations like <code>/usr/lib/systemd/system/</code> and <code>/lib/systemd/system/</code> may depend on the distribution used.

This example unit assumes that the <code>User</code> and <code>Group</code> are both <code>plex</code>, Mergerfs's executable is placed in <code>/usr/local/bin/</code>, your local storage is mounted at <code>/mnt/local</code>, your cloud storage is mounted at <code>/mnt/cloud</code>, and your merged mount is <code>/mnt/merge</code>.

[Unit]
Description=Mergerfs Mount (merge)
Requires=rclone.service
After=rclone.service

[Service]
Type=forking
ExecStart=/usr/bin/mergerfs /mnt/local:/mnt/cloud=NC /mnt/merge \
-o rw,use_ino,allow_other,func.getattr=newest,category.action=all,category.create=ff,cache.files=auto-full,statfs_ignore=nc,func.getattr=newest,dropcacheonclose=true,nonempty
KillMode=process
Restart=on-failure
User=plex
Group=plex

[Install]
WantedBy=multi-user.target

===== Verify Directory Permissions =====
Ensure the <code>User</code> that will be running Mergerfs has access to all data directories.
Running the command <code>ls -lad /directory/</code> will show the permissions for that folder. In the example below, the user and group are both <code>plex</code>.
Example:
$ ls -lad /mnt/cloud
drwxr-xr-x 6 plex plex 24576 Nov 28 21:30 /mnt/cloud
$ ls -lad /mnt/local
drwxr-xr-x 6 plex plex 24576 Nov 28 21:30 /mnt/local
$ ls -lad /mnt/merge
drwxr-xr-x 6 plex plex 24576 Nov 28 21:30 /mnt/merge

===== Enabling and starting the Unit Service File =====
Once you have created <code>merge.service</code>, you will want to enable the service:
sudo systemctl enable merge.service

You are now ready to start Mergerfs. You can do so with the <code>start</code> command:
sudo systemctl start merge.service

If you want to verify Mergerfs is running, you can run the <code>status</code> command:
$ sudo systemctl status merge.service
● merge.service - Mergerfs Mount (merge)
Loaded: loaded (/etc/systemd/system/merge.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-11-15 16:28:26 MST; 2 weeks 4 days ago
Main PID: 2392484 (mergerfs)
Tasks: 31 (limit: 76935)
Memory: 21.9G
CGroup: /system.slice/merge.service
└─2392484 /usr/local/bin/mergerfs /mnt/local:/mnt/cloud /mnt/merge -o rw,use_ino,allow_other,func.getattr=newest, >
Nov 15 16:28:25 systemname systemd[1]: Starting Mergerfs Mount (merge)...
Nov 15 16:28:26 systemname systemd[1]: Started Mergerfs Mount (merge).
=== Nightly Cloud Upload Example ===
Once Rclone and Mergefs are set up and configured, all data should be written on your local disk first. You will want to sync this data to your cloud drive then remove it to ensure your local disk does not run out of space. Below is an example bash shell script you may want to use, modeled on Animosity22's [https://github.com/animosity22/homescripts/blob/master/scripts/upload_cloud upload_cloud script].

First start by creating your script.
nano ~/.config/scripts/nightly_cloud_sync.sh
Example Script:
<syntaxhighlight lang=bash>
#!/bin/bash
# Variables to verify match your installation
# Rclone Config file
RCLONE_CONFIG=/home/plex/.config/rclone/rclone.conf
export RCLONE_CONFIG
# User account that Rclone is running as
RCLONE_USER_AGENT=plex
export RCLONE_USER_AGENT
# Local Mount - Ensure this is set to your local disk only.
LOCAL=/local
EXCLUDES=/home/plex/.config/scripts/excludes.log
LOGFILE=/home/plex/.config/scripts/upload.log
# Name of your Rclone Remote, likely cloud or cloudcrypt
REMOTE=cloud
# This will allow for 3 days for media analysis / intro generation. Feel free to reduce if needed.
MOVEAGE=3d

# Checks
# Running Check
if [[ $(pidof -x "$(basename "$0")" -o %PPID) ]]; then exit; fi
# Exclude File Check
if [[ ! -f $EXCLUDES ]] ; then
echo 'Warning: No excludes.log file found at $EXCLUDES'
exit 1
fi
# Local Disk Check
if /bin/findmnt $LOCAL -o FSTYPE -n | grep fuse; then
echo "Warning: $LOCAL is not a local disk!"
exit 1
fi
# Rclone Move Command
/usr/bin/rclone move $LOCAL $REMOTE: --log-file $LOGFILE -v --exclude-from $EXCLUDES --delete-empty-src-dirs --fast-list --min-age $MOVEAGE
</syntaxhighlight>

To add this file to your cron job list, edit your crontab. Ensure your are logged in as the users you want the crontab to run as.
crontab -e
Add the following lines at the bottom of the folder.
# Nightly Cloud Sync
12 3 * * * ~/.config/scripts/nightly_cloud_sync.sh

== Recommended Plex Server Changes ==
=== Increase the Default Cache Size of your Plex DB ===
With unlimited storage, some servers may run into database locking/timeout issues. Increasing the default cache size could help alleviate this.
# Stop Plex
# Locate your Plex DB. cd plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases
# Run this command: <code>sqlite3 com.plexapp.plugins.library.db</code>
# The SQLLite prompt will open up. Type this next: <code>PRAGMA default_cache_size = 6000000;</code> and don't forget the trailing semicolon.
# There will be no confirmation that anything happened. Press CTRL + D to exit SqlLite.
# Start Plex.
=== Increase the number of file watchers ===
Helps performance when you have a lot of files and directories in cloud storage. [https://forums.plex.tv/t/linux-tips/276247/9 Source.]
Edit your <code>sysctl.conf</code> file:
sudo nano /etc/sysctl.conf
Add the following lines at the bottom:
# Increase File Watchers for Plex
fs.inotify.max_user_watches=262144

You will need to restart your system for this change to take effect.

System status

2021-05-06T23:25:10Z

Bakerboy448: /* System Warnings */

== System ==
=== Health ===
==== Overview ====
====== Radarr ======
<section begin=radarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Radarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=radarr_system_status_health_overview />
====== Sonarr ======
<section begin=sonarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=sonarr_system_status_health_overview />
====== Lidarr ======
<section begin=lidarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Lidarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=lidarr_system_status_health_overview />
====== Readarr ======
<section begin=readarr_system_status_health_overview />
This page contains a list of health checks errors. These health checks are periodically performed performed by Readarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
<section end=readarr_system_status_health_overview />
==== System Warnings ====
===== Radarr =====
<section begin=radarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Radarr are targeted for .NET. We will likely no longer be providing legacy mono builds after 3.1 is released. You are running one of these legacy builds but your platform supports .NET.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''[[Radarr_FAQ#how_do_i_backup_restore_my_Radarr| Back-Up your existing configuration]]''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>master</code> branch. If you are on <code>develop</code> or <code>nightly</code> you'll need to adjust <code>/master/</code> in the URL.
*** '''Delete your existing binaries (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''.
****<code>wget --content-disposition <nowiki>'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop radarr</code> Stop Radarr
****<code> sudo mv /opt/Radarr /opt/Radarr.old</code> Backup the old Binaries
**** <code> tar -xvzf Radarr*.linux-core-x64.tar.gz</code> Extract the Radarr Tarball
**** <code> sudo mv Radarr/ /opt</code> Move the new Radarr Binaries
**** <code> sudo chown -R radarr:radarr /opt/Radarr</code> Ensure Radarr has permissions to its directory, this assumes it runs as the user <code>radarr</code>
**** <code> sudo rm -rf /opt/Radarr.old</code> Remove the old binaries
**** <code> sudo rm -rf Radarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script in your systemd (<code> sudo nano -e /etc/systemd/system/radarr.service</code>) to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.
***** If Radarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start radarr.service</code> Restart Radarr

* '''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''
** Radarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.8 is the absolute minimum for Radarr but Mono 5.20 is currently recommended and is the minimum requirement on nightly builds.
** The upgrade procedure for Mono varies per platform.

*'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''
** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0.

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Radarr will be unable to update itself. You’ll have to update Radarr manually or set the permissions on Radarr’s Startup directory (the installation directory) to allow Radarr to update itself.

*'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.
** Please look at System -> Info to see the current AppData & Startup directories.
** This means Radarr will be unable to update itself without risking data-loss.
** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Radarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081

** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:7878/$1 [P,L]
** For Caddy (V1) use this:
*** Note: you'll also need to add the websocket directive to your radarr configuration
proxy /radarr 127.0.0.1:7878 {
websocket
transparent
}

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#ptp_settings_old|PTP Indexer Settings Out of Date]]'''
** The following PassThePopcorn indexers have deprecated settings and should be updated.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

*'''[[#mono_support_end_of_life|Mono and x86 builds are ending]]'''
** Mono and x86 builds will no longer be supported in the next build of the application. If you are receiving this error then you are running the mono version of the application or the x86 version. Unfortunately, due to increasing difficulting in development support for these legacy versions we will be discontinuing their support and thus releases for them going forward. Thus it is advised you upgrade to a supported Operating System that does not require neither x86 nor mono. You may also be able to explore using Docker for your needs.

<section end=radarr_system_status_health_system_warnings />

===== Sonarr =====
<section begin=sonarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]'''
** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Occasionally we increase the version we build against to be able to utilize new features. Apparently you haven't applied the appropriate Windows updates in a while and need to upgrade .Net to be able to use newer versions of Sonarr.
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].

* '''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''
** Sonarr uses the .Net Framework. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. [https://dotnet.microsoft.com/download/dotnet-framework Please follow the instructions here].

* '''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''
** Sonarr is written in .Net and requires Mono to run. Various versions of Sonarr have different minimum versions of Mono to operate correctly. The ideal version of Mono varies per platform. 
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.
** The upgrade procedure for Mono varies per platform.

* '''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''
** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** The upgrade procedure for Mono varies per platform.

* '''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don't have Auto-Updating enabled, so you'll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point. But while you're at it, read the change log to find out what the relevant changes were.
** ''(This warning will not appear if your current version is less than 14 days old)''

* '''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.

* '''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''
** Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux. 
** Please look at System -> About to see the current AppData & Startup directories.
** This means Sonarr will be unable to update itself without risking data-loss.
** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.
* '''[[#package_maintainer_message|Package Maintainer Message]]'''
** Please refer to the specific message your package maintainer is indicating to you. This is not a Sonarr issue. For additional information, refer to your package maintainer. Your package maintainer can be found in System -> Status -> About. Note that this includes docker and your package maintainer is whomever maintains your docker image.

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=sonarr_system_status_health_system_warnings />

===== Lidarr =====
<section begin=lidarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Lidarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''Back-Up your existing configuration''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>develop</code> branch. If you are on <code>nightly</code> you'll need to adjust <code>/develop/</code> in the URL.
***'''Delete your existing binaries (contents or folder of /opt/Lidarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''
****<code>wget --content-disposition <nowiki>'http://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop lidarr.service</code> Stop Lidarr
****<code> sudo mv /opt/Lidarr /opt/Lidarr.old</code> Backup the old Binaries
****<code> tar -xvzf Lidarr*.linux-core-x64.tar.gz</code> Extract the Lidarr Tarball
****<code> sudo mv Lidarr/ /opt</code> Move the new Lidarr Binaries
****<code> sudo chown -R lidarr:lidarr /opt/Lidarr</code> Ensure Lidarr has permissions to its directory, this assumes it runs as the user <code>lidarr</code>
****<code> sudo rm -rf /opt/Lidarr.old</code> Remove the old binaries
****<code> sudo rm -rf Lidarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script (<code> sudo nano -e /etc/systemd/system/lidarr.service</code>) to call <code>Lidarr</code> instead of calling it with mono like <code>mono --debug Lidarr.exe</code>. In other words you want, as an example, <code>/opt/Lidarr/Lidarr</code> and '''not''' <code>mono --debug /opt/Lidarr/Lidarr</code>.
***** If Lidarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start lidarr.service</code> Restart Lidarr

*'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''
** Lidarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.
** See "Update to .NET Core version above"

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081
** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:8686/$1 [P,L]

*'''[[#fpcalc_upgrade|Fpcalc Needs Upgrading]]'''
Lidarr can use chromaprint audio fingerprinting to identify tracks. This depends on an external binary, which is distributed with Lidarr for Windows and macOS, but must be provided independently on Linux.

To fix this on a native Linux instance, install the appropriate package using your package manager and make sure that fpcalc is on your PATH (this can be checked using which fpcalc and verifying that the correct location of fpcalc is returned):

{| class="wikitable"
|- style="font-weight:bold; text-align:center; vertical-align:middle;"
! Distribution
! Package
|-
| style="vertical-align:middle;" | Debian/Ubuntu
| <code>libchromaprint-tools</code>
|-
| style="vertical-align:middle;" | Fedora/CentOS
| <code>chromaprint-tools</code>
|-
| style="vertical-align:middle;" | Arch
| <code>chromaprint</code>
|-
| style="vertical-align:middle;" | OpenSUSE
|<code> chromaprint-fpcalc</code>
|-
| style="vertical-align:middle;" | Synology
| <code>chromaprint</code>
|}

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=lidarr_system_status_health_system_warnings />

===== Readarr =====
<section begin=readarr_system_status_health_system_warnings />
*'''[[#branch_is_not_a_valid_release_branch|Branch is not a valid release branch]]'''
** The branch you have set is not a valid release branch. You will not receive updates. Please change to one of the current release branches.

* '''[[#update_to_net_core_version|Update to .NET Core version]]'''
** Newer versions of Readarr are targeted for .NET Core. We provide legacy mono builds for those platforms that cannot use .NET Core. You are running one of these legacy builds but your platform supports .NET Core.
** Fixing Docker installs
*** Re-pull your container
** Fixing Standalone installs
***'''Back-Up your existing configuration''' before the next step.
*** This should only happen on Linux hosts. '''Do not install .net core runtime or SDK from microsoft.''' To remedy, download the correct build for your architecture. Please note that the links are for the <code>master</code> branch. If you are on <code>develop</code> or <code>nightly</code> you'll need to adjust <code>/master/</code> in the URL.
***'''Delete your existing binaries (contents or folder of /opt/Readarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.
***'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES. YOU MUST DELETE THE OLD ONES FIRST'''.
****<code>wget --content-disposition <nowiki>'http://readarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'</nowiki></code> Download the .net binaries. The example is for a x64 (AMD64) installation.
***** For most users, this would be <code>.linux-core-x64.tar.gz</code> selected via <code>arch=x64</code> in the url. For ARM use <code>arch=arm</code> and for ARM64 use <code>arch=arm64</code>
****<code> sudo systemctl stop readarr</code> Stop Readarr
****<code> sudo mv /opt/Readarr /opt/Readarr.old</code> Backup the old Binaries
****<code> tar -xvzf Readarr*.linux-core-x64.tar.gz</code> Extract the Readarr Tarball
****<code> sudo mv Readarr/ /opt</code> Move the new Readarr Binaries
****<code> sudo chown -R readarr:readarr /opt/Readarr</code> Ensure Readarr has permissions to its directory, this assumes it runs as the user <code>readarr</code>
****<code> sudo rm -rf /opt/Readarr.old</code> Remove the old binaries
****<code> sudo rm -rf Readarr*.linux-core-x64.tar.gz</code> Remove the Tarball
**** Update your startup script (<code> sudo nano -e /etc/systemd/system/readarr.service</code>) to call <code>Readarr</code> instead of calling it with mono like <code>mono --debug Readarr.exe</code>. In other words you want, as an example, <code>/opt/Readarr/Readarr</code> and '''not''' <code>mono --debug /opt/Readarr/Readarr</code>.
***** If Readarr doesn’t start, ensure you have [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux the dependencies listed here] installed.
****<code> systemctl daemon-reload</code> Reload the Systemd Files
****<code> sudo systemctl start readarr.service</code> Restart Readarr

*'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''
** Readarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.
** See "Update to .NET Core version above"

*'''[[#new_update_is_available|New update is available]]'''
** Rejoice, the developers have released a new update. This generally means awesome new features and squashed piles of bugs (right?). Apparently you don’t have Auto-Updating enabled, so you’ll have to figure out how to update on your platform. Pressing the Install button on the System -> Updates page is probably a good starting point.
**''(This warning will not appear if your current version is less than 14 days old)''

*'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

*'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''
** The update branch setup in Settings/General is for a previous version of Lidarr, therefore the instance will not see correct update information in the System/Updates feed and may not receive new updates when released.

*'''[[#Could_not_connect_to_signalr|Could not connect to signalR]]'''
** signalR drives the dynamic UI updates, so if your browser cannot connect to signalR on your server you won’t see any real time updates in the UI.
** The most common occurrence of this is use of a reverse proxy or cloudflare
** Cloudflare needs websockets enabled.
** Nginx requires the following addition to the location block for the app:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
** Make sure you '''do not''' include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. '''THIS WILL NOT WORK'''
** See https://github.com/aspnet/AspNetCore/issues/17081
** For Apache2 reverse proxy, you need to enable the following modules: <code>proxy</code>, <code>proxy_http</code>, and <code>proxy_wstunnel</code>. Then, add this websocket tunnel directive to your vhost configuration:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:8787/$1 [P,L]

*'''[[#proxy_failed_resolve_ip|Failed to resolve the IP Address for the Configured Proxy Host]]'''
** Review your proxy settings and ensure they are accurate
** Ensure your proxy is up, running, and accessible

*'''[[#proxy_failed_test|Proxy Failed Test]]'''
** Your configured proxy failed to test successfully, review the HTTP error provided and/or check logs for more details.

*'''[[#system_time_off|System Time is off by more than 1 day]]'''
** System time is off by more than 1 day. Scheduled tasks may not run correctly until the time is corrected
** Review your system time and ensure it is synced to an authoritative time server and accurate

*'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''
** MediaInfo Library could not be loaded.

*'''[[#mono_tls_legacy|Mono Legacy TLS enabled]]'''
** Mono 4.x tls workaround still enabled, consider removing MONO_TLS_PROVIDER=legacy environment option

<section end=readarr_system_status_health_system_warnings />

==== Download Clients ====
===== Radarr =====
<section begin=radarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Radarr to be able to download media. Since Radarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Radarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Radarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Radarr.
*** Ensure SSL encryption is not turned on if you're using both your Radarr instance and your download client on a local network. See [[Radarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Radarr. Therefore Radarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Radarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Radarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Radarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Radarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Radarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Radarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

[https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Radarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#permissions_error|Permissions Error]]'''
** Radarr or the user radarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end=radarr_system_status_health_download_clients />

===== Sonarr =====
<section begin=sonarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Sonarr to be able to download media. Since Sonarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Sonarr.
*** Ensure SSL encryption is not turned on if you're using both your Sonarr instance and your download client on a local network. See [[Sonarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Sonarr. Therefore Sonarr has decided to temporarily stop querying the download client on it's normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Sonarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Sonarr to prevent the errors.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Sonarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Sonarr/V3/Sonarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* '''[[#permissions_error|Permissions Error]]'''
** Sonarr or the user sonarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end="sonarr_system_status_health_download_clients" />

===== Lidarr =====
<section begin=lidarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Lidarr to be able to download media. Since Lidarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Lidarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Lidarr.
*** Ensure SSL encryption is not turned on if you're using both your Lidarr instance and your download client on a local network. See [[Lidarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Lidarr. Therefore Lidarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Lidarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Lidarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Lidarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished song is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Lidarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Lidarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/audio</code> and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/audio</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Lidarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* '''[[#permissions_error|Permissions Error]]'''
** Lidarr or the user lidarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=lidarr_system_status_health_download_clients />
===== Readarr =====
<section begin=readarr_system_status_health_download_clients />
* '''[[#no_download_client_is_available|No download client is available]]'''
** A properly configured and enabled download client is required for Readarr to be able to download media. Since Readarr supports different download clients, you should determine which best matches your requirements. If you already have a download client installed, you should configure Lidarr to use it and create a category. See Settings -> Download Client.

* '''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''
** Readarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
** This is typically due to improperly configured download client. Things you can typically check:
*** Your download clients IP Address if its on the same bare metal machine this is typically <code>127.0.0.1</code>
*** The Port number of that your download client is using these are filled out with the default port number but if you've changed it you'll need to have the same one entered into Readarr.
*** Ensure SSL encryption is not turned on if you're using both your Readarr instance and your download client on a local network. See [[Readarr FAQ#Invalid Certificate and other HTTPS or SSL issues|the SSL FAQ entry]] for more information.

* '''[[#download_clients_are_unavailable_due_to_failures|Download clients are unavailable due to failure]]'''
** One or more of your download clients is not responding to requests made by Readarr. Therefore Readarr has decided to temporarily stop querying the download client on it’s normal 1 minute cycle, which is normally used to track active downloads and import finished ones. However, Readarr will continue to attempt to send downloads to the client, but will in all likeliness fail.
** You should inspect System->Logs to see what the reason is for the failures.
** If you no longer use this download client, disable it in Readarr to prevent the errors.

* '''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''
** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* '''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''
** This error is typically associated with bad docker paths within either your download client or Readarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Readarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished book is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Readarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Readarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/books</code> and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/books</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* '''[[#downloads_in_root_folder|Downloading into Root Folder]]'''
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Readarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* '''[[#bad_download_client_settings|Bad Download Client Settings]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* '''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* '''[[#permissions_error|Permissions Error]]'''
** Readarr or the user readarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* '''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* '''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=readarr_system_status_health_download_clients />

==== Completed/Failed Download Handling ====
===== Radarr =====
<section begin=radarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=radarr_system_status_health_complete_failed_download_handling />

===== Sonarr =====
<section begin=sonarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the
<section end=sonarr_system_status_health_complete_failed_download_handling />

===== Lidarr =====
<section begin=lidarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidrr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=lidarr_system_status_health_complete_failed_download_handling />

===== Readarr =====
<section begin=readarr_system_status_health_complete_failed_download_handling />
* '''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=readarr_system_status_health_complete_failed_download_handling />

==== Indexers ====
===== Radarr =====
<section begin=radarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_radarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Radarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_radarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Radarr will not grab new releases automatically]]'''
** So Radarr uses the RSS feed to pick up new releases as they come along. More info on that [[Radarr FAQ#How does Radarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Radarr will only be able to find new releases via the RSS feeds. But searching for movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=radarr_system_status_health_indexers />

===== Sonarr =====
<section begin=sonarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_sonarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Sonarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_sonarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Sonarr will not grab new releases automatically]]'''
** So Sonarr uses the RSS feed to pick up new releases as they come along. More info on that [[Sonarr FAQ#How does Sonarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''
** None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=sonarr_system_status_health_indexers />
===== Lidarr =====
<section begin=lidarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Lidarr will not grab new releases automatically]]'''
** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for music (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=lidarr_system_status_health_indexers />
===== Readarr =====
<section begin=readarr_system_status_health_indexers />
* '''[[#no_indexers_available_with_automatic_search_enabled_readarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Readarr will not provide any automatic search results]]'''
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*'''[[#no_indexers_available_with_rss_sync_enabled_readarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Readarr will not grab new releases automatically]]'''
** So Readarr uses the RSS feed to pick up new releases as they come along. More info on that [[Readarr FAQ#How does Readarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* '''[[#no_indexers_are_enabled|No indexers are enabled]]'''
** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]
* '''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' 
** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for books (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* '''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' 
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* '''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''
** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=readarr_system_status_health_indexers />

==== Folders ====
===== Radarr =====
<section begin=radarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder
***# Easiest way to find this is to go to the Movies (Library) Tab
***# Create a custom filter with the old root folder path
***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files
<section end=radarr_system_status_health_folders />
===== Sonarr =====
<section begin=sonarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder
***# Go to the Series > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these series to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files
* '''[[#import_list_missing_root_folder|Import List missing root folder]]'''
** This error is typically identified if a list is looking for a root folder but that root folder is no longer available.
**#Go to Settings > Import Lists
**#Edit the import lists that were mentioned in the health check
**#Save
<section end=sonarr_system_status_health_folders />
===== Lidarr =====
<section begin=lidarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these artists to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files
<section end=lidarr_system_status_health_folders />
===== Readarr =====
<section begin=readarr_system_status_health_folders />
* '''[[#missing_root_folder|Missing root folder]]'''
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these authors to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files
<section end=readarr_system_status_health_folders />

==== Media ====
===== Radarr =====
<section begin=radarr_system_status_health_media />
* '''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''
** The movie is linked to a TMDb Id that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It. 
** You can find and edit deleted movies by creating a custom filter using the following steps: 1. Click Movies from the left menu 2. Click the dropdown on Filter and select “Custom Filter” 3. Enter a label, for example “Deleted Movies” 4. Make the filter as follows: Status is Deleted 5. Click save and select the newly created filter from the filter dropdown menu

* '''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''
** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.
<section end=radarr_system_status_health_media />
===== Sonarr =====
<section begin=sonarr_system_status_health_media />
* '''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''
** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.
<section end=sonarr_system_status_health_media />
===== Lidarr =====
<section begin=lidarr_system_status_health_media />
Text
<section end=lidarr_system_status_health_media />
===== Readarr =====
<section begin=readarr_system_status_health_media />
Text
<section end=readarr_system_status_health_media />

=== Disk Space ===
==== Radarr ====
<section begin=radarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=radarr_system_status_disk_space />
==== Sonarr ====
<section begin=sonarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=sonarr_system_status_disk_space />
==== Lidarr ====
<section begin=lidarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=lidarr_system_status_disk_space />
==== Readarr ====
<section begin=readarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=readarr_system_status_disk_space />

=== About ===
==== Radarr ====
<section begin=radarr_system_status_about />
This will tell you about your current install of Radarr
<section end=radarr_system_status_about />
==== Sonarr ====
<section begin=sonarr_system_status_about />
This will tell you about your current install of Radarr
<section end=sonarr_system_status_about />
==== Lidarr ====
<section begin=lidarr_system_status_about />
This will tell you about your current install of Lidarr
<section end=lidarr_system_status_about />
==== Readarr ====
<section begin=readarr_system_status_about />
This will tell you about your current install of Readarr
<section end=readarr_system_status_about />

=== More Info ===
==== Radarr ====
<section begin=radarr_system_status_more_info />
* Home Page: [https://radarr.video Radarr's home page]
* Wiki: [https://wiki.servarr.com/Radarr You're here already]
* Reddit: [https://reddit.com/r/radarr r/radarr]
* Discord: [https://radarr.video/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/radarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Radarr/Radarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]
<section end=radarr_system_status_more_info />
==== Sonarr ====
<section begin=sonarr_system_status_more_info />
* Home page: [https://sonarr.tv Sonarr's home page]
* Forums: [https://forums.sonarr.tv Sonarr Forums]
* Discord: [https://discord.gg/M6BvZn5 Join our discord]
* Reddit: [https://reddit.com/r/sonarr r/sonarr]
* Twitter: [https://twitter.com/sonarrtv @sonarrtv]
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]
* Wiki: [https://wiki.servarr.com/sonarr You're here already]
* Donations: If you're feeling generous and would like to donate [https://sonarr.tv/donate click here]
* Source: https://github.com/Sonarr/Sonarr Github]
* Feature Requests: Got a great idea drop it on Github [https://github.com/Sonarr/Sonarr/issues here]
<section end=sonarr_system_status_more_info />
==== Lidarr ====
<section begin=lidarr_system_status_more_info />
* Home page: [https://lidarr.audio Lidarr's home page]
* Wiki: [https://wiki.servarr.com/Lidarr You're here already]
* Reddit: [https://reddit.com/r/lidarr r/lidarr]
* Discord: [https://lidarr.audio/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/lidarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/lidarr/Lidarr/ Github]
* Feature Requests: Got a great idea drop it on GitHub [https://github.com/Lidarr/Lidarr/issues here]
<section end=lidarr_system_status_more_info />
==== Readarr ====
<section begin=readarr_system_status_more_info />
* Home page: [https://readarr.com Readarr's home page]
* Wiki: [https://wiki.servarr.com/Readarr You're here already]
* Reddit: [https://reddit.com/r/readarr r/readarr]
* Discord: [https://readarr.com/discord Join our discord]
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Readarr/Readarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Readarr/Readarr/issues click here]
<section end=readarr_system_status_more_info />

=== Templates ===