<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wikiold.servarr.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Drazzilb</id>
	<title>Servarr - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wikiold.servarr.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Drazzilb"/>
	<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/Special:Contributions/Drazzilb"/>
	<updated>2026-06-04T17:00:02Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.2</generator>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Definitions&amp;diff=3272</id>
		<title>Definitions</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Definitions&amp;diff=3272"/>
		<updated>2021-03-01T14:16:27Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Supported Flags */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Download Protocols ===&lt;br /&gt;
* &amp;lt;code&amp;gt;Usenet&amp;lt;/code&amp;gt; - (USEr NETwork) A public access network on the Internet that provides group discussions and group email. It is a giant, dispersed bulletin board that is maintained by volunteers who provide news and mail feeds to other nodes. All Usenet content is &amp;quot;NetNews,&amp;quot; and a running collection of messages about a subject is a &amp;quot;newsgroup.&amp;quot;&lt;br /&gt;
:'''Note:''' This is typically a paid service with a direct connection to the servers containing the data you're wishing to acquire. The connections can be quite fast and typically can saturate any home download connection. &amp;lt;br&amp;gt; For more information about Usenet and discussions about them we'd recommend you look at [https://www.reddit.com/r/usenet/ r/usenet]&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;Torrents&amp;lt;/code&amp;gt; - In the BitTorrent file distribution system, a torrent file or meta-info file is a computer file that contains metadata about files and folders to be distributed, and usually also a list of the network locations of trackers, which are computers that help participants in the system find each other and form efficient distribution groups called swarms. A torrent file acts like a table of contents (index) that allows computers to find information through the use of a Bittorrent client. A torrent file gives addresses identifying computers that can send parts of the requested file.&lt;br /&gt;
:'''Note:''' Torrents in of them selves are completely innocuous and is simply a file sharing system. To share a file between two people is free. However, the service for finding the files (Trackers) and the computers that are hosting them can lead to a cost however there are may Trackers that are completely free to use. Torrent speeds are limited to the amount of seeders in a swarm. &amp;lt;br&amp;gt; For more information about Torrents and discussions about them we'd recommend you look at [https://www.reddit.com/r/torrents/ r/torrents]&lt;br /&gt;
&lt;br /&gt;
=== Indexers/Trackers ===&lt;br /&gt;
==== Usenet ====&lt;br /&gt;
* &amp;lt;code&amp;gt;Indexers&amp;lt;/code&amp;gt; - Usenet indexing sites allow you to search Usenet for specific posts. Some display the newsgroup and full subjects of each post matching the search criteria. Others allow you to download an NZB file which contains information about each post that your download client can use to automatically download the files. Indexes typically have a fee (usually to help cover server costs)that is typically paid yearly (some have an unlimited membership). &amp;lt;br&amp;gt; For more information about Indexers and discussions about them we'd recommend you look at  [https://reddit.com/r/indexers r/indexers]&lt;br /&gt;
&lt;br /&gt;
==== Torrents ====&lt;br /&gt;
* &amp;lt;code&amp;gt;Trackers&amp;lt;/code&amp;gt; - Torrent trackers are servers that keep track of the peers who are available at the moment to offer you the requested files. These are a special type of servers that help in better communication between torrent clients and peers to speed up downloads.&lt;br /&gt;
** &amp;lt;code&amp;gt;Seeders&amp;lt;/code&amp;gt; - Seeders are people who have a complete copy of the file. Seeders are only uploading because they already have the file finished, so there's no reason to download it.&lt;br /&gt;
** &amp;lt;code&amp;gt;Leechers&amp;lt;/code&amp;gt; - Leechers are people with an incomplete copy of the file. Due to the nature of torrents, you are always sharing the part of the file that you have downloaded. So you are always uploading to others while you download the file yourself.&lt;br /&gt;
** &amp;lt;code&amp;gt;Ratio&amp;lt;/code&amp;gt; - The ratio of what you have uploaded versus downloaded. Calculated as uploaded quantity / downloaded quantity.&lt;br /&gt;
&lt;br /&gt;
=== Seedboxes ===&lt;br /&gt;
&lt;br /&gt;
=== Common File Containers ===&lt;br /&gt;
*&amp;lt;code&amp;gt;MKV&amp;lt;/code&amp;gt; - An MKV file is a video file saved in the Matroska multimedia container format. It supports several types of audio and video codecs and may include .SRT, .SSA, .USF (Universal Subtitle Format), or VobSub subtitles. MKV files are typically used for storing short video clips, TV shows, and movies.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;MP4&amp;lt;/code&amp;gt; - An MP4 file is a multimedia file commonly used to store a movie or video clip. It may also contain subtitles or images. MP4 is short for MPEG-4 Part 14, which is a container format based on the QuickTime File Format (QTFF) used by .MOV and .QT files&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3&amp;lt;/code&amp;gt; - An MP3 file is an audio file saved in a compressed audio format developed by the Moving Picture Experts Group (MPEG) that uses &amp;quot;Layer 3&amp;quot; audio compression (MP3). It is most commonly used to store music, but may also contain other types of audio content, such as a lecture, sermon, audiobook, or podcast.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;AAC&amp;lt;/code&amp;gt; - Compressed audio file similar to an .MP3 file, but offers several performance improvements; examples include a higher coding efficiency for both stationary and transient signals, a simpler filterbank, and better handling of frequencies above 16 kHz; maintains quality nearly indistinguishable from the original audio source.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;OGG&amp;lt;/code&amp;gt; - An OGG file is a compressed audio file that uses free, unpatented Ogg Vorbis audio compression. It is similar to an .MP3 file, but sounds better than an MP3 file of equal size, and may include song metadata, such as artist information and track data. OGG files are supported by many software music players and some portable music players.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;FLAC&amp;lt;/code&amp;gt; - A FLAC file is an audio file compressed in the Free Lossless Audio Codec (FLAC) format, which is an open source lossless audio compression format. It is similar to an .MP3 file, but is compressed without any loss in quality or loss of any original audio data.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For a list of different video containers and its capabilities click [https://en.wikipedia.org/wiki/Comparison_of_video_container_formats#Video_coding_formats_support HERE]&lt;br /&gt;
&lt;br /&gt;
For a list of different audio containers and its capabilities click &lt;br /&gt;
[https://en.wikipedia.org/wiki/Comparison_of_video_container_formats#Audio_coding_formats_support HERE]&lt;br /&gt;
&lt;br /&gt;
=== Bitrates ===&lt;br /&gt;
&amp;lt;section begin=bitrates /&amp;gt;&lt;br /&gt;
Bitrate, as the name implies, describes the rate at which bits are transferred from one location to another. In other words, it measures how much data is transmitted in a given amount of time. Bitrate is commonly measured in bits per second (bps), kilobits per second (Kbps), or megabits per second (Mbps). For example, a DSL connection may be able to download data at 768 kbps, while a Firewire 800 connection can transfer data up to 800 Mbps.&lt;br /&gt;
&lt;br /&gt;
Bitrate can also describe the quality of an audio or video file. For example, an MP3 audio file that is compressed at 192 Kbps will have a greater dynamic range and may sound slightly more clear than the same audio file compressed at 128 Kbps. This is because more bits are used to represent the audio data for each second of playback. Similarly, a video file that is compressed at 3000 Kbps will look better than the same file compressed at 1000 Kbps. Just like the quality of an image is measured in resolution, the quality of an audio or video file is measured by the bitrate.&lt;br /&gt;
&amp;lt;section end=bitrates  /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Scene Naming ===&lt;br /&gt;
&amp;lt;section begin=scene naming /&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;PROPER&amp;lt;/code&amp;gt; - means there was a problem with the previous release. Downloads tagged as PROPER shows that the problems have been fixed in that release. This is done by a Group that did not release the original.&lt;br /&gt;
* &amp;lt;code&amp;gt;REPACK&amp;lt;/code&amp;gt; -  means there was a problem with the previous release and is corrected by the original Group. Downloads tagged as REPACK shows that the problems have been fixed in that release. This is done by a Group that did release the original.&lt;br /&gt;
&amp;lt;section end=scene naming /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Qualities ===&lt;br /&gt;
==== Video Qualities ====&lt;br /&gt;
&amp;lt;section begin=video-qualities /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=Unknown /&amp;gt;*&amp;lt;code&amp;gt;Unknown&amp;lt;/code&amp;gt; - Self Explanatory&amp;lt;section end=Unknown /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;WORKPRINT&amp;lt;/code&amp;gt; - A workprint of a film generally contains timecode and usually has watermarks from the studio involved in the production of the film. These &amp;quot;proxy&amp;quot; copies of a film often go between the editorial and visual effects departments of the film crew. A workprint may be of any resolution, but are generally lower quality versions of the film used to show progress on the editorial or post-production process. Therefore, these may not be at all the same as a theatrical version of the film, and may be missing many of the visual effects or audio that end up making it to the theatrical release.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;CAM&amp;lt;/code&amp;gt; - is a theater rip usually done with a digital video camera. A mini tripod is sometimes used, but a lot of the time this won't be feasible, so the camera may shake. Seating placement isn't always ideal, and it might be filmed from an awkward angle. If cropped properly, this is hard to tell unless there's text on the screen, but a lot of times these are left with triangular borders on the top and bottom of the screen. Sound is taken from the onboard microphone of the camera, and especially in comedies, laughter can often be heard during the film. Due to these factors picture and sound quality are usually quite poor, but sometimes we're lucky, and the theater will be fairly empty and a fairly clear signal will be heard.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;TELESYNC&amp;lt;/code&amp;gt; - is the same spec as a CAM except it uses an external audio source (most likely an audio jack in the chair for the disabled). A direct audio source does not guarantee good quality audio, as a lot of background noise can interfere. Sometimes a telesync is filmed in an empty cinema or from the projection booth with a professional camera, giving better picture quality. Quality ranges drastically. A high percentage of telesyncs are CAMs that have been mislabeled.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;TELECINE&amp;lt;/code&amp;gt; - A telecine machine copies the film digitally from the reels. Sound and picture should be very good, but due to the equipment and cost involved telecines are fairly uncommon. Generally, the film will be in correct aspect ratio, although 4:3 telecines have existed. TC should not be confused with TimeCode, which is a visible counter on screen throughout the film.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;section begin=REGIONAL /&amp;gt;&amp;lt;code&amp;gt;REGIONAL&amp;lt;/code&amp;gt; - &amp;lt;--------------------- Needs definition&amp;lt;section end=REGIONAL /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;DVDSCR&amp;lt;/code&amp;gt; - A pre-release DVD often sent to awards judges and various other places for promotional use. A screener is supplied on a DVD or other large enough media. The main draw back is a “ticker” (a message that scrolls past at the bottom of the screen, with the copyright and anti-copy telephone number). Also, if the screener contains any serial numbers, or any other markings that could lead to the source of the tape, these will have to be blocked, usually with a black mark over the section. This is sometimes only for a few seconds, but unfortunately on some copies this will last for the entire film, and some can be quite big. Depending on the equipment used, screener quality can range from excellent to very poor. Usually transferred to SVCD, DivX/XviD, or MP4.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=SDTV /&amp;gt;*&amp;lt;code&amp;gt;SDTV&amp;lt;/code&amp;gt; - Post air rips from an analog source (usually cable television or OTA standard definition). The image quality is generally good (for the resolution) and they are usually encoded in DivX/XviD or MP4.&amp;lt;section end=SDTV /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=DVD /&amp;gt;*&amp;lt;code&amp;gt;DVD&amp;lt;/code&amp;gt; - A re-encode of the final released DVD9. If possible this is released PRE retail. It should be excellent quality (for the resolution). DVDrips are usually released in DivX/XviD or MP4.&amp;lt;section end=DVD /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;DVD-R&amp;lt;/code&amp;gt; - Same as DVD, but re-compressed to fit a single-layer DVD (generally reduces the original source bitrate by half, so the source material may have already been compressed from the original DVD copy and has been compressed a third time by the ripper).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=WEBDL-480p /&amp;gt;*&amp;lt;code&amp;gt;WEBDL-480p&amp;lt;/code&amp;gt; - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 480p (SD) quality. &amp;lt;section end=WEBDL-480p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=WEBRip-480p /&amp;gt;*&amp;lt;code&amp;gt;WEBRip-480p&amp;lt;/code&amp;gt; - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 480p (SD) quality.&amp;lt;section end=WEBRip-480p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=Bluray-480p /&amp;gt;*&amp;lt;code&amp;gt;Bluray-480p&amp;lt;/code&amp;gt; - A re-encode of the final released Blu-ray, downscaled to 480p resolution (720x480 @ 16:9, any other Aspect Ratio may be a different resolution). If possible this is released PRE retail. It should be excellent quality for the resolution. Bitrates may vary, but these are generally encoded to DivX, XviD, or AVC and offer the tradeoff of a small perceived quality reduction over the original source while drastically reducing filesize. These are generally MKV or MP4, but some DivX/XviD are around as well which use AVI.&amp;lt;section end=Bluray-480p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;Bluray-576p&amp;lt;/code&amp;gt; - Same as Bluray-480p, but in 576p (720x576). 576p is the standard PAL resolution for SDTV (although some manufacturers represent HDTV as anything above 480p, 576p offers barely any perceived quality increase over 480p). Bitrates may vary, but these are generally encoded to AVC or HEVC and offer the tradeoff of a small perceived quality reduction over the original source while drastically reducing filesize. These are generally MKV or MP4 container.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=HDTV-720p /&amp;gt;*&amp;lt;code&amp;gt;HDTV-720p&amp;lt;/code&amp;gt; - A re-encode of the final released Blu-ray, but broadcast over HD cable or satellite (1280x720 @ 16:9, any other aspect ratio may be a different resolution). It may be modified for runtime or content depending on the network it came from. This is released usually several months after a retail release, but sometimes upscaled versions of a Standard Definition film are released on cable channels such as STARZ or HBO, and they would be the only HD copies of that specific film available. These are generally MKV or MP4.&amp;lt;section end=HDTV-720p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;WEBDL-720p&amp;lt;/code&amp;gt; - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 720p quality.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=WEBRip-720p /&amp;gt;*&amp;lt;code&amp;gt;WEBRip-720p&amp;lt;/code&amp;gt; - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 720p quality.&amp;lt;section end=WEBRip-720p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=Bluray-720p /&amp;gt;*&amp;lt;code&amp;gt;Bluray-720p&amp;lt;/code&amp;gt; - A re-encode of the final released Blu-ray, downscaled to 720p resolution (1280x720 @ 16:9, any other aspect ratio may be a different resolution). If possible this is released PRE retail. It should be excellent quality for the resolution. Bitrates may vary, but these are generally encoded to AVC or HEVC and offer the tradeoff of a small perceived quality reduction over the original source while drastically reducing filesize. These are generally MKV or MP4 container.&amp;lt;section end=Bluray-720p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=HDTV-1080p /&amp;gt;*&amp;lt;code&amp;gt;HDTV-1080p&amp;lt;/code&amp;gt; - A re-encode of the final released Blu-ray, but broadcast over HD cable or satellite (1920x1080 @ 16:9, any other aspect ratio may be a different resolution). It may be modified for runtime or content depending on the network it came from. This is released usually several months after a retail release, but sometimes upscaled versions of a Standard Definition film are released on cable channels such as STARZ or HBO, and they would be the only HD copies of that specific film available. These are generally MKV or MP4 container.&amp;lt;section end=HDTV-1080p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=WEBDL-1080p /&amp;gt;*&amp;lt;code&amp;gt;WEBDL-1080p&amp;lt;/code&amp;gt; - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 1080p quality.&amp;lt;section end=WEBDL-1080p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=WEBRip-1080p /&amp;gt;*&amp;lt;code&amp;gt;WEBRip-1080p&amp;lt;/code&amp;gt; - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 1080p quality.&amp;lt;section end=WEBRip-1080p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=Bluray-1080p /&amp;gt;*&amp;lt;code&amp;gt;Bluray-1080p&amp;lt;/code&amp;gt; - A re-encode of the final released Blu-ray, at its native 1080p resolution (1920x1080 @ 16:9, any other aspect ratio may be a different resolution). If possible this is released PRE retail. It should be excellent quality and the same resolution as the source. Bitrates may vary, but these are generally encoded to AVC or HEVC and offer the tradeoff of a small perceived quality reduction over the original source while slightly reducing filesize. These are generally MKV or MP4 container.&amp;lt;section end=Bluray-1080p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=1080p Remux /&amp;gt;*&amp;lt;code&amp;gt;Remux-1080p&amp;lt;/code&amp;gt; - A remux is a rip of a Blu-ray or HD DVD disc to another container format or just stripping the disc of menus and bonus material while keeping the contents of its audio and video streams intact (also keeping the current codecs), guaranteeing the exact 1:1 movie quality as on original disc. This is at 1080p quality.&amp;lt;section end=1080p Remux /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=HDTV-2160p /&amp;gt;*&amp;lt;code&amp;gt;HDTV-2160p&amp;lt;/code&amp;gt; - TVRip is a capture source from an capture card.  HDTV stands for captured source from HD television. With an HDTV source, the quality can sometimes even surpass DVD. Movies in this format are starting to grow in popularity. Some advertisement and commercial banner can be seen on some releases during playback. This is at 2160p (4K) quality.&amp;lt;section end=HDTV-2160p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=WEBDL-2160p /&amp;gt;*&amp;lt;code&amp;gt;WEBDL-2160p&amp;lt;/code&amp;gt; - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 2160p (4K) quality.&amp;lt;section end=WEBDL-2160p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=WEBRip-2160p /&amp;gt;*&amp;lt;code&amp;gt;WEBRip-2160p&amp;lt;/code&amp;gt; - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 2160p (4k) quality.&amp;lt;section end=WEBRip-2160p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=Bluray-2160p /&amp;gt;*&amp;lt;code&amp;gt;Bluray-2160p&amp;lt;/code&amp;gt; - A re-encode of the final released Blu-ray, at its native 21600p resolution (3840x2160 @ 16:9, any other aspect ratio may be a different resolution). 4K versions of films that are released in generally HEVC codec and could be either 8-bit or 10-bit color reproduction or from an HDR source. slightly reducing filesize. These are generally MKV or MP4 container.&amp;lt;section end=Bluray-2160p /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section begin=2160p-Remux /&amp;gt;*&amp;lt;code&amp;gt;Remux-2160p&amp;lt;/code&amp;gt; - A remux is a rip of a Blu-ray or HD DVD disc to another container format or just stripping the disc of menus and bonus material while keeping the contents of its audio and video streams intact (also keeping the current codecs), guaranteeing the exact 1:1 movie quality as on original disc. This is at 2160p (4K) quality.&amp;lt;section end=2160p-Remux /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;code&amp;gt;BR-DISK&amp;lt;/code&amp;gt; - The original Blu-ray disc, with it's AVC/HEVC folder structure and no change in container format. Some media players are unable to deal with these, but they are generally used for archival purposes. The original Blu-ray disc content is unmodified. Most of the time, these have been run through an HDCP decryption process already via the ripper. Sometimes they are still encrypted.&lt;br /&gt;
&amp;lt;section end=video-qualities /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Audio Qualities ====&lt;br /&gt;
&amp;lt;section begin=audio-qualities /&amp;gt;&lt;br /&gt;
*&amp;lt;code&amp;gt;AAC-192&amp;lt;/code&amp;gt; - An AAC file with a 192 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;AAC-256&amp;lt;/code&amp;gt; - An AAC file with a 256 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;AAC-320&amp;lt;/code&amp;gt; - An AAC file with a 320 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;AAC-VBR&amp;lt;/code&amp;gt; - An AAC file with a variable bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;ALAC&amp;lt;/code&amp;gt; - Audio file created with the Apple Lossless Audio Codec (ALAC); used for storing digital music losslessly without losing any sound quality from the original audio data; differs from lossy audio codecs such as AAC.&lt;br /&gt;
*&amp;lt;code&amp;gt;APE&amp;lt;/code&amp;gt; - Audio file compressed using Monkey's Audio lossless compression algorithm; includes error detection and support for tags that store information about audio files; sometimes created with .CUE files to comprise an audio CD image.&lt;br /&gt;
&amp;lt;section begin=FLAC /&amp;gt;*&amp;lt;code&amp;gt;FLAC&amp;lt;/code&amp;gt; - A FLAC file is an audio file compressed in the Free Lossless Audio Codec (FLAC) format, which is an open source lossless audio compression format. It is similar to a .MP3 file, but is compressed without any loss in quality or loss of any original audio data.&amp;lt;section end=FLAC /&amp;gt;&lt;br /&gt;
*&amp;lt;code&amp;gt;FLAC 24bit&amp;lt;/code&amp;gt; - A FLAC file with 24-bit encoding, allowing a much wider dynamic range than CD, and sampling rates all the way up to 192kHz&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-8&amp;lt;/code&amp;gt; - A MP3 file with a 8 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-16&amp;lt;/code&amp;gt; - A MP3 file with a 16 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-24&amp;lt;/code&amp;gt; - A MP3 file with a 24 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-32&amp;lt;/code&amp;gt; - A MP3 file with a 32 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-40&amp;lt;/code&amp;gt; - A MP3 file with a 40 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-48&amp;lt;/code&amp;gt; - A MP3 file with a 48 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-56&amp;lt;/code&amp;gt; - A MP3 file with a 56 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-64&amp;lt;/code&amp;gt; - A MP3 file with a 64 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-80&amp;lt;/code&amp;gt; - A MP3 file with a 80 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-96&amp;lt;/code&amp;gt; - A MP3 file with a 96 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-112&amp;lt;/code&amp;gt; - A MP3 file with a 112 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-128&amp;lt;/code&amp;gt; - A MP3 file with a 128 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-160&amp;lt;/code&amp;gt; - A MP3 file with a 160 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-192&amp;lt;/code&amp;gt; - A MP3 file with a 192 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-224&amp;lt;/code&amp;gt; - A MP3 file with a 224 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-256&amp;lt;/code&amp;gt; - A MP3 file with a 256 kbps bitrate&lt;br /&gt;
&amp;lt;section begin=MP3-320 /&amp;gt;*&amp;lt;code&amp;gt;MP3-320&amp;lt;/code&amp;gt; - An MP3 file with a 320 kbps bitrate&amp;lt;section end=MP3-320 /&amp;gt;&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-VBR-V0&amp;lt;/code&amp;gt; - An MP3 file with a variable bitrate (version 0)&lt;br /&gt;
*&amp;lt;code&amp;gt;MP3-VBR-V2&amp;lt;/code&amp;gt; - An MP3 file with a variable bitrate (version 2)&lt;br /&gt;
*&amp;lt;code&amp;gt;OGG Vorbis Q5&amp;lt;/code&amp;gt; - An OOG file with an 160 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;OGG Vorbis Q6&amp;lt;/code&amp;gt; - An OOG file with a 192 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;OGG Vorbis Q7&amp;lt;/code&amp;gt; - An OOG file with a 224 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;OGG Vorbis Q8&amp;lt;/code&amp;gt; - An OOG file with a 256 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;OGG Vorbis Q9&amp;lt;/code&amp;gt; - An OOG file with a 320 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;OGG Vorbis Q10&amp;lt;/code&amp;gt; - An OOG file with a 500 kbps bitrate&lt;br /&gt;
*&amp;lt;code&amp;gt;Unknown&amp;lt;/code&amp;gt; - Self Explanatory&lt;br /&gt;
*&amp;lt;code&amp;gt;WavPack&amp;lt;/code&amp;gt; - WavPack compresses high-quality audio to between thirty and seventy percent and supports both mono and stereo audio ranging from 8 to 32 bits. Typically these are audio files in an &amp;lt;code&amp;gt;.WV&amp;lt;/code&amp;gt; container&lt;br /&gt;
*&amp;lt;code&amp;gt;WAV&amp;lt;/code&amp;gt; - A WAV file is an audio file saved in the WAVE format, which is a standard digital audio file format utilized for storing waveform data. WAV files may contain audio recordings with different sampling rates and bitrates but are often saved in a 44.1 KHz, 16-bit, stereo format, which is the standard format used for CD audio.&lt;br /&gt;
*&amp;lt;code&amp;gt;WMA&amp;lt;/code&amp;gt; - A WMA file is an audio file saved in the Advanced Systems Format (ASF) proprietary format developed by Microsoft. It contains Windows Media Audio and metadata objects such as the title, artist, album, and genre of the track. WMA files are similar to .MP3 files and primarily used for streaming music from the web.&lt;br /&gt;
&amp;lt;section end=audio-qualities /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== eBook Qualities ====&lt;br /&gt;
&amp;lt;section begin=ebook-qualities /&amp;gt;&lt;br /&gt;
*&amp;lt;code&amp;gt;Unknown&amp;lt;/code&amp;gt; - Self Explanatory&lt;br /&gt;
*&amp;lt;code&amp;gt;PDF&amp;lt;/code&amp;gt; - A PDF file is a multi-platform document created by Adobe Acrobat or another PDF application. The PDF format is commonly used for saving documents and publications in a standard format that can be viewed on multiple platforms. In many cases, PDF files are created from existing documents instead of from scratch. With that being said PDF isn't a book format it is originally designed as a printing format so a lot of features you'll find with other formats will not be available.&lt;br /&gt;
*&amp;lt;code&amp;gt;MOBI&amp;lt;/code&amp;gt; - A MOBI file is an eBook saved in the MOBI format, a format originally used by the Mobipocket Reader but now supported by several different readers. It contains an eBook and may incorporate DRM copyright protection to prevent copying or unauthorized viewing. MOBI files are supported by various eReaders, tablets, PDAs, and desktop computer applications.&lt;br /&gt;
*&amp;lt;code&amp;gt;EPUB&amp;lt;/code&amp;gt; - An EPUB file is a digital ebook saved in the EPUB format, an open XML-based format for digital books and publications. It provides a standard digital publication format for publishers and consumers. EPUB files can be viewed with supporting software programs and hardware devices, such as the Amazon Kindle and Barnes &amp;amp; Noble NOOK.&lt;br /&gt;
*&amp;lt;code&amp;gt;AZW3&amp;lt;/code&amp;gt; - An AZW3 file is an eBook created in the Kindle Format 8 (KF8), Amazon's successor to the .AZW format. It supports newer features such as HTML5 and CSS3 support as well as many other formatting capabilities. AZW3 files often include DRM protection and are used as the download format for many Amazon eBooks.&lt;br /&gt;
&amp;lt;section end=ebook-qualities /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Indexer Flags ===&lt;br /&gt;
&lt;br /&gt;
Torrent Indexers sometimes have torrents that, while they contain the same video, have other attributes that differentiate them. In Radarr, these are called Indexer Flags and you can do some cool stuff with them. See the table below, for a list of available flags and what they signify.&lt;br /&gt;
&lt;br /&gt;
==== Uses ====&lt;br /&gt;
&lt;br /&gt;
Indexer Flags can be used for multiple things in Radarr. Under Settings -&amp;amp;gt; Indexers, you can e.g. specify that all releases with any indexer flag is preferred. This is useful, if you occasionally want to download a golden popcorn release over a normal encode.&lt;br /&gt;
&lt;br /&gt;
If you want more control over indexer flags, there are two other options:&lt;br /&gt;
&lt;br /&gt;
==== 1. Required Flags ====&lt;br /&gt;
&lt;br /&gt;
In your indexer settings, you can specify, what exact flags are required, for a release to be downloaded for this indexer. This allows you to have a strict indexer only download freeleech torrents as an example. To require an indexer flag, look at the table below, take the flag name and put it in the corresponding field in your indexer’s settings.&lt;br /&gt;
&lt;br /&gt;
==== 2. Custom Formats ====&lt;br /&gt;
&lt;br /&gt;
'''(Radarr Only)'''&lt;br /&gt;
Indexer Flags can be used as Format Tags in a Custom Format. Check out the [[Radarr Settings#Custom Formats|Custom Formats]] section for more information.&lt;br /&gt;
&lt;br /&gt;
==== Supported Flags ====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&lt;br /&gt;
!width=&amp;quot;33%&amp;quot;| Flag Name&lt;br /&gt;
!width=&amp;quot;33%&amp;quot;| Symbol&lt;br /&gt;
!width=&amp;quot;33%&amp;quot;| Description&lt;br /&gt;
|-&lt;br /&gt;
| G_Freeleech&lt;br /&gt;
| ⬇⬇&lt;br /&gt;
| Sometimes, torrent sites set a torrent to be freeleech. This means, that the download of this torrent will not count towards your download quota or ratio. This is really useful, if you do not have the best ratio yet.&lt;br /&gt;
|-&lt;br /&gt;
| G_Halfleech&lt;br /&gt;
| ⇩⇩&lt;br /&gt;
| Similar to G_Freeleech, G_Halfleech signifies that only half of the size of this torrent will count towards your download quota or ratio.&lt;br /&gt;
|-&lt;br /&gt;
| G_DoubleUpload&lt;br /&gt;
| ⬆&lt;br /&gt;
| Similar to G_Freeleech, G_DoubleUpload signifies that any amount of data you upload via seeding is counted twice towards your upload quota and ratio. This is very useful, if you want to build up a ratio buffer.&lt;br /&gt;
|-&lt;br /&gt;
| PTP_Golden&lt;br /&gt;
| 🌟&lt;br /&gt;
| On PassThePopcorn, some torrents are given the Golden tag, when they meet certain encoding standards. These are usually the best encodes, with almost no perceptible quality loss. You can learn more on their wiki page.&lt;br /&gt;
|-&lt;br /&gt;
| PTP_Approved&lt;br /&gt;
| ✔&lt;br /&gt;
| On PassThePopcorn, some torrents are approved, when they meet the minimum standards for encoding (e.g. no low bitrates). See their wiki for more information.&lt;br /&gt;
|-&lt;br /&gt;
| HDB_Internal&lt;br /&gt;
| 🚪&lt;br /&gt;
| Releases on HDBits receive this tag, when the release was uploaded by one of the release groups of HDBits themselves.&lt;br /&gt;
|-&lt;br /&gt;
| G_Scene&lt;br /&gt;
| ☠&lt;br /&gt;
| This flag is applied to releases that are reported to be from a scene release group by your indexer.&lt;br /&gt;
|-&lt;br /&gt;
| G_Freeleech75&lt;br /&gt;
| ⇩⬇&lt;br /&gt;
| Similar to G_Freeleech, G_Freeleech75 signifies that only 25% of the size of this torrent will count towards your download quota or ratio.&lt;br /&gt;
|-&lt;br /&gt;
| G_Freeleech25&lt;br /&gt;
| ⇩&lt;br /&gt;
| Similar to G_Freeleech, G_Freeleech25 signifies that only 75% of the size of this torrent will count towards your download quota or ratio.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=3071</id>
		<title>Template:Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=3071"/>
		<updated>2021-01-27T18:16:43Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to Contribute ==&lt;br /&gt;
&lt;br /&gt;
We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
Setup guides, FAQ, the more information we have on the [[{{{ARRNAME}}}|wiki]] the better please contact one of Team {{{ARRNAME}}} for assistance with getting set up with the wiki.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
&lt;br /&gt;
=== Tools required ===&lt;br /&gt;
:* Visual Studio 2019 or higher [https://www.visualstudio.com/vs/ VisualStudio].  The [https://www.visualstudio.com/downloads/ community version] is free and works.&lt;br /&gt;
:* HTML/Javascript editor of choice (VS Code/Sublime Text/Webstorm/Atom/etc)&lt;br /&gt;
:* [https://git-scm.com/downloads Git]&lt;br /&gt;
:* [https://nodejs.org/en/download/ NodeJS] (Node 10.X.X or higher)&lt;br /&gt;
:* [https://yarnpkg.com/ Yarn]&lt;br /&gt;
:* Net 5 SDK &lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
&lt;br /&gt;
# Fork {{{ARRNAME}}}&lt;br /&gt;
# Clone the repository into your development machine. [https://docs.github.com/en/free-pro-team@latest/github/getting-started-with-github *info*]&lt;br /&gt;
# Install the required Node Packages `yarn install`&lt;br /&gt;
# Start gulp to monitor your dev environment for any changes that need post processing using `yarn start` command.&lt;br /&gt;
# Build the project in Visual Studio, Setting startup project to `{{{ARRNAME}}}.Console` and framework to `netcoreapp31`&lt;br /&gt;
# Debug the project in Visual Studio&lt;br /&gt;
# Open http://localhost:{{{ARRPORT}}}&lt;br /&gt;
&lt;br /&gt;
=== Contributing Code ===&lt;br /&gt;
:* If you're adding a new, already requested feature, please comment on [https://github.com/{{{ARRNAME}}}/{{{ARRNAME}}}/issues Github Issues] so work is not duplicated (If you want to add something not already on there, please talk to us first)&lt;br /&gt;
:* Rebase from {{{ARRNAME}}}'s develop branch, don't merge&lt;br /&gt;
:* Make meaningful commits, or squash them&lt;br /&gt;
:* Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements&lt;br /&gt;
:* Reach out to us on the discord if you have any questions&lt;br /&gt;
:* Add tests (unit/integration)&lt;br /&gt;
:* Commit with *nix line endings for consistency (We checkout Windows and commit *nix)&lt;br /&gt;
:* One feature/bug fix per pull request to keep things clean and easy to understand&lt;br /&gt;
:* Use 4 spaces instead of tabs, this is the default for VS 2019 and WebStorm (to my knowledge)&lt;br /&gt;
&lt;br /&gt;
=== Pull Requesting ===&lt;br /&gt;
:* Only make pull requests to develop, never master, if you make a PR to master we'll comment on it and close it&lt;br /&gt;
:* You're probably going to get some comments or questions from us, they will be to ensure consistency and maintainability&lt;br /&gt;
:* We'll try to respond to pull requests as soon as possible, if its been a day or two, please reach out to us, we may have missed it&lt;br /&gt;
:* Each PR should come from its own [http://martinfowler.com/bliki/FeatureBranch.html feature branch] not develop in your fork, it should have a meaningful branch name (what is being added/fixed)&lt;br /&gt;
    - new-feature (Good)&lt;br /&gt;
    - fix-bug (Good)&lt;br /&gt;
    - patch (Bad)&lt;br /&gt;
    - develop (Bad)&lt;br /&gt;
&lt;br /&gt;
If you have any questions about any of this, please let us know.&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Radarr_Contributing&amp;diff=3070</id>
		<title>Radarr Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Radarr_Contributing&amp;diff=3070"/>
		<updated>2021-01-25T23:23:16Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Contributing|ARRNAME=Radarr|ARRPORT=7878}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=System_status&amp;diff=3066</id>
		<title>System status</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=System_status&amp;diff=3066"/>
		<updated>2021-01-24T17:47:27Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Readarr */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== System ==&lt;br /&gt;
=== Health ===&lt;br /&gt;
==== Overview ====&lt;br /&gt;
====== Radarr ======&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Sonarr ======&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Lidarr ======&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Readarr ======&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
==== System Warnings ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Newer versions of Radarr 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Radarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Radarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Radarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Radarr/Radarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Radarr/Radarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Radarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_8_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;updating_will_not_be_possible_to_prevent_deleting_appdata_on_update&amp;quot;&amp;gt;'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be &amp;lt;code&amp;gt;C:\ProgramData&amp;lt;/code&amp;gt; for Windows and, &amp;lt;code&amp;gt;~/.config&amp;lt;/code&amp;gt; for linux.&lt;br /&gt;
** Please look at System -&amp;amp;gt; Info to see the current AppData &amp;amp;amp; Startup directories.&lt;br /&gt;
** This means Radarr will be unable to update itself without risking data-loss.&lt;br /&gt;
** 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 &amp;lt;code&amp;gt;~/.config/Radarr&amp;lt;/code&amp;gt; directory to preserve your database.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:&lt;br /&gt;
 proxy_http_version 1.1;&lt;br /&gt;
 proxy_set_header Upgrade $http_upgrade;&lt;br /&gt;
 proxy_set_header Connection $http_connection;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
 Include /etc/apache2/mods-available/proxy_wstunnel.load&lt;br /&gt;
 ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&lt;br /&gt;
 ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&lt;br /&gt;
* For Caddy (V1) use this:&lt;br /&gt;
** Note: you'll also need to add the websocket directive to your radarr configuration&lt;br /&gt;
  proxy /radarr 127.0.0.1:7878 {&lt;br /&gt;
      websocket&lt;br /&gt;
      transparent&lt;br /&gt;
  }&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_net_framework_is_old_and_unsupported&amp;quot;&amp;gt;'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]&amp;lt;/span&amp;gt;'''&lt;br /&gt;
** 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.&lt;br /&gt;
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_net_framework_is_supported_but_upgrading_is_recommended&amp;quot;&amp;gt;'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_mono_version_is_old_and_unsupported&amp;quot;&amp;gt;'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.&lt;br /&gt;
** The upgrade procedure for Mono varies per platform.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_mono_version_is_supported_but_upgrading_is_recommended&amp;quot;&amp;gt;'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The upgrade procedure for Mono varies per platform.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; 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.&lt;br /&gt;
** ''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;updating_will_not_be_possible_to_prevent_deleting_appdata_on_update&amp;quot;&amp;gt;'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
**Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be &amp;lt;code&amp;gt;C:\ProgramData&amp;lt;/code&amp;gt; for Windows and, &amp;lt;code&amp;gt;~/.config&amp;lt;/code&amp;gt; for linux.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Please look at System -&amp;amp;gt; About to see the current AppData &amp;amp;amp; Startup directories.&lt;br /&gt;
** This means Sonarr will be unable to update itself without risking data-loss.&lt;br /&gt;
** 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 &amp;lt;code&amp;gt;~/.config/Sonarr&amp;lt;/code&amp;gt; directory to preserve your database.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Lidarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Lidarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Lidarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Lidarr/Lidarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Lidarr/Lidarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Lidarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_8_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Readarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Readarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Readarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Readarr/Readarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Readarr/Readarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Readarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_2_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Raedarr 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Download Clients ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Radarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Radarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Radarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Radarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Radarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Radarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Radarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Radarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Radarr when the download client tells Radarr it's done Radarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Sonarr to prevent the errors.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Lidarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Lidarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Lidarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Lidarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Lidarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Lidarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Lidarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Lidarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Readarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Readarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Readarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Radarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Readarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Readarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Readarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Readarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Readarr when the download client tells Readarr it's done Readarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Completed/Failed Download Handling ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** 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. * If you added a post-processing script to Sabnzbd/NzbGet to notify Radarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occassionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
**''(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.)''&lt;br /&gt;
** It's recommended to switch to 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.&lt;br /&gt;
** If you wish to enable Completed Download Handling you should verify the following:&lt;br /&gt;
*** '''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 download client.&lt;br /&gt;
*** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.&lt;br /&gt;
*** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** 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 Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occassionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** 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. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occassionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Indexers ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&amp;lt;br /&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
**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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results&amp;quot;&amp;gt;'''[[#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]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Simply put you do not have any of your indexers set to allow automatic searches&lt;br /&gt;
*** Go into Settings &amp;gt; Indexers, select an indexer you'd like to allow Automatic Searches and then click save.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically&amp;quot;&amp;gt;'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers avaiable with RSS syn enabled, Lidarr will not grab new releases automatically]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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]]&lt;br /&gt;
** To correct this issue go to Settings &amp;gt; Indexers, select an indexer you have and enable RSS Sync&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Folders ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Easiest way to find this is to go to the Movies (Library) Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path&lt;br /&gt;
***# 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.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the movie folders to '&amp;lt;root path&amp;gt;' ?''' 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&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Series &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the series folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Sonarr to move your files&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Library &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the artist folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Lidarr to move your files&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Library &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the author folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Readarr to move your files&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Media ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_media /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;movie_was_removed_from_tmdb&amp;quot;&amp;gt;'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** The movie is linked to a TMDbId 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** 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&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;lists_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_media /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;series_removed_from_thetvdb&amp;quot;&amp;gt;'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_media /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_media /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_media /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Disk Space ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=radarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=readarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== About ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Radarr&lt;br /&gt;
&amp;lt;section end=radarr_system_status_about /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Radarr&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_about /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Lidarr&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_about /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Readarr&lt;br /&gt;
&amp;lt;section end=readarr_system_status_about /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== More Info ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://radarr.video Radarr's home page]&lt;br /&gt;
* Discord: [https://discord.gg/r5wJPt9 Join our discord]&lt;br /&gt;
* Reddit: [htttps://reddit.com/r/radarr]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]&lt;br /&gt;
* Source: [https://github.com/Radarr/Radarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]&lt;br /&gt;
&amp;lt;section end=radarr_system_status_more_info /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://radarr.video Radarr's home page]&lt;br /&gt;
* Forums: [forums.sonarr.tv Official Sonarr Forums]&lt;br /&gt;
* Discord: [discord.gg/M6BvZn5 Join our discord]&lt;br /&gt;
* Reddit: [https://reddit.com/r/sonarr]&lt;br /&gt;
* Twitter: [@sonarrtv]&lt;br /&gt;
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://sonarr.tv/donate here]&lt;br /&gt;
* Source: [github.com/Sonarr/Sonarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it on Github [github.com/Sonarr/Sonarr/issuess here] or the Forums [forums.sonarr.tv here]&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_more_info /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [lidarr.audio Lidarr's home page]&lt;br /&gt;
* Discord: [https://discord.com/invite/5WQc3S8 Join our discord]&lt;br /&gt;
* Reddit: [https://reddit.com/r/lidarr Lidarr's SubReddit]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/lidarr here]&lt;br /&gt;
* Source: [https://github.com/lidarr/Lidarr/ Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it on GitHub [github.com/Lidarr/Lidarr/issues here] &lt;br /&gt;
&amp;lt;section end=lidarr_system_status_more_info /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://readarr.com Readarr's home page]&lt;br /&gt;
* Reddit: [https://reddit.com/r/readarr]&lt;br /&gt;
* Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]&lt;br /&gt;
* Source: [https://github.com/Readarr/Readarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it [https://github.com/Readarr/Readarr/issues here]&lt;br /&gt;
&amp;lt;section end=readarr_system_status_more_info /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Templates ===&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=System_status&amp;diff=3065</id>
		<title>System status</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=System_status&amp;diff=3065"/>
		<updated>2021-01-24T17:47:16Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Sonarr */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== System ==&lt;br /&gt;
=== Health ===&lt;br /&gt;
==== Overview ====&lt;br /&gt;
====== Radarr ======&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Sonarr ======&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Lidarr ======&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Readarr ======&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
==== System Warnings ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Newer versions of Radarr 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Radarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Radarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Radarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Radarr/Radarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Radarr/Radarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Radarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_8_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;updating_will_not_be_possible_to_prevent_deleting_appdata_on_update&amp;quot;&amp;gt;'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be &amp;lt;code&amp;gt;C:\ProgramData&amp;lt;/code&amp;gt; for Windows and, &amp;lt;code&amp;gt;~/.config&amp;lt;/code&amp;gt; for linux.&lt;br /&gt;
** Please look at System -&amp;amp;gt; Info to see the current AppData &amp;amp;amp; Startup directories.&lt;br /&gt;
** This means Radarr will be unable to update itself without risking data-loss.&lt;br /&gt;
** 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 &amp;lt;code&amp;gt;~/.config/Radarr&amp;lt;/code&amp;gt; directory to preserve your database.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:&lt;br /&gt;
 proxy_http_version 1.1;&lt;br /&gt;
 proxy_set_header Upgrade $http_upgrade;&lt;br /&gt;
 proxy_set_header Connection $http_connection;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
 Include /etc/apache2/mods-available/proxy_wstunnel.load&lt;br /&gt;
 ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&lt;br /&gt;
 ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&lt;br /&gt;
* For Caddy (V1) use this:&lt;br /&gt;
** Note: you'll also need to add the websocket directive to your radarr configuration&lt;br /&gt;
  proxy /radarr 127.0.0.1:7878 {&lt;br /&gt;
      websocket&lt;br /&gt;
      transparent&lt;br /&gt;
  }&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_net_framework_is_old_and_unsupported&amp;quot;&amp;gt;'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]&amp;lt;/span&amp;gt;'''&lt;br /&gt;
** 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.&lt;br /&gt;
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_net_framework_is_supported_but_upgrading_is_recommended&amp;quot;&amp;gt;'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_mono_version_is_old_and_unsupported&amp;quot;&amp;gt;'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.&lt;br /&gt;
** The upgrade procedure for Mono varies per platform.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_mono_version_is_supported_but_upgrading_is_recommended&amp;quot;&amp;gt;'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The upgrade procedure for Mono varies per platform.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; 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.&lt;br /&gt;
** ''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;updating_will_not_be_possible_to_prevent_deleting_appdata_on_update&amp;quot;&amp;gt;'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
**Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be &amp;lt;code&amp;gt;C:\ProgramData&amp;lt;/code&amp;gt; for Windows and, &amp;lt;code&amp;gt;~/.config&amp;lt;/code&amp;gt; for linux.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Please look at System -&amp;amp;gt; About to see the current AppData &amp;amp;amp; Startup directories.&lt;br /&gt;
** This means Sonarr will be unable to update itself without risking data-loss.&lt;br /&gt;
** 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 &amp;lt;code&amp;gt;~/.config/Sonarr&amp;lt;/code&amp;gt; directory to preserve your database.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Lidarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Lidarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Lidarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Lidarr/Lidarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Lidarr/Lidarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Lidarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_8_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Readarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Readarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Readarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Readarr/Readarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Readarr/Readarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Readarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_2_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Raedarr 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Download Clients ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Radarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Radarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Radarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Radarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Radarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Radarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Radarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Radarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Radarr when the download client tells Radarr it's done Radarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Sonarr to prevent the errors.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Lidarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Lidarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Lidarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Lidarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Lidarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Lidarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Lidarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Lidarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Readarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Readarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Readarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Radarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Readarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Readarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Readarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Readarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Readarr when the download client tells Readarr it's done Readarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Completed/Failed Download Handling ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** 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. * If you added a post-processing script to Sabnzbd/NzbGet to notify Radarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occassionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
**''(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.)''&lt;br /&gt;
** It's recommended to switch to 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.&lt;br /&gt;
** If you wish to enable Completed Download Handling you should verify the following:&lt;br /&gt;
*** '''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 download client.&lt;br /&gt;
*** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.&lt;br /&gt;
*** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** 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 Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occassionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.&lt;br /&gt;
** 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. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occassionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Indexers ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&amp;lt;br /&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
**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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results&amp;quot;&amp;gt;'''[[#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]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Simply put you do not have any of your indexers set to allow automatic searches&lt;br /&gt;
*** Go into Settings &amp;gt; Indexers, select an indexer you'd like to allow Automatic Searches and then click save.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically&amp;quot;&amp;gt;'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers avaiable with RSS syn enabled, Lidarr will not grab new releases automatically]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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]]&lt;br /&gt;
** To correct this issue go to Settings &amp;gt; Indexers, select an indexer you have and enable RSS Sync&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Folders ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Easiest way to find this is to go to the Movies (Library) Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path&lt;br /&gt;
***# 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.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the movie folders to '&amp;lt;root path&amp;gt;' ?''' 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&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Series &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the series folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Sonarr to move your files&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Library &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the artist folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Lidarr to move your files&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Library &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the author folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Readarr to move your files&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Media ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_media /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;movie_was_removed_from_tmdb&amp;quot;&amp;gt;'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** The movie is linked to a TMDbId 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** 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&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;lists_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_media /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;series_removed_from_thetvdb&amp;quot;&amp;gt;'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_media /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_media /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_media /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Disk Space ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=radarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=readarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== About ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Radarr&lt;br /&gt;
&amp;lt;section end=radarr_system_status_about /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Radarr&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_about /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Lidarr&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_about /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Readarr&lt;br /&gt;
&amp;lt;section end=readarr_system_status_about /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== More Info ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://radarr.video Radarr's home page]&lt;br /&gt;
* Discord: [https://discord.gg/r5wJPt9 Join our discord]&lt;br /&gt;
* Reddit: [htttps://reddit.com/r/radarr]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]&lt;br /&gt;
* Source: [https://github.com/Radarr/Radarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]&lt;br /&gt;
&amp;lt;section end=radarr_system_status_more_info /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://radarr.video Radarr's home page]&lt;br /&gt;
* Forums: [forums.sonarr.tv Official Sonarr Forums]&lt;br /&gt;
* Discord: [discord.gg/M6BvZn5 Join our discord]&lt;br /&gt;
* Reddit: [https://reddit.com/r/sonarr]&lt;br /&gt;
* Twitter: [@sonarrtv]&lt;br /&gt;
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://sonarr.tv/donate here]&lt;br /&gt;
* Source: [github.com/Sonarr/Sonarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it on Github [github.com/Sonarr/Sonarr/issuess here] or the Forums [forums.sonarr.tv here]&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_more_info /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [lidarr.audio Lidarr's home page]&lt;br /&gt;
* Discord: [https://discord.com/invite/5WQc3S8 Join our discord]&lt;br /&gt;
* Reddit: [https://reddit.com/r/lidarr Lidarr's SubReddit]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/lidarr here]&lt;br /&gt;
* Source: [https://github.com/lidarr/Lidarr/ Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it on GitHub [github.com/Lidarr/Lidarr/issues here] &lt;br /&gt;
&amp;lt;section end=lidarr_system_status_more_info /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://readarr.com Readarr's home page]&lt;br /&gt;
* Reddit: [https://reddit.com/r/readarr]&lt;br /&gt;
* Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]&lt;br /&gt;
* Source: [https://github.com/Readarr/Readarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it [https://github.com/Readarr/Readarr/issues here]&lt;br /&gt;
&amp;lt;section end=readarr_system_status_more_info /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Templates ===&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=System_status&amp;diff=3064</id>
		<title>System status</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=System_status&amp;diff=3064"/>
		<updated>2021-01-24T17:46:47Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Radarr */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== System ==&lt;br /&gt;
=== Health ===&lt;br /&gt;
==== Overview ====&lt;br /&gt;
====== Radarr ======&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Sonarr ======&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Lidarr ======&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Readarr ======&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
==== System Warnings ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Newer versions of Radarr 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Radarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Radarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Radarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Radarr/Radarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Radarr/Radarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Radarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_8_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;updating_will_not_be_possible_to_prevent_deleting_appdata_on_update&amp;quot;&amp;gt;'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be &amp;lt;code&amp;gt;C:\ProgramData&amp;lt;/code&amp;gt; for Windows and, &amp;lt;code&amp;gt;~/.config&amp;lt;/code&amp;gt; for linux.&lt;br /&gt;
** Please look at System -&amp;amp;gt; Info to see the current AppData &amp;amp;amp; Startup directories.&lt;br /&gt;
** This means Radarr will be unable to update itself without risking data-loss.&lt;br /&gt;
** 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 &amp;lt;code&amp;gt;~/.config/Radarr&amp;lt;/code&amp;gt; directory to preserve your database.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:&lt;br /&gt;
 proxy_http_version 1.1;&lt;br /&gt;
 proxy_set_header Upgrade $http_upgrade;&lt;br /&gt;
 proxy_set_header Connection $http_connection;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
 Include /etc/apache2/mods-available/proxy_wstunnel.load&lt;br /&gt;
 ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&lt;br /&gt;
 ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&lt;br /&gt;
* For Caddy (V1) use this:&lt;br /&gt;
** Note: you'll also need to add the websocket directive to your radarr configuration&lt;br /&gt;
  proxy /radarr 127.0.0.1:7878 {&lt;br /&gt;
      websocket&lt;br /&gt;
      transparent&lt;br /&gt;
  }&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_net_framework_is_old_and_unsupported&amp;quot;&amp;gt;'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]&amp;lt;/span&amp;gt;'''&lt;br /&gt;
** 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.&lt;br /&gt;
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_net_framework_is_supported_but_upgrading_is_recommended&amp;quot;&amp;gt;'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_mono_version_is_old_and_unsupported&amp;quot;&amp;gt;'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.&lt;br /&gt;
** The upgrade procedure for Mono varies per platform.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_mono_version_is_supported_but_upgrading_is_recommended&amp;quot;&amp;gt;'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The upgrade procedure for Mono varies per platform.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; 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.&lt;br /&gt;
** ''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;updating_will_not_be_possible_to_prevent_deleting_appdata_on_update&amp;quot;&amp;gt;'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
**Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be &amp;lt;code&amp;gt;C:\ProgramData&amp;lt;/code&amp;gt; for Windows and, &amp;lt;code&amp;gt;~/.config&amp;lt;/code&amp;gt; for linux.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Please look at System -&amp;amp;gt; About to see the current AppData &amp;amp;amp; Startup directories.&lt;br /&gt;
** This means Sonarr will be unable to update itself without risking data-loss.&lt;br /&gt;
** 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 &amp;lt;code&amp;gt;~/.config/Sonarr&amp;lt;/code&amp;gt; directory to preserve your database.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Lidarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Lidarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Lidarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Lidarr/Lidarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Lidarr/Lidarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Lidarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_8_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Readarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Readarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Readarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Readarr/Readarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Readarr/Readarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Readarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_2_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Raedarr 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Download Clients ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Radarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Radarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Radarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Radarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Radarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Radarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Radarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Radarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Radarr when the download client tells Radarr it's done Radarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Sonarr to prevent the errors.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Lidarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Lidarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Lidarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Lidarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Lidarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Lidarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Lidarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Lidarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Readarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Readarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Readarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Radarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Readarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Readarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Readarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Readarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Readarr when the download client tells Readarr it's done Readarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Completed/Failed Download Handling ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** 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. * If you added a post-processing script to Sabnzbd/NzbGet to notify Radarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occassionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
**''(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.)''&lt;br /&gt;
** It's recommended to switch to 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.&lt;br /&gt;
** If you don't wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn't recommended.&lt;br /&gt;
** If you wish to enable Completed Download Handling you should verify the following:&lt;br /&gt;
*** '''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 download client.&lt;br /&gt;
*** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.&lt;br /&gt;
*** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** 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 Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occassionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.&lt;br /&gt;
** 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. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occassionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Indexers ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&amp;lt;br /&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
**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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results&amp;quot;&amp;gt;'''[[#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]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Simply put you do not have any of your indexers set to allow automatic searches&lt;br /&gt;
*** Go into Settings &amp;gt; Indexers, select an indexer you'd like to allow Automatic Searches and then click save.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically&amp;quot;&amp;gt;'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers avaiable with RSS syn enabled, Lidarr will not grab new releases automatically]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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]]&lt;br /&gt;
** To correct this issue go to Settings &amp;gt; Indexers, select an indexer you have and enable RSS Sync&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Folders ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Easiest way to find this is to go to the Movies (Library) Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path&lt;br /&gt;
***# 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.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the movie folders to '&amp;lt;root path&amp;gt;' ?''' 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&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Series &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the series folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Sonarr to move your files&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Library &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the artist folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Lidarr to move your files&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Library &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the author folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Readarr to move your files&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Media ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_media /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;movie_was_removed_from_tmdb&amp;quot;&amp;gt;'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** The movie is linked to a TMDbId 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** 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&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;lists_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_media /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;series_removed_from_thetvdb&amp;quot;&amp;gt;'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_media /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_media /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_media /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Disk Space ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=radarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=readarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== About ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Radarr&lt;br /&gt;
&amp;lt;section end=radarr_system_status_about /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Radarr&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_about /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Lidarr&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_about /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Readarr&lt;br /&gt;
&amp;lt;section end=readarr_system_status_about /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== More Info ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://radarr.video Radarr's home page]&lt;br /&gt;
* Discord: [https://discord.gg/r5wJPt9 Join our discord]&lt;br /&gt;
* Reddit: [htttps://reddit.com/r/radarr]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]&lt;br /&gt;
* Source: [https://github.com/Radarr/Radarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]&lt;br /&gt;
&amp;lt;section end=radarr_system_status_more_info /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://radarr.video Radarr's home page]&lt;br /&gt;
* Forums: [forums.sonarr.tv Official Sonarr Forums]&lt;br /&gt;
* Discord: [discord.gg/M6BvZn5 Join our discord]&lt;br /&gt;
* Reddit: [https://reddit.com/r/sonarr]&lt;br /&gt;
* Twitter: [@sonarrtv]&lt;br /&gt;
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://sonarr.tv/donate here]&lt;br /&gt;
* Source: [github.com/Sonarr/Sonarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it on Github [github.com/Sonarr/Sonarr/issuess here] or the Forums [forums.sonarr.tv here]&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_more_info /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [lidarr.audio Lidarr's home page]&lt;br /&gt;
* Discord: [https://discord.com/invite/5WQc3S8 Join our discord]&lt;br /&gt;
* Reddit: [https://reddit.com/r/lidarr Lidarr's SubReddit]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/lidarr here]&lt;br /&gt;
* Source: [https://github.com/lidarr/Lidarr/ Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it on GitHub [github.com/Lidarr/Lidarr/issues here] &lt;br /&gt;
&amp;lt;section end=lidarr_system_status_more_info /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://readarr.com Readarr's home page]&lt;br /&gt;
* Reddit: [https://reddit.com/r/readarr]&lt;br /&gt;
* Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]&lt;br /&gt;
* Source: [https://github.com/Readarr/Readarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it [https://github.com/Readarr/Readarr/issues here]&lt;br /&gt;
&amp;lt;section end=readarr_system_status_more_info /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Templates ===&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=System_status&amp;diff=3063</id>
		<title>System status</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=System_status&amp;diff=3063"/>
		<updated>2021-01-24T17:46:21Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Lidarr */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== System ==&lt;br /&gt;
=== Health ===&lt;br /&gt;
==== Overview ====&lt;br /&gt;
====== Radarr ======&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Sonarr ======&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Lidarr ======&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Readarr ======&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
==== System Warnings ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Newer versions of Radarr 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Radarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Radarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Radarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Radarr/Radarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Radarr/Radarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Radarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_8_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;updating_will_not_be_possible_to_prevent_deleting_appdata_on_update&amp;quot;&amp;gt;'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be &amp;lt;code&amp;gt;C:\ProgramData&amp;lt;/code&amp;gt; for Windows and, &amp;lt;code&amp;gt;~/.config&amp;lt;/code&amp;gt; for linux.&lt;br /&gt;
** Please look at System -&amp;amp;gt; Info to see the current AppData &amp;amp;amp; Startup directories.&lt;br /&gt;
** This means Radarr will be unable to update itself without risking data-loss.&lt;br /&gt;
** 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 &amp;lt;code&amp;gt;~/.config/Radarr&amp;lt;/code&amp;gt; directory to preserve your database.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:&lt;br /&gt;
 proxy_http_version 1.1;&lt;br /&gt;
 proxy_set_header Upgrade $http_upgrade;&lt;br /&gt;
 proxy_set_header Connection $http_connection;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
 Include /etc/apache2/mods-available/proxy_wstunnel.load&lt;br /&gt;
 ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&lt;br /&gt;
 ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&lt;br /&gt;
* For Caddy (V1) use this:&lt;br /&gt;
** Note: you'll also need to add the websocket directive to your radarr configuration&lt;br /&gt;
  proxy /radarr 127.0.0.1:7878 {&lt;br /&gt;
      websocket&lt;br /&gt;
      transparent&lt;br /&gt;
  }&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_net_framework_is_old_and_unsupported&amp;quot;&amp;gt;'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]&amp;lt;/span&amp;gt;'''&lt;br /&gt;
** 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.&lt;br /&gt;
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_net_framework_is_supported_but_upgrading_is_recommended&amp;quot;&amp;gt;'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_mono_version_is_old_and_unsupported&amp;quot;&amp;gt;'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.&lt;br /&gt;
** The upgrade procedure for Mono varies per platform.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_mono_version_is_supported_but_upgrading_is_recommended&amp;quot;&amp;gt;'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The upgrade procedure for Mono varies per platform.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; 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.&lt;br /&gt;
** ''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;updating_will_not_be_possible_to_prevent_deleting_appdata_on_update&amp;quot;&amp;gt;'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
**Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be &amp;lt;code&amp;gt;C:\ProgramData&amp;lt;/code&amp;gt; for Windows and, &amp;lt;code&amp;gt;~/.config&amp;lt;/code&amp;gt; for linux.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Please look at System -&amp;amp;gt; About to see the current AppData &amp;amp;amp; Startup directories.&lt;br /&gt;
** This means Sonarr will be unable to update itself without risking data-loss.&lt;br /&gt;
** 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 &amp;lt;code&amp;gt;~/.config/Sonarr&amp;lt;/code&amp;gt; directory to preserve your database.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Lidarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Lidarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Lidarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Lidarr/Lidarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Lidarr/Lidarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Lidarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_8_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Readarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Readarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Readarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Readarr/Readarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Readarr/Readarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Readarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_2_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Raedarr 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Download Clients ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Radarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Radarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Radarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Radarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Radarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Radarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Radarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Radarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Radarr when the download client tells Radarr it's done Radarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Sonarr to prevent the errors.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Lidarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Lidarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Lidarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Lidarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Lidarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Lidarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Lidarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Lidarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Readarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Readarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Readarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Radarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Readarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Readarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Readarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Readarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Readarr when the download client tells Readarr it's done Readarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Completed/Failed Download Handling ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.&lt;br /&gt;
** 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. * If you added a post-processing script to Sabnzbd/NzbGet to notify Radarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occassionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
**''(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.)''&lt;br /&gt;
** It's recommended to switch to 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.&lt;br /&gt;
** If you don't wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn't recommended.&lt;br /&gt;
** If you wish to enable Completed Download Handling you should verify the following:&lt;br /&gt;
*** '''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 download client.&lt;br /&gt;
*** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.&lt;br /&gt;
*** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** 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 Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occassionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.&lt;br /&gt;
** 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. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occassionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Indexers ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&amp;lt;br /&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
**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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results&amp;quot;&amp;gt;'''[[#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]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Simply put you do not have any of your indexers set to allow automatic searches&lt;br /&gt;
*** Go into Settings &amp;gt; Indexers, select an indexer you'd like to allow Automatic Searches and then click save.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically&amp;quot;&amp;gt;'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers avaiable with RSS syn enabled, Lidarr will not grab new releases automatically]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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]]&lt;br /&gt;
** To correct this issue go to Settings &amp;gt; Indexers, select an indexer you have and enable RSS Sync&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Folders ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Easiest way to find this is to go to the Movies (Library) Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path&lt;br /&gt;
***# 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.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the movie folders to '&amp;lt;root path&amp;gt;' ?''' 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&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Series &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the series folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Sonarr to move your files&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Library &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the artist folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Lidarr to move your files&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Library &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the author folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Readarr to move your files&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Media ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_media /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;movie_was_removed_from_tmdb&amp;quot;&amp;gt;'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** The movie is linked to a TMDbId 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** 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&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;lists_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_media /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;series_removed_from_thetvdb&amp;quot;&amp;gt;'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_media /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_media /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_media /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Disk Space ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=radarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=readarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== About ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Radarr&lt;br /&gt;
&amp;lt;section end=radarr_system_status_about /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Radarr&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_about /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Lidarr&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_about /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Readarr&lt;br /&gt;
&amp;lt;section end=readarr_system_status_about /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== More Info ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://radarr.video Radarr's home page]&lt;br /&gt;
* Discord: [https://discord.gg/r5wJPt9 Join our discord]&lt;br /&gt;
* Reddit: [htttps://reddit.com/r/radarr]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]&lt;br /&gt;
* Source: [https://github.com/Radarr/Radarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]&lt;br /&gt;
&amp;lt;section end=radarr_system_status_more_info /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://radarr.video Radarr's home page]&lt;br /&gt;
* Forums: [forums.sonarr.tv Official Sonarr Forums]&lt;br /&gt;
* Discord: [discord.gg/M6BvZn5 Join our discord]&lt;br /&gt;
* Reddit: [https://reddit.com/r/sonarr]&lt;br /&gt;
* Twitter: [@sonarrtv]&lt;br /&gt;
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://sonarr.tv/donate here]&lt;br /&gt;
* Source: [github.com/Sonarr/Sonarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it on Github [github.com/Sonarr/Sonarr/issuess here] or the Forums [forums.sonarr.tv here]&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_more_info /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [lidarr.audio Lidarr's home page]&lt;br /&gt;
* Discord: [https://discord.com/invite/5WQc3S8 Join our discord]&lt;br /&gt;
* Reddit: [https://reddit.com/r/lidarr Lidarr's SubReddit]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/lidarr here]&lt;br /&gt;
* Source: [https://github.com/lidarr/Lidarr/ Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it on GitHub [github.com/Lidarr/Lidarr/issues here] &lt;br /&gt;
&amp;lt;section end=lidarr_system_status_more_info /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://readarr.com Readarr's home page]&lt;br /&gt;
* Reddit: [https://reddit.com/r/readarr]&lt;br /&gt;
* Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]&lt;br /&gt;
* Source: [https://github.com/Readarr/Readarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it [https://github.com/Readarr/Readarr/issues here]&lt;br /&gt;
&amp;lt;section end=readarr_system_status_more_info /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Templates ===&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2952</id>
		<title>WikiMap</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2952"/>
		<updated>2021-01-07T19:52:58Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Miscellaneous */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please use https://github.com/Servarr/Wiki to track issues&lt;br /&gt;
Please use this page for easy access to templates&lt;br /&gt;
&lt;br /&gt;
This page to act as an overall map of the wiki as many templates and sections are in use via transclusion.&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Templates ==&lt;br /&gt;
&lt;br /&gt;
# [[Template:Appdata Directory]]&lt;br /&gt;
# [[Template:Installation]]&lt;br /&gt;
# [[Template:Troubleshooting]]&lt;br /&gt;
# [[Template:Contributing]]&lt;br /&gt;
# [[Template:FAQ]]&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous ==&lt;br /&gt;
# [[Sandbox]] &amp;lt;- Test code and do any testing here before sending it to live&lt;br /&gt;
# [[Useful Tools]]&lt;br /&gt;
# [[Cloud Setup|Rclone/Mergerfs/Gdrive setup &amp;amp; links]]&lt;br /&gt;
# [[Docker Guide]]&lt;br /&gt;
# [[Definitions]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Plex]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Network]]&lt;br /&gt;
# [[Clear Cache Cookies and Local Storage]]&lt;br /&gt;
# [[Troubleshooting Misc]]&lt;br /&gt;
# [[Appdata Directory Misc]]&lt;br /&gt;
# [[Installation Misc]]&lt;br /&gt;
# [[Docker on arm synology|Docker on ARM Synology]]&lt;br /&gt;
# [[Filters]]&lt;br /&gt;
# [[FAQ Misc]]&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Pages ==&lt;br /&gt;
* [[Radarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Sonarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Lidarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Readarr]]&lt;br /&gt;
&lt;br /&gt;
== API Documentation ==&lt;br /&gt;
* [https://radarr.video/docs/api/ Radarr]&lt;br /&gt;
&lt;br /&gt;
* Sonarr&lt;br /&gt;
&lt;br /&gt;
* Lidarr&lt;br /&gt;
&lt;br /&gt;
* Readarr&lt;br /&gt;
&lt;br /&gt;
== *ARR Pages ==&lt;br /&gt;
&amp;lt;section begin=radarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Radarr]]&lt;br /&gt;
**[[Radarr Installation]]&lt;br /&gt;
**[[Radarr Quick Start Guide]]&lt;br /&gt;
**[[Radarr Library|Radarr Library (Movies)]]&lt;br /&gt;
**[[Radarr Calendar]]&lt;br /&gt;
**[[Radarr Activity]]&lt;br /&gt;
**[[Radarr Settings]]&lt;br /&gt;
**[[Radarr System]]&lt;br /&gt;
**[[Radarr Troubleshooting]]&lt;br /&gt;
**[[Radarr FAQ]]&lt;br /&gt;
**[[Radarr Tips and Tricks]]&lt;br /&gt;
**[[Radarr Contributing]]&amp;lt;section end=radarr_wiki_pages /&amp;gt;&amp;lt;section begin=sonarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Sonarr]]&lt;br /&gt;
**[[Sonarr Installation]]&lt;br /&gt;
**[[Sonarr Quick Start Guide]]&lt;br /&gt;
**[[Sonarr Library|Sonarr Library (Series)]]&lt;br /&gt;
**[[Sonarr Calendar]]&lt;br /&gt;
**[[Sonarr Activity]]&lt;br /&gt;
**[[Sonarr Wanted]]&lt;br /&gt;
**[[Sonarr Settings]]&lt;br /&gt;
**[[Sonarr System]]&lt;br /&gt;
**[[Sonarr Troubleshooting]]&lt;br /&gt;
**[[Sonarr FAQ]]&lt;br /&gt;
**[[Sonarr Tips and Tricks]]&lt;br /&gt;
**[[Sonarr Contributing]]&amp;lt;section end=sonarr_wiki_pages /&amp;gt;&amp;lt;section begin=lidarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Lidarr]]&lt;br /&gt;
**[[Lidarr Installation]]&lt;br /&gt;
**[[Lidarr Quick Start Guide]]&lt;br /&gt;
**[[Lidarr Library|Lidarr Library (Artist)]]&lt;br /&gt;
**[[Lidarr Calendar]]&lt;br /&gt;
**[[Lidarr Activity]]&lt;br /&gt;
**[[Lidarr Wanted]]&lt;br /&gt;
**[[Lidarr Settings]]&lt;br /&gt;
**[[Lidarr System]]&lt;br /&gt;
**[[Lidarr Troubleshooting]]&lt;br /&gt;
**[[Lidarr FAQ]]&lt;br /&gt;
**[[Lidarr Tips and Tricks]]&lt;br /&gt;
**[[Lidarr Contributing]]&amp;lt;section end=lidarr_wiki_pages /&amp;gt;&amp;lt;section begin=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Readarr]]&lt;br /&gt;
**[[Readarr Installation]]&lt;br /&gt;
**[[Readarr Quick Start Guide]]&lt;br /&gt;
**[[Readarr Library|Readarr Library]]&lt;br /&gt;
**[[Readarr Calendar]]&lt;br /&gt;
**[[Readarr Activity]]&lt;br /&gt;
**[[Readarr Wanted]]&lt;br /&gt;
**[[Readarr Settings]]&lt;br /&gt;
**[[Readarr System]]&lt;br /&gt;
**[[Readarr Troubleshooting]]&lt;br /&gt;
**[[Readarr FAQ]]&lt;br /&gt;
**[[Readarr Tips and Tricks]]&lt;br /&gt;
**[[Readarr Contributing]]&amp;lt;section end=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== * ARR UI Pages ==&lt;br /&gt;
Note: All templates or sections are housed within their respective pages. To edit those templates click on the page then to the template page.&lt;br /&gt;
=== Movies/Series/Library ===&lt;br /&gt;
# [[Library]]&lt;br /&gt;
# [[Library Add New]]&lt;br /&gt;
# [[Library Import]]&lt;br /&gt;
# [[Library Discover]] &amp;lt;-- Radarr&lt;br /&gt;
# [[Library Mass Editor]] &amp;lt;-- Sonarr/Lidarr&lt;br /&gt;
# [[Library Bulk Monitoring Editor]] &amp;lt;--Season Pass/Album Studio/Bookshelf combined&lt;br /&gt;
# [[Library Unmapped Files]] &amp;lt;-- Lidarr/Readarr&lt;br /&gt;
&lt;br /&gt;
=== Calendar ===&lt;br /&gt;
# [[Calendar]]&lt;br /&gt;
&lt;br /&gt;
=== Activity ===&lt;br /&gt;
# [[Activity]]&lt;br /&gt;
# [[Activity Queue]]&lt;br /&gt;
# [[Activity History]]&lt;br /&gt;
# [[Activity Blacklist]]&lt;br /&gt;
&lt;br /&gt;
=== Wanted ===&lt;br /&gt;
# [[Wanted]]&lt;br /&gt;
# [[Wanted Missing]]&lt;br /&gt;
# [[Wanted Cutoff Unmet]]&lt;br /&gt;
&lt;br /&gt;
=== Settings ===&lt;br /&gt;
# [[Settings Media Management]]&lt;br /&gt;
# [[Settings Profiles]]&lt;br /&gt;
# [[Settings Quality]]&lt;br /&gt;
# [[Settings Custom Formats]]&lt;br /&gt;
# [[Settings Indexers]]&lt;br /&gt;
# [[Settings Download Clients]]&lt;br /&gt;
# [[Settings Lists]]&lt;br /&gt;
# [[Settings Connect]]&lt;br /&gt;
# [[Settings Metadata]]&lt;br /&gt;
# [[Settings Tags]]&lt;br /&gt;
# [[Settings General]]&lt;br /&gt;
# [[Settings UI]]&lt;br /&gt;
=== System ===&lt;br /&gt;
# [[System status|System Status]]&lt;br /&gt;
# [[System tasks|System Tasks]]&lt;br /&gt;
# [[System backup|System Backup]]&lt;br /&gt;
# [[System updates|System Updates]]&lt;br /&gt;
# [[System events|System Events]]&lt;br /&gt;
# [[System log files|System Log Files]]&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2951</id>
		<title>WikiMap</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2951"/>
		<updated>2021-01-07T19:52:13Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Stand Alone Templates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please use https://github.com/Servarr/Wiki to track issues&lt;br /&gt;
Please use this page for easy access to templates&lt;br /&gt;
&lt;br /&gt;
This page to act as an overall map of the wiki as many templates and sections are in use via transclusion.&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Templates ==&lt;br /&gt;
&lt;br /&gt;
# [[Template:Appdata Directory]]&lt;br /&gt;
# [[Template:Installation]]&lt;br /&gt;
# [[Template:Troubleshooting]]&lt;br /&gt;
# [[Template:Contributing]]&lt;br /&gt;
# [[Template:FAQ]]&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous ==&lt;br /&gt;
# [[Sandbox]] &amp;lt;- Test code and do any testing here before sending it to live&lt;br /&gt;
# [[Useful Tools]]&lt;br /&gt;
# [[Cloud Setup|Rclone/Mergerfs/Gdrive setup &amp;amp; links]]&lt;br /&gt;
# [[Docker Guide]]&lt;br /&gt;
# [[Definitions]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Plex]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Network]]&lt;br /&gt;
# [[Clear Cache Cookies and Local Storage]]&lt;br /&gt;
# [[Troubleshooting Misc]]&lt;br /&gt;
# [[Appdata Directory Misc]]&lt;br /&gt;
# [[Installation Misc]]&lt;br /&gt;
# [[Docker on arm synology|Docker on ARM Synology]]&lt;br /&gt;
# [[Filters]]&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Pages ==&lt;br /&gt;
* [[Radarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Sonarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Lidarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Readarr]]&lt;br /&gt;
&lt;br /&gt;
== API Documentation ==&lt;br /&gt;
* [https://radarr.video/docs/api/ Radarr]&lt;br /&gt;
&lt;br /&gt;
* Sonarr&lt;br /&gt;
&lt;br /&gt;
* Lidarr&lt;br /&gt;
&lt;br /&gt;
* Readarr&lt;br /&gt;
&lt;br /&gt;
== *ARR Pages ==&lt;br /&gt;
&amp;lt;section begin=radarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Radarr]]&lt;br /&gt;
**[[Radarr Installation]]&lt;br /&gt;
**[[Radarr Quick Start Guide]]&lt;br /&gt;
**[[Radarr Library|Radarr Library (Movies)]]&lt;br /&gt;
**[[Radarr Calendar]]&lt;br /&gt;
**[[Radarr Activity]]&lt;br /&gt;
**[[Radarr Settings]]&lt;br /&gt;
**[[Radarr System]]&lt;br /&gt;
**[[Radarr Troubleshooting]]&lt;br /&gt;
**[[Radarr FAQ]]&lt;br /&gt;
**[[Radarr Tips and Tricks]]&lt;br /&gt;
**[[Radarr Contributing]]&amp;lt;section end=radarr_wiki_pages /&amp;gt;&amp;lt;section begin=sonarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Sonarr]]&lt;br /&gt;
**[[Sonarr Installation]]&lt;br /&gt;
**[[Sonarr Quick Start Guide]]&lt;br /&gt;
**[[Sonarr Library|Sonarr Library (Series)]]&lt;br /&gt;
**[[Sonarr Calendar]]&lt;br /&gt;
**[[Sonarr Activity]]&lt;br /&gt;
**[[Sonarr Wanted]]&lt;br /&gt;
**[[Sonarr Settings]]&lt;br /&gt;
**[[Sonarr System]]&lt;br /&gt;
**[[Sonarr Troubleshooting]]&lt;br /&gt;
**[[Sonarr FAQ]]&lt;br /&gt;
**[[Sonarr Tips and Tricks]]&lt;br /&gt;
**[[Sonarr Contributing]]&amp;lt;section end=sonarr_wiki_pages /&amp;gt;&amp;lt;section begin=lidarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Lidarr]]&lt;br /&gt;
**[[Lidarr Installation]]&lt;br /&gt;
**[[Lidarr Quick Start Guide]]&lt;br /&gt;
**[[Lidarr Library|Lidarr Library (Artist)]]&lt;br /&gt;
**[[Lidarr Calendar]]&lt;br /&gt;
**[[Lidarr Activity]]&lt;br /&gt;
**[[Lidarr Wanted]]&lt;br /&gt;
**[[Lidarr Settings]]&lt;br /&gt;
**[[Lidarr System]]&lt;br /&gt;
**[[Lidarr Troubleshooting]]&lt;br /&gt;
**[[Lidarr FAQ]]&lt;br /&gt;
**[[Lidarr Tips and Tricks]]&lt;br /&gt;
**[[Lidarr Contributing]]&amp;lt;section end=lidarr_wiki_pages /&amp;gt;&amp;lt;section begin=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Readarr]]&lt;br /&gt;
**[[Readarr Installation]]&lt;br /&gt;
**[[Readarr Quick Start Guide]]&lt;br /&gt;
**[[Readarr Library|Readarr Library]]&lt;br /&gt;
**[[Readarr Calendar]]&lt;br /&gt;
**[[Readarr Activity]]&lt;br /&gt;
**[[Readarr Wanted]]&lt;br /&gt;
**[[Readarr Settings]]&lt;br /&gt;
**[[Readarr System]]&lt;br /&gt;
**[[Readarr Troubleshooting]]&lt;br /&gt;
**[[Readarr FAQ]]&lt;br /&gt;
**[[Readarr Tips and Tricks]]&lt;br /&gt;
**[[Readarr Contributing]]&amp;lt;section end=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== * ARR UI Pages ==&lt;br /&gt;
Note: All templates or sections are housed within their respective pages. To edit those templates click on the page then to the template page.&lt;br /&gt;
=== Movies/Series/Library ===&lt;br /&gt;
# [[Library]]&lt;br /&gt;
# [[Library Add New]]&lt;br /&gt;
# [[Library Import]]&lt;br /&gt;
# [[Library Discover]] &amp;lt;-- Radarr&lt;br /&gt;
# [[Library Mass Editor]] &amp;lt;-- Sonarr/Lidarr&lt;br /&gt;
# [[Library Bulk Monitoring Editor]] &amp;lt;--Season Pass/Album Studio/Bookshelf combined&lt;br /&gt;
# [[Library Unmapped Files]] &amp;lt;-- Lidarr/Readarr&lt;br /&gt;
&lt;br /&gt;
=== Calendar ===&lt;br /&gt;
# [[Calendar]]&lt;br /&gt;
&lt;br /&gt;
=== Activity ===&lt;br /&gt;
# [[Activity]]&lt;br /&gt;
# [[Activity Queue]]&lt;br /&gt;
# [[Activity History]]&lt;br /&gt;
# [[Activity Blacklist]]&lt;br /&gt;
&lt;br /&gt;
=== Wanted ===&lt;br /&gt;
# [[Wanted]]&lt;br /&gt;
# [[Wanted Missing]]&lt;br /&gt;
# [[Wanted Cutoff Unmet]]&lt;br /&gt;
&lt;br /&gt;
=== Settings ===&lt;br /&gt;
# [[Settings Media Management]]&lt;br /&gt;
# [[Settings Profiles]]&lt;br /&gt;
# [[Settings Quality]]&lt;br /&gt;
# [[Settings Custom Formats]]&lt;br /&gt;
# [[Settings Indexers]]&lt;br /&gt;
# [[Settings Download Clients]]&lt;br /&gt;
# [[Settings Lists]]&lt;br /&gt;
# [[Settings Connect]]&lt;br /&gt;
# [[Settings Metadata]]&lt;br /&gt;
# [[Settings Tags]]&lt;br /&gt;
# [[Settings General]]&lt;br /&gt;
# [[Settings UI]]&lt;br /&gt;
=== System ===&lt;br /&gt;
# [[System status|System Status]]&lt;br /&gt;
# [[System tasks|System Tasks]]&lt;br /&gt;
# [[System backup|System Backup]]&lt;br /&gt;
# [[System updates|System Updates]]&lt;br /&gt;
# [[System events|System Events]]&lt;br /&gt;
# [[System log files|System Log Files]]&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Settings_Download_Clients&amp;diff=2945</id>
		<title>Settings Download Clients</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Settings_Download_Clients&amp;diff=2945"/>
		<updated>2021-01-05T17:18:08Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Download Clients ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
&amp;lt;section begin=settings_download_client_overview /&amp;gt;&lt;br /&gt;
Downloading and importing is where most people experience issues. From a high level perspective, the software needs to be able to communicate with your download client and have access to the files it downloads. There is a large variety of supported download clients and an even bigger variety of setups. This means that while there are some common setups there isn't one right setup and everyone's setup can be a little different. But there are many wrong setups.&lt;br /&gt;
&amp;lt;section end=settings_download_client_overview /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Download Clients ===&lt;br /&gt;
'''TEMPLATE'''&lt;br /&gt;
&lt;br /&gt;
=== Complete Download Handling ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
Completed Download Handling is how Radarr imports media from your download client to your series folders.&lt;br /&gt;
'''Many common issues are related to [[Docker Guide|bad Docker paths and/or other Docker permissions issues]].'''&lt;br /&gt;
* Enable - Automatically import completed downloads from the download client&lt;br /&gt;
* Remove - Remove completed downloads when finished (usenet) or stopped/complete (torrents)&lt;br /&gt;
* Check For Finished Downloads Interval -  How often to query the download client&lt;br /&gt;
Remove Completed Downloads&lt;br /&gt;
&lt;br /&gt;
# Radarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings.&lt;br /&gt;
# Radarr will monitor your download clients active downloads that use that category name. It monitors this via your download client's API.&lt;br /&gt;
# When the download is completed, Radarr will know the final file location as reported by your download client. This file location can be almost anywhere, as long as it is somewhere separate from your media folder.&lt;br /&gt;
# Radarr will scan that completed file location for video files. It will parse the video file name to match it to a movie. If it can do that, it will rename the file according to your specifications, and move it to the assigned library folder.&lt;br /&gt;
# Leftover files from the download will be sent to your trash or recycling.&lt;br /&gt;
&lt;br /&gt;
If you download using a BitTorrent client, the process is slightly different:&lt;br /&gt;
&lt;br /&gt;
* Completed files are left in their original location to allow you to seed. When files are imported to your assigned library folder Radarr will attempt to hardlink the file or fall back to copy (use double space) if hard links are not supported.&lt;br /&gt;
* If the &amp;quot;Completed Download Handling - Remove&amp;quot; option is enabled in settings, Radarr will delete the original file and torrent from your client, but only if the client reports that seeding is complete and torrent is stopped.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section end=radarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
Completed Download Handling is how Sonarr imports media from your download client to your series folders.&lt;br /&gt;
'''Many common issues are related to [[Docker Guide|bad Docker paths and/or other Docker permissions issues]].'''&lt;br /&gt;
* Enable - Automatically import completed downloads from the download client&lt;br /&gt;
* Remove - Remove completed downloads when finished (usenet) or stopped/complete (torrents)&lt;br /&gt;
Remove Completed Downloads&lt;br /&gt;
&lt;br /&gt;
# Sonarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings.&lt;br /&gt;
# Sonarr will monitor your download clients active downloads that use that category name. It monitors this via your download client's API.&lt;br /&gt;
# When the download is completed, Sonarr will know the final file location as reported by your download client. This file location can be almost anywhere, as long as it is somewhere separate from your media folder.&lt;br /&gt;
# Sonarr will scan that completed file location for video files. It will parse the video file name to match it to an episode. If it can do that, it will rename the file according to your specifications, and move it to the assigned library folder.&lt;br /&gt;
# Leftover files from the download will be sent to your trash or recycling.&lt;br /&gt;
&lt;br /&gt;
If you download using a BitTorrent client, the process is slightly different:&lt;br /&gt;
&lt;br /&gt;
* Completed files are left in their original location to allow you to seed. When files are imported to your assigned library folder Sonarr will attempt to hardlink the file or fall back to copy (use double space) if hard links are not supported.&lt;br /&gt;
* If the &amp;quot;Completed Download Handling - Remove&amp;quot; option is enabled in settings, Sonarr will delete the original file and torrent from your client, but only if the client reports that seeding is complete and torrent is stopped.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section end=sonarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
Completed Download Handling is how Lidarr imports media from your download client to your series folders.&lt;br /&gt;
'''Many common issues are related to [[Docker Guide|bad Docker paths and/or other Docker permissions issues]].'''&lt;br /&gt;
* Enable - Automatically import completed downloads from the download client&lt;br /&gt;
* Remove - Remove completed downloads when finished (usenet) or stopped/complete (torrents)&lt;br /&gt;
Remove Completed Downloads&lt;br /&gt;
&lt;br /&gt;
# Lidarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings.&lt;br /&gt;
# Lidarr will monitor your download clients active downloads that use that category name. It monitors this via your download client's API.&lt;br /&gt;
# When the download is completed, Lidarr will know the final file location as reported by your download client. This file location can be almost anywhere, as long as it is somewhere separate from your media folder.&lt;br /&gt;
# Lidarr will scan that completed file location for audio files. It will parse the file name to match it to a track. If it can do that, it will rename the file according to your specifications, and move it to the assigned library folder.&lt;br /&gt;
# Leftover files from the download will be sent to your trash or recycling.&lt;br /&gt;
&lt;br /&gt;
If you download using a BitTorrent client, the process is slightly different:&lt;br /&gt;
&lt;br /&gt;
* Completed files are left in their original location to allow you to seed. When files are imported to your assigned library folder Lidarr will attempt to hardlink the file or fall back to copy (use double space) if hard links are not supported.&lt;br /&gt;
* If the &amp;quot;Completed Download Handling - Remove&amp;quot; option is enabled in settings, Lidarr will delete the original file and torrent from your client, but only if the client reports that seeding is complete and torrent is stopped.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section end=lidarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
Completed Download Handling is how Readarr imports media from your download client to your series folders.&lt;br /&gt;
'''Many common issues are related to [[Docker Guide|bad Docker paths and/or other Docker permissions issues]].'''&lt;br /&gt;
* Enable - Automatically import completed downloads from the download client&lt;br /&gt;
* Remove - Remove completed downloads when finished (usenet) or stopped/complete (torrents)&lt;br /&gt;
Remove Completed Downloads&lt;br /&gt;
&lt;br /&gt;
# Readarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings.&lt;br /&gt;
# Readarr will monitor your download clients active downloads that use that category name. It monitors this via your download client's API.&lt;br /&gt;
# When the download is completed, Readar will know the final file location as reported by your download client. This file location can be almost anywhere, as long as it is somewhere separate from your media folder.&lt;br /&gt;
# Readarr will scan that completed file location for book files. It will parse the file name to match it to a book. If it can do that, it will rename the file according to your specifications, and move it to the assigned library folder.&lt;br /&gt;
# Leftover files from the download will be sent to your trash or recycling.&lt;br /&gt;
&lt;br /&gt;
If you download using a BitTorrent client, the process is slightly different:&lt;br /&gt;
&lt;br /&gt;
* Completed files are left in their original location to allow you to seed. When files are imported to your assigned library folder Readarr will attempt to hardlink the file or fall back to copy (use double space) if hard links are not supported.&lt;br /&gt;
* If the &amp;quot;Completed Download Handling - Remove&amp;quot; option is enabled in settings, Readarr will delete the original file and torrent from your client, but only if the client reports that seeding is complete and torrent is stopped.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section end=readarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Failed Download Handling ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
'''&amp;quot;Redownload&amp;quot;''' - Radarr will handle failed downloads if '''Redownload''' is enabled. Automatically search for and attempt to download a different release within your '''Quality Profiles''' if the download fails for any reason. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;'''Remove'''&amp;quot; - Radarr will send a request to your Download Client to remove the download history of your failed download if '''Remove''' is enabled. &lt;br /&gt;
&lt;br /&gt;
('''Note''': &amp;quot;'''Remove'''&amp;quot; is only presented if you have toggled &amp;quot;'''Show Advanced'''&amp;quot; settings).&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
'''&amp;quot;Redownload&amp;quot;''' - Sonarr will handle failed downloads if '''Redownload''' is enabled. Automatically search for and attempt to download a different release within your '''Quality Profiles''' if the download fails for any reason. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;'''Remove'''&amp;quot; - Sonarr will send a request to your Download Client to remove the download history of your failed download if '''Remove''' is enabled. &lt;br /&gt;
&lt;br /&gt;
('''Note''': &amp;quot;'''Remove'''&amp;quot; is only presented if you have toggled &amp;quot;'''Show Advanced'''&amp;quot; settings).&lt;br /&gt;
====Lidarr====&lt;br /&gt;
'''&amp;quot;Redownload&amp;quot;''' - Lidarr will handle failed downloads if '''Redownload''' is enabled. Automatically search for and attempt to download a different release within your '''Quality Profiles''' if the download fails for any reason. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;'''Remove'''&amp;quot; - Lidarr will send a request to your Download Client to remove the download history of your failed download if '''Remove''' is enabled. &lt;br /&gt;
&lt;br /&gt;
('''Note''': &amp;quot;'''Remove'''&amp;quot; is only presented if you have toggled &amp;quot;'''Show Advanced'''&amp;quot; settings).&lt;br /&gt;
====Readarr====&lt;br /&gt;
'''&amp;quot;Redownload&amp;quot;''' - Readarr will handle failed downloads if '''Redownload''' is enabled. Automatically search for and attempt to download a different release within your '''Quality Profiles''' if the download fails for any reason. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;'''Remove'''&amp;quot; - Readarr will send a request to your Download Client to remove the download history of your failed download if '''Remove''' is enabled. &lt;br /&gt;
&lt;br /&gt;
('''Note''': &amp;quot;'''Remove'''&amp;quot; is only presented if you have toggled &amp;quot;'''Show Advanced'''&amp;quot; settings).&lt;br /&gt;
&lt;br /&gt;
=== Remote Path Mapping ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
Remote Path Mapping acts as a dumb find &amp;lt;code&amp;gt;Remote Path&amp;lt;/code&amp;gt; and replace with &amp;lt;code&amp;gt;Local Path&amp;lt;/code&amp;gt;&lt;br /&gt;
This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.&lt;br /&gt;
&lt;br /&gt;
One of our amazing community members have created an excellent guide to help you out if you think remotte path mapping is what will work for you [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ here]&lt;br /&gt;
&amp;lt;section end=radarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
Remote Path Mapping acts as a dumb find &amp;lt;code&amp;gt;Remote Path&amp;lt;/code&amp;gt; and replace with &amp;lt;code&amp;gt;Local Path&amp;lt;/code&amp;gt;&lt;br /&gt;
This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.&lt;br /&gt;
&lt;br /&gt;
One of our amazing community members have created an excellent guide to help you out if you think remotte path mapping is what will work for you [https://trash-guides.info/Sonarr/V3/Sonarr-remote-path-mapping/ here]&lt;br /&gt;
&amp;lt;section end=sonarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
Remote Path Mapping acts as a dumb find &amp;lt;code&amp;gt;Remote Path&amp;lt;/code&amp;gt; and replace with &amp;lt;code&amp;gt;Local Path&amp;lt;/code&amp;gt;&lt;br /&gt;
This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.&lt;br /&gt;
&lt;br /&gt;
One of our amazing community members have created an excellent guide to help you out if you think remotte path mapping is what will work for you [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ here]&lt;br /&gt;
The guide is for Radarr but all concepts are exactly the same for Lidarr&lt;br /&gt;
&amp;lt;section end=lidarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
Remote Path Mapping acts as a dumb find &amp;lt;code&amp;gt;Remote Path&amp;lt;/code&amp;gt; and replace with &amp;lt;code&amp;gt;Local Path&amp;lt;/code&amp;gt;&lt;br /&gt;
This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.&lt;br /&gt;
&lt;br /&gt;
One of our amazing community members have created an excellent guide to help you out if you think remotte path mapping is what will work for you [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ here]&lt;br /&gt;
The guide is for Radarr but all concepts are exactly the same for Readarr&lt;br /&gt;
&amp;lt;section end=readarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Templates ===&lt;br /&gt;
* [[Template:settings_download_clients_download_clients]]&lt;br /&gt;
* [[Tempalte:settings_download_clients_failed_download_handling]]&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Settings_Download_Clients&amp;diff=2944</id>
		<title>Settings Download Clients</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Settings_Download_Clients&amp;diff=2944"/>
		<updated>2021-01-05T17:17:18Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Download Clients ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
&amp;lt;section begin=settings_download_client_overview /&amp;gt;&lt;br /&gt;
Downloading and importing is where most people experience issues. From a high level perspective, the software needs to be able to communicate with your download client and have access to the files it downloads. There is a large variety of supported download clients and an even bigger variety of setups. This means that while there are some common setups there isn't one right setup and everyone's setup can be a little different. But there are many wrong setups.&lt;br /&gt;
&amp;lt;section end=settings_download_client_overview /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Download Clients ===&lt;br /&gt;
'''TEMPLATE'''&lt;br /&gt;
&lt;br /&gt;
=== Complete Download Handling ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
Completed Download Handling is how Radarr imports media from your download client to your series folders.&lt;br /&gt;
'''Many common issues are related to [[Docker Guide|bad Docker paths and/or other Docker permissions issues]].'''&lt;br /&gt;
* Enable - Automatically import completed downloads from the download client&lt;br /&gt;
* Remove - Remove completed downloads when finished (usenet) or stopped/complete (torrents)&lt;br /&gt;
* Check For Finished Downloads Interval -  How often to query the download client&lt;br /&gt;
Remove Completed Downloads&lt;br /&gt;
&lt;br /&gt;
# Radarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings.&lt;br /&gt;
# Radarr will monitor your download clients active downloads that use that category name. It monitors this via your download client's API.&lt;br /&gt;
# When the download is completed, Radarr will know the final file location as reported by your download client. This file location can be almost anywhere, as long as it is somewhere separate from your media folder.&lt;br /&gt;
# Radarr will scan that completed file location for video files. It will parse the video file name to match it to a movie. If it can do that, it will rename the file according to your specifications, and move it to the assigned library folder.&lt;br /&gt;
# Leftover files from the download will be sent to your trash or recycling.&lt;br /&gt;
&lt;br /&gt;
If you download using a BitTorrent client, the process is slightly different:&lt;br /&gt;
&lt;br /&gt;
* Completed files are left in their original location to allow you to seed. When files are imported to your assigned library folder Radarr will attempt to hardlink the file or fall back to copy (use double space) if hard links are not supported.&lt;br /&gt;
* If the &amp;quot;Completed Download Handling - Remove&amp;quot; option is enabled in settings, Radarr will delete the original file and torrent from your client, but only if the client reports that seeding is complete and torrent is stopped.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section end=radarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
Completed Download Handling is how Sonarr imports media from your download client to your series folders.&lt;br /&gt;
'''Many common issues are related to [[Docker Guide|bad Docker paths and/or other Docker permissions issues]].'''&lt;br /&gt;
* Enable - Automatically import completed downloads from the download client&lt;br /&gt;
* Remove - Remove completed downloads when finished (usenet) or stopped/complete (torrents)&lt;br /&gt;
Remove Completed Downloads&lt;br /&gt;
&lt;br /&gt;
# Sonarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings.&lt;br /&gt;
# Sonarr will monitor your download clients active downloads that use that category name. It monitors this via your download client's API.&lt;br /&gt;
# When the download is completed, Sonarr will know the final file location as reported by your download client. This file location can be almost anywhere, as long as it is somewhere separate from your media folder.&lt;br /&gt;
# Sonarr will scan that completed file location for video files. It will parse the video file name to match it to an episode. If it can do that, it will rename the file according to your specifications, and move it to the assigned library folder.&lt;br /&gt;
# Leftover files from the download will be sent to your trash or recycling.&lt;br /&gt;
&lt;br /&gt;
If you download using a BitTorrent client, the process is slightly different:&lt;br /&gt;
&lt;br /&gt;
* Completed files are left in their original location to allow you to seed. When files are imported to your assigned library folder Sonarr will attempt to hardlink the file or fall back to copy (use double space) if hard links are not supported.&lt;br /&gt;
* If the &amp;quot;Completed Download Handling - Remove&amp;quot; option is enabled in settings, Sonarr will delete the original file and torrent from your client, but only if the client reports that seeding is complete and torrent is stopped.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section end=sonarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
Completed Download Handling is how Lidarr imports media from your download client to your series folders.&lt;br /&gt;
'''Many common issues are related to [[Docker Guide|bad Docker paths and/or other Docker permissions issues]].'''&lt;br /&gt;
* Enable - Automatically import completed downloads from the download client&lt;br /&gt;
* Remove - Remove completed downloads when finished (usenet) or stopped/complete (torrents)&lt;br /&gt;
Remove Completed Downloads&lt;br /&gt;
&lt;br /&gt;
# Lidarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings.&lt;br /&gt;
# Lidarr will monitor your download clients active downloads that use that category name. It monitors this via your download client's API.&lt;br /&gt;
# When the download is completed, Lidarr will know the final file location as reported by your download client. This file location can be almost anywhere, as long as it is somewhere separate from your media folder.&lt;br /&gt;
# Lidarr will scan that completed file location for audio files. It will parse the file name to match it to a track. If it can do that, it will rename the file according to your specifications, and move it to the assigned library folder.&lt;br /&gt;
# Leftover files from the download will be sent to your trash or recycling.&lt;br /&gt;
&lt;br /&gt;
If you download using a BitTorrent client, the process is slightly different:&lt;br /&gt;
&lt;br /&gt;
* Completed files are left in their original location to allow you to seed. When files are imported to your assigned library folder Lidarr will attempt to hardlink the file or fall back to copy (use double space) if hard links are not supported.&lt;br /&gt;
* If the &amp;quot;Completed Download Handling - Remove&amp;quot; option is enabled in settings, Lidarr will delete the original file and torrent from your client, but only if the client reports that seeding is complete and torrent is stopped.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section end=lidarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
Completed Download Handling is how Readarr imports media from your download client to your series folders.&lt;br /&gt;
'''Many common issues are related to [[Docker Guide|bad Docker paths and/or other Docker permissions issues]].'''&lt;br /&gt;
* Enable - Automatically import completed downloads from the download client&lt;br /&gt;
* Remove - Remove completed downloads when finished (usenet) or stopped/complete (torrents)&lt;br /&gt;
Remove Completed Downloads&lt;br /&gt;
&lt;br /&gt;
# Readarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings.&lt;br /&gt;
# Readarr will monitor your download clients active downloads that use that category name. It monitors this via your download client's API.&lt;br /&gt;
# When the download is completed, Readar will know the final file location as reported by your download client. This file location can be almost anywhere, as long as it is somewhere separate from your media folder.&lt;br /&gt;
# Readarr will scan that completed file location for book files. It will parse the file name to match it to a book. If it can do that, it will rename the file according to your specifications, and move it to the assigned library folder.&lt;br /&gt;
# Leftover files from the download will be sent to your trash or recycling.&lt;br /&gt;
&lt;br /&gt;
If you download using a BitTorrent client, the process is slightly different:&lt;br /&gt;
&lt;br /&gt;
* Completed files are left in their original location to allow you to seed. When files are imported to your assigned library folder Readarr will attempt to hardlink the file or fall back to copy (use double space) if hard links are not supported.&lt;br /&gt;
* If the &amp;quot;Completed Download Handling - Remove&amp;quot; option is enabled in settings, Readarr will delete the original file and torrent from your client, but only if the client reports that seeding is complete and torrent is stopped.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section end=readarr_settings_download_clients_complete_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Failed Download Handling ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
'''&amp;quot;Redownload&amp;quot;''' - Radarr will handle failed downloads if '''Redownload''' is enabled. Automatically search for and attempt to download a different release within your '''Quality Profiles''' if the download fails for any reason. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;'''Remove'''&amp;quot; - Radarr will send a request to your Download Client to remove the download history of your failed download if '''Remove''' is enabled. &lt;br /&gt;
&lt;br /&gt;
('''Note''': &amp;quot;'''Remove'''&amp;quot; is only presented if you have toggled &amp;quot;'''Show Advanced'''&amp;quot; settings).&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
'''&amp;quot;Redownload&amp;quot;''' - Sonarr will handle failed downloads if '''Redownload''' is enabled. Automatically search for and attempt to download a different release within your '''Quality Profiles''' if the download fails for any reason. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;'''Remove'''&amp;quot; - Sonarr will send a request to your Download Client to remove the download history of your failed download if '''Remove''' is enabled. &lt;br /&gt;
&lt;br /&gt;
('''Note''': &amp;quot;'''Remove'''&amp;quot; is only presented if you have toggled &amp;quot;'''Show Advanced'''&amp;quot; settings).&lt;br /&gt;
====Lidarr====&lt;br /&gt;
'''&amp;quot;Redownload&amp;quot;''' - Lidarr will handle failed downloads if '''Redownload''' is enabled. Automatically search for and attempt to download a different release within your '''Quality Profiles''' if the download fails for any reason. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;'''Remove'''&amp;quot; - Lidarr will send a request to your Download Client to remove the download history of your failed download if '''Remove''' is enabled. &lt;br /&gt;
&lt;br /&gt;
('''Note''': &amp;quot;'''Remove'''&amp;quot; is only presented if you have toggled &amp;quot;'''Show Advanced'''&amp;quot; settings).&lt;br /&gt;
====Readarr====&lt;br /&gt;
'''&amp;quot;Redownload&amp;quot;''' - Readarr will handle failed downloads if '''Redownload''' is enabled. Automatically search for and attempt to download a different release within your '''Quality Profiles''' if the download fails for any reason. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;'''Remove'''&amp;quot; - Readarr will send a request to your Download Client to remove the download history of your failed download if '''Remove''' is enabled. &lt;br /&gt;
&lt;br /&gt;
('''Note''': &amp;quot;'''Remove'''&amp;quot; is only presented if you have toggled &amp;quot;'''Show Advanced'''&amp;quot; settings).&lt;br /&gt;
&lt;br /&gt;
=== Remote Path Mapping ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
Remote Path Mapping acts as a dumb find &amp;lt;code&amp;gt;Remote Path&amp;lt;/code&amp;gt; and replace with &amp;lt;code&amp;gt;Local Path&amp;lt;/code&amp;gt;&lt;br /&gt;
This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.&lt;br /&gt;
One of our amazing community members have created an excellent guide to help you out if you think remotte path mapping is what will work for you [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ here]&lt;br /&gt;
&amp;lt;section end=radarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
Remote Path Mapping acts as a dumb find &amp;lt;code&amp;gt;Remote Path&amp;lt;/code&amp;gt; and replace with &amp;lt;code&amp;gt;Local Path&amp;lt;/code&amp;gt;&lt;br /&gt;
This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.&lt;br /&gt;
One of our amazing community members have created an excellent guide to help you out if you think remotte path mapping is what will work for you [https://trash-guides.info/Sonarr/V3/Sonarr-remote-path-mapping/ here]&lt;br /&gt;
&amp;lt;section end=sonarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
Remote Path Mapping acts as a dumb find &amp;lt;code&amp;gt;Remote Path&amp;lt;/code&amp;gt; and replace with &amp;lt;code&amp;gt;Local Path&amp;lt;/code&amp;gt;&lt;br /&gt;
This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.&lt;br /&gt;
One of our amazing community members have created an excellent guide to help you out if you think remotte path mapping is what will work for you [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ here]&lt;br /&gt;
The guide is for Radarr but all concepts are exactly the same for Lidarr&lt;br /&gt;
&amp;lt;section end=lidarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
Remote Path Mapping acts as a dumb find &amp;lt;code&amp;gt;Remote Path&amp;lt;/code&amp;gt; and replace with &amp;lt;code&amp;gt;Local Path&amp;lt;/code&amp;gt;&lt;br /&gt;
This is primarily used for either merged local/remote setups using mergerfs or similar or is used for when the application and download client are not on the same server.&lt;br /&gt;
One of our amazing community members have created an excellent guide to help you out if you think remotte path mapping is what will work for you [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ here]&lt;br /&gt;
The guide is for Radarr but all concepts are exactly the same for Readarr&lt;br /&gt;
&amp;lt;section end=readarr_settings_download_clients_remote_path_mapping /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Templates ===&lt;br /&gt;
* [[Template:settings_download_clients_download_clients]]&lt;br /&gt;
* [[Tempalte:settings_download_clients_failed_download_handling]]&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Wanted_Cutoff_Unmet&amp;diff=2943</id>
		<title>Wanted Cutoff Unmet</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Wanted_Cutoff_Unmet&amp;diff=2943"/>
		<updated>2021-01-04T17:16:06Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Radarr ==&lt;br /&gt;
&amp;lt;section begin=radarr_wanted_cutoff_unmet /&amp;gt;&lt;br /&gt;
Information about the cutoff unmet section coming soon(tm)&lt;br /&gt;
&amp;lt;section end=radarr_wanted_cutoff_unmet /&amp;gt;&lt;br /&gt;
== Sonarr ==&lt;br /&gt;
&amp;lt;section begin=sonarr_wanted_cutoff_unmet /&amp;gt;&lt;br /&gt;
TThe '''Wanted''' -&amp;gt; '''Cutoff Unmet''' section contains a list of the episodes that have not yet reached their cut off. The cut off is set within your [[Sonarr Settings#Profiles|profiles]] &lt;br /&gt;
:* Tthe cut off is where you essentially tell Sonarr that the quality of the video file is good enough for you and you no longer wish for Sonarr to keep searching for better.&lt;br /&gt;
:* There are a couple of options available to you on this page&lt;br /&gt;
:[[file:wanted-cut-off-unmet.png|frameless|none|900px|alt=Sonarr Cut off unmet]]&lt;br /&gt;
# Search Selected - By selecting episodes on your list you can perform an '''Automatic''' search to try to see if there are any upgrades to your existing files.&lt;br /&gt;
# Unmonitor Selected - By selecting certain episodes on your list you can tell Sonarr to no longer look for any upgrades by '''Unmonitoring''' that episode.&lt;br /&gt;
# Seach All - This can be dangerous (depending on how big your list is) as you're telling Sonarr to search every file that hasn't met the cut off. This can be useful if you do not have a massive list.&lt;br /&gt;
# Filter - This will allow you to filter out your results. This is useful if you're wanting to search a specific set of episodes or series&lt;br /&gt;
&lt;br /&gt;
&amp;lt;section end=sonarr_wanted_cutoff_unmet /&amp;gt;&lt;br /&gt;
== Lidarr ==&lt;br /&gt;
&amp;lt;section begin=lidarr_wanted_cutoff_unmet /&amp;gt;&lt;br /&gt;
Information about the cutoff unmet section coming soon(tm)&lt;br /&gt;
&amp;lt;section end=lidarr_wanted_cutoff_unmet /&amp;gt;&lt;br /&gt;
== Readarr ==&lt;br /&gt;
&amp;lt;section begin=readarr_wanted_cutoff_unmet /&amp;gt;&lt;br /&gt;
Information about the cutoff unmet section coming soon(tm)&lt;br /&gt;
&amp;lt;section end=readarr_wanted_cutoff_unmet /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=File:Wanted-cut-off-unmet.png&amp;diff=2942</id>
		<title>File:Wanted-cut-off-unmet.png</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=File:Wanted-cut-off-unmet.png&amp;diff=2942"/>
		<updated>2021-01-04T17:14:48Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Lidarr_Library&amp;diff=2941</id>
		<title>Lidarr Library</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Lidarr_Library&amp;diff=2941"/>
		<updated>2021-01-04T16:57:31Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Library ==&lt;br /&gt;
{{#lst::Library|lidarr_library}}&lt;br /&gt;
=== Filters ===&lt;br /&gt;
{{#lst::Filters|lidarr_filters}}&lt;br /&gt;
== Add New ==&lt;br /&gt;
{{#lst::Library Add New|lidarr_library_add_new}}&lt;br /&gt;
== Mass Editor ==&lt;br /&gt;
{{#lst::Library Mass Editor|lidarr_library_mass_editor}}&lt;br /&gt;
== Album Studio ==&lt;br /&gt;
{{#lst::Library Bulk Monitoring Editor|lidarr_library_bulk_monitoring_editor}}&lt;br /&gt;
== Unmapped Files ==&lt;br /&gt;
{{#lst::Library Unmapped Files|lidarr_library_unmapped_files}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Settings_Connect&amp;diff=2932</id>
		<title>Settings Connect</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Settings_Connect&amp;diff=2932"/>
		<updated>2021-01-02T20:06:41Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Connect ==&lt;br /&gt;
=== Connections ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_settings_connect_connections /&amp;gt;&lt;br /&gt;
Connections are how you want Radarr to communicate with the outside world.&lt;br /&gt;
* By pressing the &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; button you'll be presented with a new window which will allow you to configure many different endpoints&lt;br /&gt;
** There are many different endpoints&lt;br /&gt;
*** [https://boxcar.io Boxcar]&lt;br /&gt;
*** [[Radarr_Tips_and_Tricks#Custom_Post_Processing_Scripts|Custom Scripts]] - This allows you to make a custom script for when a particular action happens this script will run&lt;br /&gt;
*** [https://discord.com Discord] - By far one of the most common ways to push notifications of actions happening on your Radarr&lt;br /&gt;
*** [https://discordnotifier.com Discord Notifier] - The brainchild of one of the Radarr developers allowing you to have beautiful discord notifications with very fine tuned control. Constantly being updated and a favorite amongst many of the Radarr team.&lt;br /&gt;
*** Email - Simply send yourself or somebody you want to annoy with email. If you're using Gmail and have 2-factor authentication enabled you need to use an App Specific password: https://support.google.com/accounts/answer/185833&lt;br /&gt;
*** [https://emby.media Emby]&lt;br /&gt;
*** [https://gotify.net Gotify]&lt;br /&gt;
*** [https://joaoapps.com/join/ Join]&lt;br /&gt;
*** [https://kodi.tv Kodi] - Kodi spawned from the love of media. It is an entertainment hub that brings all your digital media together into a beautiful and user friendly package. It is 100% free and open source, very customisable and runs on a wide variety of devices. It is supported by a dedicated team of volunteers and a huge community.&lt;br /&gt;
**** By adding Kodi as a connection you can update Kodi's library when a new movie has been added to Radarr&lt;br /&gt;
*** [https://plex.tv Plex Media Server] - The server for your self hosted Plex system, Enabling this is much like Kodi will allow you to push an update to your plex server notifying it that a new/upgraded movie is available&lt;br /&gt;
*** [https://www.prowlapp.com Prowl]&lt;br /&gt;
*** [https://www.pushbullet.com Pushbullet]&lt;br /&gt;
*** [https://pushover.net Pushover]&lt;br /&gt;
*** [https://sendgrid.com Sendgrid]&lt;br /&gt;
*** [https://slack.com Slack]&lt;br /&gt;
*** [https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/application_indexservice_desc Synology Indexer]&lt;br /&gt;
*** [https://telegram.org Telegram]&lt;br /&gt;
*** [https://trakt.tv/dashboard Trakt]&lt;br /&gt;
*** [https://twitter.com Twitter]&lt;br /&gt;
**** Create a Twitter application (if you haven’t already) at https://apps.twitter.com/&lt;br /&gt;
**** Fill in the mandatory fields as well as the callback URL, set it to a publicly available URL (not localhost), it doesn’t need to exist, but it does need to be set, using &amp;lt;code&amp;gt;https://radarr.video/twitter&amp;lt;/code&amp;gt; is sufficient.&lt;br /&gt;
&lt;br /&gt;
* Connection Triggers&lt;br /&gt;
** On Grab - Be notified when movies are available for download and has been sent to a download client&lt;br /&gt;
** On Import - Be notified when movies are successfully imported&lt;br /&gt;
** On Upgrade - Be notified when movies are upgraded to a better quality&lt;br /&gt;
** On Rename - Be notified when movies are renamed&lt;br /&gt;
** On Delete - ?TBD?&lt;br /&gt;
** On Health Issue - Be notified on health check failures&lt;br /&gt;
** Include Health Warnings - Be notified on health warnings in addition to errors.&lt;br /&gt;
&amp;lt;section end=radarr_settings_connect_connections /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_settings_connect_connections /&amp;gt;&lt;br /&gt;
Connections are how you want Sonarr to communicate with the outside world.&lt;br /&gt;
* By pressing the &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; button you'll be presented with a new window which will allow you to configure many different endpoints&lt;br /&gt;
** There are many different endpoints&lt;br /&gt;
*** [https://boxcar.io Boxcar]&lt;br /&gt;
*** Custom scripts - This allows you to make a custom script for when a particular action happens this script will run&lt;br /&gt;
*** [https://discord.com Discord] - By far one of the most common ways to push notifications of actions happening on your Sonarr&lt;br /&gt;
*** Email - Simply send yourself or somebody you want to annoy with emails. If you're using Gmail and have 2-factor authentication enabled you need to use an App Specific password: https://support.google.com/accounts/answer/185833&lt;br /&gt;
*** [https://emby.media Emby]&lt;br /&gt;
*** [https://gotify.net Gotify]&lt;br /&gt;
*** [https://joaoapps.com/join/ Join]&lt;br /&gt;
*** [https://kodi.tv Kodi] - Kodi spawned from the love of media. It is an entertainment hub that brings all your digital media together into a beautiful and user friendly package. It is 100% free and open source, very customisable and runs on a wide variety of devices. It is supported by a dedicated team of volunteers and a huge community.&lt;br /&gt;
**** By adding Kodi as a connection you can update Kodi's library when a new episode has been added to Sonarr&lt;br /&gt;
*** [https://plex.tv Plex Home Theater]&lt;br /&gt;
*** [https://plex.tv Plex Media Center]&lt;br /&gt;
*** [https://plex.tv Plex Media Server] - The server for your self hosted Plex system, Enabling this is much like Kodi will allow you to push an update to your plex server notifying it that a new/upgraded episode is available&lt;br /&gt;
*** [https://www.prowlapp.com Prowl]&lt;br /&gt;
*** [https://www.pushbullet.com Pushbullet]&lt;br /&gt;
*** [https://pushover.net Pushover]&lt;br /&gt;
*** [https://sendgrid.com Sendgrid]&lt;br /&gt;
*** [https://slack.com Slack]&lt;br /&gt;
*** [https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/application_indexservice_desc Synology Indexer]&lt;br /&gt;
*** [https://telegram.org Telegram]&lt;br /&gt;
*** [https://trakt.tv/dashboard Trakt]&lt;br /&gt;
*** [https://twitter.com Twitter]&lt;br /&gt;
&lt;br /&gt;
* Connection Triggers&lt;br /&gt;
** On Grab - Be notified when episodes are available for download and has been sent to a download client&lt;br /&gt;
** On Import - Be notified when episodes are successfully imported&lt;br /&gt;
** On Upgrade - Be notified when episodes are upgraded to a better quality&lt;br /&gt;
** On Rename - Be notified when episodes are renamed&lt;br /&gt;
** On Health Issue - Be notified on health check failures&lt;br /&gt;
** Include Health Warnings - Be notified on health warnings in addition to errors.&lt;br /&gt;
&amp;lt;section end=sonarr_settings_connect_connections /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_settings_connect_connections /&amp;gt;&lt;br /&gt;
Connections are how you want Lidarr to communicate with the outside world.&lt;br /&gt;
* By pressing the &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; button you'll be presented with a new window which will allow you to configure many different endpoints&lt;br /&gt;
** There are many different endpoints&lt;br /&gt;
*** [https://boxcar.io Boxcar]&lt;br /&gt;
*** Custom scripts - This allows you to make a custom script for when a particular action happens this script will run&lt;br /&gt;
*** [https://discord.com Discord] - By far one of the most common ways to push notifications of actions happening on your Lidarr&lt;br /&gt;
*** [https://discordnotifier.com Discord Notifier] - The brainchild of one of the Lidarr developers allowing you to have beautiful discord notifications with very fine tuned control. Constantly being updated and a favorite amongst many of the Lidarr team.&lt;br /&gt;
*** Email - Simply send yourself or somebody you want to annoy with email. If you're using Gmail and have 2-factor authentication enabled you need to use an App Specific password: https://support.google.com/accounts/answer/185833&lt;br /&gt;
*** [https://emby.media Emby]&lt;br /&gt;
*** [https://gotify.net Gotify]&lt;br /&gt;
*** [https://joaoapps.com/join/ Join]&lt;br /&gt;
*** [https://kodi.tv Kodi] - Kodi spawned from the love of media. It is an entertainment hub that brings all your digital media together into a beautiful and user friendly package. It is 100% free and open source, very customisable and runs on a wide variety of devices. It is supported by a dedicated team of volunteers and a huge community.&lt;br /&gt;
**** By adding Kodi as a connection you can update Kodi's library when a new movie has been added to Lidarr&lt;br /&gt;
*** [https://plex.tv Plex Media Server] - The server for your self hosted Plex system, Enabling this is much like Kodi will allow you to push an update to your plex server notifying it that a new/upgraded movie is available&lt;br /&gt;
*** [https://www.prowlapp.com Prowl]&lt;br /&gt;
*** [https://www.pushbullet.com Pushbullet]&lt;br /&gt;
*** [https://pushover.net Pushover]&lt;br /&gt;
*** [https://sendgrid.com Sendgrid]&lt;br /&gt;
*** [https://slack.com Slack]&lt;br /&gt;
*** [http://www.subsonic.org Subsonic]&lt;br /&gt;
*** [https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/application_indexservice_desc Synology Indexer]&lt;br /&gt;
*** [https://telegram.org Telegram]&lt;br /&gt;
*** [https://twitter.com Twitter]&lt;br /&gt;
&lt;br /&gt;
* Connection Triggers&lt;br /&gt;
** On Grab - Be notified when episodes are available for download and has been sent to a download client&lt;br /&gt;
** On Import - Be notified when episodes are successfully imported&lt;br /&gt;
** On Upgrade - Be notified when episodes are upgraded to a better quality&lt;br /&gt;
** On Rename - Be notified when episodes are renamed&lt;br /&gt;
** On Health Issue - Be notified on health check failures&lt;br /&gt;
** Include Health Warnings - Be notified on health warnings in addition to errors.&lt;br /&gt;
&amp;lt;section end=lidarr_settings_connect_connections /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_settings_connect_connections /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=readarr_settings_connect_connections /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Templates ===&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Readarr_Library&amp;diff=2928</id>
		<title>Readarr Library</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Readarr_Library&amp;diff=2928"/>
		<updated>2021-01-01T19:53:25Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Library */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Library ==&lt;br /&gt;
{{#lst::Library|readarr_library}}&lt;br /&gt;
=== Filters ===&lt;br /&gt;
{{#lst::Filters|readarr_filters}}&lt;br /&gt;
&lt;br /&gt;
== Add New ==&lt;br /&gt;
{{#lst::Library Add New|readarr_library_add_new}}&lt;br /&gt;
== Mass Editor ==&lt;br /&gt;
{{#lst::Library Mass Editor|readarr_library_mass_editor}}&lt;br /&gt;
== Book Shelf ==&lt;br /&gt;
{{#lst::Library Bulk Monitoring Editor|readarr_library_bulk_monitoring_editor}}&lt;br /&gt;
== Unmapped Files ==&lt;br /&gt;
{{#lst::Library Unmapped Files|readarr_library_unmapped_files}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Lidarr_Library&amp;diff=2927</id>
		<title>Lidarr Library</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Lidarr_Library&amp;diff=2927"/>
		<updated>2021-01-01T19:52:27Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Library */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Library ==&lt;br /&gt;
{{#lst::Library|lidarr_library}}&lt;br /&gt;
=== Filters ===&lt;br /&gt;
{{#lst::Filters|lidarr_filters}}&lt;br /&gt;
&lt;br /&gt;
== Add New ==&lt;br /&gt;
{{#lst::Library Add New|lidarr_library_add_new}}&lt;br /&gt;
== Mass Editor ==&lt;br /&gt;
{{#lst::Library Mass Editor|lidarr_library_mass_editor}}&lt;br /&gt;
== Album Studio ==&lt;br /&gt;
{{#lst::Library Bulk Monitoring Editor|lidarr_library_bulk_monitoring_editor}}&lt;br /&gt;
== Unmapped Files ==&lt;br /&gt;
{{#lst::Library Unmapped Files|lidarr_library_unmapped_files}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Sonarr_Library&amp;diff=2926</id>
		<title>Sonarr Library</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Sonarr_Library&amp;diff=2926"/>
		<updated>2021-01-01T19:51:58Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Series ==&lt;br /&gt;
{{#lst::Library|sonarr_library}}&lt;br /&gt;
=== Filters ===&lt;br /&gt;
{{#lst::Filters|sonarr_filters}}&lt;br /&gt;
== Add New ==&lt;br /&gt;
{{#lst::Library Add New|sonarr_library_add_new}}&lt;br /&gt;
== Library Import ==&lt;br /&gt;
{{#lst::Library Import|sonarr_library_import}}&lt;br /&gt;
== Mass Editor ==&lt;br /&gt;
{{#lst::Library Mass Editor|sonarr_library_mass_editor}}&lt;br /&gt;
== Season Pass ==&lt;br /&gt;
{{#lst::Library Bulk Monitoring Editor|sonarr_library_bulk_monitoring_editor}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Sonarr_Library&amp;diff=2925</id>
		<title>Sonarr Library</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Sonarr_Library&amp;diff=2925"/>
		<updated>2021-01-01T19:51:48Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Series */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Series ==&lt;br /&gt;
{{#lst::Library|sonarr_library}}&lt;br /&gt;
=== Filters ===&lt;br /&gt;
{{#lst::Filters|sonarr_filters}}&lt;br /&gt;
&lt;br /&gt;
== Add New ==&lt;br /&gt;
{{#lst::Library Add New|sonarr_library_add_new}}&lt;br /&gt;
== Library Import ==&lt;br /&gt;
{{#lst::Library Import|sonarr_library_import}}&lt;br /&gt;
== Mass Editor ==&lt;br /&gt;
{{#lst::Library Mass Editor|sonarr_library_mass_editor}}&lt;br /&gt;
== Season Pass ==&lt;br /&gt;
{{#lst::Library Bulk Monitoring Editor|sonarr_library_bulk_monitoring_editor}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Radarr_Library&amp;diff=2924</id>
		<title>Radarr Library</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Radarr_Library&amp;diff=2924"/>
		<updated>2021-01-01T19:50:34Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Movies ==&lt;br /&gt;
{{#lst::Library|radarr_library}}&lt;br /&gt;
=== Filters ===&lt;br /&gt;
{{#lst::Filters|radarr_filters}}&lt;br /&gt;
== Add New ==&lt;br /&gt;
{{#lst::Library Add New|radarr_library_add_new}}&lt;br /&gt;
== Library Import ==&lt;br /&gt;
{{#lst::Library Import|radarr_library_import}}&lt;br /&gt;
== Discover ==&lt;br /&gt;
{{#lst::Library Discover|radarr_library_discover}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Filters&amp;diff=2923</id>
		<title>Filters</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Filters&amp;diff=2923"/>
		<updated>2021-01-01T19:49:31Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: Created page with &amp;quot;== Radarr == &amp;lt;section begin=radarr_filters /&amp;gt; Information about filters coming soon(tm). &amp;lt;section end=radarr_filters /&amp;gt; == Sonarr == &amp;lt;section begin=sonarr_filters /&amp;gt; Informati...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Radarr ==&lt;br /&gt;
&amp;lt;section begin=radarr_filters /&amp;gt;&lt;br /&gt;
Information about filters coming soon(tm).&lt;br /&gt;
&amp;lt;section end=radarr_filters /&amp;gt;&lt;br /&gt;
== Sonarr ==&lt;br /&gt;
&amp;lt;section begin=sonarr_filters /&amp;gt;&lt;br /&gt;
Information about filters coming soon(tm).&lt;br /&gt;
&amp;lt;section end=sonarr_filters /&amp;gt;&lt;br /&gt;
== Lidarr ==&lt;br /&gt;
&amp;lt;section begin=lidarr_filters /&amp;gt;&lt;br /&gt;
Information about filters coming soon(tm).&lt;br /&gt;
&amp;lt;section end=lidarr_filters /&amp;gt;&lt;br /&gt;
== Readarr ==&lt;br /&gt;
&amp;lt;section begin=readarr_filters /&amp;gt;&lt;br /&gt;
Information about filters coming soon(tm).&lt;br /&gt;
&amp;lt;section end=readarr_filters /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2922</id>
		<title>WikiMap</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2922"/>
		<updated>2021-01-01T19:47:18Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Miscellaneous */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please use https://github.com/Servarr/Wiki to track issues&lt;br /&gt;
Please use this page for easy access to templates&lt;br /&gt;
&lt;br /&gt;
This page to act as an overall map of the wiki as many templates and sections are in use via transclusion.&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Templates ==&lt;br /&gt;
&lt;br /&gt;
# [[Template:Appdata Directory]]&lt;br /&gt;
# [[Template:Installation]]&lt;br /&gt;
# [[Template:Troubleshooting]]&lt;br /&gt;
# [[Template:Contributing]]&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous ==&lt;br /&gt;
# [[Sandbox]] &amp;lt;- Test code and do any testing here before sending it to live&lt;br /&gt;
# [[Useful Tools]]&lt;br /&gt;
# [[Cloud Setup|Rclone/Mergerfs/Gdrive setup &amp;amp; links]]&lt;br /&gt;
# [[Docker Guide]]&lt;br /&gt;
# [[Definitions]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Plex]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Network]]&lt;br /&gt;
# [[Clear Cache Cookies and Local Storage]]&lt;br /&gt;
# [[Troubleshooting Misc]]&lt;br /&gt;
# [[Appdata Directory Misc]]&lt;br /&gt;
# [[Installation Misc]]&lt;br /&gt;
# [[Docker on arm synology|Docker on ARM Synology]]&lt;br /&gt;
# [[Filters]]&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Pages ==&lt;br /&gt;
* [[Radarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Sonarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Lidarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Readarr]]&lt;br /&gt;
&lt;br /&gt;
== API Documentation ==&lt;br /&gt;
* [https://radarr.video/docs/api/ Radarr]&lt;br /&gt;
&lt;br /&gt;
* Sonarr&lt;br /&gt;
&lt;br /&gt;
* Lidarr&lt;br /&gt;
&lt;br /&gt;
* Readarr&lt;br /&gt;
&lt;br /&gt;
== *ARR Pages ==&lt;br /&gt;
&amp;lt;section begin=radarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Radarr]]&lt;br /&gt;
**[[Radarr Installation]]&lt;br /&gt;
**[[Radarr Quick Start Guide]]&lt;br /&gt;
**[[Radarr Library|Radarr Library (Movies)]]&lt;br /&gt;
**[[Radarr Calendar]]&lt;br /&gt;
**[[Radarr Activity]]&lt;br /&gt;
**[[Radarr Settings]]&lt;br /&gt;
**[[Radarr System]]&lt;br /&gt;
**[[Radarr Troubleshooting]]&lt;br /&gt;
**[[Radarr FAQ]]&lt;br /&gt;
**[[Radarr Tips and Tricks]]&lt;br /&gt;
**[[Radarr Contributing]]&amp;lt;section end=radarr_wiki_pages /&amp;gt;&amp;lt;section begin=sonarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Sonarr]]&lt;br /&gt;
**[[Sonarr Installation]]&lt;br /&gt;
**[[Sonarr Quick Start Guide]]&lt;br /&gt;
**[[Sonarr Library|Sonarr Library (Series)]]&lt;br /&gt;
**[[Sonarr Calendar]]&lt;br /&gt;
**[[Sonarr Activity]]&lt;br /&gt;
**[[Sonarr Wanted]]&lt;br /&gt;
**[[Sonarr Settings]]&lt;br /&gt;
**[[Sonarr System]]&lt;br /&gt;
**[[Sonarr Troubleshooting]]&lt;br /&gt;
**[[Sonarr FAQ]]&lt;br /&gt;
**[[Sonarr Tips and Tricks]]&lt;br /&gt;
**[[Sonarr Contributing]]&amp;lt;section end=sonarr_wiki_pages /&amp;gt;&amp;lt;section begin=lidarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Lidarr]]&lt;br /&gt;
**[[Lidarr Installation]]&lt;br /&gt;
**[[Lidarr Quick Start Guide]]&lt;br /&gt;
**[[Lidarr Library|Lidarr Library (Artist)]]&lt;br /&gt;
**[[Lidarr Calendar]]&lt;br /&gt;
**[[Lidarr Activity]]&lt;br /&gt;
**[[Lidarr Wanted]]&lt;br /&gt;
**[[Lidarr Settings]]&lt;br /&gt;
**[[Lidarr System]]&lt;br /&gt;
**[[Lidarr Troubleshooting]]&lt;br /&gt;
**[[Lidarr FAQ]]&lt;br /&gt;
**[[Lidarr Tips and Tricks]]&lt;br /&gt;
**[[Lidarr Contributing]]&amp;lt;section end=lidarr_wiki_pages /&amp;gt;&amp;lt;section begin=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Readarr]]&lt;br /&gt;
**[[Readarr Installation]]&lt;br /&gt;
**[[Readarr Quick Start Guide]]&lt;br /&gt;
**[[Readarr Library|Readarr Library]]&lt;br /&gt;
**[[Readarr Calendar]]&lt;br /&gt;
**[[Readarr Activity]]&lt;br /&gt;
**[[Readarr Wanted]]&lt;br /&gt;
**[[Readarr Settings]]&lt;br /&gt;
**[[Readarr System]]&lt;br /&gt;
**[[Readarr Troubleshooting]]&lt;br /&gt;
**[[Readarr FAQ]]&lt;br /&gt;
**[[Readarr Tips and Tricks]]&lt;br /&gt;
**[[Readarr Contributing]]&amp;lt;section end=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== * ARR UI Pages ==&lt;br /&gt;
Note: All templates or sections are housed within their respective pages. To edit those templates click on the page then to the template page.&lt;br /&gt;
=== Movies/Series/Library ===&lt;br /&gt;
# [[Library]]&lt;br /&gt;
# [[Library Add New]]&lt;br /&gt;
# [[Library Import]]&lt;br /&gt;
# [[Library Discover]] &amp;lt;-- Radarr&lt;br /&gt;
# [[Library Mass Editor]] &amp;lt;-- Sonarr/Lidarr&lt;br /&gt;
# [[Library Bulk Monitoring Editor]] &amp;lt;--Season Pass/Album Studio/Bookshelf combined&lt;br /&gt;
# [[Library Unmapped Files]] &amp;lt;-- Lidarr/Readarr&lt;br /&gt;
&lt;br /&gt;
=== Calendar ===&lt;br /&gt;
# [[Calendar]]&lt;br /&gt;
&lt;br /&gt;
=== Activity ===&lt;br /&gt;
# [[Activity]]&lt;br /&gt;
# [[Activity Queue]]&lt;br /&gt;
# [[Activity History]]&lt;br /&gt;
# [[Activity Blacklist]]&lt;br /&gt;
&lt;br /&gt;
=== Wanted ===&lt;br /&gt;
# [[Wanted]]&lt;br /&gt;
# [[Wanted Missing]]&lt;br /&gt;
# [[Wanted Cutoff Unmet]]&lt;br /&gt;
&lt;br /&gt;
=== Settings ===&lt;br /&gt;
# [[Settings Media Management]]&lt;br /&gt;
# [[Settings Profiles]]&lt;br /&gt;
# [[Settings Quality]]&lt;br /&gt;
# [[Settings Custom Formats]]&lt;br /&gt;
# [[Settings Indexers]]&lt;br /&gt;
# [[Settings Download Clients]]&lt;br /&gt;
# [[Settings Lists]]&lt;br /&gt;
# [[Settings Connect]]&lt;br /&gt;
# [[Settings Metadata]]&lt;br /&gt;
# [[Settings Tags]]&lt;br /&gt;
# [[Settings General]]&lt;br /&gt;
# [[Settings UI]]&lt;br /&gt;
=== System ===&lt;br /&gt;
# [[System status|System Status]]&lt;br /&gt;
# [[System tasks|System Tasks]]&lt;br /&gt;
# [[System backup|System Backup]]&lt;br /&gt;
# [[System updates|System Updates]]&lt;br /&gt;
# [[System events|System Events]]&lt;br /&gt;
# [[System log files|System Log Files]]&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Wanted&amp;diff=2921</id>
		<title>Wanted</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Wanted&amp;diff=2921"/>
		<updated>2021-01-01T17:32:05Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Radarr ==&lt;br /&gt;
&amp;lt;section begin=radarr_wanted /&amp;gt;&lt;br /&gt;
Information about the wanted section coming soon(tm)&lt;br /&gt;
&amp;lt;section end=radarr_wanted /&amp;gt;&lt;br /&gt;
== Sonarr ==&lt;br /&gt;
&amp;lt;section begin=sonarr_wanted /&amp;gt;&lt;br /&gt;
The '''Wanted''' -&amp;gt; '''Missing''' section contains a list of the episodes you have marked to monitor that are missing from your disk (haven't been downloaded yet).&lt;br /&gt;
&lt;br /&gt;
Note: This will only include episodes completely missing from your disk, not episodes which exist on disk, but have their cutoff profile unmet.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Search Selected&amp;quot; - Here you can select certain episodes if you wish to search for them with your indexers&lt;br /&gt;
* &amp;quot;Unmonitor Selected&amp;quot; - Here you can select certain episodes and unmonitor them if you're no longer interested in them.&lt;br /&gt;
* &amp;quot;Search All&amp;quot; - Selecting here will send a search to all of your indexers for all current missing episodes. Once pressed, a dialog box will pop up with a warning to you, letting you know how many episodes will be searched for; this is particularly helpful to know if your indexers limit your api calls. &lt;br /&gt;
** '''Note''': This search process cannot be cancelled once started without restarting Sonarr.&lt;br /&gt;
&amp;lt;section end=sonarr_wanted /&amp;gt;&lt;br /&gt;
== Lidarr ==&lt;br /&gt;
&amp;lt;section begin=lidarr_wanted /&amp;gt;&lt;br /&gt;
The '''Wanted''' -&amp;gt; '''Missing''' section contains a list of the albums you have marked to monitor that are missing from your disk (haven't been downloaded yet).&lt;br /&gt;
&lt;br /&gt;
Note: This will only include albums completely missing from your disk, not albums which exist on disk, but have their cutoff profile unmet.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Search Selected&amp;quot; - Here you can select certain albums if you wish to search for them with your indexers&lt;br /&gt;
* &amp;quot;Unmonitor Selected&amp;quot; - Here you can select certain albums and unmonitor them if you're no longer interested in them.&lt;br /&gt;
* &amp;quot;Search All&amp;quot; - Selecting here will send a search to all of your indexers for all current missing albums . Once pressed, a dialog box will pop up with a warning to you, letting you know how many albums will be searched for; this is particularly helpful to know if your indexers limit your api calls. &lt;br /&gt;
**'''Note''': This search process cannot be cancelled once started without restarting Lidarr.&amp;lt;section end=lidarr_wanted /&amp;gt;&lt;br /&gt;
== Readarr ==&lt;br /&gt;
&amp;lt;section begin=readarr_wanted /&amp;gt;&lt;br /&gt;
The '''Wanted''' -&amp;gt; '''Missing''' section contains a list of the ebooks you have marked to monitor that are missing from your disk (haven't been downloaded yet).&lt;br /&gt;
&lt;br /&gt;
Note: This will only include ebooks completely missing from your disk, not ebooks which exist on disk, but have their cutoff profile unmet.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Search Selected&amp;quot; - Here you can select certain ebooks if you wish to search for them with your indexers&lt;br /&gt;
* &amp;quot;Unmonitor Selected&amp;quot; - Here you can select certain ebooks and unmonitor them if you're no longer interested in them.&lt;br /&gt;
* &amp;quot;Search All&amp;quot; - Selecting here will send a search to all of your indexers for all current missing ebooks . Once pressed, a dialog box will pop up with a warning to you, letting you know how many ebooks will be searched for; this is particularly helpful to know if your indexers limit your api calls. &lt;br /&gt;
**'''Note''': This search process cannot be cancelled once started without restarting Readarr.&lt;br /&gt;
&amp;lt;section end=readarr_wanted /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Wanted&amp;diff=2920</id>
		<title>Wanted</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Wanted&amp;diff=2920"/>
		<updated>2021-01-01T17:30:00Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Radarr ==&lt;br /&gt;
&amp;lt;section begin=radarr_wanted /&amp;gt;&lt;br /&gt;
Information about the wanted section coming soon(tm)&lt;br /&gt;
&amp;lt;section end=radarr_wanted /&amp;gt;&lt;br /&gt;
== Sonarr ==&lt;br /&gt;
&amp;lt;section begin=sonarr_wanted /&amp;gt;&lt;br /&gt;
The '''Wanted''' -&amp;gt; '''Missing''' section contains a list of the episodes you have marked to monitor that are missing from your disk (haven't been downloaded yet).&lt;br /&gt;
&lt;br /&gt;
Note: This will only include episodes completely missing from your disk, not episodes which exist on disk, but have their cutoff profile unmet.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Search Selected&amp;quot; - Here you can select certain episodes if you wish to search for them with your indexers&lt;br /&gt;
* &amp;quot;Unmonitor Selected&amp;quot; - Here you can select certain episodes and unmonitor them if you're no longer interested in them.&lt;br /&gt;
* &amp;quot;Search All&amp;quot; - Selecting here will send a search to all of your indexers for all current missing episodes. Once pressed, a dialog box will pop up with a warning to you, letting you know how many episodes will be searched for; this is particularly helpful to know if your indexers limit your api calls. &lt;br /&gt;
** '''Note''': This search process cannot be cancelled once started without restarting Sonarr.&lt;br /&gt;
&amp;lt;section end=sonarr_wanted /&amp;gt;&lt;br /&gt;
== Lidarr ==&lt;br /&gt;
&amp;lt;section begin=lidarr_wanted /&amp;gt;&lt;br /&gt;
The '''Wanted''' -&amp;gt; '''Missing''' section contains a list of the albums you have marked to monitor that are missing from your disk (haven't been downloaded yet).&lt;br /&gt;
&lt;br /&gt;
Note: This will only include albums completely missing from your disk, not albums which exist on disk, but have their cutoff profile unmet.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Search Selected&amp;quot; - Here you can select certain albums if you wish to search for them with your indexers&lt;br /&gt;
* &amp;quot;Unmonitor Selected&amp;quot; - Here you can select certain albums and unmonitor them if you're no longer interested in them.&lt;br /&gt;
* &amp;quot;Search All&amp;quot; - Selecting here will send a search to all of your indexers for all current missing albums . Once pressed, a dialog box will pop up with a warning to you, letting you know how many albums will be searched for; this is particularly helpful to know if your indexers limit your api calls. &lt;br /&gt;
**'''Note''': This search process cannot be cancelled once started without restarting Lidarr.&amp;lt;section end=lidarr_wanted /&amp;gt;&lt;br /&gt;
== Readarr ==&lt;br /&gt;
&amp;lt;section begin=readarr_wanted /&amp;gt;&lt;br /&gt;
The '''Wanted''' -&amp;gt; '''Missing''' section contains a list of the episodes you have marked to monitor that are missing from your disk (haven't been downloaded yet).&lt;br /&gt;
&lt;br /&gt;
Note: This will only include ebooks completely missing from your disk, not ebooks which exist on disk, but have their cutoff profile unmet.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Search Selected&amp;quot; - Here you can select certain ebooks if you wish to search for them with your indexers&lt;br /&gt;
* &amp;quot;Unmonitor Selected&amp;quot; - Here you can select certain ebooks and unmonitor them if you're no longer interested in them.&lt;br /&gt;
* &amp;quot;Search All&amp;quot; - Selecting here will send a search to all of your indexers for all current missing ebooks . Once pressed, a dialog box will pop up with a warning to you, letting you know how many ebooks will be searched for; this is particularly helpful to know if your indexers limit your api calls. &lt;br /&gt;
**'''Note''': This search process cannot be cancelled once started without restarting Readarr.&lt;br /&gt;
&amp;lt;section end=readarr_wanted /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Wanted&amp;diff=2918</id>
		<title>Wanted</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Wanted&amp;diff=2918"/>
		<updated>2021-01-01T16:44:48Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Radarr ==&lt;br /&gt;
&amp;lt;section begin=radarr_wanted /&amp;gt;&lt;br /&gt;
Information about the wanted section coming soon(tm)&lt;br /&gt;
&amp;lt;section end=radarr_wanted /&amp;gt;&lt;br /&gt;
== Sonarr ==&lt;br /&gt;
&amp;lt;section begin=sonarr_wanted /&amp;gt;&lt;br /&gt;
The '''Wanted''' -&amp;gt; '''Missing''' section contains a list of the episodes you have marked to monitor that are missing from your disk (haven't been downloaded yet).&lt;br /&gt;
&lt;br /&gt;
Note: This will only include episodes completely missing from your disk, not episodes which exist on disk, but have their cutoff profile unmet.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Search Selected&amp;quot; - Here you can select certain episodes if you wish to search for them with your indexers&lt;br /&gt;
* &amp;quot;Unmonitor Selected&amp;quot; - Here you can select certain episodes and unmonitor them if you're no longer interested in them.&lt;br /&gt;
* &amp;quot;Search All&amp;quot; - Selecting here will send a search to all of your indexers for all current missing episodes. Once pressed, a dialog box will pop up with a warning to you, letting you know how many episodes will be searched for; this is particularly helpful to know if your indexers limit your api calls. &lt;br /&gt;
** '''Note''': This search process cannot be cancelled once started without restarting Sonarr.&lt;br /&gt;
&amp;lt;section end=sonarr_wanted /&amp;gt;&lt;br /&gt;
== Lidarr ==&lt;br /&gt;
&amp;lt;section begin=lidarr_wanted /&amp;gt;&lt;br /&gt;
The '''Wanted''' -&amp;gt; '''Missing''' section contains a list of the episodes you have marked to monitor that are missing from your disk (haven't been downloaded yet).&lt;br /&gt;
&lt;br /&gt;
Note: This will only include episodes completely missing from your disk, not episodes which exist on disk, but have their cutoff profile unmet.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Search Selected&amp;quot; - Here you can select certain episodes if you wish to search for them with your indexers&lt;br /&gt;
* &amp;quot;Unmonitor Selected&amp;quot; - Here you can select certain episodes and unmonitor them if you're no longer interested in them.&lt;br /&gt;
* &amp;quot;Search All&amp;quot; - Selecting here will send a search to all of your indexers for all current missing episodes. Once pressed, a dialog box will pop up with a warning to you, letting you know how many episodes will be searched for; this is particularly helpful to know if your indexers limit your api calls. &lt;br /&gt;
** '''Note''': This search process cannot be cancelled once started without restarting Lidarr.&amp;lt;section end=lidarr_wanted /&amp;gt;&lt;br /&gt;
== Readarr ==&lt;br /&gt;
&amp;lt;section begin=readarr_wanted /&amp;gt;&lt;br /&gt;
The '''Wanted''' -&amp;gt; '''Missing''' section contains a list of the episodes you have marked to monitor that are missing from your disk (haven't been downloaded yet).&lt;br /&gt;
&lt;br /&gt;
Note: This will only include episodes completely missing from your disk, not episodes which exist on disk, but have their cutoff profile unmet.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Search Selected&amp;quot; - Here you can select certain episodes if you wish to search for them with your indexers&lt;br /&gt;
* &amp;quot;Unmonitor Selected&amp;quot; - Here you can select certain episodes and unmonitor them if you're no longer interested in them.&lt;br /&gt;
* &amp;quot;Search All&amp;quot; - Selecting here will send a search to all of your indexers for all current missing episodes. Once pressed, a dialog box will pop up with a warning to you, letting you know how many episodes will be searched for; this is particularly helpful to know if your indexers limit your api calls. &lt;br /&gt;
** '''Note''': This search process cannot be cancelled once started without restarting Readarr.&amp;lt;section end=readarr_wanted /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Readarr_Wanted&amp;diff=2917</id>
		<title>Readarr Wanted</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Readarr_Wanted&amp;diff=2917"/>
		<updated>2021-01-01T16:33:35Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Wanted ==&lt;br /&gt;
{{#lst::Wanted|readarr_wanted}}&lt;br /&gt;
== Cutoff Unmet ==&lt;br /&gt;
{{#lst::Wanted Cutoff Unmet|readarr_wanted_cutoff_unmet}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Lidarr_Wanted&amp;diff=2916</id>
		<title>Lidarr Wanted</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Lidarr_Wanted&amp;diff=2916"/>
		<updated>2021-01-01T16:33:18Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Wanted ==&lt;br /&gt;
{{#lst::Wanted|lidarr_wanted}}&lt;br /&gt;
== Cutoff Unmet ==&lt;br /&gt;
{{#lst::Wanted Cutoff Unmet|lidarr_wanted_cutoff_unmet}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Sonarr_Wanted&amp;diff=2915</id>
		<title>Sonarr Wanted</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Sonarr_Wanted&amp;diff=2915"/>
		<updated>2021-01-01T16:31:07Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Wanted ==&lt;br /&gt;
{{#lst::Wanted|sonarr_wanted}}&lt;br /&gt;
== Cutoff Unmet ==&lt;br /&gt;
{{#lst::Wanted Cutoff Unmet|sonarr_wanted_cutoff_unmet}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2913</id>
		<title>Template:Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2913"/>
		<updated>2021-01-01T03:40:04Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to Contribute ==&lt;br /&gt;
&lt;br /&gt;
We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
Setup guides, FAQ, the more information we have on the [[{{{ARRNAME}}}|wiki]] the better please contact one of Team {{{ARRNAME}}} for assistance with getting set up with the wiki.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
&lt;br /&gt;
=== Tools required ===&lt;br /&gt;
:* Visual Studio 2019 or higher [https://www.visualstudio.com/vs/ VisualStudio].  The [https://www.visualstudio.com/downloads/ community version] is free and works.&lt;br /&gt;
:* HTML/Javascript editor of choice (VS Code/Sublime Text/Webstorm/Atom/etc)&lt;br /&gt;
:* [https://git-scm.com/downloads Git]&lt;br /&gt;
:* [https://nodejs.org/en/download/ NodeJS] (Node 10.X.X or higher)&lt;br /&gt;
:* [https://yarnpkg.com/ Yarn]&lt;br /&gt;
:* .NET Core 3.1. &lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
&lt;br /&gt;
# Fork {{{ARRNAME}}}&lt;br /&gt;
# Clone the repository into your development machine. [https://docs.github.com/en/free-pro-team@latest/github/getting-started-with-github *info*]&lt;br /&gt;
# Install the required Node Packages `yarn install`&lt;br /&gt;
# Start gulp to monitor your dev environment for any changes that need post processing using `yarn start` command.&lt;br /&gt;
# Build the project in Visual Studio, Setting startup project to `{{{ARRNAME}}}.Console` and framework to `netcoreapp31`&lt;br /&gt;
# Debug the project in Visual Studio&lt;br /&gt;
# Open http://localhost:{{{ARRPORT}}}&lt;br /&gt;
&lt;br /&gt;
=== Contributing Code ===&lt;br /&gt;
:* If you're adding a new, already requested feature, please comment on [https://github.com/{{{ARRNAME}}}/{{{ARRNAME}}}/issues Github Issues] so work is not duplicated (If you want to add something not already on there, please talk to us first)&lt;br /&gt;
:* Rebase from {{{ARRNAME}}}'s develop branch, don't merge&lt;br /&gt;
:* Make meaningful commits, or squash them&lt;br /&gt;
:* Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements&lt;br /&gt;
:* Reach out to us on the discord if you have any questions&lt;br /&gt;
:* Add tests (unit/integration)&lt;br /&gt;
:* Commit with *nix line endings for consistency (We checkout Windows and commit *nix)&lt;br /&gt;
:* One feature/bug fix per pull request to keep things clean and easy to understand&lt;br /&gt;
:* Use 4 spaces instead of tabs, this is the default for VS 2019 and WebStorm (to my knowledge)&lt;br /&gt;
&lt;br /&gt;
=== Pull Requesting ===&lt;br /&gt;
:* Only make pull requests to develop, never master, if you make a PR to master we'll comment on it and close it&lt;br /&gt;
:* You're probably going to get some comments or questions from us, they will be to ensure consistency and maintainability&lt;br /&gt;
:* We'll try to respond to pull requests as soon as possible, if its been a day or two, please reach out to us, we may have missed it&lt;br /&gt;
:* Each PR should come from its own [http://martinfowler.com/bliki/FeatureBranch.html feature branch] not develop in your fork, it should have a meaningful branch name (what is being added/fixed)&lt;br /&gt;
    - new-feature (Good)&lt;br /&gt;
    - fix-bug (Good)&lt;br /&gt;
    - patch (Bad)&lt;br /&gt;
    - develop (Bad)&lt;br /&gt;
&lt;br /&gt;
If you have any questions about any of this, please let us know.&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2912</id>
		<title>Template:Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2912"/>
		<updated>2021-01-01T03:34:55Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to Contribute ==&lt;br /&gt;
&lt;br /&gt;
We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
Setup guides, FAQ, the more information we have on the [[{{{ARRNAME}}}|wiki]] the better please contact one of Team {{{ARRNAME}}} for assistance with getting set up with the wiki.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
&lt;br /&gt;
=== Tools required ===&lt;br /&gt;
:* Visual Studio 2019 or higher [https://www.visualstudio.com/vs/ VisualStudio].  The [https://www.visualstudio.com/downloads/ community version] is free and works.&lt;br /&gt;
:* HTML/Javascript editor of choice (VS Code/Sublime Text/Webstorm/Atom/etc)&lt;br /&gt;
:* [https://git-scm.com/downloads Git]&lt;br /&gt;
:* [https://nodejs.org/en/download/ NodeJS] (Node 10.X.X or higher)&lt;br /&gt;
:* [https://yarnpkg.com/ Yarn]&lt;br /&gt;
:* .NET Core 3.1. &lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
&lt;br /&gt;
# Fork {{{ARRNAME}}}&lt;br /&gt;
# Clone the repository into your development machine. [https://docs.github.com/en/free-pro-team@latest/github/getting-started-with-github/quickstarts *info*]&lt;br /&gt;
# Install the required Node Packages `yarn install`&lt;br /&gt;
# Start gulp to monitor your dev environment for any changes that need post processing using `yarn start` command.&lt;br /&gt;
# Build the project in Visual Studio, Setting startup project to `{{{ARRNAME}}}.Console` and framework to `netcoreapp31`&lt;br /&gt;
# Debug the project in Visual Studio&lt;br /&gt;
# Open http://localhost:{{{ARRPORT}}}&lt;br /&gt;
&lt;br /&gt;
=== Contributing Code ===&lt;br /&gt;
:* If you're adding a new, already requested feature, please comment on [https://github.com/{{{ARRNAME}}}/{{{ARRNAME}}}/issues Github Issues] so work is not duplicated (If you want to add something not already on there, please talk to us first)&amp;lt;br&amp;gt;&lt;br /&gt;
:* Rebase from {{{ARRNAME}}}'s develop branch, don't merge&lt;br /&gt;
:* Make meaningful commits, or squash them&lt;br /&gt;
:* Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements&lt;br /&gt;
:* Reach out to us on the discord if you have any questions&lt;br /&gt;
:* Add tests (unit/integration)&lt;br /&gt;
:* Commit with *nix line endings for consistency (We checkout Windows and commit *nix)&lt;br /&gt;
:* One feature/bug fix per pull request to keep things clean and easy to understand&lt;br /&gt;
:* Use 4 spaces instead of tabs, this is the default for VS 2019 and WebStorm (to my knowledge)&lt;br /&gt;
&lt;br /&gt;
=== Pull Requesting ===&lt;br /&gt;
:* Only make pull requests to develop, never master, if you make a PR to master we'll comment on it and close it&lt;br /&gt;
:* You're probably going to get some comments or questions from us, they will be to ensure consistency and maintainability&lt;br /&gt;
:* We'll try to respond to pull requests as soon as possible, if its been a day or two, please reach out to us, we may have missed it&lt;br /&gt;
:* Each PR should come from its own [http://martinfowler.com/bliki/FeatureBranch.html feature branch] not develop in your fork, it should have a meaningful branch name (what is being added/fixed)&lt;br /&gt;
    - new-feature (Good)&lt;br /&gt;
    - fix-bug (Good)&lt;br /&gt;
    - patch (Bad)&lt;br /&gt;
    - develop (Bad)&lt;br /&gt;
&lt;br /&gt;
If you have any questions about any of this, please let us know.&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Readarr_Contributing&amp;diff=2911</id>
		<title>Readarr Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Readarr_Contributing&amp;diff=2911"/>
		<updated>2021-01-01T03:28:23Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: Created page with &amp;quot;{{Contributing|ARRNAME=Readarr|ARRPORT=8787}}&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Contributing|ARRNAME=Readarr|ARRPORT=8787}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Lidarr_Contributing&amp;diff=2910</id>
		<title>Lidarr Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Lidarr_Contributing&amp;diff=2910"/>
		<updated>2021-01-01T03:28:02Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: Created page with &amp;quot;{{Contributing|ARRNAME=Lidarr|ARRPORT=8686}}&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Contributing|ARRNAME=Lidarr|ARRPORT=8686}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Sonarr_Contributing&amp;diff=2909</id>
		<title>Sonarr Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Sonarr_Contributing&amp;diff=2909"/>
		<updated>2021-01-01T03:27:17Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: Created page with &amp;quot;{{Contributing|ARRNAME=Sonarr|ARRPORT=8989}}&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Contributing|ARRNAME=Sonarr|ARRPORT=8989}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2908</id>
		<title>WikiMap</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2908"/>
		<updated>2021-01-01T03:26:33Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* *ARR Pages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please use https://github.com/Servarr/Wiki to track issues&lt;br /&gt;
Please use this page for easy access to templates&lt;br /&gt;
&lt;br /&gt;
This page to act as an overall map of the wiki as many templates and sections are in use via transclusion.&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Templates ==&lt;br /&gt;
&lt;br /&gt;
# [[Template:Appdata Directory]]&lt;br /&gt;
# [[Template:Installation]]&lt;br /&gt;
# [[Template:Troubleshooting]]&lt;br /&gt;
# [[Template:Contributing]]&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous ==&lt;br /&gt;
# [[Sandbox]] &amp;lt;- Test code and do any testing here before sending it to live&lt;br /&gt;
# [[Useful Tools]]&lt;br /&gt;
# [[Cloud Setup|Rclone/Mergerfs/Gdrive setup &amp;amp; links]]&lt;br /&gt;
# [[Docker Guide]]&lt;br /&gt;
# [[Definitions]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Plex]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Network]]&lt;br /&gt;
# [[Clear Cache Cookies and Local Storage]]&lt;br /&gt;
# [[Troubleshooting Misc]]&lt;br /&gt;
# [[Appdata Directory Misc]]&lt;br /&gt;
# [[Installation Misc]]&lt;br /&gt;
# [[Docker on arm synology|Docker on ARM Synology]]&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Pages ==&lt;br /&gt;
* [[Radarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Sonarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Lidarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Readarr]]&lt;br /&gt;
&lt;br /&gt;
== API Documentation ==&lt;br /&gt;
* [https://radarr.video/docs/api/ Radarr]&lt;br /&gt;
&lt;br /&gt;
* Sonarr&lt;br /&gt;
&lt;br /&gt;
* Lidarr&lt;br /&gt;
&lt;br /&gt;
* Readarr&lt;br /&gt;
&lt;br /&gt;
== *ARR Pages ==&lt;br /&gt;
&amp;lt;section begin=radarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Radarr]]&lt;br /&gt;
**[[Radarr Installation]]&lt;br /&gt;
**[[Radarr Quick Start Guide]]&lt;br /&gt;
**[[Radarr Library|Radarr Library (Movies)]]&lt;br /&gt;
**[[Radarr Calendar]]&lt;br /&gt;
**[[Radarr Activity]]&lt;br /&gt;
**[[Radarr Settings]]&lt;br /&gt;
**[[Radarr System]]&lt;br /&gt;
**[[Radarr Troubleshooting]]&lt;br /&gt;
**[[Radarr FAQ]]&lt;br /&gt;
**[[Radarr Tips and Tricks]]&lt;br /&gt;
**[[Radarr Contributing]]&amp;lt;section end=radarr_wiki_pages /&amp;gt;&amp;lt;section begin=sonarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Sonarr]]&lt;br /&gt;
**[[Sonarr Installation]]&lt;br /&gt;
**[[Sonarr Quick Start Guide]]&lt;br /&gt;
**[[Sonarr Library|Sonarr Library (Series)]]&lt;br /&gt;
**[[Sonarr Calendar]]&lt;br /&gt;
**[[Sonarr Activity]]&lt;br /&gt;
**[[Sonarr Wanted]]&lt;br /&gt;
**[[Sonarr Settings]]&lt;br /&gt;
**[[Sonarr System]]&lt;br /&gt;
**[[Sonarr Troubleshooting]]&lt;br /&gt;
**[[Sonarr FAQ]]&lt;br /&gt;
**[[Sonarr Tips and Tricks]]&lt;br /&gt;
**[[Sonarr Contributing]]&amp;lt;section end=sonarr_wiki_pages /&amp;gt;&amp;lt;section begin=lidarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Lidarr]]&lt;br /&gt;
**[[Lidarr Installation]]&lt;br /&gt;
**[[Lidarr Quick Start Guide]]&lt;br /&gt;
**[[Lidarr Library|Lidarr Library (Artist)]]&lt;br /&gt;
**[[Lidarr Calendar]]&lt;br /&gt;
**[[Lidarr Activity]]&lt;br /&gt;
**[[Lidarr Wanted]]&lt;br /&gt;
**[[Lidarr Settings]]&lt;br /&gt;
**[[Lidarr System]]&lt;br /&gt;
**[[Lidarr Troubleshooting]]&lt;br /&gt;
**[[Lidarr FAQ]]&lt;br /&gt;
**[[Lidarr Tips and Tricks]]&lt;br /&gt;
**[[Lidarr Contributing]]&amp;lt;section end=lidarr_wiki_pages /&amp;gt;&amp;lt;section begin=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Readarr]]&lt;br /&gt;
**[[Readarr Installation]]&lt;br /&gt;
**[[Readarr Quick Start Guide]]&lt;br /&gt;
**[[Readarr Library|Readarr Library]]&lt;br /&gt;
**[[Readarr Calendar]]&lt;br /&gt;
**[[Readarr Activity]]&lt;br /&gt;
**[[Readarr Wanted]]&lt;br /&gt;
**[[Readarr Settings]]&lt;br /&gt;
**[[Readarr System]]&lt;br /&gt;
**[[Readarr Troubleshooting]]&lt;br /&gt;
**[[Readarr FAQ]]&lt;br /&gt;
**[[Readarr Tips and Tricks]]&lt;br /&gt;
**[[Readarr Contributing]]&amp;lt;section end=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== * ARR UI Pages ==&lt;br /&gt;
Note: All templates or sections are housed within their respective pages. To edit those templates click on the page then to the template page.&lt;br /&gt;
=== Movies/Series/Library ===&lt;br /&gt;
# [[Library]]&lt;br /&gt;
# [[Library Add New]]&lt;br /&gt;
# [[Library Import]]&lt;br /&gt;
# [[Library Discover]] &amp;lt;-- Radarr&lt;br /&gt;
# [[Library Mass Editor]] &amp;lt;-- Sonarr/Lidarr&lt;br /&gt;
# [[Library Bulk Monitoring Editor]] &amp;lt;--Season Pass/Album Studio/Bookshelf combined&lt;br /&gt;
# [[Library Unmapped Files]] &amp;lt;-- Lidarr/Readarr&lt;br /&gt;
&lt;br /&gt;
=== Calendar ===&lt;br /&gt;
# [[Calendar]]&lt;br /&gt;
&lt;br /&gt;
=== Activity ===&lt;br /&gt;
# [[Activity]]&lt;br /&gt;
# [[Activity Queue]]&lt;br /&gt;
# [[Activity History]]&lt;br /&gt;
# [[Activity Blacklist]]&lt;br /&gt;
&lt;br /&gt;
=== Wanted ===&lt;br /&gt;
# [[Wanted]]&lt;br /&gt;
# [[Wanted Missing]]&lt;br /&gt;
# [[Wanted Cutoff Unmet]]&lt;br /&gt;
&lt;br /&gt;
=== Settings ===&lt;br /&gt;
# [[Settings Media Management]]&lt;br /&gt;
# [[Settings Profiles]]&lt;br /&gt;
# [[Settings Quality]]&lt;br /&gt;
# [[Settings Custom Formats]]&lt;br /&gt;
# [[Settings Indexers]]&lt;br /&gt;
# [[Settings Download Clients]]&lt;br /&gt;
# [[Settings Lists]]&lt;br /&gt;
# [[Settings Connect]]&lt;br /&gt;
# [[Settings Metadata]]&lt;br /&gt;
# [[Settings Tags]]&lt;br /&gt;
# [[Settings General]]&lt;br /&gt;
# [[Settings UI]]&lt;br /&gt;
=== System ===&lt;br /&gt;
# [[System status|System Status]]&lt;br /&gt;
# [[System tasks|System Tasks]]&lt;br /&gt;
# [[System backup|System Backup]]&lt;br /&gt;
# [[System updates|System Updates]]&lt;br /&gt;
# [[System events|System Events]]&lt;br /&gt;
# [[System log files|System Log Files]]&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2907</id>
		<title>Template:Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2907"/>
		<updated>2021-01-01T03:24:55Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: Drazzilb moved page Contributing to Template:Contributing without leaving a redirect: Made into a template&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to Contribute ==&lt;br /&gt;
&lt;br /&gt;
We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
Setup guides, FAQ, the more information we have on the [[{{{ARRNAME}}}|wiki]] the better please contact one of Team {{{ARRNAME}}} for assistance with getting set up with the wiki.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
&lt;br /&gt;
=== Tools required ===&lt;br /&gt;
:* Visual Studio 2019 or higher [https://www.visualstudio.com/vs/ VisualStudio].  The [https://www.visualstudio.com/downloads/ community version] is free and works.&lt;br /&gt;
:* HTML/Javascript editor of choice (VS Code/Sublime Text/Webstorm/Atom/etc)&lt;br /&gt;
:* [https://git-scm.com/downloads Git]&lt;br /&gt;
:* [https://nodejs.org/en/download/ NodeJS] (Node 10.X.X or higher)&lt;br /&gt;
:* [https://yarnpkg.com/ Yarn]&lt;br /&gt;
:* .NET Core 3.1. &lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
&lt;br /&gt;
# Fork {{{ARRNAME}}}&lt;br /&gt;
# Clone the repository into your development machine. [https://help.github.com/articles/working-with-repositories *info*]&lt;br /&gt;
# Install the required Node Packages `yarn install`&lt;br /&gt;
# Start gulp to monitor your dev environment for any changes that need post processing using `yarn start` command.&lt;br /&gt;
# Build the project in Visual Studio, Setting startup project to `{{{ARRNAME}}}.Console` and framework to `netcoreapp31`&lt;br /&gt;
# Debug the project in Visual Studio&lt;br /&gt;
# Open http://localhost:{{{ARRPORT}}}&lt;br /&gt;
&lt;br /&gt;
=== Contributing Code ===&lt;br /&gt;
:* If you're adding a new, already requested feature, please comment on [https://github.com/{{{ARRNAME}}}/{{{ARRNAME}}}/issues Github Issues] so work is not duplicated (If you want to add something not already on there, please talk to us first)&amp;lt;br&amp;gt;&lt;br /&gt;
:* Rebase from {{{ARRNAME}}}'s develop branch, don't merge&lt;br /&gt;
:* Make meaningful commits, or squash them&lt;br /&gt;
:* Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements&lt;br /&gt;
:* Reach out to us on the discord if you have any questions&lt;br /&gt;
:* Add tests (unit/integration)&lt;br /&gt;
:* Commit with *nix line endings for consistency (We checkout Windows and commit *nix)&lt;br /&gt;
:* One feature/bug fix per pull request to keep things clean and easy to understand&lt;br /&gt;
:* Use 4 spaces instead of tabs, this is the default for VS 2019 and WebStorm (to my knowledge)&lt;br /&gt;
&lt;br /&gt;
=== Pull Requesting ===&lt;br /&gt;
:* Only make pull requests to develop, never master, if you make a PR to master we'll comment on it and close it&lt;br /&gt;
:* You're probably going to get some comments or questions from us, they will be to ensure consistency and maintainability&lt;br /&gt;
:* We'll try to respond to pull requests as soon as possible, if its been a day or two, please reach out to us, we may have missed it&lt;br /&gt;
:* Each PR should come from its own [http://martinfowler.com/bliki/FeatureBranch.html feature branch] not develop in your fork, it should have a meaningful branch name (what is being added/fixed)&lt;br /&gt;
    - new-feature (Good)&lt;br /&gt;
    - fix-bug (Good)&lt;br /&gt;
    - patch (Bad)&lt;br /&gt;
    - develop (Bad)&lt;br /&gt;
&lt;br /&gt;
If you have any questions about any of this, please let us know.&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2906</id>
		<title>WikiMap</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2906"/>
		<updated>2021-01-01T03:24:19Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Stand Alone Templates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please use https://github.com/Servarr/Wiki to track issues&lt;br /&gt;
Please use this page for easy access to templates&lt;br /&gt;
&lt;br /&gt;
This page to act as an overall map of the wiki as many templates and sections are in use via transclusion.&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Templates ==&lt;br /&gt;
&lt;br /&gt;
# [[Template:Appdata Directory]]&lt;br /&gt;
# [[Template:Installation]]&lt;br /&gt;
# [[Template:Troubleshooting]]&lt;br /&gt;
# [[Template:Contributing]]&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous ==&lt;br /&gt;
# [[Sandbox]] &amp;lt;- Test code and do any testing here before sending it to live&lt;br /&gt;
# [[Useful Tools]]&lt;br /&gt;
# [[Cloud Setup|Rclone/Mergerfs/Gdrive setup &amp;amp; links]]&lt;br /&gt;
# [[Docker Guide]]&lt;br /&gt;
# [[Definitions]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Plex]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Network]]&lt;br /&gt;
# [[Clear Cache Cookies and Local Storage]]&lt;br /&gt;
# [[Troubleshooting Misc]]&lt;br /&gt;
# [[Appdata Directory Misc]]&lt;br /&gt;
# [[Installation Misc]]&lt;br /&gt;
# [[Docker on arm synology|Docker on ARM Synology]]&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Pages ==&lt;br /&gt;
* [[Radarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Sonarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Lidarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Readarr]]&lt;br /&gt;
&lt;br /&gt;
== API Documentation ==&lt;br /&gt;
* [https://radarr.video/docs/api/ Radarr]&lt;br /&gt;
&lt;br /&gt;
* Sonarr&lt;br /&gt;
&lt;br /&gt;
* Lidarr&lt;br /&gt;
&lt;br /&gt;
* Readarr&lt;br /&gt;
&lt;br /&gt;
== *ARR Pages ==&lt;br /&gt;
&amp;lt;section begin=radarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Radarr]]&lt;br /&gt;
**[[Radarr Installation]]&lt;br /&gt;
**[[Radarr Quick Start Guide]]&lt;br /&gt;
**[[Radarr Library|Radarr Library (Movies)]]&lt;br /&gt;
**[[Radarr Calendar]]&lt;br /&gt;
**[[Radarr Activity]]&lt;br /&gt;
**[[Radarr Settings]]&lt;br /&gt;
**[[Radarr System]]&lt;br /&gt;
**[[Radarr Troubleshooting]]&lt;br /&gt;
**[[Radarr FAQ]]&lt;br /&gt;
**[[Radarr Tips and Tricks]]&lt;br /&gt;
**[[Radarr Contributing]]&amp;lt;section end=radarr_wiki_pages /&amp;gt;&amp;lt;section begin=sonarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Sonarr]]&lt;br /&gt;
**[[Sonarr Installation]]&lt;br /&gt;
**[[Sonarr Quick Start Guide]]&lt;br /&gt;
**[[Sonarr Library|Sonarr Library (Series)]]&lt;br /&gt;
**[[Sonarr Calendar]]&lt;br /&gt;
**[[Sonarr Activity]]&lt;br /&gt;
**[[Sonarr Wanted]]&lt;br /&gt;
**[[Sonarr Settings]]&lt;br /&gt;
**[[Sonarr System]]&lt;br /&gt;
**[[Sonarr Troubleshooting]]&lt;br /&gt;
**[[Sonarr FAQ]]&lt;br /&gt;
**[[Sonarr Contributing]]&lt;br /&gt;
**[[Sonarr Tips and Tricks]]&lt;br /&gt;
**[[Sonarr Contributing]]&amp;lt;section end=sonarr_wiki_pages /&amp;gt;&amp;lt;section begin=lidarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Lidarr]]&lt;br /&gt;
**[[Lidarr Installation]]&lt;br /&gt;
**[[Lidarr Quick Start Guide]]&lt;br /&gt;
**[[Lidarr Library|Lidarr Library (Artist)]]&lt;br /&gt;
**[[Lidarr Calendar]]&lt;br /&gt;
**[[Lidarr Activity]]&lt;br /&gt;
**[[Lidarr Wanted]]&lt;br /&gt;
**[[Lidarr Settings]]&lt;br /&gt;
**[[Lidarr System]]&lt;br /&gt;
**[[Lidarr Troubleshooting]]&lt;br /&gt;
**[[Lidarr FAQ]]&lt;br /&gt;
**[[Lidarr Tips and Tricks]]&lt;br /&gt;
**[[Lidarr Contributing]]&amp;lt;section end=lidarr_wiki_pages /&amp;gt;&amp;lt;section begin=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Readarr]]&lt;br /&gt;
**[[Readarr Installation]]&lt;br /&gt;
**[[Readarr Quick Start Guide]]&lt;br /&gt;
**[[Readarr Library|Readarr Library]]&lt;br /&gt;
**[[Readarr Calendar]]&lt;br /&gt;
**[[Readarr Activity]]&lt;br /&gt;
**[[Readarr Wanted]]&lt;br /&gt;
**[[Readarr Settings]]&lt;br /&gt;
**[[Readarr System]]&lt;br /&gt;
**[[Readarr Troubleshooting]]&lt;br /&gt;
**[[Readarr FAQ]]&lt;br /&gt;
**[[Readarr Tips and Tricks]]&lt;br /&gt;
**[[Readarr Contributing]]&amp;lt;section end=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== * ARR UI Pages ==&lt;br /&gt;
Note: All templates or sections are housed within their respective pages. To edit those templates click on the page then to the template page.&lt;br /&gt;
=== Movies/Series/Library ===&lt;br /&gt;
# [[Library]]&lt;br /&gt;
# [[Library Add New]]&lt;br /&gt;
# [[Library Import]]&lt;br /&gt;
# [[Library Discover]] &amp;lt;-- Radarr&lt;br /&gt;
# [[Library Mass Editor]] &amp;lt;-- Sonarr/Lidarr&lt;br /&gt;
# [[Library Bulk Monitoring Editor]] &amp;lt;--Season Pass/Album Studio/Bookshelf combined&lt;br /&gt;
# [[Library Unmapped Files]] &amp;lt;-- Lidarr/Readarr&lt;br /&gt;
&lt;br /&gt;
=== Calendar ===&lt;br /&gt;
# [[Calendar]]&lt;br /&gt;
&lt;br /&gt;
=== Activity ===&lt;br /&gt;
# [[Activity]]&lt;br /&gt;
# [[Activity Queue]]&lt;br /&gt;
# [[Activity History]]&lt;br /&gt;
# [[Activity Blacklist]]&lt;br /&gt;
&lt;br /&gt;
=== Wanted ===&lt;br /&gt;
# [[Wanted]]&lt;br /&gt;
# [[Wanted Missing]]&lt;br /&gt;
# [[Wanted Cutoff Unmet]]&lt;br /&gt;
&lt;br /&gt;
=== Settings ===&lt;br /&gt;
# [[Settings Media Management]]&lt;br /&gt;
# [[Settings Profiles]]&lt;br /&gt;
# [[Settings Quality]]&lt;br /&gt;
# [[Settings Custom Formats]]&lt;br /&gt;
# [[Settings Indexers]]&lt;br /&gt;
# [[Settings Download Clients]]&lt;br /&gt;
# [[Settings Lists]]&lt;br /&gt;
# [[Settings Connect]]&lt;br /&gt;
# [[Settings Metadata]]&lt;br /&gt;
# [[Settings Tags]]&lt;br /&gt;
# [[Settings General]]&lt;br /&gt;
# [[Settings UI]]&lt;br /&gt;
=== System ===&lt;br /&gt;
# [[System status|System Status]]&lt;br /&gt;
# [[System tasks|System Tasks]]&lt;br /&gt;
# [[System backup|System Backup]]&lt;br /&gt;
# [[System updates|System Updates]]&lt;br /&gt;
# [[System events|System Events]]&lt;br /&gt;
# [[System log files|System Log Files]]&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2905</id>
		<title>WikiMap</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2905"/>
		<updated>2021-01-01T03:24:03Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Miscellaneous */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please use https://github.com/Servarr/Wiki to track issues&lt;br /&gt;
Please use this page for easy access to templates&lt;br /&gt;
&lt;br /&gt;
This page to act as an overall map of the wiki as many templates and sections are in use via transclusion.&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Templates ==&lt;br /&gt;
&lt;br /&gt;
# [[Template:Appdata Directory]]&lt;br /&gt;
# [[Template:Installation]]&lt;br /&gt;
# [[Template:Troubleshooting]]&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous ==&lt;br /&gt;
# [[Sandbox]] &amp;lt;- Test code and do any testing here before sending it to live&lt;br /&gt;
# [[Useful Tools]]&lt;br /&gt;
# [[Cloud Setup|Rclone/Mergerfs/Gdrive setup &amp;amp; links]]&lt;br /&gt;
# [[Docker Guide]]&lt;br /&gt;
# [[Definitions]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Plex]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Network]]&lt;br /&gt;
# [[Clear Cache Cookies and Local Storage]]&lt;br /&gt;
# [[Troubleshooting Misc]]&lt;br /&gt;
# [[Appdata Directory Misc]]&lt;br /&gt;
# [[Installation Misc]]&lt;br /&gt;
# [[Docker on arm synology|Docker on ARM Synology]]&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Pages ==&lt;br /&gt;
* [[Radarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Sonarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Lidarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Readarr]]&lt;br /&gt;
&lt;br /&gt;
== API Documentation ==&lt;br /&gt;
* [https://radarr.video/docs/api/ Radarr]&lt;br /&gt;
&lt;br /&gt;
* Sonarr&lt;br /&gt;
&lt;br /&gt;
* Lidarr&lt;br /&gt;
&lt;br /&gt;
* Readarr&lt;br /&gt;
&lt;br /&gt;
== *ARR Pages ==&lt;br /&gt;
&amp;lt;section begin=radarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Radarr]]&lt;br /&gt;
**[[Radarr Installation]]&lt;br /&gt;
**[[Radarr Quick Start Guide]]&lt;br /&gt;
**[[Radarr Library|Radarr Library (Movies)]]&lt;br /&gt;
**[[Radarr Calendar]]&lt;br /&gt;
**[[Radarr Activity]]&lt;br /&gt;
**[[Radarr Settings]]&lt;br /&gt;
**[[Radarr System]]&lt;br /&gt;
**[[Radarr Troubleshooting]]&lt;br /&gt;
**[[Radarr FAQ]]&lt;br /&gt;
**[[Radarr Tips and Tricks]]&lt;br /&gt;
**[[Radarr Contributing]]&amp;lt;section end=radarr_wiki_pages /&amp;gt;&amp;lt;section begin=sonarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Sonarr]]&lt;br /&gt;
**[[Sonarr Installation]]&lt;br /&gt;
**[[Sonarr Quick Start Guide]]&lt;br /&gt;
**[[Sonarr Library|Sonarr Library (Series)]]&lt;br /&gt;
**[[Sonarr Calendar]]&lt;br /&gt;
**[[Sonarr Activity]]&lt;br /&gt;
**[[Sonarr Wanted]]&lt;br /&gt;
**[[Sonarr Settings]]&lt;br /&gt;
**[[Sonarr System]]&lt;br /&gt;
**[[Sonarr Troubleshooting]]&lt;br /&gt;
**[[Sonarr FAQ]]&lt;br /&gt;
**[[Sonarr Contributing]]&lt;br /&gt;
**[[Sonarr Tips and Tricks]]&lt;br /&gt;
**[[Sonarr Contributing]]&amp;lt;section end=sonarr_wiki_pages /&amp;gt;&amp;lt;section begin=lidarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Lidarr]]&lt;br /&gt;
**[[Lidarr Installation]]&lt;br /&gt;
**[[Lidarr Quick Start Guide]]&lt;br /&gt;
**[[Lidarr Library|Lidarr Library (Artist)]]&lt;br /&gt;
**[[Lidarr Calendar]]&lt;br /&gt;
**[[Lidarr Activity]]&lt;br /&gt;
**[[Lidarr Wanted]]&lt;br /&gt;
**[[Lidarr Settings]]&lt;br /&gt;
**[[Lidarr System]]&lt;br /&gt;
**[[Lidarr Troubleshooting]]&lt;br /&gt;
**[[Lidarr FAQ]]&lt;br /&gt;
**[[Lidarr Tips and Tricks]]&lt;br /&gt;
**[[Lidarr Contributing]]&amp;lt;section end=lidarr_wiki_pages /&amp;gt;&amp;lt;section begin=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Readarr]]&lt;br /&gt;
**[[Readarr Installation]]&lt;br /&gt;
**[[Readarr Quick Start Guide]]&lt;br /&gt;
**[[Readarr Library|Readarr Library]]&lt;br /&gt;
**[[Readarr Calendar]]&lt;br /&gt;
**[[Readarr Activity]]&lt;br /&gt;
**[[Readarr Wanted]]&lt;br /&gt;
**[[Readarr Settings]]&lt;br /&gt;
**[[Readarr System]]&lt;br /&gt;
**[[Readarr Troubleshooting]]&lt;br /&gt;
**[[Readarr FAQ]]&lt;br /&gt;
**[[Readarr Tips and Tricks]]&lt;br /&gt;
**[[Readarr Contributing]]&amp;lt;section end=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== * ARR UI Pages ==&lt;br /&gt;
Note: All templates or sections are housed within their respective pages. To edit those templates click on the page then to the template page.&lt;br /&gt;
=== Movies/Series/Library ===&lt;br /&gt;
# [[Library]]&lt;br /&gt;
# [[Library Add New]]&lt;br /&gt;
# [[Library Import]]&lt;br /&gt;
# [[Library Discover]] &amp;lt;-- Radarr&lt;br /&gt;
# [[Library Mass Editor]] &amp;lt;-- Sonarr/Lidarr&lt;br /&gt;
# [[Library Bulk Monitoring Editor]] &amp;lt;--Season Pass/Album Studio/Bookshelf combined&lt;br /&gt;
# [[Library Unmapped Files]] &amp;lt;-- Lidarr/Readarr&lt;br /&gt;
&lt;br /&gt;
=== Calendar ===&lt;br /&gt;
# [[Calendar]]&lt;br /&gt;
&lt;br /&gt;
=== Activity ===&lt;br /&gt;
# [[Activity]]&lt;br /&gt;
# [[Activity Queue]]&lt;br /&gt;
# [[Activity History]]&lt;br /&gt;
# [[Activity Blacklist]]&lt;br /&gt;
&lt;br /&gt;
=== Wanted ===&lt;br /&gt;
# [[Wanted]]&lt;br /&gt;
# [[Wanted Missing]]&lt;br /&gt;
# [[Wanted Cutoff Unmet]]&lt;br /&gt;
&lt;br /&gt;
=== Settings ===&lt;br /&gt;
# [[Settings Media Management]]&lt;br /&gt;
# [[Settings Profiles]]&lt;br /&gt;
# [[Settings Quality]]&lt;br /&gt;
# [[Settings Custom Formats]]&lt;br /&gt;
# [[Settings Indexers]]&lt;br /&gt;
# [[Settings Download Clients]]&lt;br /&gt;
# [[Settings Lists]]&lt;br /&gt;
# [[Settings Connect]]&lt;br /&gt;
# [[Settings Metadata]]&lt;br /&gt;
# [[Settings Tags]]&lt;br /&gt;
# [[Settings General]]&lt;br /&gt;
# [[Settings UI]]&lt;br /&gt;
=== System ===&lt;br /&gt;
# [[System status|System Status]]&lt;br /&gt;
# [[System tasks|System Tasks]]&lt;br /&gt;
# [[System backup|System Backup]]&lt;br /&gt;
# [[System updates|System Updates]]&lt;br /&gt;
# [[System events|System Events]]&lt;br /&gt;
# [[System log files|System Log Files]]&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Radarr_Contributing&amp;diff=2904</id>
		<title>Radarr Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Radarr_Contributing&amp;diff=2904"/>
		<updated>2021-01-01T03:23:38Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: Created page with &amp;quot;{{Contributing|ARRNAME=Radarr|ARRPORT=7979}}&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Contributing|ARRNAME=Radarr|ARRPORT=7979}}&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2903</id>
		<title>WikiMap</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2903"/>
		<updated>2021-01-01T03:22:08Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* *ARR Pages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please use https://github.com/Servarr/Wiki to track issues&lt;br /&gt;
Please use this page for easy access to templates&lt;br /&gt;
&lt;br /&gt;
This page to act as an overall map of the wiki as many templates and sections are in use via transclusion.&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Templates ==&lt;br /&gt;
&lt;br /&gt;
# [[Template:Appdata Directory]]&lt;br /&gt;
# [[Template:Installation]]&lt;br /&gt;
# [[Template:Troubleshooting]]&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous ==&lt;br /&gt;
# [[Sandbox]] &amp;lt;- Test code and do any testing here before sending it to live&lt;br /&gt;
# [[Useful Tools]]&lt;br /&gt;
# [[Cloud Setup|Rclone/Mergerfs/Gdrive setup &amp;amp; links]]&lt;br /&gt;
# [[Docker Guide]]&lt;br /&gt;
# [[Definitions]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Plex]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Network]]&lt;br /&gt;
# [[Clear Cache Cookies and Local Storage]]&lt;br /&gt;
# [[Troubleshooting Misc]]&lt;br /&gt;
# [[Appdata Directory Misc]]&lt;br /&gt;
# [[Installation Misc]]&lt;br /&gt;
# [[Docker on arm synology|Docker on ARM Synology]]&lt;br /&gt;
# [[Contributing]] &amp;lt;--- Will make into template&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Pages ==&lt;br /&gt;
* [[Radarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Sonarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Lidarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Readarr]]&lt;br /&gt;
&lt;br /&gt;
== API Documentation ==&lt;br /&gt;
* [https://radarr.video/docs/api/ Radarr]&lt;br /&gt;
&lt;br /&gt;
* Sonarr&lt;br /&gt;
&lt;br /&gt;
* Lidarr&lt;br /&gt;
&lt;br /&gt;
* Readarr&lt;br /&gt;
&lt;br /&gt;
== *ARR Pages ==&lt;br /&gt;
&amp;lt;section begin=radarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Radarr]]&lt;br /&gt;
**[[Radarr Installation]]&lt;br /&gt;
**[[Radarr Quick Start Guide]]&lt;br /&gt;
**[[Radarr Library|Radarr Library (Movies)]]&lt;br /&gt;
**[[Radarr Calendar]]&lt;br /&gt;
**[[Radarr Activity]]&lt;br /&gt;
**[[Radarr Settings]]&lt;br /&gt;
**[[Radarr System]]&lt;br /&gt;
**[[Radarr Troubleshooting]]&lt;br /&gt;
**[[Radarr FAQ]]&lt;br /&gt;
**[[Radarr Tips and Tricks]]&lt;br /&gt;
**[[Radarr Contributing]]&amp;lt;section end=radarr_wiki_pages /&amp;gt;&amp;lt;section begin=sonarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Sonarr]]&lt;br /&gt;
**[[Sonarr Installation]]&lt;br /&gt;
**[[Sonarr Quick Start Guide]]&lt;br /&gt;
**[[Sonarr Library|Sonarr Library (Series)]]&lt;br /&gt;
**[[Sonarr Calendar]]&lt;br /&gt;
**[[Sonarr Activity]]&lt;br /&gt;
**[[Sonarr Wanted]]&lt;br /&gt;
**[[Sonarr Settings]]&lt;br /&gt;
**[[Sonarr System]]&lt;br /&gt;
**[[Sonarr Troubleshooting]]&lt;br /&gt;
**[[Sonarr FAQ]]&lt;br /&gt;
**[[Sonarr Contributing]]&lt;br /&gt;
**[[Sonarr Tips and Tricks]]&lt;br /&gt;
**[[Sonarr Contributing]]&amp;lt;section end=sonarr_wiki_pages /&amp;gt;&amp;lt;section begin=lidarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Lidarr]]&lt;br /&gt;
**[[Lidarr Installation]]&lt;br /&gt;
**[[Lidarr Quick Start Guide]]&lt;br /&gt;
**[[Lidarr Library|Lidarr Library (Artist)]]&lt;br /&gt;
**[[Lidarr Calendar]]&lt;br /&gt;
**[[Lidarr Activity]]&lt;br /&gt;
**[[Lidarr Wanted]]&lt;br /&gt;
**[[Lidarr Settings]]&lt;br /&gt;
**[[Lidarr System]]&lt;br /&gt;
**[[Lidarr Troubleshooting]]&lt;br /&gt;
**[[Lidarr FAQ]]&lt;br /&gt;
**[[Lidarr Tips and Tricks]]&lt;br /&gt;
**[[Lidarr Contributing]]&amp;lt;section end=lidarr_wiki_pages /&amp;gt;&amp;lt;section begin=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Readarr]]&lt;br /&gt;
**[[Readarr Installation]]&lt;br /&gt;
**[[Readarr Quick Start Guide]]&lt;br /&gt;
**[[Readarr Library|Readarr Library]]&lt;br /&gt;
**[[Readarr Calendar]]&lt;br /&gt;
**[[Readarr Activity]]&lt;br /&gt;
**[[Readarr Wanted]]&lt;br /&gt;
**[[Readarr Settings]]&lt;br /&gt;
**[[Readarr System]]&lt;br /&gt;
**[[Readarr Troubleshooting]]&lt;br /&gt;
**[[Readarr FAQ]]&lt;br /&gt;
**[[Readarr Tips and Tricks]]&lt;br /&gt;
**[[Readarr Contributing]]&amp;lt;section end=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== * ARR UI Pages ==&lt;br /&gt;
Note: All templates or sections are housed within their respective pages. To edit those templates click on the page then to the template page.&lt;br /&gt;
=== Movies/Series/Library ===&lt;br /&gt;
# [[Library]]&lt;br /&gt;
# [[Library Add New]]&lt;br /&gt;
# [[Library Import]]&lt;br /&gt;
# [[Library Discover]] &amp;lt;-- Radarr&lt;br /&gt;
# [[Library Mass Editor]] &amp;lt;-- Sonarr/Lidarr&lt;br /&gt;
# [[Library Bulk Monitoring Editor]] &amp;lt;--Season Pass/Album Studio/Bookshelf combined&lt;br /&gt;
# [[Library Unmapped Files]] &amp;lt;-- Lidarr/Readarr&lt;br /&gt;
&lt;br /&gt;
=== Calendar ===&lt;br /&gt;
# [[Calendar]]&lt;br /&gt;
&lt;br /&gt;
=== Activity ===&lt;br /&gt;
# [[Activity]]&lt;br /&gt;
# [[Activity Queue]]&lt;br /&gt;
# [[Activity History]]&lt;br /&gt;
# [[Activity Blacklist]]&lt;br /&gt;
&lt;br /&gt;
=== Wanted ===&lt;br /&gt;
# [[Wanted]]&lt;br /&gt;
# [[Wanted Missing]]&lt;br /&gt;
# [[Wanted Cutoff Unmet]]&lt;br /&gt;
&lt;br /&gt;
=== Settings ===&lt;br /&gt;
# [[Settings Media Management]]&lt;br /&gt;
# [[Settings Profiles]]&lt;br /&gt;
# [[Settings Quality]]&lt;br /&gt;
# [[Settings Custom Formats]]&lt;br /&gt;
# [[Settings Indexers]]&lt;br /&gt;
# [[Settings Download Clients]]&lt;br /&gt;
# [[Settings Lists]]&lt;br /&gt;
# [[Settings Connect]]&lt;br /&gt;
# [[Settings Metadata]]&lt;br /&gt;
# [[Settings Tags]]&lt;br /&gt;
# [[Settings General]]&lt;br /&gt;
# [[Settings UI]]&lt;br /&gt;
=== System ===&lt;br /&gt;
# [[System status|System Status]]&lt;br /&gt;
# [[System tasks|System Tasks]]&lt;br /&gt;
# [[System backup|System Backup]]&lt;br /&gt;
# [[System updates|System Updates]]&lt;br /&gt;
# [[System events|System Events]]&lt;br /&gt;
# [[System log files|System Log Files]]&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2902</id>
		<title>Template:Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2902"/>
		<updated>2021-01-01T03:20:28Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to Contribute ==&lt;br /&gt;
&lt;br /&gt;
We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
Setup guides, FAQ, the more information we have on the [[{{{ARRNAME}}}|wiki]] the better please contact one of Team {{{ARRNAME}}} for assistance with getting set up with the wiki.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
&lt;br /&gt;
=== Tools required ===&lt;br /&gt;
:* Visual Studio 2019 or higher [https://www.visualstudio.com/vs/ VisualStudio].  The [https://www.visualstudio.com/downloads/ community version] is free and works.&lt;br /&gt;
:* HTML/Javascript editor of choice (VS Code/Sublime Text/Webstorm/Atom/etc)&lt;br /&gt;
:* [https://git-scm.com/downloads Git]&lt;br /&gt;
:* [https://nodejs.org/en/download/ NodeJS] (Node 10.X.X or higher)&lt;br /&gt;
:* [https://yarnpkg.com/ Yarn]&lt;br /&gt;
:* .NET Core 3.1. &lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
&lt;br /&gt;
# Fork {{{ARRNAME}}}&lt;br /&gt;
# Clone the repository into your development machine. [https://help.github.com/articles/working-with-repositories *info*]&lt;br /&gt;
# Install the required Node Packages `yarn install`&lt;br /&gt;
# Start gulp to monitor your dev environment for any changes that need post processing using `yarn start` command.&lt;br /&gt;
# Build the project in Visual Studio, Setting startup project to `{{{ARRNAME}}}.Console` and framework to `netcoreapp31`&lt;br /&gt;
# Debug the project in Visual Studio&lt;br /&gt;
# Open http://localhost:{{{ARRPORT}}}&lt;br /&gt;
&lt;br /&gt;
=== Contributing Code ===&lt;br /&gt;
:* If you're adding a new, already requested feature, please comment on [https://github.com/{{{ARRNAME}}}/{{{ARRNAME}}}/issues Github Issues] so work is not duplicated (If you want to add something not already on there, please talk to us first)&amp;lt;br&amp;gt;&lt;br /&gt;
:* Rebase from {{{ARRNAME}}}'s develop branch, don't merge&lt;br /&gt;
:* Make meaningful commits, or squash them&lt;br /&gt;
:* Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements&lt;br /&gt;
:* Reach out to us on the discord if you have any questions&lt;br /&gt;
:* Add tests (unit/integration)&lt;br /&gt;
:* Commit with *nix line endings for consistency (We checkout Windows and commit *nix)&lt;br /&gt;
:* One feature/bug fix per pull request to keep things clean and easy to understand&lt;br /&gt;
:* Use 4 spaces instead of tabs, this is the default for VS 2019 and WebStorm (to my knowledge)&lt;br /&gt;
&lt;br /&gt;
=== Pull Requesting ===&lt;br /&gt;
:* Only make pull requests to develop, never master, if you make a PR to master we'll comment on it and close it&lt;br /&gt;
:* You're probably going to get some comments or questions from us, they will be to ensure consistency and maintainability&lt;br /&gt;
:* We'll try to respond to pull requests as soon as possible, if its been a day or two, please reach out to us, we may have missed it&lt;br /&gt;
:* Each PR should come from its own [http://martinfowler.com/bliki/FeatureBranch.html feature branch] not develop in your fork, it should have a meaningful branch name (what is being added/fixed)&lt;br /&gt;
    - new-feature (Good)&lt;br /&gt;
    - fix-bug (Good)&lt;br /&gt;
    - patch (Bad)&lt;br /&gt;
    - develop (Bad)&lt;br /&gt;
&lt;br /&gt;
If you have any questions about any of this, please let us know.&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2901</id>
		<title>Template:Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2901"/>
		<updated>2021-01-01T03:18:43Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to Contribute ==&lt;br /&gt;
&lt;br /&gt;
We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
Setup guides, FAQ, the more information we have on the [[{{{ARRNAME}}}|wiki]] the better please contact one of Team {{{ARRNAME}}} for assistance with getting set up with the wiki.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
&lt;br /&gt;
=== Tools required ===&lt;br /&gt;
:* Visual Studio 2019 or higher (https://www.visualstudio.com/vs/).  The community version is free and works (https://www.visualstudio.com/downloads/). &amp;lt;br&amp;gt;&lt;br /&gt;
:* HTML/Javascript editor of choice (VS Code/Sublime Text/Webstorm/Atom/etc) &amp;lt;br&amp;gt;&lt;br /&gt;
:* [https://git-scm.com/downloads Git] &amp;lt;br&amp;gt;&lt;br /&gt;
:* [https://nodejs.org/en/download/ NodeJS] (Node 10.X.X or higher) &amp;lt;br&amp;gt;&lt;br /&gt;
:* [https://yarnpkg.com/ Yarn] &amp;lt;br&amp;gt;&lt;br /&gt;
:* .NET Core 3.1.  &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
&lt;br /&gt;
# Fork {{{ARRNAME}}}&lt;br /&gt;
# Clone the repository into your development machine. [https://help.github.com/articles/working-with-repositories *info*]&lt;br /&gt;
# Install the required Node Packages `yarn install`&lt;br /&gt;
# Start gulp to monitor your dev environment for any changes that need post processing using `yarn start` command.&lt;br /&gt;
# Build the project in Visual Studio, Setting startup project to `{{{ARRNAME}}}.Console` and framework to `netcoreapp31`&lt;br /&gt;
# Debug the project in Visual Studio&lt;br /&gt;
# Open http://localhost:{{{ARRPORT}}}&lt;br /&gt;
&lt;br /&gt;
=== Contributing Code ===&lt;br /&gt;
:* If you're adding a new, already requested feature, please comment on [https://github.com/{{{ARRNAME}}}/{{{ARRNAME}}}/issues Github Issues] so work is not duplicated (If you want to add something not already on there, please talk to us first)&amp;lt;br&amp;gt;&lt;br /&gt;
:* Rebase from {{{ARRNAME}}}'s develop branch, don't merge &amp;lt;br&amp;gt;&lt;br /&gt;
:* Make meaningful commits, or squash them &amp;lt;br&amp;gt;&lt;br /&gt;
:* Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements &amp;lt;br&amp;gt;&lt;br /&gt;
:* Reach out to us on the discord if you have any questions &amp;lt;br&amp;gt;&lt;br /&gt;
:* Add tests (unit/integration) &amp;lt;br&amp;gt;&lt;br /&gt;
:* Commit with *nix line endings for consistency (We checkout Windows and commit *nix) &amp;lt;br&amp;gt;&lt;br /&gt;
:* One feature/bug fix per pull request to keep things clean and easy to understand &amp;lt;br&amp;gt;&lt;br /&gt;
:* Use 4 spaces instead of tabs, this is the default for VS 2019 and WebStorm (to my knowledge) &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Pull Requesting ===&lt;br /&gt;
:* Only make pull requests to develop, never master, if you make a PR to master we'll comment on it and close it &amp;lt;br&amp;gt;&lt;br /&gt;
:* You're probably going to get some comments or questions from us, they will be to ensure consistency and maintainability &amp;lt;br&amp;gt;&lt;br /&gt;
:* We'll try to respond to pull requests as soon as possible, if its been a day or two, please reach out to us, we may have missed it &amp;lt;br&amp;gt;&lt;br /&gt;
:* Each PR should come from its own [http://martinfowler.com/bliki/FeatureBranch.html feature branch] not develop in your fork, it should have a meaningful branch name (what is being added/fixed) &amp;lt;br&amp;gt;&lt;br /&gt;
    - new-feature (Good)&lt;br /&gt;
    - fix-bug (Good)&lt;br /&gt;
    - patch (Bad)&lt;br /&gt;
    - develop (Bad)&lt;br /&gt;
&lt;br /&gt;
If you have any questions about any of this, please let us know.&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2900</id>
		<title>Template:Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2900"/>
		<updated>2021-01-01T03:16:05Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to Contribute ==&lt;br /&gt;
&lt;br /&gt;
We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
Setup guides, FAQ, the more information we have on the [[{{{ARRNAME}}}|wiki]] the better please contact one of Team {{{ARRNAME}}} for assistance with getting set up with the wiki.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
&lt;br /&gt;
=== Tools required ===&lt;br /&gt;
- Visual Studio 2019 or higher (https://www.visualstudio.com/vs/).  The community version is free and works (https://www.visualstudio.com/downloads/). &amp;lt;br&amp;gt;&lt;br /&gt;
- HTML/Javascript editor of choice (VS Code/Sublime Text/Webstorm/Atom/etc) &amp;lt;br&amp;gt;&lt;br /&gt;
- [https://git-scm.com/downloads Git] &amp;lt;br&amp;gt;&lt;br /&gt;
- [https://nodejs.org/en/download/ NodeJS] (Node 10.X.X or higher) &amp;lt;br&amp;gt;&lt;br /&gt;
- [https://yarnpkg.com/ Yarn] &amp;lt;br&amp;gt;&lt;br /&gt;
- .NET Core 3.1.  &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
&lt;br /&gt;
# Fork {{{ARRNAME}}}&lt;br /&gt;
# Clone the repository into your development machine. [https://help.github.com/articles/working-with-repositories *info*]&lt;br /&gt;
# Install the required Node Packages `yarn install`&lt;br /&gt;
# Start gulp to monitor your dev environment for any changes that need post processing using `yarn start` command.&lt;br /&gt;
# Build the project in Visual Studio, Setting startup project to `{{{ARRNAME}}}.Console` and framework to `netcoreapp31`&lt;br /&gt;
# Debug the project in Visual Studio&lt;br /&gt;
# Open http://localhost:{{{ARRPORT}}}&lt;br /&gt;
&lt;br /&gt;
=== Contributing Code ===&lt;br /&gt;
- If you're adding a new, already requested feature, please comment on [https://github.com/{{{ARRNAME}}}/{{{ARRNAME}}}/issues Github Issues] so work is not duplicated (If you want to add something not already on there, please talk to us first)&amp;lt;br&amp;gt;&lt;br /&gt;
- Rebase from {{{ARRNAME}}}'s develop branch, don't merge &amp;lt;br&amp;gt;&lt;br /&gt;
- Make meaningful commits, or squash them &amp;lt;br&amp;gt;&lt;br /&gt;
- Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements &amp;lt;br&amp;gt;&lt;br /&gt;
- Reach out to us on the discord if you have any questions &amp;lt;br&amp;gt;&lt;br /&gt;
- Add tests (unit/integration) &amp;lt;br&amp;gt;&lt;br /&gt;
- Commit with *nix line endings for consistency (We checkout Windows and commit *nix) &amp;lt;br&amp;gt;&lt;br /&gt;
- One feature/bug fix per pull request to keep things clean and easy to understand &amp;lt;br&amp;gt;&lt;br /&gt;
- Use 4 spaces instead of tabs, this is the default for VS 2019 and WebStorm (to my knowledge) &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Pull Requesting ===&lt;br /&gt;
- Only make pull requests to develop, never master, if you make a PR to master we'll comment on it and close it &amp;lt;br&amp;gt;&lt;br /&gt;
- You're probably going to get some comments or questions from us, they will be to ensure consistency and maintainability &amp;lt;br&amp;gt;&lt;br /&gt;
- We'll try to respond to pull requests as soon as possible, if its been a day or two, please reach out to us, we may have missed it &amp;lt;br&amp;gt;&lt;br /&gt;
- Each PR should come from its own [http://martinfowler.com/bliki/FeatureBranch.html feature branch] not develop in your fork, it should have a meaningful branch name (what is being added/fixed) &amp;lt;br&amp;gt;&lt;br /&gt;
    - new-feature (Good)&lt;br /&gt;
    - fix-bug (Good)&lt;br /&gt;
    - patch (Bad)&lt;br /&gt;
    - develop (Bad)&lt;br /&gt;
&lt;br /&gt;
If you have any questions about any of this, please let us know.&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2899</id>
		<title>Template:Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2899"/>
		<updated>2021-01-01T03:13:27Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to Contribute ==&lt;br /&gt;
&lt;br /&gt;
We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
Setup guides, FAQ, the more information we have on the [[{{{ARRNAME}}}|wiki]] the better please contact one of Team {{{ARRNAME}}} for assistance with getting set up with the wiki.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
&lt;br /&gt;
=== Tools required ===&lt;br /&gt;
* Visual Studio 2019 or higher (https://www.visualstudio.com/vs/).  The community version is free and works (https://www.visualstudio.com/downloads/). &lt;br /&gt;
* HTML/Javascript editor of choice (VS Code/Sublime Text/Webstorm/Atom/etc) &lt;br /&gt;
* [https://git-scm.com/downloads Git] &lt;br /&gt;
* [https://nodejs.org/en/download/ NodeJS] (Node 10.X.X or higher) &lt;br /&gt;
* [https://yarnpkg.com/ Yarn] &lt;br /&gt;
* .NET Core 3.1.  &lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
&lt;br /&gt;
# Fork {{{ARRNAME}}}&lt;br /&gt;
# Clone the repository into your development machine. [https://help.github.com/articles/working-with-repositories *info*]&lt;br /&gt;
# Install the required Node Packages `yarn install`&lt;br /&gt;
# Start gulp to monitor your dev environment for any changes that need post processing using `yarn start` command.&lt;br /&gt;
# Build the project in Visual Studio, Setting startup project to `{{{ARRNAME}}}.Console` and framework to `netcoreapp31`&lt;br /&gt;
# Debug the project in Visual Studio&lt;br /&gt;
# Open http://localhost:7878&lt;br /&gt;
&lt;br /&gt;
=== Contributing Code ===&lt;br /&gt;
* If you're adding a new, already requested feature, please comment on [https://github.com/{{{ARRNAME}}}/{{{ARRNAME}}}/issues Github Issues] so work is not duplicated (If you want to add something not already on there, please talk to us first)&lt;br /&gt;
* Rebase from {{{ARRNAME}}}'s develop branch, don't merge&lt;br /&gt;
* Make meaningful commits, or squash them&lt;br /&gt;
* Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements&lt;br /&gt;
* Reach out to us on the discord if you have any questions&lt;br /&gt;
* Add tests (unit/integration)&lt;br /&gt;
* Commit with *nix line endings for consistency (We checkout Windows and commit *nix)&lt;br /&gt;
* One feature/bug fix per pull request to keep things clean and easy to understand&lt;br /&gt;
* Use 4 spaces instead of tabs, this is the default for VS 2019 and WebStorm (to my knowledge)&lt;br /&gt;
&lt;br /&gt;
=== Pull Requesting ===&lt;br /&gt;
* Only make pull requests to develop, never master, if you make a PR to master we'll comment on it and close it&lt;br /&gt;
* You're probably going to get some comments or questions from us, they will be to ensure consistency and maintainability&lt;br /&gt;
* We'll try to respond to pull requests as soon as possible, if its been a day or two, please reach out to us, we may have missed it&lt;br /&gt;
* Each PR should come from its own [http://martinfowler.com/bliki/FeatureBranch.html feature branch] not develop in your fork, it should have a meaningful branch name (what is being added/fixed)&lt;br /&gt;
** new-feature (Good)&lt;br /&gt;
** fix-bug (Good)&lt;br /&gt;
** patch (Bad)&lt;br /&gt;
** develop (Bad)&lt;br /&gt;
&lt;br /&gt;
If you have any questions about any of this, please let us know.&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2898</id>
		<title>Template:Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2898"/>
		<updated>2021-01-01T03:11:27Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to Contribute ==&lt;br /&gt;
&lt;br /&gt;
We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
Setup guides, FAQ, the more information we have on the [[{{{ARRNAME}}}|wiki]] the better please contact one of Team {{{ARRNAME}}} for assistance with getting set up with the wiki.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
&lt;br /&gt;
=== Tools required ===&lt;br /&gt;
- Visual Studio 2019 or higher (https://www.visualstudio.com/vs/).  The community version is free and works (https://www.visualstudio.com/downloads/).&amp;lt;br&amp;gt;&lt;br /&gt;
- HTML/Javascript editor of choice (VS Code/Sublime Text/Webstorm/Atom/etc)&amp;lt;br&amp;gt;&lt;br /&gt;
- [https://git-scm.com/downloads Git]&amp;lt;br&amp;gt;&lt;br /&gt;
- [https://nodejs.org/en/download/ NodeJS] (Node 10.X.X or higher)&amp;lt;br&amp;gt;&lt;br /&gt;
- [https://yarnpkg.com/ Yarn]&amp;lt;br&amp;gt;&lt;br /&gt;
- .NET Core 3.1. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
&lt;br /&gt;
1. Fork {{{ARRNAME}}}&lt;br /&gt;
2. Clone the repository into your development machine. [https://help.github.com/articles/working-with-repositories *info*]&lt;br /&gt;
3. Install the required Node Packages `yarn install`&lt;br /&gt;
4. Start gulp to monitor your dev environment for any changes that need post processing using `yarn start` command.&lt;br /&gt;
5. Build the project in Visual Studio, Setting startup project to `{{{ARRNAME}}}.Console` and framework to `netcoreapp31`&lt;br /&gt;
6. Debug the project in Visual Studio&lt;br /&gt;
7. Open http://localhost:7878&lt;br /&gt;
&lt;br /&gt;
=== Contributing Code ===&lt;br /&gt;
- If you're adding a new, already requested feature, please comment on [https://github.com/{{{ARRNAME}}}/{{{ARRNAME}}}/issues Github Issues] so work is not duplicated (If you want to add something not already on there, please talk to us first)&lt;br /&gt;
- Rebase from {{{ARRNAME}}}'s develop branch, don't merge&lt;br /&gt;
- Make meaningful commits, or squash them&lt;br /&gt;
- Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements&lt;br /&gt;
- Reach out to us on the discord if you have any questions&lt;br /&gt;
- Add tests (unit/integration)&lt;br /&gt;
- Commit with *nix line endings for consistency (We checkout Windows and commit *nix)&lt;br /&gt;
- One feature/bug fix per pull request to keep things clean and easy to understand&lt;br /&gt;
- Use 4 spaces instead of tabs, this is the default for VS 2019 and WebStorm (to my knowledge)&lt;br /&gt;
&lt;br /&gt;
=== Pull Requesting ===&lt;br /&gt;
- Only make pull requests to develop, never master, if you make a PR to master we'll comment on it and close it&lt;br /&gt;
- You're probably going to get some comments or questions from us, they will be to ensure consistency and maintainability&lt;br /&gt;
- We'll try to respond to pull requests as soon as possible, if its been a day or two, please reach out to us, we may have missed it&lt;br /&gt;
- Each PR should come from its own [http://martinfowler.com/bliki/FeatureBranch.html feature branch] not develop in your fork, it should have a meaningful branch name (what is being added/fixed)&lt;br /&gt;
  - new-feature (Good)&lt;br /&gt;
  - fix-bug (Good)&lt;br /&gt;
  - patch (Bad)&lt;br /&gt;
  - develop (Bad)&lt;br /&gt;
&lt;br /&gt;
If you have any questions about any of this, please let us know.&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2897</id>
		<title>Template:Contributing</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Contributing&amp;diff=2897"/>
		<updated>2021-01-01T03:07:26Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: Created page with &amp;quot;== How to Contribute ==  We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.  == Documentation == Setup guides, F...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to Contribute ==&lt;br /&gt;
&lt;br /&gt;
We're always looking for people to help make {{{ARRNAME}}} even better, there are a number of ways to contribute.&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
Setup guides, FAQ, the more information we have on the [[{{{ARRNAME}}}|wiki]] the better please contact one of Team {{{ARRNAME}}} for assistance with getting set up with the wiki.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
&lt;br /&gt;
=== Tools required ===&lt;br /&gt;
- Visual Studio 2019 or higher (https://www.visualstudio.com/vs/).  The community version is free and works (https://www.visualstudio.com/downloads/).&lt;br /&gt;
- HTML/Javascript editor of choice (VS Code/Sublime Text/Webstorm/Atom/etc)&lt;br /&gt;
- [https://git-scm.com/downloads Git]&lt;br /&gt;
- [https://nodejs.org/en/download/ NodeJS] (Node 10.X.X or higher)&lt;br /&gt;
- [https://yarnpkg.com/ Yarn]&lt;br /&gt;
- .NET Core 3.1. &lt;br /&gt;
&lt;br /&gt;
=== Getting started ===&lt;br /&gt;
&lt;br /&gt;
1. Fork {{{ARRNAME}}}&lt;br /&gt;
2. Clone the repository into your development machine. [https://help.github.com/articles/working-with-repositories *info*]&lt;br /&gt;
3. Install the required Node Packages `yarn install`&lt;br /&gt;
4. Start gulp to monitor your dev environment for any changes that need post processing using `yarn start` command.&lt;br /&gt;
5. Build the project in Visual Studio, Setting startup project to `{{{ARRNAME}}}.Console` and framework to `netcoreapp31`&lt;br /&gt;
6. Debug the project in Visual Studio&lt;br /&gt;
7. Open http://localhost:7878&lt;br /&gt;
&lt;br /&gt;
### Contributing Code ###&lt;br /&gt;
- If you're adding a new, already requested feature, please comment on [https://github.com/{{{ARRNAME}}}/{{{ARRNAME}}}/issues Github Issues] so work is not duplicated (If you want to add something not already on there, please talk to us first)&lt;br /&gt;
- Rebase from {{{ARRNAME}}}'s develop branch, don't merge&lt;br /&gt;
- Make meaningful commits, or squash them&lt;br /&gt;
- Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements&lt;br /&gt;
- Reach out to us on the discord if you have any questions&lt;br /&gt;
- Add tests (unit/integration)&lt;br /&gt;
- Commit with *nix line endings for consistency (We checkout Windows and commit *nix)&lt;br /&gt;
- One feature/bug fix per pull request to keep things clean and easy to understand&lt;br /&gt;
- Use 4 spaces instead of tabs, this is the default for VS 2019 and WebStorm (to my knowledge)&lt;br /&gt;
&lt;br /&gt;
### Pull Requesting ###&lt;br /&gt;
- Only make pull requests to develop, never master, if you make a PR to master we'll comment on it and close it&lt;br /&gt;
- You're probably going to get some comments or questions from us, they will be to ensure consistency and maintainability&lt;br /&gt;
- We'll try to respond to pull requests as soon as possible, if its been a day or two, please reach out to us, we may have missed it&lt;br /&gt;
- Each PR should come from its own [http://martinfowler.com/bliki/FeatureBranch.html feature branch] not develop in your fork, it should have a meaningful branch name (what is being added/fixed)&lt;br /&gt;
  - new-feature (Good)&lt;br /&gt;
  - fix-bug (Good)&lt;br /&gt;
  - patch (Bad)&lt;br /&gt;
  - develop (Bad)&lt;br /&gt;
&lt;br /&gt;
If you have any questions about any of this, please let us know.&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Installation&amp;diff=2890</id>
		<title>Template:Installation</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Installation&amp;diff=2890"/>
		<updated>2020-12-26T15:47:40Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Debian / Ubuntu */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;&lt;br /&gt;
&amp;lt;templatedata&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
	&amp;quot;params&amp;quot;: {&lt;br /&gt;
		&amp;quot;ARRNAME&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Name of the ARR&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;Radarr&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;string&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true,&lt;br /&gt;
			&amp;quot;default&amp;quot;: &amp;quot;Fake Radarr&amp;quot;&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;RunArrCommandLinux&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Command to Start &amp;amp; Run ARR Linux&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;./opt/Radarr/Radarr -nobrowser -data=/home/radarr/.config/Radarr/&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;string&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;RunArrCommandOSX&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Command to Start &amp;amp; Run ARR OSX&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;./opt/Radarr/Radarr -nobrowser -data=/home/radarr/.config/Radarr/&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;string&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;ArrExecutableNameWin&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Executable Name for Windows&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;Radarr.exe&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;string&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;ArrDownloadLink&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Link to the Arr Downloads&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;url&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;ArrLinuxAutoStart&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Autostart file instructions&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;ARRPORT&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Port number for the ARR&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;Radarr: 7878, Sonarr: 8989, Lidarr: 8686, Readarr: 8787&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;number&amp;quot;,&lt;br /&gt;
			&amp;quot;default&amp;quot;: &amp;quot;7878&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;ARRNAME2&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Used for lowercase ARR names, this is not a required field only used if needed&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;radarr, sonarr, lidarr, readarr&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;string&amp;quot;&lt;br /&gt;
		}&lt;br /&gt;
	},&lt;br /&gt;
	&amp;quot;paramOrder&amp;quot;: [&lt;br /&gt;
		&amp;quot;ARRNAME&amp;quot;,&lt;br /&gt;
		&amp;quot;RunArrCommandLinux&amp;quot;,&lt;br /&gt;
		&amp;quot;RunArrCommandOSX&amp;quot;,&lt;br /&gt;
		&amp;quot;ArrExecutableNameWin&amp;quot;,&lt;br /&gt;
		&amp;quot;ArrDownloadLink&amp;quot;,&lt;br /&gt;
		&amp;quot;ArrLinuxAutoStart&amp;quot;,&lt;br /&gt;
		&amp;quot;ARRPORT&amp;quot;,&lt;br /&gt;
		&amp;quot;ARRNAME2&amp;quot;&lt;br /&gt;
	],&lt;br /&gt;
	&amp;quot;description&amp;quot;: &amp;quot;This template is expressly for the steps and processes of installing all the various ARR software on multiple different platforms&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/templatedata&amp;gt;&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installing =&lt;br /&gt;
== Windows ==&lt;br /&gt;
&lt;br /&gt;
== OSX ==&lt;br /&gt;
{{#lst::Installation Misc|{{{ARRNAME2}}}_osx_big_sur_installation}}&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
=== Debian / Ubuntu ===&lt;br /&gt;
Most of the &amp;quot;arr&amp;quot; software runs on mono, however newer version may run on .NET Core. If a .NET Core version is available, it will likely offer significant speed and resource enhancements. Some &amp;quot;arr&amp;quot; software supports repository based automatic installs, and some must be installed manually.&lt;br /&gt;
&lt;br /&gt;
{{#lst::Installation Misc|{{{ARRNAME2}}}_linux_ubuntu_NetCore_manual_installation}}&lt;br /&gt;
&lt;br /&gt;
===== Mono Install =====&lt;br /&gt;
{{#lst::Installation Misc|{{{ARRNAME2}}}_linux_ubuntu_repository_installation}}&lt;br /&gt;
&lt;br /&gt;
====== Manual Install (Mono) ======&lt;br /&gt;
Manual Installs need to have dependencies installed first.&lt;br /&gt;
&lt;br /&gt;
Mono:&lt;br /&gt;
 sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys FA7E0328081BFF6A14DA29AA6A19B38D3D831EF&lt;br /&gt;
 echo &amp;quot;deb https://download.mono-project.com/repo/ubuntu stable-focal main&amp;quot; | sudo tee /etc/apt/sources.list.d/mono-official-stable.list&lt;br /&gt;
 sudo apt update &amp;amp;&amp;amp; sudo apt install mono-devel&lt;br /&gt;
Curl&lt;br /&gt;
 sudo apt install curl&lt;br /&gt;
Mediainfo:&lt;br /&gt;
 sudo apt install mediainfo&lt;br /&gt;
sqlite3:&lt;br /&gt;
 sudo apt install sqlite3&lt;br /&gt;
&lt;br /&gt;
Now download the newest mono version release of {{{ARRNAME}}}:&lt;br /&gt;
 wget --content-disposition '{{{ARRPackageFileMono}}}'&lt;br /&gt;
&lt;br /&gt;
Uncompress:&lt;br /&gt;
 tar -xvzf {{{ARRNAME}}}*.tar.gz&lt;br /&gt;
Move to your preferred install location (typically &amp;lt;code&amp;gt;/opt/{{{ARRNAME}}}/&amp;lt;/code&amp;gt;&lt;br /&gt;
 sudo mv {{{ARRNAME}}}/ /opt&lt;br /&gt;
Finally, make sure you grant the needed permission to your install directory:&lt;br /&gt;
 sudo chown {{{ARRNAME2}}}:{{{ARRNAME2}}} /opt/{{{ARRNAME}}}&lt;br /&gt;
&lt;br /&gt;
You can start {{{ARRNAME}}} with the following command:&lt;br /&gt;
 /usr/bin/mono --debug /opt/{{{ARRNAME}}}/{{{ARRNAME}}}.exe -nobrowser&lt;br /&gt;
&lt;br /&gt;
=== Auto Start Using Systemd ===&lt;br /&gt;
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. &amp;lt;code&amp;gt;User&amp;lt;/code&amp;gt; account names and &amp;lt;code&amp;gt;Group&amp;lt;/code&amp;gt; names are typically all lowercase, as are the directory structures mapped to them as part of the home directory.&lt;br /&gt;
&lt;br /&gt;
==== Preparing the Unit Service File ====&lt;br /&gt;
Several items may need to be changed to match your installation:&lt;br /&gt;
&lt;br /&gt;
# &amp;lt;code&amp;gt;User&amp;lt;/code&amp;gt; should match the service account that {{{ARRNAME2}}} will run as.&lt;br /&gt;
# &amp;lt;code&amp;gt;Group&amp;lt;/code&amp;gt; should match the service account group that {{{ARRNAME2}}} will run as.&lt;br /&gt;
# &amp;lt;code&amp;gt;ExecStart&amp;lt;/code&amp;gt; has several items that should match your installation &amp;lt;code&amp;gt;/opt/{{{ARRNAME}}}/{{{ARRNAME}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
## Executable Path Default location is &amp;lt;code&amp;gt;/opt/{{{ARRNAME}}}/{{{ARRNAME}}}&amp;lt;/code&amp;gt;, but you may need to update if you installed {{{ARRNAME}}} elsewhere.&lt;br /&gt;
## Data Directory Default location is &amp;lt;code&amp;gt;-data=/home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/&amp;lt;/code&amp;gt;, but you may need to update if you want to keep your database and settings elsewhere.&lt;br /&gt;
## Mono Path (if Mono is being used) Default location is &amp;lt;code&amp;gt;/usr/bin/mono&amp;lt;/code&amp;gt;, but you may need to update if you installed Mono elsewhere.&lt;br /&gt;
&lt;br /&gt;
The unit service file should be named &amp;lt;code&amp;gt;{{{ARRNAME}}}.service&amp;lt;/code&amp;gt; and the best place for it is &amp;lt;code&amp;gt;/etc/systemd/system/&amp;lt;/code&amp;gt;. Alternative locations like &amp;lt;code&amp;gt;/usr/lib/systemd/system/&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;/lib/systemd/system/&amp;lt;/code&amp;gt; may depend on the distribution used.&lt;br /&gt;
&lt;br /&gt;
This example unit assumes that the &amp;lt;code&amp;gt;User&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;Group&amp;lt;/code&amp;gt; are both &amp;lt;code&amp;gt;{{{ARRNAME2}}}&amp;lt;/code&amp;gt;, {{{ARRNAME}}}'s executable is placed in &amp;lt;code&amp;gt;/opt/{{{ARRNAME}}}/&amp;lt;/code&amp;gt;, the data directory is placed in &amp;lt;code&amp;gt;/home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}&amp;lt;/code&amp;gt;, and the Mono executable (if being used) is placed in &amp;lt;code&amp;gt;/usr/bin/mono&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
{{#lst::Installation Misc|{{{ARRNAME2}}}_installation_unit_service_file}}&lt;br /&gt;
&lt;br /&gt;
==== Verify Directory Permissions ====&lt;br /&gt;
Ensure the &amp;lt;code&amp;gt;User&amp;lt;/code&amp;gt; that will be running {{{ARRNAME}}} has access to both the executable directory and data directory.&lt;br /&gt;
Running the command &amp;lt;code&amp;gt;ls -lad /directory/&amp;lt;/code&amp;gt; will show the permissions for that folder.&lt;br /&gt;
Example:&lt;br /&gt;
 $ ls -lad /opt/{{{ARRNAME}}}&lt;br /&gt;
 drwxr-xr-x 6 {{{ARRNAME2}}} {{{ARRNAME2}}} 24576 Nov 28 21:30 /opt/{{{ARRNAME}}}/&lt;br /&gt;
 $ ls -lad /home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/&lt;br /&gt;
 drwxr-xr-x 6 {{{ARRNAME2}}} {{{ARRNAME2}}} 24576 Nov 28 21:30 /home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/&lt;br /&gt;
&lt;br /&gt;
==== Enabling and starting the Unit Service File ====&lt;br /&gt;
Once you have created &amp;lt;code&amp;gt;{{{ARRNAME}}}.service&amp;lt;/code&amp;gt;, you will want to enable the service:&lt;br /&gt;
 sudo systemctl enable {{{ARRNAME}}}.service&lt;br /&gt;
&lt;br /&gt;
You are now ready to start {{{ARRNAME}}}. You can do so with the &amp;lt;code&amp;gt;start&amp;lt;/code&amp;gt; command:&lt;br /&gt;
 sudo systemctl start {{{ARRNAME}}}.service&lt;br /&gt;
&lt;br /&gt;
If you want to verify {{{ARRNAME}}} is running, you can run the &amp;lt;code&amp;gt;status&amp;lt;/code&amp;gt; command:&lt;br /&gt;
  $ sudo systemctl status {{{ARRNAME}}}.service&lt;br /&gt;
 ● {{{ARRNAME}}}.service - {{{ARRNAME}}}Service&lt;br /&gt;
    Loaded: loaded (/usr/lib/systemd/system/{{{ARRNAME}}}.service; enabled; vendor preset: disabled)&lt;br /&gt;
    Active: active (running) since Tue 2017-03-07 10:23:44 PST; 5min ago&lt;br /&gt;
  Main PID: 19978 ({{{ARRNAME}}})&lt;br /&gt;
     Tasks: 16 (limit: 4915)&lt;br /&gt;
    Memory: 114.6M&lt;br /&gt;
       CPU: 9.331s&lt;br /&gt;
    CGroup: /system.slice/{{{ARRNAME}}}.service&lt;br /&gt;
            └─19978 /opt/{{{ARRNAME}}}/{{{ARRNAME}}} -nobrowser -data=/home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/&lt;br /&gt;
 Mar 07 10:23:44 apollo systemd[1]: Started {{{ARRNAME}}} Service.&lt;br /&gt;
=== NGINX Reverse Proxy ===&lt;br /&gt;
A reverse proxy allows you to set up {{{ARRNAME}}} so you can access it from the web without using the port number. Rather than mydomain.com:{{{ARRPORT}}} you would use mydomain.com/{{{ARRNAME}}} instead.&lt;br /&gt;
&lt;br /&gt;
(Link to NGINX Install Wiki Page)&lt;br /&gt;
&lt;br /&gt;
Create a text file named {{{ARRNAME}}}.conf and place it in your default NGINX App directory, typically &amp;lt;code&amp;gt;/etc/nginx/conf.d/apps&amp;lt;/code&amp;gt;&lt;br /&gt;
# {{{ARRNAME}}} Reverse Proxy&lt;br /&gt;
# Be sure to set your Base-URL in {{{ARRNAME}}}&lt;br /&gt;
    location /{{{ARRNAME2}}} {&lt;br /&gt;
            proxy_pass http://127.0.0.1:{{{ARRPORT}}}/{{{ARRNAME2}}};&lt;br /&gt;
            proxy_set_header X-Real-IP $remote_addr;&lt;br /&gt;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;&lt;br /&gt;
            proxy_set_header X-Forwarded-Proto $scheme;&lt;br /&gt;
            proxy_http_version 1.1;&lt;br /&gt;
            proxy_no_cache $cookie_session;&lt;br /&gt;
            proxy_set_header Upgrade $http_upgrade;&lt;br /&gt;
            proxy_set_header Connection $http_connection;&lt;br /&gt;
            # Allow the {{{ARRNAME}}} API&lt;br /&gt;
            location /{{{ARRNAME2}}}/api { auth_request off;&lt;br /&gt;
                    proxy_pass http://127.0.0.1:{{{ARRPORT}}}/{{{ARRNAME2}}}/api;&lt;br /&gt;
            }&lt;br /&gt;
    }&lt;br /&gt;
Please note: It is important to ensure that the line &amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt; is accurate. The NGINX documentation recommends setting this to &amp;lt;code&amp;gt;Upgrade&amp;lt;/code&amp;gt; rather than &amp;lt;code&amp;gt;$http_connection;&amp;lt;/code&amp;gt; but this will NOT work.&lt;br /&gt;
&lt;br /&gt;
Once you have saved the file, test your NGINX config:&lt;br /&gt;
  sudo nginx -t&lt;br /&gt;
Which should show this:&lt;br /&gt;
  nginx: the configuration file /etc/nginx/nginx.conf syntax is ok&lt;br /&gt;
  nginx: configuration file /etc/nginx/nginx.conf test is successful&lt;br /&gt;
Now you can have NGINX reload it's configuration to use the new file:&lt;br /&gt;
  sudo nginx -s reload&lt;br /&gt;
Finally, make sure you add your URL Base to {{{ARRNAME}}}. This should match what you have next to the word Location in the {{{ARRNAME}}}.conf file, with the leading slash, likely this: &amp;lt;code&amp;gt;/{{{ARRNAME2}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
The URL base can be set here: https://wiki.servarr.com/{{{ARRNAME}}}_Settings#Host&lt;br /&gt;
&lt;br /&gt;
== NAS ==&lt;br /&gt;
=== FreeNAS ===&lt;br /&gt;
=== Qnap ===&lt;br /&gt;
=== Synology ===&lt;br /&gt;
* For those of you that are using Synology and would like to install {{{ARRNAME}}} head on over to TRaSH's Guides [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/#synology here]. &lt;br /&gt;
* This guide works directly with docker-compose as this is typically a much better/faster way to get you up and running&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;center&amp;gt;'''NOTE:'''&amp;lt;/center&amp;gt;&lt;br /&gt;
 If your Synology doesn't support dockers you will need to look at the packages that are fully maintained by   the Synology community. &lt;br /&gt;
 If you get any error messages concerning the Arr then you need to ask them to fix or update it as these are not maintained by any of the Arr Devs.&lt;br /&gt;
&lt;br /&gt;
== Docker ==&lt;br /&gt;
&lt;br /&gt;
== Docker on unRAID ==&lt;br /&gt;
* Installation of {{{ARRNAME}}} is quite simple when it comes to unRAID as they have made installing Docker containers a breeze.&lt;br /&gt;
&amp;lt;ol style=&amp;quot;list-style-type: decimal;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;Simply head on over to the community applications store on the top bar of your browser. &amp;lt;br /&amp;gt;&amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  [[File:unraid-install1.png|frameless|750px|alt=Community Applications|Communitty Applications]]&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;In the search field type in {{{ARRNAME}}}&amp;lt;br /&amp;gt;&lt;br /&gt;
  &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;Select which docker image you would like to install. There are several to choose from&amp;lt;br /&amp;gt;&lt;br /&gt;
  &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  [[File:{{{ARRNAME}}}-unraid-install.png|frameless|none|750px|alt=Installation Options|Installation Options]]&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Depending on which container you go with will determine the steps in which you take. Some containers come preloaded with volumes mapped already. This is really up to your liking how you would like your container volumes to be laid out. It is highly recommended to follow the guide listed [[Docker Guide|here]] for your volume mapping&amp;lt;br /&amp;gt;&lt;br /&gt;
  &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;p&amp;gt; Depending on which container you select you may recieve a pop up asking you to '''Choose A Branch To Install''' when in doubt go with the &amp;lt;code&amp;gt;Default :latest&amp;lt;/code&amp;gt; branch&amp;lt;/p&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Once you have selected which container you are going to go with, you will need to either create the volumes for {{{ARRNAME}}} to be able to use or simply use the pre-filled ones. (Highly recommended to remove the pre-filled and use your own, to remove the pre-filled ones).&amp;lt;br /&amp;gt;&amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt; To remove the pre-filled paths simply select the toggle in the upper right from '''Basic''' to '''Advanced''' view then scroll down to the pre-filled path and click '''Remove'''&amp;lt;/p&amp;gt;&lt;br /&gt;
[[File:unraid-install3.png|frameless|750px|alt=Toggle Advanced|Toggle Advanced]]&lt;br /&gt;
    &amp;lt;ol&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; To create new volumes simply select the &amp;lt;code&amp;gt; Add another Path, Port, Variable, Label or Device&amp;lt;/code&amp;gt; text at the bottom above the '''Apply''' button.&amp;lt;br /&amp;gt;&lt;br /&gt;
      &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Once the new window appears you will want to use the drop down box next to '''Config Type:''' and make sure that it is set to '''Path'''.&amp;lt;br /&amp;gt;&lt;br /&gt;
      &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; From here you will want to fill out all pertinant information:&amp;lt;br /&amp;gt;&lt;br /&gt;
      &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
      &amp;lt;ol&amp;gt;&lt;br /&gt;
        &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;'''Name:''' The name of this path, this can be any unique name more like a note to know what this path is for.&amp;lt;br /&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
        &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;'''Container Path:''' This will be the path that {{{ARRNAME}}} will see inside the container &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; is a favorite&amp;lt;br /&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
        &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;'''Host Path:''' This is the path to the host (unRAID) machine, This will be &amp;lt;code&amp;gt;/mnt/user/&amp;lt;Your User Share&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
        &amp;lt;p&amp;gt; '''NOTE''' If you follow the [[Docker Guide]] you will only need one Volume path to be made as all information that {{{ARRNAME}}} will need will be in one share &amp;lt;code&amp;gt;/mnt/user/data&amp;lt;/code&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
        &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; The last three items '''Default Value:''', '''Access Mode&amp;quot;''', and '''Description:''' Can be left alone.&amp;lt;br /&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
        &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Click '''ADD'''&amp;lt;br /&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
[[File:unraid-install4.png|frameless|750px|alt=Add New path|Add New Path]]&lt;br /&gt;
      &amp;lt;/ol&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Last thing to check is to make sure Host Port for {{{ARRPORT}}} is filled in with &amp;lt;code&amp;gt;{{{ARRPORT}}}&amp;lt;/code&amp;gt;, ''UNLESS'' This port causes any conflicts with any other container. If it does please choose a different port that is not in use.&amp;lt;br /&amp;gt;&lt;br /&gt;
      &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Click '''APPLY'''&amp;lt;br /&amp;gt;&lt;br /&gt;
      &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;/ol&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Now the {{{ARRNAME}}}'s container is being downloaded, once complete simply click the '''OK''' button at the bottom of the new pop up window&amp;lt;br /&amp;gt;&lt;br /&gt;
    &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Click '''DOCKER''' on the top row of your browser.&amp;lt;br /&amp;gt;&lt;br /&gt;
    &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Now all you will need to do is simply left click on your newly created container and select '''WebUI'''.&amp;lt;br /&amp;gt;&lt;br /&gt;
  &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  [[File:unraid-install2.png|frameless|none|250x240px|alt=Select WebUI|Select WebUI]]&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Now a new browser tab should show up with {{{ARRNAME}}} running in all its glory. '''ENJOY'''&amp;lt;br /&amp;gt;&lt;br /&gt;
  &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Template:Installation&amp;diff=2889</id>
		<title>Template:Installation</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Template:Installation&amp;diff=2889"/>
		<updated>2020-12-26T15:45:56Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Debian / Ubuntu */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;&lt;br /&gt;
&amp;lt;templatedata&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
	&amp;quot;params&amp;quot;: {&lt;br /&gt;
		&amp;quot;ARRNAME&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Name of the ARR&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;Radarr&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;string&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true,&lt;br /&gt;
			&amp;quot;default&amp;quot;: &amp;quot;Fake Radarr&amp;quot;&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;RunArrCommandLinux&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Command to Start &amp;amp; Run ARR Linux&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;./opt/Radarr/Radarr -nobrowser -data=/home/radarr/.config/Radarr/&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;string&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;RunArrCommandOSX&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Command to Start &amp;amp; Run ARR OSX&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;./opt/Radarr/Radarr -nobrowser -data=/home/radarr/.config/Radarr/&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;string&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;ArrExecutableNameWin&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Executable Name for Windows&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;Radarr.exe&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;string&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;ArrDownloadLink&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Link to the Arr Downloads&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;url&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;ArrLinuxAutoStart&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Autostart file instructions&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;ARRPORT&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Port number for the ARR&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;Radarr: 7878, Sonarr: 8989, Lidarr: 8686, Readarr: 8787&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;number&amp;quot;,&lt;br /&gt;
			&amp;quot;default&amp;quot;: &amp;quot;7878&amp;quot;,&lt;br /&gt;
			&amp;quot;required&amp;quot;: true&lt;br /&gt;
		},&lt;br /&gt;
		&amp;quot;ARRNAME2&amp;quot;: {&lt;br /&gt;
			&amp;quot;description&amp;quot;: &amp;quot;Used for lowercase ARR names, this is not a required field only used if needed&amp;quot;,&lt;br /&gt;
			&amp;quot;example&amp;quot;: &amp;quot;radarr, sonarr, lidarr, readarr&amp;quot;,&lt;br /&gt;
			&amp;quot;type&amp;quot;: &amp;quot;string&amp;quot;&lt;br /&gt;
		}&lt;br /&gt;
	},&lt;br /&gt;
	&amp;quot;paramOrder&amp;quot;: [&lt;br /&gt;
		&amp;quot;ARRNAME&amp;quot;,&lt;br /&gt;
		&amp;quot;RunArrCommandLinux&amp;quot;,&lt;br /&gt;
		&amp;quot;RunArrCommandOSX&amp;quot;,&lt;br /&gt;
		&amp;quot;ArrExecutableNameWin&amp;quot;,&lt;br /&gt;
		&amp;quot;ArrDownloadLink&amp;quot;,&lt;br /&gt;
		&amp;quot;ArrLinuxAutoStart&amp;quot;,&lt;br /&gt;
		&amp;quot;ARRPORT&amp;quot;,&lt;br /&gt;
		&amp;quot;ARRNAME2&amp;quot;&lt;br /&gt;
	],&lt;br /&gt;
	&amp;quot;description&amp;quot;: &amp;quot;This template is expressly for the steps and processes of installing all the various ARR software on multiple different platforms&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/templatedata&amp;gt;&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Installing =&lt;br /&gt;
== Windows ==&lt;br /&gt;
&lt;br /&gt;
== OSX ==&lt;br /&gt;
{{#lst::Installation Misc|{{{ARRNAME2}}}_osx_big_sur_installation}}&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
=== Debian / Ubuntu ===&lt;br /&gt;
Most of the &amp;quot;arr&amp;quot; software runs on mono, however newer version may run on .NET Core. If a .NET Core version is available, it will likely offer significant speed and resource enhancements. Some &amp;quot;arr&amp;quot; software supports repository based automatic installs, and some must be installed manually.&lt;br /&gt;
&lt;br /&gt;
===== Mono Install =====&lt;br /&gt;
{{#lst::Installation Misc|{{{ARRNAME2}}}_linux_ubuntu_repository_installation}}&lt;br /&gt;
&lt;br /&gt;
{{#lst::Installation Misc|{{{ARRNAME2}}}_linux_ubuntu_NetCore_manual_installation}}&lt;br /&gt;
&lt;br /&gt;
====== Manual Install (Mono) ======&lt;br /&gt;
Manual Installs need to have dependencies installed first.&lt;br /&gt;
&lt;br /&gt;
Mono:&lt;br /&gt;
 sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys FA7E0328081BFF6A14DA29AA6A19B38D3D831EF&lt;br /&gt;
 echo &amp;quot;deb https://download.mono-project.com/repo/ubuntu stable-focal main&amp;quot; | sudo tee /etc/apt/sources.list.d/mono-official-stable.list&lt;br /&gt;
 sudo apt update &amp;amp;&amp;amp; sudo apt install mono-devel&lt;br /&gt;
Curl&lt;br /&gt;
 sudo apt install curl&lt;br /&gt;
Mediainfo:&lt;br /&gt;
 sudo apt install mediainfo&lt;br /&gt;
sqlite3:&lt;br /&gt;
 sudo apt install sqlite3&lt;br /&gt;
&lt;br /&gt;
Now download the newest mono version release of {{{ARRNAME}}}:&lt;br /&gt;
 wget --content-disposition '{{{ARRPackageFileMono}}}'&lt;br /&gt;
&lt;br /&gt;
Uncompress:&lt;br /&gt;
 tar -xvzf {{{ARRNAME}}}*.tar.gz&lt;br /&gt;
Move to your preferred install location (typically &amp;lt;code&amp;gt;/opt/{{{ARRNAME}}}/&amp;lt;/code&amp;gt;&lt;br /&gt;
 sudo mv {{{ARRNAME}}}/ /opt&lt;br /&gt;
Finally, make sure you grant the needed permission to your install directory:&lt;br /&gt;
 sudo chown {{{ARRNAME2}}}:{{{ARRNAME2}}} /opt/{{{ARRNAME}}}&lt;br /&gt;
&lt;br /&gt;
You can start {{{ARRNAME}}} with the following command:&lt;br /&gt;
 /usr/bin/mono --debug /opt/{{{ARRNAME}}}/{{{ARRNAME}}}.exe -nobrowser&lt;br /&gt;
&lt;br /&gt;
=== Auto Start Using Systemd ===&lt;br /&gt;
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. &amp;lt;code&amp;gt;User&amp;lt;/code&amp;gt; account names and &amp;lt;code&amp;gt;Group&amp;lt;/code&amp;gt; names are typically all lowercase, as are the directory structures mapped to them as part of the home directory.&lt;br /&gt;
&lt;br /&gt;
==== Preparing the Unit Service File ====&lt;br /&gt;
Several items may need to be changed to match your installation:&lt;br /&gt;
&lt;br /&gt;
# &amp;lt;code&amp;gt;User&amp;lt;/code&amp;gt; should match the service account that {{{ARRNAME2}}} will run as.&lt;br /&gt;
# &amp;lt;code&amp;gt;Group&amp;lt;/code&amp;gt; should match the service account group that {{{ARRNAME2}}} will run as.&lt;br /&gt;
# &amp;lt;code&amp;gt;ExecStart&amp;lt;/code&amp;gt; has several items that should match your installation &amp;lt;code&amp;gt;/opt/{{{ARRNAME}}}/{{{ARRNAME}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
## Executable Path Default location is &amp;lt;code&amp;gt;/opt/{{{ARRNAME}}}/{{{ARRNAME}}}&amp;lt;/code&amp;gt;, but you may need to update if you installed {{{ARRNAME}}} elsewhere.&lt;br /&gt;
## Data Directory Default location is &amp;lt;code&amp;gt;-data=/home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/&amp;lt;/code&amp;gt;, but you may need to update if you want to keep your database and settings elsewhere.&lt;br /&gt;
## Mono Path (if Mono is being used) Default location is &amp;lt;code&amp;gt;/usr/bin/mono&amp;lt;/code&amp;gt;, but you may need to update if you installed Mono elsewhere.&lt;br /&gt;
&lt;br /&gt;
The unit service file should be named &amp;lt;code&amp;gt;{{{ARRNAME}}}.service&amp;lt;/code&amp;gt; and the best place for it is &amp;lt;code&amp;gt;/etc/systemd/system/&amp;lt;/code&amp;gt;. Alternative locations like &amp;lt;code&amp;gt;/usr/lib/systemd/system/&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;/lib/systemd/system/&amp;lt;/code&amp;gt; may depend on the distribution used.&lt;br /&gt;
&lt;br /&gt;
This example unit assumes that the &amp;lt;code&amp;gt;User&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;Group&amp;lt;/code&amp;gt; are both &amp;lt;code&amp;gt;{{{ARRNAME2}}}&amp;lt;/code&amp;gt;, {{{ARRNAME}}}'s executable is placed in &amp;lt;code&amp;gt;/opt/{{{ARRNAME}}}/&amp;lt;/code&amp;gt;, the data directory is placed in &amp;lt;code&amp;gt;/home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}&amp;lt;/code&amp;gt;, and the Mono executable (if being used) is placed in &amp;lt;code&amp;gt;/usr/bin/mono&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
{{#lst::Installation Misc|{{{ARRNAME2}}}_installation_unit_service_file}}&lt;br /&gt;
&lt;br /&gt;
==== Verify Directory Permissions ====&lt;br /&gt;
Ensure the &amp;lt;code&amp;gt;User&amp;lt;/code&amp;gt; that will be running {{{ARRNAME}}} has access to both the executable directory and data directory.&lt;br /&gt;
Running the command &amp;lt;code&amp;gt;ls -lad /directory/&amp;lt;/code&amp;gt; will show the permissions for that folder.&lt;br /&gt;
Example:&lt;br /&gt;
 $ ls -lad /opt/{{{ARRNAME}}}&lt;br /&gt;
 drwxr-xr-x 6 {{{ARRNAME2}}} {{{ARRNAME2}}} 24576 Nov 28 21:30 /opt/{{{ARRNAME}}}/&lt;br /&gt;
 $ ls -lad /home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/&lt;br /&gt;
 drwxr-xr-x 6 {{{ARRNAME2}}} {{{ARRNAME2}}} 24576 Nov 28 21:30 /home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/&lt;br /&gt;
&lt;br /&gt;
==== Enabling and starting the Unit Service File ====&lt;br /&gt;
Once you have created &amp;lt;code&amp;gt;{{{ARRNAME}}}.service&amp;lt;/code&amp;gt;, you will want to enable the service:&lt;br /&gt;
 sudo systemctl enable {{{ARRNAME}}}.service&lt;br /&gt;
&lt;br /&gt;
You are now ready to start {{{ARRNAME}}}. You can do so with the &amp;lt;code&amp;gt;start&amp;lt;/code&amp;gt; command:&lt;br /&gt;
 sudo systemctl start {{{ARRNAME}}}.service&lt;br /&gt;
&lt;br /&gt;
If you want to verify {{{ARRNAME}}} is running, you can run the &amp;lt;code&amp;gt;status&amp;lt;/code&amp;gt; command:&lt;br /&gt;
  $ sudo systemctl status {{{ARRNAME}}}.service&lt;br /&gt;
 ● {{{ARRNAME}}}.service - {{{ARRNAME}}}Service&lt;br /&gt;
    Loaded: loaded (/usr/lib/systemd/system/{{{ARRNAME}}}.service; enabled; vendor preset: disabled)&lt;br /&gt;
    Active: active (running) since Tue 2017-03-07 10:23:44 PST; 5min ago&lt;br /&gt;
  Main PID: 19978 ({{{ARRNAME}}})&lt;br /&gt;
     Tasks: 16 (limit: 4915)&lt;br /&gt;
    Memory: 114.6M&lt;br /&gt;
       CPU: 9.331s&lt;br /&gt;
    CGroup: /system.slice/{{{ARRNAME}}}.service&lt;br /&gt;
            └─19978 /opt/{{{ARRNAME}}}/{{{ARRNAME}}} -nobrowser -data=/home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/&lt;br /&gt;
 Mar 07 10:23:44 apollo systemd[1]: Started {{{ARRNAME}}} Service.&lt;br /&gt;
=== NGINX Reverse Proxy ===&lt;br /&gt;
A reverse proxy allows you to set up {{{ARRNAME}}} so you can access it from the web without using the port number. Rather than mydomain.com:{{{ARRPORT}}} you would use mydomain.com/{{{ARRNAME}}} instead.&lt;br /&gt;
&lt;br /&gt;
(Link to NGINX Install Wiki Page)&lt;br /&gt;
&lt;br /&gt;
Create a text file named {{{ARRNAME}}}.conf and place it in your default NGINX App directory, typically &amp;lt;code&amp;gt;/etc/nginx/conf.d/apps&amp;lt;/code&amp;gt;&lt;br /&gt;
# {{{ARRNAME}}} Reverse Proxy&lt;br /&gt;
# Be sure to set your Base-URL in {{{ARRNAME}}}&lt;br /&gt;
    location /{{{ARRNAME2}}} {&lt;br /&gt;
            proxy_pass http://127.0.0.1:{{{ARRPORT}}}/{{{ARRNAME2}}};&lt;br /&gt;
            proxy_set_header X-Real-IP $remote_addr;&lt;br /&gt;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;&lt;br /&gt;
            proxy_set_header X-Forwarded-Proto $scheme;&lt;br /&gt;
            proxy_http_version 1.1;&lt;br /&gt;
            proxy_no_cache $cookie_session;&lt;br /&gt;
            proxy_set_header Upgrade $http_upgrade;&lt;br /&gt;
            proxy_set_header Connection $http_connection;&lt;br /&gt;
            # Allow the {{{ARRNAME}}} API&lt;br /&gt;
            location /{{{ARRNAME2}}}/api { auth_request off;&lt;br /&gt;
                    proxy_pass http://127.0.0.1:{{{ARRPORT}}}/{{{ARRNAME2}}}/api;&lt;br /&gt;
            }&lt;br /&gt;
    }&lt;br /&gt;
Please note: It is important to ensure that the line &amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt; is accurate. The NGINX documentation recommends setting this to &amp;lt;code&amp;gt;Upgrade&amp;lt;/code&amp;gt; rather than &amp;lt;code&amp;gt;$http_connection;&amp;lt;/code&amp;gt; but this will NOT work.&lt;br /&gt;
&lt;br /&gt;
Once you have saved the file, test your NGINX config:&lt;br /&gt;
  sudo nginx -t&lt;br /&gt;
Which should show this:&lt;br /&gt;
  nginx: the configuration file /etc/nginx/nginx.conf syntax is ok&lt;br /&gt;
  nginx: configuration file /etc/nginx/nginx.conf test is successful&lt;br /&gt;
Now you can have NGINX reload it's configuration to use the new file:&lt;br /&gt;
  sudo nginx -s reload&lt;br /&gt;
Finally, make sure you add your URL Base to {{{ARRNAME}}}. This should match what you have next to the word Location in the {{{ARRNAME}}}.conf file, with the leading slash, likely this: &amp;lt;code&amp;gt;/{{{ARRNAME2}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
The URL base can be set here: https://wiki.servarr.com/{{{ARRNAME}}}_Settings#Host&lt;br /&gt;
&lt;br /&gt;
== NAS ==&lt;br /&gt;
=== FreeNAS ===&lt;br /&gt;
=== Qnap ===&lt;br /&gt;
=== Synology ===&lt;br /&gt;
* For those of you that are using Synology and would like to install {{{ARRNAME}}} head on over to TRaSH's Guides [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/#synology here]. &lt;br /&gt;
* This guide works directly with docker-compose as this is typically a much better/faster way to get you up and running&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;center&amp;gt;'''NOTE:'''&amp;lt;/center&amp;gt;&lt;br /&gt;
 If your Synology doesn't support dockers you will need to look at the packages that are fully maintained by   the Synology community. &lt;br /&gt;
 If you get any error messages concerning the Arr then you need to ask them to fix or update it as these are not maintained by any of the Arr Devs.&lt;br /&gt;
&lt;br /&gt;
== Docker ==&lt;br /&gt;
&lt;br /&gt;
== Docker on unRAID ==&lt;br /&gt;
* Installation of {{{ARRNAME}}} is quite simple when it comes to unRAID as they have made installing Docker containers a breeze.&lt;br /&gt;
&amp;lt;ol style=&amp;quot;list-style-type: decimal;&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;Simply head on over to the community applications store on the top bar of your browser. &amp;lt;br /&amp;gt;&amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  [[File:unraid-install1.png|frameless|750px|alt=Community Applications|Communitty Applications]]&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;In the search field type in {{{ARRNAME}}}&amp;lt;br /&amp;gt;&lt;br /&gt;
  &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;Select which docker image you would like to install. There are several to choose from&amp;lt;br /&amp;gt;&lt;br /&gt;
  &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  [[File:{{{ARRNAME}}}-unraid-install.png|frameless|none|750px|alt=Installation Options|Installation Options]]&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Depending on which container you go with will determine the steps in which you take. Some containers come preloaded with volumes mapped already. This is really up to your liking how you would like your container volumes to be laid out. It is highly recommended to follow the guide listed [[Docker Guide|here]] for your volume mapping&amp;lt;br /&amp;gt;&lt;br /&gt;
  &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;p&amp;gt; Depending on which container you select you may recieve a pop up asking you to '''Choose A Branch To Install''' when in doubt go with the &amp;lt;code&amp;gt;Default :latest&amp;lt;/code&amp;gt; branch&amp;lt;/p&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Once you have selected which container you are going to go with, you will need to either create the volumes for {{{ARRNAME}}} to be able to use or simply use the pre-filled ones. (Highly recommended to remove the pre-filled and use your own, to remove the pre-filled ones).&amp;lt;br /&amp;gt;&amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt; To remove the pre-filled paths simply select the toggle in the upper right from '''Basic''' to '''Advanced''' view then scroll down to the pre-filled path and click '''Remove'''&amp;lt;/p&amp;gt;&lt;br /&gt;
[[File:unraid-install3.png|frameless|750px|alt=Toggle Advanced|Toggle Advanced]]&lt;br /&gt;
    &amp;lt;ol&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; To create new volumes simply select the &amp;lt;code&amp;gt; Add another Path, Port, Variable, Label or Device&amp;lt;/code&amp;gt; text at the bottom above the '''Apply''' button.&amp;lt;br /&amp;gt;&lt;br /&gt;
      &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Once the new window appears you will want to use the drop down box next to '''Config Type:''' and make sure that it is set to '''Path'''.&amp;lt;br /&amp;gt;&lt;br /&gt;
      &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; From here you will want to fill out all pertinant information:&amp;lt;br /&amp;gt;&lt;br /&gt;
      &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
      &amp;lt;ol&amp;gt;&lt;br /&gt;
        &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;'''Name:''' The name of this path, this can be any unique name more like a note to know what this path is for.&amp;lt;br /&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
        &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;'''Container Path:''' This will be the path that {{{ARRNAME}}} will see inside the container &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; is a favorite&amp;lt;br /&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
        &amp;lt;li&amp;gt;&amp;lt;p&amp;gt;'''Host Path:''' This is the path to the host (unRAID) machine, This will be &amp;lt;code&amp;gt;/mnt/user/&amp;lt;Your User Share&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
        &amp;lt;p&amp;gt; '''NOTE''' If you follow the [[Docker Guide]] you will only need one Volume path to be made as all information that {{{ARRNAME}}} will need will be in one share &amp;lt;code&amp;gt;/mnt/user/data&amp;lt;/code&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
        &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; The last three items '''Default Value:''', '''Access Mode&amp;quot;''', and '''Description:''' Can be left alone.&amp;lt;br /&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
        &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Click '''ADD'''&amp;lt;br /&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
[[File:unraid-install4.png|frameless|750px|alt=Add New path|Add New Path]]&lt;br /&gt;
      &amp;lt;/ol&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Last thing to check is to make sure Host Port for {{{ARRPORT}}} is filled in with &amp;lt;code&amp;gt;{{{ARRPORT}}}&amp;lt;/code&amp;gt;, ''UNLESS'' This port causes any conflicts with any other container. If it does please choose a different port that is not in use.&amp;lt;br /&amp;gt;&lt;br /&gt;
      &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
      &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Click '''APPLY'''&amp;lt;br /&amp;gt;&lt;br /&gt;
      &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;/ol&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Now the {{{ARRNAME}}}'s container is being downloaded, once complete simply click the '''OK''' button at the bottom of the new pop up window&amp;lt;br /&amp;gt;&lt;br /&gt;
    &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Click '''DOCKER''' on the top row of your browser.&amp;lt;br /&amp;gt;&lt;br /&gt;
    &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Now all you will need to do is simply left click on your newly created container and select '''WebUI'''.&amp;lt;br /&amp;gt;&lt;br /&gt;
  &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
  [[File:unraid-install2.png|frameless|none|250x240px|alt=Select WebUI|Select WebUI]]&lt;br /&gt;
  &amp;lt;li&amp;gt;&amp;lt;p&amp;gt; Now a new browser tab should show up with {{{ARRNAME}}} running in all its glory. '''ENJOY'''&amp;lt;br /&amp;gt;&lt;br /&gt;
  &amp;lt;/p&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2887</id>
		<title>WikiMap</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=WikiMap&amp;diff=2887"/>
		<updated>2020-12-24T16:47:59Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: /* Miscellaneous */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please use https://github.com/Servarr/Wiki to track issues&lt;br /&gt;
Please use this page for easy access to templates&lt;br /&gt;
&lt;br /&gt;
This page to act as an overall map of the wiki as many templates and sections are in use via transclusion.&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Templates ==&lt;br /&gt;
&lt;br /&gt;
# [[Template:Appdata Directory]]&lt;br /&gt;
# [[Template:Installation]]&lt;br /&gt;
# [[Template:Troubleshooting]]&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous ==&lt;br /&gt;
# [[Sandbox]] &amp;lt;- Test code and do any testing here before sending it to live&lt;br /&gt;
# [[Useful Tools]]&lt;br /&gt;
# [[Cloud Setup|Rclone/Mergerfs/Gdrive setup &amp;amp; links]]&lt;br /&gt;
# [[Docker Guide]]&lt;br /&gt;
# [[Definitions]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Plex]]&lt;br /&gt;
# [[Discord-Notifier-unRAID-Network]]&lt;br /&gt;
# [[Clear Cache Cookies and Local Storage]]&lt;br /&gt;
# [[Troubleshooting Misc]]&lt;br /&gt;
# [[Appdata Directory Misc]]&lt;br /&gt;
# [[Installation Misc]]&lt;br /&gt;
# [[Docker on arm synology|Docker on ARM Synology]]&lt;br /&gt;
# [[Contributing]] &amp;lt;--- Will make into template&lt;br /&gt;
&lt;br /&gt;
== Stand Alone Pages ==&lt;br /&gt;
* [[Radarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Sonarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Lidarr]]&lt;br /&gt;
&lt;br /&gt;
* [[Readarr]]&lt;br /&gt;
&lt;br /&gt;
== API Documentation ==&lt;br /&gt;
* [https://radarr.video/docs/api/ Radarr]&lt;br /&gt;
&lt;br /&gt;
* Sonarr&lt;br /&gt;
&lt;br /&gt;
* Lidarr&lt;br /&gt;
&lt;br /&gt;
* Readarr&lt;br /&gt;
&lt;br /&gt;
== *ARR Pages ==&lt;br /&gt;
&amp;lt;section begin=radarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Radarr]]&lt;br /&gt;
**[[Radarr Installation]]&lt;br /&gt;
**[[Radarr Quick Start Guide]]&lt;br /&gt;
**[[Radarr Library|Radarr Library (Movies)]]&lt;br /&gt;
**[[Radarr Calendar]]&lt;br /&gt;
**[[Radarr Activity]]&lt;br /&gt;
**[[Radarr Settings]]&lt;br /&gt;
**[[Radarr System]]&lt;br /&gt;
**[[Radarr Troubleshooting]]&lt;br /&gt;
**[[Radarr FAQ]]&lt;br /&gt;
**[[Radarr Tips and Tricks]]&amp;lt;section end=radarr_wiki_pages /&amp;gt;&amp;lt;section begin=sonarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Sonarr]]&lt;br /&gt;
**[[Sonarr Installation]]&lt;br /&gt;
**[[Sonarr Quick Start Guide]]&lt;br /&gt;
**[[Sonarr Library|Sonarr Library (Series)]]&lt;br /&gt;
**[[Sonarr Calendar]]&lt;br /&gt;
**[[Sonarr Activity]]&lt;br /&gt;
**[[Sonarr Wanted]]&lt;br /&gt;
**[[Sonarr Settings]]&lt;br /&gt;
**[[Sonarr System]]&lt;br /&gt;
**[[Sonarr Troubleshooting]]&lt;br /&gt;
**[[Sonarr FAQ]]&lt;br /&gt;
**[[Sonarr Tips and Tricks]]&amp;lt;section end=sonarr_wiki_pages /&amp;gt;&amp;lt;section begin=lidarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Lidarr]]&lt;br /&gt;
**[[Lidarr Installation]]&lt;br /&gt;
**[[Lidarr Quick Start Guide]]&lt;br /&gt;
**[[Lidarr Library|Lidarr Library (Artist)]]&lt;br /&gt;
**[[Lidarr Calendar]]&lt;br /&gt;
**[[Lidarr Activity]]&lt;br /&gt;
**[[Lidarr Wanted]]&lt;br /&gt;
**[[Lidarr Settings]]&lt;br /&gt;
**[[Lidarr System]]&lt;br /&gt;
**[[Lidarr Troubleshooting]]&lt;br /&gt;
**[[Lidarr FAQ]]&lt;br /&gt;
**[[Lidarr Tips and Tricks]]&amp;lt;section end=lidarr_wiki_pages /&amp;gt;&amp;lt;section begin=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
*[[Readarr]]&lt;br /&gt;
**[[Readarr Installation]]&lt;br /&gt;
**[[Readarr Quick Start Guide]]&lt;br /&gt;
**[[Readarr Library|Readarr Library]]&lt;br /&gt;
**[[Readarr Calendar]]&lt;br /&gt;
**[[Readarr Activity]]&lt;br /&gt;
**[[Readarr Wanted]]&lt;br /&gt;
**[[Readarr Settings]]&lt;br /&gt;
**[[Readarr System]]&lt;br /&gt;
**[[Readarr Troubleshooting]]&lt;br /&gt;
**[[Readarr FAQ]]&lt;br /&gt;
**[[Readarr Tips and Tricks]]&amp;lt;section end=readarr_wiki_pages /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== * ARR UI Pages ==&lt;br /&gt;
Note: All templates or sections are housed within their respective pages. To edit those templates click on the page then to the template page.&lt;br /&gt;
=== Movies/Series/Library ===&lt;br /&gt;
# [[Library]]&lt;br /&gt;
# [[Library Add New]]&lt;br /&gt;
# [[Library Import]]&lt;br /&gt;
# [[Library Discover]] &amp;lt;-- Radarr&lt;br /&gt;
# [[Library Mass Editor]] &amp;lt;-- Sonarr/Lidarr&lt;br /&gt;
# [[Library Bulk Monitoring Editor]] &amp;lt;--Season Pass/Album Studio/Bookshelf combined&lt;br /&gt;
# [[Library Unmapped Files]] &amp;lt;-- Lidarr/Readarr&lt;br /&gt;
&lt;br /&gt;
=== Calendar ===&lt;br /&gt;
# [[Calendar]]&lt;br /&gt;
&lt;br /&gt;
=== Activity ===&lt;br /&gt;
# [[Activity]]&lt;br /&gt;
# [[Activity Queue]]&lt;br /&gt;
# [[Activity History]]&lt;br /&gt;
# [[Activity Blacklist]]&lt;br /&gt;
&lt;br /&gt;
=== Wanted ===&lt;br /&gt;
# [[Wanted]]&lt;br /&gt;
# [[Wanted Missing]]&lt;br /&gt;
# [[Wanted Cutoff Unmet]]&lt;br /&gt;
&lt;br /&gt;
=== Settings ===&lt;br /&gt;
# [[Settings Media Management]]&lt;br /&gt;
# [[Settings Profiles]]&lt;br /&gt;
# [[Settings Quality]]&lt;br /&gt;
# [[Settings Custom Formats]]&lt;br /&gt;
# [[Settings Indexers]]&lt;br /&gt;
# [[Settings Download Clients]]&lt;br /&gt;
# [[Settings Lists]]&lt;br /&gt;
# [[Settings Connect]]&lt;br /&gt;
# [[Settings Metadata]]&lt;br /&gt;
# [[Settings Tags]]&lt;br /&gt;
# [[Settings General]]&lt;br /&gt;
# [[Settings UI]]&lt;br /&gt;
=== System ===&lt;br /&gt;
# [[System status|System Status]]&lt;br /&gt;
# [[System tasks|System Tasks]]&lt;br /&gt;
# [[System backup|System Backup]]&lt;br /&gt;
# [[System updates|System Updates]]&lt;br /&gt;
# [[System events|System Events]]&lt;br /&gt;
# [[System log files|System Log Files]]&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=System_status&amp;diff=2886</id>
		<title>System status</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=System_status&amp;diff=2886"/>
		<updated>2020-12-24T15:38:55Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== System ==&lt;br /&gt;
=== Health ===&lt;br /&gt;
==== Overview ====&lt;br /&gt;
====== Radarr ======&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Sonarr ======&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Lidarr ======&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
====== Readarr ======&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_overview /&amp;gt;&lt;br /&gt;
==== System Warnings ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Newer versions of Radarr 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Radarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Radarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Radarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Radarr/Radarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Radarr/Radarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Radarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
** Managed/tooled installs&lt;br /&gt;
*** For instructions for Swizzin installs, please read the [https://swizzin.ltd/applications/radarr/#migrating-to-v3-on-net-core Swizzin Docs article]&lt;br /&gt;
*** For instructions on Whatbox, please see the [https://whatbox.ca/wiki/Radarr#radarr_v3_(unstable) WB Wiki article]&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_8_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;updating_will_not_be_possible_to_prevent_deleting_appdata_on_update&amp;quot;&amp;gt;'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be &amp;lt;code&amp;gt;C:\ProgramData&amp;lt;/code&amp;gt; for Windows and, &amp;lt;code&amp;gt;~/.config&amp;lt;/code&amp;gt; for linux.&lt;br /&gt;
** Please look at System -&amp;amp;gt; Info to see the current AppData &amp;amp;amp; Startup directories.&lt;br /&gt;
** This means Radarr will be unable to update itself without risking data-loss.&lt;br /&gt;
** 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 &amp;lt;code&amp;gt;~/.config/Radarr&amp;lt;/code&amp;gt; directory to preserve your database.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within radarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:&lt;br /&gt;
 proxy_http_version 1.1;&lt;br /&gt;
 proxy_set_header Upgrade $http_upgrade;&lt;br /&gt;
 proxy_set_header Connection $http_connection;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
 Include /etc/apache2/mods-available/proxy_wstunnel.load&lt;br /&gt;
 ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&lt;br /&gt;
 ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&lt;br /&gt;
* For Caddy (V1) use this:&lt;br /&gt;
** Note: you'll also need to add the websocket directive to your radarr configuration&lt;br /&gt;
  proxy /radarr 127.0.0.1:7878 {&lt;br /&gt;
      websocket&lt;br /&gt;
      transparent&lt;br /&gt;
  }&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_net_framework_is_old_and_unsupported&amp;quot;&amp;gt;'''[[#currently_installed_net_framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]&amp;lt;/span&amp;gt;'''&lt;br /&gt;
** 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.&lt;br /&gt;
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_net_framework_is_supported_but_upgrading_is_recommended&amp;quot;&amp;gt;'''[[#currently_installed_net_framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Upgrading the .Net Framework is very straightforward on Windows, although it often requires a restart. Please follow the instructions here: https://dotnet.microsoft.com/download/dotnet-framework.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_mono_version_is_old_and_unsupported&amp;quot;&amp;gt;'''[[#currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.&lt;br /&gt;
** The upgrade procedure for Mono varies per platform.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;currently_installed_mono_version_is_supported_but_upgrading_is_recommended&amp;quot;&amp;gt;'''[[#currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The upgrade procedure for Mono varies per platform.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; 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.&lt;br /&gt;
** ''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;updating_will_not_be_possible_to_prevent_deleting_appdata_on_update&amp;quot;&amp;gt;'''[[#updating_will_not_be_possible_to_prevent_deleting_appdata_on_update|Updating will not be possible to prevent deleting AppData on Update]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
**Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be &amp;lt;code&amp;gt;C:\ProgramData&amp;lt;/code&amp;gt; for Windows and, &amp;lt;code&amp;gt;~/.config&amp;lt;/code&amp;gt; for linux.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Please look at System -&amp;amp;gt; About to see the current AppData &amp;amp;amp; Startup directories.&lt;br /&gt;
** This means Sonarr will be unable to update itself without risking data-loss.&lt;br /&gt;
** 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 &amp;lt;code&amp;gt;~/.config/Sonarr&amp;lt;/code&amp;gt; directory to preserve your database.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for radarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://lidarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Lidarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Lidarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Lidarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Lidarr/Lidarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Lidarr/Lidarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Lidarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
** Managed/tooled installs&lt;br /&gt;
*** For instructions for Swizzin installs, please read the [https://swizzin.ltd/applications/lidarr/#migrating-to-v3-on-net-core Swizzin Docs article]&lt;br /&gt;
*** For instructions on Whatbox, please see the [https://whatbox.ca/wiki/Lidarr#lidarr(unstable) WB Wiki article]&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_8_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;update_to_net_core_version&amp;quot;&amp;gt;'''[[#update_to_net_core_version|Update to .NET Core version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** Fixing Docker installs&lt;br /&gt;
*** Re-pull your container&lt;br /&gt;
** Fixing Standalone installs&lt;br /&gt;
*** This should only happen on Linux hosts.  &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Do not install .net core runtime or SDK from microsoft.'''&amp;lt;/span&amp;gt; To remedy, download the correct build for your architecture: &lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64 x64]&lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm64 arm64]&lt;br /&gt;
****[https://readarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=arm arm]&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''Back-Up your existing configuration'''&amp;lt;/span&amp;gt; before the next step.&lt;br /&gt;
*** '''Delete your existing binaries' (contents or folder of /opt/Readarr)''' and replace with the contents of the &amp;lt;code&amp;gt;.tar.gz&amp;lt;/code&amp;gt; you just downloaded.&lt;br /&gt;
***&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.&amp;lt;br&amp;gt; YOU MUST DELETE THE OLD ONES FIRST'''.&amp;lt;/span&amp;gt; &lt;br /&gt;
**** Update your startup script to call &amp;lt;code&amp;gt;Readarr&amp;lt;/code&amp;gt; instead of calling it with mono like &amp;lt;code&amp;gt;mono --debug Readarr.exe&amp;lt;/code&amp;gt;. In other words you want, as an example, &amp;lt;code&amp;gt;/opt/Readarr/Readarr&amp;lt;/code&amp;gt; and '''not''' &amp;lt;code&amp;gt;mono  --debug /opt/Readarr/Readarr&amp;lt;/code&amp;gt;.&lt;br /&gt;
*** If Readarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&amp;amp;pivots=os-linux here] installed.&lt;br /&gt;
** Managed/tooled installs&lt;br /&gt;
*** For instructions for Swizzin installs, please read the [https://swizzin.ltd/applications/radarr/#migrating-to-v3-on-net-core Swizzin Docs article]&lt;br /&gt;
*** For instructions on Whatbox, please see the [https://whatbox.ca/wiki/Radarr#radarr_v3_(unstable) WB Wiki article]&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;mono_version_is_less_than_5_2_upgrade_for_improved_stability&amp;quot;&amp;gt;'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Raedarr 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.&lt;br /&gt;
** See &amp;quot;Update to .NET Core version above&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;new_update_is_available&amp;quot;&amp;gt;'''[[#new_update_is_available|New update is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Updates page is probably a good starting point.&lt;br /&gt;
**''(This warning will not appear if your current version is less than 14 days old)''&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;cannot_install_update_because_startup_folder_is_not_writable_by_the_user&amp;quot;&amp;gt;'''[[#cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;branch_is_for_a_previous_version&amp;quot;&amp;gt;'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
**'''Note:''' Please note that v0.2 will only have critical bugs resolved as of August 2020. Any additional development or features will be solely in V3. Each push to the “develop” branch creates a build on “nightly” release channel (release channel is the “branch” within Lidarr’s settings), once we push a build to Github it will show up on “develop” release channel.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;could_not_connect_to_signalr&amp;quot;&amp;gt;'''[[#could_not_connect_to_signalr|Could not connect to signalR]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** The most common occurrence of this is on V3 combined with an nginx reverse proxy. Nginx requires the following addition to the location block for Lidarr:&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_http_version 1.1;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Upgrade $http_upgrade;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;proxy_set_header Connection $http_connection;&amp;lt;/code&amp;gt;&lt;br /&gt;
** Make sure you &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''do not'''&amp;lt;/span&amp;gt; include &amp;lt;code&amp;gt;proxy_set_header Connection &amp;quot;Upgrade&amp;quot;;&amp;lt;/code&amp;gt; as suggested by the nginx documentation. &amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;'''THIS WILL NOT WORK'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** See https://github.com/aspnet/AspNetCore/issues/17081&lt;br /&gt;
** For apache reverse proxy you need to add to the configuration:&lt;br /&gt;
*::&amp;lt;code&amp;gt;Include /etc/apache2/mods-available/proxy_wstunnel.load&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPass &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
*::&amp;lt;code&amp;gt;ProxyPassReverse &amp;quot;/socket&amp;quot; &amp;quot;ws://127.0.0.1:7878/socket&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_system_warnings /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Download Clients ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Radarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Radarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Radarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Radarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Radarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Radarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Radarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Radarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Radarr when the download client tells Radarr it's done Radarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Sonarr to prevent the errors.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Lidarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Lidarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Lidarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Lidarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Lidarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Lidarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Lidarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Lidarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_download_client_is_available&amp;quot;&amp;gt;'''[[#no_download_client_is_available|No download client is available]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 -&amp;amp;gt; Download Client.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;unable_to_communicate_with_download_client&amp;quot;&amp;gt;'''[[#unable_to_communicate_with_download_client|Unable to communicate with download client]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** This is typically due to improperlly configured download client. Things you can typically check:&lt;br /&gt;
*** Your download clients IP Address if its on the same bare metal machien this is typically &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
*** 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.&lt;br /&gt;
*** 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|here]] for more information on this one in our FAQ.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;download_clients_are_unavailable_due_to_failure&amp;quot;&amp;gt;'''[[#download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You should inspect System-&amp;amp;gt;Logs to see what the reason is for the failures.&lt;br /&gt;
** If you no longer use this download client, disable it in Readarr to prevent the errors.&lt;br /&gt;
&lt;br /&gt;
*  &amp;lt;span id=&amp;quot;enable_complete_download_handling&amp;quot;&amp;gt;'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** ''(Completed Download Handling is enabled by default for new users.)''&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;docker_bad_remote_path_mapping&amp;quot;&amp;gt;'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically associated with bad docker paths within either your download client or Readarr&lt;br /&gt;
*** An example of this would be:&lt;br /&gt;
**** Download client: &amp;lt;code&amp;gt;Download Path: /downloads:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Readarr: &amp;lt;code&amp;gt;Download Path: /data:/mnt/user/downloads&amp;lt;/code&amp;gt;&lt;br /&gt;
**** Within this example the download client places its downloads into &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; and therefore tells Radarr when its complete that the finished movie is in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;. Readarr then comes along and says &amp;quot;Okay, cool, let me check in &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt;&amp;quot; Well, inside Readarr you did not allocate a &amp;lt;code&amp;gt;/downloads&amp;lt;/code&amp;gt; path you allocated a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; path so it throws this error.&lt;br /&gt;
**** The easiest fix for this is  '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.&lt;br /&gt;
**** Team Readarr is a big fan of simply using &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt;.&lt;br /&gt;
***** Download client: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Readarr: &amp;lt;code&amp;gt;/data:/mnt/user/data&amp;lt;/code&amp;gt;&lt;br /&gt;
***** Now within the download client you can specify where in &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; you'd like to place your downloads, now this varies depending on the client but you should be able to tell it &amp;quot;Yeah download client place my files into.&amp;quot; &amp;lt;code&amp;gt;/data/torrents (or usenet)/movies&amp;lt;/code&amp;gt; and since you used &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; in Readarr when the download client tells Readarr it's done Readarr will come along and say &amp;quot;Sweet, I have a &amp;lt;code&amp;gt;/data&amp;lt;/code&amp;gt; and I also can see &amp;lt;code&amp;gt;/torrents (or usenet)/movies&amp;lt;/code&amp;gt; all is right in the world.&amp;quot;&lt;br /&gt;
*** 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 (if you're using torrents you SERIOUSLY need to be using this) but the general concept of containers and how path mapping works is the core of these discussions.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_download_clients /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Completed/Failed Download Handling ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.&lt;br /&gt;
** 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. * If you added a post-processing script to Sabnzbd/NzbGet to notify Radarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Radarr attempts to resolve this issue automatically, occassionally Radarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
**''(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.)''&lt;br /&gt;
** It's recommended to switch to 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.&lt;br /&gt;
** If you don't wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn't recommended.&lt;br /&gt;
** If you wish to enable Completed Download Handling you should verify the following:&lt;br /&gt;
*** '''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 download client.&lt;br /&gt;
*** If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts.&lt;br /&gt;
*** Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.&lt;br /&gt;
** 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 Lidarr are on the same machine since it gets the path to be imported directly from the download client. * If you added a post-processing script to Sabnzbd/NzbGet to notify Lidarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Lidarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Lidarr attempts to resolve this issue automatically, occassionally Lidarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;completed_download_handling_is_disabled&amp;quot;&amp;gt;'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** ''(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.)''&lt;br /&gt;
** It’s recommended to switch to 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.&lt;br /&gt;
** If you don’t wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn’t recommended.&lt;br /&gt;
** 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. * If you added a post-processing script to Sabnzbd/NzbGet to notify Readarr that it should scan the Drone Factory. You ''SHOULD'' disable this script to prevent conflicts. * Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)&amp;lt;br /&amp;gt;&lt;br /&gt;
** You should reconfigure Readarr to use a different Drone Factory Folder or disable it altogether.&amp;lt;br /&amp;gt;&lt;br /&gt;
** Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.&lt;br /&gt;
** Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item. If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id. Readarr attempts to resolve this issue automatically, occassionally Readarr may be unable to make that association and cause a ‘Completed’ download to be listed in the History -&amp;amp;gt; Queue table forever. The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_complete_failed_download_handling /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Indexers ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Radarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Sonarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&amp;lt;br /&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
**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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results&amp;quot;&amp;gt;'''[[#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]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Simply put you do not have any of your indexers set to allow automatic searches&lt;br /&gt;
*** Go into Settings &amp;gt; Indexers, select an indexer you'd like to allow Automatic Searches and then click save.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span id=&amp;quot;no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically&amp;quot;&amp;gt;'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers avaiable with RSS syn enabled, Lidarr will not grab new releases automatically]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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]]&lt;br /&gt;
** To correct this issue go to Settings &amp;gt; Indexers, select an indexer you have and enable RSS Sync&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Lidarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;no_indexers_are_enabled&amp;quot;&amp;gt;'''[[#no_indexers_are_enabled|No indexers are enabled]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** Readarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;enabled_indexers_do_not_support_searching&amp;quot;&amp;gt;'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' &amp;lt;/span&amp;gt;&lt;br /&gt;
** 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 movies (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;indexers_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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).&lt;br /&gt;
** 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.&lt;br /&gt;
** You can prevent the warning by disabling the affected indexer.&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_indexers /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Folders ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Easiest way to find this is to go to the Movies (Library) Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path&lt;br /&gt;
***# 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.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the movie folders to '&amp;lt;root path&amp;gt;' ?''' 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&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Series &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the series folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Sonarr to move your files&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Library &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the artist folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Lidarr to move your files&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;missing_root_folder&amp;quot;&amp;gt;'''[[#missing_root_folder|Missing root folder]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.&lt;br /&gt;
*** 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&lt;br /&gt;
***# Go to the Library &amp;gt; Mass Editor Tab&lt;br /&gt;
***# Create a custom filter with the old root folder path &lt;br /&gt;
***# Once the series have been found find the  '''Root Paths''' drop down and select the new root path that you want these movies to be moved to.&lt;br /&gt;
***# Next you'll recieve a pop-up that states '''Would you like to move the author folders to '&amp;lt;root path&amp;gt;'?''' Simply select No if the you do not want Readarr to move your files&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_folders /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Media ====&lt;br /&gt;
===== Radarr =====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_health_media /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;movie_was_removed_from_tmdb&amp;quot;&amp;gt;'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** The movie is linked to a TMDbId 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.&amp;lt;br /&amp;gt;&lt;br /&gt;
** 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&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span id=&amp;quot;lists_are_unavailable_due_to_failures&amp;quot;&amp;gt;'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=radarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Sonarr =====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_health_media /&amp;gt;&lt;br /&gt;
* &amp;lt;span id=&amp;quot;series_removed_from_thetvdb&amp;quot;&amp;gt;'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''&amp;lt;/span&amp;gt;&lt;br /&gt;
** 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.&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Lidarr =====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_health_media /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_health_media /&amp;gt;&lt;br /&gt;
===== Readarr =====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_health_media /&amp;gt;&lt;br /&gt;
Text&lt;br /&gt;
&amp;lt;section end=readarr_system_status_health_media /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Disk Space ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=radarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
* This section will show you available disk space&lt;br /&gt;
** In docker this can be tricky as it will typically show you the available space w/in your Docker image&lt;br /&gt;
&amp;lt;section end=readarr_system_status_disk_space /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== About ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Radarr&lt;br /&gt;
&amp;lt;section end=radarr_system_status_about /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Radarr&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_about /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Lidarr&lt;br /&gt;
&amp;lt;section end=lidarr_system_status_about /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_about /&amp;gt;&lt;br /&gt;
This will tell you about your current install of Readarr&lt;br /&gt;
&amp;lt;section end=readarr_system_status_about /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== More Info ===&lt;br /&gt;
==== Radarr ====&lt;br /&gt;
&amp;lt;section begin=radarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://radarr.video Radarr's home page]&lt;br /&gt;
* Discord: [https://discord.gg/r5wJPt9 Join our discord]&lt;br /&gt;
* Reddit: [htttps://reddit.com/r/radarr]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]&lt;br /&gt;
* Source: [https://github.com/Radarr/Radarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]&lt;br /&gt;
&amp;lt;section end=radarr_system_status_more_info /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Sonarr ====&lt;br /&gt;
&amp;lt;section begin=sonarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://radarr.video Radarr's home page]&lt;br /&gt;
* Forums: [forums.sonarr.tv Official Sonarr Forums]&lt;br /&gt;
* Discord: [discord.gg/M6BvZn5 Join our discord]&lt;br /&gt;
* Reddit: [https://reddit.com/r/sonarr]&lt;br /&gt;
* Twitter: [@sonarrtv]&lt;br /&gt;
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://sonarr.tv/donate here]&lt;br /&gt;
* Source: [github.com/Sonarr/Sonarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it on Github [github.com/Sonarr/Sonarr/issuess here] or the Forums [forums.sonarr.tv here]&lt;br /&gt;
&amp;lt;section end=sonarr_system_status_more_info /&amp;gt;&lt;br /&gt;
==== Lidarr ====&lt;br /&gt;
&amp;lt;section begin=lidarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [lidarr.audio Lidarr's home page]&lt;br /&gt;
* Discord: [https://discord.com/invite/5WQc3S8 Join our discord]&lt;br /&gt;
* Reddit: [https://reddit.com/r/lidarr Lidarr's SubReddit]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/lidarr here]&lt;br /&gt;
* Source: [https://github.com/lidarr/Lidarr/ Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it on GitHub [github.com/Lidarr/Lidarr/issues here] &lt;br /&gt;
&amp;lt;section end=lidarr_system_status_more_info /&amp;gt;&lt;br /&gt;
==== Readarr ====&lt;br /&gt;
&amp;lt;section begin=readarr_system_status_more_info /&amp;gt;&lt;br /&gt;
* Home page: [https://readarr.com Readarr's home page]&lt;br /&gt;
* Reddit: [https://reddit.com/r/readarr]&lt;br /&gt;
* Discord: [https://discord.com/invite/rkEXY2Rbgn Join our discord]&lt;br /&gt;
* Wiki: [https://wiki.servarr.com You're here already]&lt;br /&gt;
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]&lt;br /&gt;
* Source: [https://github.com/Readarr/Readarr Github]&lt;br /&gt;
* Feature Requests: Got as great idea drop it [https://github.com/Readarr/Readarr/issues here]&lt;br /&gt;
&amp;lt;section end=readarr_system_status_more_info /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Templates ===&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
	<entry>
		<id>https://wikiold.servarr.com/index.php?title=Installation_Misc&amp;diff=2883</id>
		<title>Installation Misc</title>
		<link rel="alternate" type="text/html" href="https://wikiold.servarr.com/index.php?title=Installation_Misc&amp;diff=2883"/>
		<updated>2020-12-24T06:29:32Z</updated>

		<summary type="html">&lt;p&gt;Drazzilb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Installation ==&lt;br /&gt;
=== Radarr ===&lt;br /&gt;
==== Windows ====&lt;br /&gt;
&lt;br /&gt;
==== OSX ====&lt;br /&gt;
&lt;br /&gt;
==== Linux ====&lt;br /&gt;
&amp;lt;section begin=radarr_linux_ubuntu_NetCore_manual_installation /&amp;gt;&lt;br /&gt;
===== .NET Core Install =====&lt;br /&gt;
There are no dependencies needed for the .NET Core Install path.&lt;br /&gt;
&lt;br /&gt;
====== Manual Install ======&lt;br /&gt;
Go to the Radarr download page, and pick the appropriate file: https://github.com/Radarr/Radarr/releases&lt;br /&gt;
&lt;br /&gt;
[[File:ARR Download Link Example.png|thumb|right|Example of Radarr download options]]&lt;br /&gt;
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 &amp;lt;code&amp;gt;.linux-core-x64.tar.gz&amp;lt;/code&amp;gt; if it is available.&lt;br /&gt;
&lt;br /&gt;
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)&lt;br /&gt;
  wget --content-disposition 'http://radarr.servarr.com/v1/update/master/updatefile?os=linux&amp;amp;runtime=netcore&amp;amp;arch=x64'&lt;br /&gt;
Uncompress:&lt;br /&gt;
 tar -xvzf Radarr*.linux-core-x64.tar.gz&lt;br /&gt;
Move to your preferred install location (typically &amp;lt;code&amp;gt;/opt/Radarr/&amp;lt;/code&amp;gt;&lt;br /&gt;
 sudo mv Radarr/ /opt&lt;br /&gt;
Finally, make sure you grant the needed permission to your install directory:&lt;br /&gt;
 sudo chown radarr:radarr /opt/Radarr&lt;br /&gt;
&lt;br /&gt;
You can start Radarr with the following command:&lt;br /&gt;
 /opt/Radarr/Radarr -nobrowser&lt;br /&gt;
&amp;lt;section end=radarr_linux_ubuntu_NetCore_manual_installation /&amp;gt;&lt;br /&gt;
==== NAS ====&lt;br /&gt;
&lt;br /&gt;
==== Docker ====&lt;br /&gt;
&lt;br /&gt;
==== Docker on unRAID ====&lt;br /&gt;
&lt;br /&gt;
=== Sonarr ===&lt;br /&gt;
==== Windows ====&lt;br /&gt;
&lt;br /&gt;
==== OSX ====&lt;br /&gt;
&amp;lt;section begin=sonarr_osx_big_sur_installation /&amp;gt;&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;After downloading Sonarr V3 from [https://services.sonarr.tv/v1/download/phantom-develop/latest?version=3&amp;amp;os=macos&amp;amp;installer=true here]The &amp;lt;code&amp;gt;zip&amp;lt;/code&amp;gt; file will be located in your downloads directory.&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt;After the downlaod 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.&amp;lt;/li&amp;gt;&lt;br /&gt;
  [[File:Move-sonarr-to-applications.gif|center|frameless|750x750px]]&lt;br /&gt;
  &amp;lt;li&amp;gt; From there if you go to your launch pad you'll notice that Sonarr is now in there, double click on Sonarr&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt; You'll probably get a pop up that says &amp;quot;Sonarr.app&amp;quot; cannot be opened because the developer cannot be verified.&amp;lt;/li&amp;gt;&lt;br /&gt;
[[File:sonarr-developer-cannot-be-verified.png|none|frameless|250px]]&lt;br /&gt;
  &amp;lt;li&amp;gt; Dont fret we can get this fixed.&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;ol&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;Click on System Preferences in your dock&amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;Click Security and Privacy&amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; Click '''Open Anyways'''&amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; You'll get a pop up that looks something like this:&amp;lt;/li&amp;gt;&lt;br /&gt;
[[File:sonarr-developer-cannot-be-verified2.png|none|framless|250px]]&lt;br /&gt;
    &amp;lt;li&amp;gt; Click Open &amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;/ol&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt; Now since Sonarr uses the Mono Framework Version 5.20 or later if you do not already have that installed you'll recieve a pop up like this&amp;lt;/li&amp;gt;&lt;br /&gt;
[[File:sonarr-cannot-launch-sonarr-mono.png|none|frameless|250px]]&lt;br /&gt;
  &amp;lt;ul&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;Note: If Mono is already installed skip these steps&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;/ul&amp;gt;&lt;br /&gt;
  &amp;lt;ol&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; Click Download &amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; 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)'''&amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; Once the download is complete go to your downloads folder and click the new pkg file that was downloaded and install it&amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt; After installation is complete go back and reopen Sonarr &amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;/ol&amp;gt;&lt;br /&gt;
  &amp;lt;li&amp;gt; Now browse to &amp;lt;code&amp;gt;http://localhost:8989&amp;lt;/code&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
Now you're all set Sonarr is now up and running on your system Have fun&lt;br /&gt;
&amp;lt;section end=sonarr_osx_big_sur_installation /&amp;gt;&lt;br /&gt;
==== Linux ====&lt;br /&gt;
&amp;lt;section begin=sonarr_linux_ubuntu_repository_installation /&amp;gt;&lt;br /&gt;
====== Repository Install (Mono) ======&lt;br /&gt;
Repository installs will typically automatically install needed dependencies.&lt;br /&gt;
Add the Sonarr Repository:&lt;br /&gt;
 sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 0xA236C58F409091A18ACA53CBEBFF6B99D9B78493&lt;br /&gt;
 echo &amp;quot;deb http://apt.sonarr.tv/ master main&amp;quot; | sudo tee /etc/apt/sources.list.d/sonarr.list&lt;br /&gt;
Update and install: &lt;br /&gt;
 sudo apt update&lt;br /&gt;
 sudo apt install nzbdrone &lt;br /&gt;
To start Sonarr, you need to call the mono executable:&lt;br /&gt;
 /usr/bin/mono --debug /opt/NzbDrone/NzbDrone.exe&lt;br /&gt;
&amp;lt;section end=sonarr_linux_ubuntu_repository_installation /&amp;gt;&lt;br /&gt;
==== NAS ====&lt;br /&gt;
&lt;br /&gt;
==== Docker ====&lt;br /&gt;
&lt;br /&gt;
==== Docker on unRAID ====&lt;br /&gt;
&lt;br /&gt;
=== Lidarr ===&lt;br /&gt;
&lt;br /&gt;
==== Windows ====&lt;br /&gt;
&lt;br /&gt;
==== OSX ====&lt;br /&gt;
&lt;br /&gt;
==== Linux ====&lt;br /&gt;
&lt;br /&gt;
==== NAS ====&lt;br /&gt;
&lt;br /&gt;
==== Docker ====&lt;br /&gt;
&lt;br /&gt;
==== Docker on unRAID ====&lt;br /&gt;
=== Readarr ===&lt;br /&gt;
&lt;br /&gt;
==== Windows ====&lt;br /&gt;
&lt;br /&gt;
==== OSX ====&lt;br /&gt;
&lt;br /&gt;
==== Linux ====&lt;br /&gt;
&amp;lt;section begin=readarr_linux_ubuntu_NetCore_manual_installation /&amp;gt;&lt;br /&gt;
===== .NET Core Install =====&lt;br /&gt;
There are no dependencies needed for the .NET Core Install path.&lt;br /&gt;
&lt;br /&gt;
====== Manual Install ======&lt;br /&gt;
Go to the Readarr discord and locate the binaries&lt;br /&gt;
&lt;br /&gt;
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)&lt;br /&gt;
  wget --content-disposition '{Readarr is pre-alpha; link hidden from the public}'&lt;br /&gt;
Uncompress:&lt;br /&gt;
 tar -xvzf Readarr*.linux-core-x64.tar.gz&lt;br /&gt;
Move to your preferred install location (typically &amp;lt;code&amp;gt;/opt/Readarr/&amp;lt;/code&amp;gt;&lt;br /&gt;
 sudo mv Readarr/ /opt&lt;br /&gt;
Finally, make sure you grant the needed permission to your install directory:&lt;br /&gt;
 sudo chown readarr:readarr /opt/readarr&lt;br /&gt;
&lt;br /&gt;
You can start Readarr with the following command:&lt;br /&gt;
 /opt/Readarr/Readarr -nobrowser&lt;br /&gt;
&amp;lt;section end=readarr_linux_ubuntu_NetCore_manual_installation /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== NAS ====&lt;br /&gt;
&lt;br /&gt;
==== Docker ====&lt;br /&gt;
&lt;br /&gt;
==== Docker on unRAID ====&lt;br /&gt;
&lt;br /&gt;
== Code Blocks ==&lt;br /&gt;
=== Radarr ===&lt;br /&gt;
==== Preparing the Unit Service File Code Block 1 ====&lt;br /&gt;
&amp;lt;section begin=radarr_installation_unit_service_file /&amp;gt;&lt;br /&gt;
 [Unit]&lt;br /&gt;
 Description=Radarr Daemon&lt;br /&gt;
 After=syslog.target network.target&lt;br /&gt;
 &lt;br /&gt;
 [Service]&lt;br /&gt;
 # Change the user and group variables here.&lt;br /&gt;
 User=radarr&lt;br /&gt;
 Group=radarr&lt;br /&gt;
 &lt;br /&gt;
 Type=simple&lt;br /&gt;
 &lt;br /&gt;
 # NetCore install:&lt;br /&gt;
 #ExecStart=/opt/Radarr/Radarr -nobrowser -data=/home/radarr/.config/Radarr/&lt;br /&gt;
 &lt;br /&gt;
 TimeoutStopSec=20&lt;br /&gt;
 KillMode=process&lt;br /&gt;
 Restart=on-failure&lt;br /&gt;
 &lt;br /&gt;
 [Install]&lt;br /&gt;
 WantedBy=multi-user.target&lt;br /&gt;
&amp;lt;section end=radarr_installation_unit_service_file /&amp;gt;&lt;br /&gt;
=== Sonarr ===&lt;br /&gt;
==== Preparing the Unit Service File Code Block 1 ====&lt;br /&gt;
&amp;lt;section begin=sonarr_installation_unit_service_file /&amp;gt;&lt;br /&gt;
 [Unit]&lt;br /&gt;
 Description=Sonarr Daemon&lt;br /&gt;
 After=syslog.target network.target&lt;br /&gt;
 &lt;br /&gt;
 [Service]&lt;br /&gt;
 # Change the user and group variables here.&lt;br /&gt;
 User=sonarr&lt;br /&gt;
 Group=sonarr&lt;br /&gt;
 &lt;br /&gt;
 Type=simple&lt;br /&gt;
 &lt;br /&gt;
 # Mono Install:&lt;br /&gt;
 #ExecStart=/usr/bin/mono --debug /opt/Sonarr/Sonarr.exe -nobrowser -data=/home/sonarr/.config/Sonarr/&lt;br /&gt;
 &lt;br /&gt;
 TimeoutStopSec=20&lt;br /&gt;
 KillMode=process&lt;br /&gt;
 Restart=on-failure&lt;br /&gt;
 &lt;br /&gt;
 [Install]&lt;br /&gt;
 WantedBy=multi-user.target&lt;br /&gt;
&amp;lt;section end=sonarr_installation_unit_service_file /&amp;gt;&lt;br /&gt;
=== Lidarr ===&lt;br /&gt;
==== Preparing the Unit Service File Code Block 1 ====&lt;br /&gt;
&amp;lt;section begin=lidarr_installation_unit_service_file /&amp;gt;&lt;br /&gt;
 [Unit]&lt;br /&gt;
 Description=Lidarr Daemon&lt;br /&gt;
 After=syslog.target network.target&lt;br /&gt;
 &lt;br /&gt;
 [Service]&lt;br /&gt;
 # Change the user and group variables here.&lt;br /&gt;
 User=lidarr&lt;br /&gt;
 Group=lidarr&lt;br /&gt;
 &lt;br /&gt;
 Type=simple&lt;br /&gt;
 &lt;br /&gt;
 # NetCore install:&lt;br /&gt;
 #ExecStart=/opt/Lidarr/Lidarr -nobrowser -data=/home/lidarr/.config/Lidarr/&lt;br /&gt;
 &lt;br /&gt;
 TimeoutStopSec=20&lt;br /&gt;
 KillMode=process&lt;br /&gt;
 Restart=on-failure&lt;br /&gt;
 &lt;br /&gt;
 [Install]&lt;br /&gt;
 WantedBy=multi-user.target&lt;br /&gt;
&amp;lt;section end=lidarr_installation_unit_service_file /&amp;gt;&lt;br /&gt;
=== Readarr ===&lt;br /&gt;
==== Preparing the Unit Service File Code Block 1 ====&lt;br /&gt;
&amp;lt;section begin=readarr_installation_unit_service_file /&amp;gt;&lt;br /&gt;
 [Unit]&lt;br /&gt;
 Description=Readarr Daemon&lt;br /&gt;
 After=syslog.target network.target&lt;br /&gt;
 &lt;br /&gt;
 [Service]&lt;br /&gt;
 # Change the user and group variables here.&lt;br /&gt;
 User=readarr&lt;br /&gt;
 Group=readarr&lt;br /&gt;
 &lt;br /&gt;
 Type=simple&lt;br /&gt;
 &lt;br /&gt;
 # NetCore install:&lt;br /&gt;
 #ExecStart=/opt/Readarr/Readarr -nobrowser -data=/home/readarr/.config/Readarr/&lt;br /&gt;
 &lt;br /&gt;
 TimeoutStopSec=20&lt;br /&gt;
 KillMode=process&lt;br /&gt;
 Restart=on-failure&lt;br /&gt;
 &lt;br /&gt;
 [Install]&lt;br /&gt;
 WantedBy=multi-user.target&lt;br /&gt;
&amp;lt;section end=readarr_installation_unit_service_file /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Drazzilb</name></author>
	</entry>
</feed>