https://wikiold.servarr.com/api.php?action=feedcontributions&feedformat=atom&user=Flying-sausagesServarr - User contributions [en]2026-05-18T20:43:51ZUser contributionsMediaWiki 1.35.2https://wikiold.servarr.com/index.php?title=Template:Installation&diff=3062Template:Installation2021-01-23T18:36:46Z<p>Flying-sausages: Change indentation levels in Linux chapter</p>
<hr />
<div><br />
<noinclude><br />
<templatedata><br />
{<br />
"params": {<br />
"ARRNAME": {<br />
"description": "Name of the ARR",<br />
"example": "Radarr",<br />
"type": "string",<br />
"required": true,<br />
"default": "Fake Radarr"<br />
},<br />
"RunArrCommandLinux": {<br />
"description": "Command to Start & Run ARR Linux",<br />
"example": "./opt/Radarr/Radarr -nobrowser -data=/home/radarr/.config/Radarr/",<br />
"type": "string",<br />
"required": true<br />
},<br />
"RunArrCommandOSX": {<br />
"description": "Command to Start & Run ARR OSX",<br />
"example": "./opt/Radarr/Radarr -nobrowser -data=/home/radarr/.config/Radarr/",<br />
"type": "string",<br />
"required": true<br />
},<br />
"ArrExecutableNameWin": {<br />
"description": "Executable Name for Windows",<br />
"example": "Radarr.exe",<br />
"type": "string",<br />
"required": true<br />
},<br />
"ArrDownloadLink": {<br />
"description": "Link to the Arr Downloads",<br />
"type": "url",<br />
"required": true<br />
},<br />
"ArrLinuxAutoStart": {<br />
"description": "Autostart file instructions",<br />
"required": true<br />
},<br />
"ARRPORT": {<br />
"description": "Port number for the ARR",<br />
"example": "Radarr: 7878, Sonarr: 8989, Lidarr: 8686, Readarr: 8787",<br />
"type": "number",<br />
"default": "7878",<br />
"required": true<br />
},<br />
"ARRNAME2": {<br />
"description": "Used for lowercase ARR names, this is not a required field only used if needed",<br />
"example": "radarr, sonarr, lidarr, readarr",<br />
"type": "string"<br />
}<br />
},<br />
"paramOrder": [<br />
"ARRNAME",<br />
"RunArrCommandLinux",<br />
"RunArrCommandOSX",<br />
"ArrExecutableNameWin",<br />
"ArrDownloadLink",<br />
"ArrLinuxAutoStart",<br />
"ARRPORT",<br />
"ARRNAME2"<br />
],<br />
"description": "This template is expressly for the steps and processes of installing all the various ARR software on multiple different platforms"<br />
}<br />
</templatedata><br />
</noinclude><br />
<br />
= Installing =<br />
== Windows ==<br />
<br />
== OSX ==<br />
{{#lst::Installation Misc|{{{ARRNAME2}}}_osx_big_sur_installation}}<br />
<br />
== Linux ==<br />
<br />
=== Debian / Ubuntu ===<br />
Most of the "arr" 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 "arr" software supports repository based automatic installs, and some must be installed manually.<br />
<br />
{{#lst::Installation Misc|{{{ARRNAME2}}}_linux_ubuntu_NetCore_manual_installation}}<br />
<br />
==== Mono Install ====<br />
{{#lst::Installation Misc|{{{ARRNAME2}}}_linux_ubuntu_repository_installation}}<br />
<br />
===== Manual Install (Mono) =====<br />
Manual Installs need to have dependencies installed first.<br />
<br />
Mono:<br />
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys FA7E0328081BFF6A14DA29AA6A19B38D3D831EF<br />
echo "deb https://download.mono-project.com/repo/ubuntu stable-focal main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list<br />
sudo apt update && sudo apt install mono-devel<br />
Curl<br />
sudo apt install curl<br />
Mediainfo:<br />
sudo apt install mediainfo<br />
sqlite3:<br />
sudo apt install sqlite3<br />
<br />
Now download the newest mono version release of {{{ARRNAME}}}:<br />
wget --content-disposition '{{{ARRPackageFileMono}}}'<br />
<br />
Uncompress:<br />
tar -xvzf {{{ARRNAME}}}*.tar.gz<br />
Move to your preferred install location (typically <code>/opt/{{{ARRNAME}}}/</code><br />
sudo mv {{{ARRNAME}}}/ /opt<br />
Finally, make sure you grant the needed permission to your install directory:<br />
sudo chown {{{ARRNAME2}}}:{{{ARRNAME2}}} /opt/{{{ARRNAME}}}<br />
<br />
You can start {{{ARRNAME}}} with the following command:<br />
/usr/bin/mono --debug /opt/{{{ARRNAME}}}/{{{ARRNAME}}}.exe -nobrowser<br />
<br />
=== Auto Start Using Systemd ===<br />
Most modern Linux distributions have switched to systemd, which involves a simple unit service file which gets enabled and started. It is important to remember that in Linux, capitalization matters. <code>User</code> account names and <code>Group</code> names are typically all lowercase, as are the directory structures mapped to them as part of the home directory.<br />
<br />
==== Preparing the Unit Service File ====<br />
Several items may need to be changed to match your installation:<br />
<br />
# <code>User</code> should match the service account that {{{ARRNAME2}}} will run as.<br />
# <code>Group</code> should match the service account group that {{{ARRNAME2}}} will run as.<br />
# <code>ExecStart</code> has several items that should match your installation <code>/opt/{{{ARRNAME}}}/{{{ARRNAME}}}</code><br />
## Executable Path Default location is <code>/opt/{{{ARRNAME}}}/{{{ARRNAME}}}</code>, but you may need to update if you installed {{{ARRNAME}}} elsewhere.<br />
## Data Directory Default location is <code>-data=/home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/</code>, but you may need to update if you want to keep your database and settings elsewhere.<br />
## Mono Path (if Mono is being used) Default location is <code>/usr/bin/mono</code>, but you may need to update if you installed Mono elsewhere.<br />
<br />
The unit service file should be named <code>{{{ARRNAME}}}.service</code> and the best place for it is <code>/etc/systemd/system/</code>. Alternative locations like <code>/usr/lib/systemd/system/</code> and <code>/lib/systemd/system/</code> may depend on the distribution used.<br />
<br />
This example unit assumes that the <code>User</code> and <code>Group</code> are both <code>{{{ARRNAME2}}}</code>, {{{ARRNAME}}}'s executable is placed in <code>/opt/{{{ARRNAME}}}/</code>, the data directory is placed in <code>/home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}</code>, and the Mono executable (if being used) is placed in <code>/usr/bin/mono</code>.<br />
<br />
{{#lst::Installation Misc|{{{ARRNAME2}}}_installation_unit_service_file}}<br />
<br />
==== Verify Directory Permissions ====<br />
Ensure the <code>User</code> that will be running {{{ARRNAME}}} has access to both the executable directory and data directory.<br />
Running the command <code>ls -lad /directory/</code> will show the permissions for that folder.<br />
Example:<br />
$ ls -lad /opt/{{{ARRNAME}}}<br />
drwxr-xr-x 6 {{{ARRNAME2}}} {{{ARRNAME2}}} 24576 Nov 28 21:30 /opt/{{{ARRNAME}}}/<br />
$ ls -lad /home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/<br />
drwxr-xr-x 6 {{{ARRNAME2}}} {{{ARRNAME2}}} 24576 Nov 28 21:30 /home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/<br />
<br />
==== Enabling and starting the Unit Service File ====<br />
Once you have created <code>{{{ARRNAME}}}.service</code>, you will want to enable the service:<br />
sudo systemctl enable {{{ARRNAME}}}.service<br />
<br />
You are now ready to start {{{ARRNAME}}}. You can do so with the <code>start</code> command:<br />
sudo systemctl start {{{ARRNAME}}}.service<br />
<br />
If you want to verify {{{ARRNAME}}} is running, you can run the <code>status</code> command:<br />
$ sudo systemctl status {{{ARRNAME}}}.service<br />
● {{{ARRNAME}}}.service - {{{ARRNAME}}}Service<br />
Loaded: loaded (/usr/lib/systemd/system/{{{ARRNAME}}}.service; enabled; vendor preset: disabled)<br />
Active: active (running) since Tue 2017-03-07 10:23:44 PST; 5min ago<br />
Main PID: 19978 ({{{ARRNAME}}})<br />
Tasks: 16 (limit: 4915)<br />
Memory: 114.6M<br />
CPU: 9.331s<br />
CGroup: /system.slice/{{{ARRNAME}}}.service<br />
└─19978 /opt/{{{ARRNAME}}}/{{{ARRNAME}}} -nobrowser -data=/home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/<br />
Mar 07 10:23:44 apollo systemd[1]: Started {{{ARRNAME}}} Service.<br />
=== NGINX Reverse Proxy ===<br />
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.<br />
<br />
(Link to NGINX Install Wiki Page)<br />
<br />
Create a text file named {{{ARRNAME}}}.conf and place it in your default NGINX App directory, typically <code>/etc/nginx/conf.d/apps</code><br />
# {{{ARRNAME}}} Reverse Proxy<br />
# Be sure to set your Base-URL in {{{ARRNAME}}}<br />
location /{{{ARRNAME2}}} {<br />
proxy_pass http://127.0.0.1:{{{ARRPORT}}}/{{{ARRNAME2}}};<br />
proxy_set_header X-Real-IP $remote_addr;<br />
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br />
proxy_set_header X-Forwarded-Proto $scheme;<br />
proxy_http_version 1.1;<br />
proxy_no_cache $cookie_session;<br />
proxy_set_header Upgrade $http_upgrade;<br />
proxy_set_header Connection $http_connection;<br />
# Allow the {{{ARRNAME}}} API<br />
location /{{{ARRNAME2}}}/api { auth_request off;<br />
proxy_pass http://127.0.0.1:{{{ARRPORT}}}/{{{ARRNAME2}}}/api;<br />
}<br />
}<br />
Please note: It is important to ensure that the line <code>proxy_set_header Connection $http_connection;</code> is accurate. The NGINX documentation recommends setting this to <code>Upgrade</code> rather than <code>$http_connection;</code> but this will NOT work.<br />
<br />
Once you have saved the file, test your NGINX config:<br />
sudo nginx -t<br />
Which should show this:<br />
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok<br />
nginx: configuration file /etc/nginx/nginx.conf test is successful<br />
Now you can have NGINX reload it's configuration to use the new file:<br />
sudo nginx -s reload<br />
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: <code>/{{{ARRNAME2}}}</code><br />
The URL base can be set here: https://wiki.servarr.com/{{{ARRNAME}}}_Settings#Host<br />
<br />
== NAS ==<br />
=== FreeNAS ===<br />
=== Qnap ===<br />
=== Synology ===<br />
* 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]. <br />
* This guide works directly with docker-compose as this is typically a much better/faster way to get you up and running<br />
<br><center>'''NOTE:'''</center><br />
If your Synology doesn't support dockers you will need to look at the packages that are fully maintained by the Synology community. <br />
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.<br />
<br />
== Docker ==<br />
<br />
== Docker on unRAID ==<br />
* Installation of {{{ARRNAME}}} is quite simple when it comes to unRAID as they have made installing Docker containers a breeze.<br />
<ol style="list-style-type: decimal;"><br />
<li><p>Simply head on over to the community applications store on the top bar of your browser. <br /></p></li><br />
[[File:unraid-install1.png|frameless|750px|alt=Community Applications|Communitty Applications]]<br />
<li><p>In the search field type in {{{ARRNAME}}}<br /><br />
</p></li><br />
<li><p>Select which docker image you would like to install. There are several to choose from<br /><br />
</p></li><br />
[[File:{{{ARRNAME}}}-unraid-install.png|frameless|none|750px|alt=Installation Options|Installation Options]]<br />
<li><p> 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<br /><br />
</p></li><br />
<p> 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 <code>Default :latest</code> branch</p><br />
<li><p> 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).<br /></p></li><br />
<p> 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'''</p><br />
[[File:unraid-install3.png|frameless|750px|alt=Toggle Advanced|Toggle Advanced]]<br />
<ol><br />
<li><p> To create new volumes simply select the <code> Add another Path, Port, Variable, Label or Device</code> text at the bottom above the '''Apply''' button.<br /><br />
</p></li><br />
<li><p> 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'''.<br /><br />
</p></li><br />
<li><p> From here you will want to fill out all pertinant information:<br /><br />
</p></li><br />
<ol><br />
<li><p>'''Name:''' The name of this path, this can be any unique name more like a note to know what this path is for.<br /><br />
</p></li><br />
<li><p>'''Container Path:''' This will be the path that {{{ARRNAME}}} will see inside the container <code>/data</code> is a favorite<br /><br />
</p></li><br />
<li><p>'''Host Path:''' This is the path to the host (unRAID) machine, This will be <code>/mnt/user/<Your User Share></code><br /><br />
</p></li><br />
<p> '''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 <code>/mnt/user/data</code></p><br />
<li><p> The last three items '''Default Value:''', '''Access Mode"''', and '''Description:''' Can be left alone.<br /><br />
</p></li><br />
<li><p> Click '''ADD'''<br /><br />
</p></li><br />
[[File:unraid-install4.png|frameless|750px|alt=Add New path|Add New Path]]<br />
</ol><br />
<li><p> Last thing to check is to make sure Host Port for {{{ARRPORT}}} is filled in with <code>{{{ARRPORT}}}</code>, ''UNLESS'' This port causes any conflicts with any other container. If it does please choose a different port that is not in use.<br /><br />
</p></li><br />
<li><p> Click '''APPLY'''<br /><br />
</p></li><br />
</ol><br />
<li><p> Now the {{{ARRNAME}}}'s container is being downloaded, once complete simply click the '''OK''' button at the bottom of the new pop up window<br /><br />
</p></li><br />
<li><p> Click '''DOCKER''' on the top row of your browser.<br /><br />
</p></li><br />
<li><p> Now all you will need to do is simply left click on your newly created container and select '''WebUI'''.<br /><br />
</p></li><br />
[[File:unraid-install2.png|frameless|none|250x240px|alt=Select WebUI|Select WebUI]]<br />
<li><p> Now a new browser tab should show up with {{{ARRNAME}}} running in all its glory. '''ENJOY'''<br /><br />
</p></li><br />
</ol></div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=Template:Ombox&diff=3012Template:Ombox2021-01-18T16:40:34Z<p>Flying-sausages: 1 revision imported: Imported anchor templates from mediawiki</p>
<hr />
<div><templatestyles src="Template:Ombox/styles.css" /><br />
{{#invoke:Message box|ombox}}<noinclude> <br />
{{documentation}} <br />
<!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --> <br />
</noinclude></div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=Template:Module_other&diff=3010Template:Module other2021-01-18T16:40:34Z<p>Flying-sausages: 1 revision imported: Imported anchor templates from mediawiki</p>
<hr />
<div>{{#switch:<br />
<!--If no or empty "demospace" parameter then detect namespace--><br />
{{#if:{{{demospace|}}}<br />
| {{lc: {{{demospace}}} }} <!--Use lower case "demospace"--><br />
| {{#ifeq:{{NAMESPACE}}|{{ns:Module}}<br />
| module<br />
| other<br />
}}<br />
}}<br />
| module = {{{1|}}}<br />
| other<br />
| #default = {{{2|}}}<br />
}}<!--End switch--><noinclude><br />
<br />
{{documentation}}<br />
<!-- Add categories and interwikis to the /doc subpage, not here! --><br />
</noinclude></div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=Template:High-use&diff=3008Template:High-use2021-01-18T16:40:34Z<p>Flying-sausages: 1 revision imported: Imported anchor templates from mediawiki</p>
<hr />
<div>#REDIRECT [[Template:High-risk]]</div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=Template:High-risk/en&diff=3006Template:High-risk/en2021-01-18T16:40:34Z<p>Flying-sausages: 1 revision imported: Imported anchor templates from mediawiki</p>
<hr />
<div><noinclude><br />
<languages/><br />
</noinclude>{{#switch:<br />
| =<br />
{{ombox<br />
| type = content<br />
| image = [[File:OOjs UI icon alert-warning.svg|40px|alt=]]<br />
| imageright =<br />
| text = '''This {{#switch:{{NAMESPACE}}|Module=Lua module|#default=template}} is used on {{#if:{{{1|}}}|approximately {{formatnum:{{{1}}}}}|many}} pages.'''<br /><br />
To avoid large-scale disruption and unnecessary server load, any changes to this {{#switch:{{NAMESPACE}}|Module=module|#default=template}} should first be tested in its [[{{#switch:{{SUBPAGENAME}}|doc|sandbox={{SUBJECTSPACE}}:{{BASEPAGENAME}}|#default={{SUBJECTPAGENAME}}}}/sandbox|/sandbox]] or [[{{#switch:{{SUBPAGENAME}}|doc|sandbox={{SUBJECTSPACE}}:{{BASEPAGENAME}}|#default={{SUBJECTPAGENAME}}}}/testcases|/testcases]] subpages{{#switch:{{NAMESPACE}}|Module=.|#default=&#32;or in your own [[Special:MyLanguage/Help:Subpages#Use of subpages|user subpage]].}}<br />
The tested changes can then be added to this page in one single edit.<br />
Please consider discussing any changes {{#if:{{{2|}}}|at [[{{trim|{{{2}}}}}]]|on the [[{{#switch:{{SUBPAGENAME}}|doc|sandbox={{TALKSPACE}}:{{BASEPAGENAME}}|#default={{TALKPAGENAME}}}}|talk page]]}} before implementing them.<br />
}}<br />
| #default=<br />
{{#invoke:Template translation|renderTranslatedTemplate|template=Template:High-risk|noshift=1|uselang={{int:lang}}}}<br />
}}<noinclude><br />
{{Documentation|content=<br />
<br />
This is the {{tl|high-risk}} message box. It is meant to be put at the top of the documentation page on the most high-use (high-risk) templates and Lua modules (the template detects the name space), i.e., for templates used on a large number of pages<br />
<br />
'''''Note:''''' It is normal that some of the links in the message box are red.<br />
=== Usage ===<br />
The template can be used as is. But it can also take some parameters:<br />
<br />
* First parameter is the number of pages.<br />
* Second parameter is the name of some other talk page if you want discussion to be made there instead. But a better option might be to redirect the talkpage of your template to that other talkpage.<br />
<br />
===Examples===<br />
<pre><br />
{{high-risk| 30,000+ | Project:Current issues}}<br />
</pre><br />
<br />
{{high-risk| 30,000+ | Project:Current issues}}<br />
<br />
<pre><br />
{{high-risk| 30,000+ }}<br />
</pre><br />
<br />
{{high-risk| 30,000+ }}<br />
<br />
<pre><br />
{{high-risk| | Project:Current issues}}<br />
</pre><br />
<br />
{{high-risk| | Project:Current issues}}<br />
<br />
The full code for a /doc page top may look like this:<br />
<br />
<pre><br />
{{documentation subpage}}<br />
<!-- Categories go where indicated at the bottom of this page, please; interwikis go to Wikidata (see also: [[Wikipedia:Wikidata]]). --><br />
{{high-risk| 30,000+ }}<br />
</pre><br />
<br />
=== Technical details ===<br />
The [[{{translatable}}/sandbox|/sandbox]] and [[{{translatable}}/testcases|/testcases]] links are the standard names for such subpages. If those pages are created then the green /doc box for the template will detect them and link to them in its heading. For instance see the top of this documentation.<br />
<br />
=== See also ===<br />
* {{tl|intricate template}} – For the intricate, i.e., complex templates.<br />
* {{tl|pp-template}} – The protection template that usually is put on high-risk templates.<br />
* {{tl|used in system}} – For templates used in the user interface.<br />
<br />
}}<br />
</noinclude></div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=Template:High-risk&diff=3004Template:High-risk2021-01-18T16:40:34Z<p>Flying-sausages: 1 revision imported: Imported anchor templates from mediawiki</p>
<hr />
<div><noinclude><br />
<languages/><br />
</noinclude>{{#switch:<translate></translate><br />
| =<br />
{{ombox<br />
| type = content<br />
| image = [[File:OOjs UI icon alert-warning.svg|40px|alt=]]<br />
| imageright =<br />
| text = '''<translate><!--T:3--> This {{<tvar|1>#switch:{{NAMESPACE}}</>|<tvar|2>Module</>=Lua module|<tvar|3>#default</>=template}} is used on {{<tvar|4>#if:{{{1|}}}</>|approximately <tvar|5>{{formatnum:{{{1}}}}}</>|many}} pages.</translate>'''<br /><br />
<translate><!--T:2--> To avoid large-scale disruption and unnecessary server load, any changes to this {{<tvar|1>#switch:{{NAMESPACE}}</>|<tvar|2>Module</>=module|<tvar|3>#default</>=template}} should first be tested in its [[<tvar|4>{{#switch:{{SUBPAGENAME}}|doc|sandbox={{SUBJECTSPACE}}:{{BASEPAGENAME}}|#default={{SUBJECTPAGENAME}}}}/sandbox</>|/sandbox]] or [[<tvar|5>{{#switch:{{SUBPAGENAME}}|doc|sandbox={{SUBJECTSPACE}}:{{BASEPAGENAME}}|#default={{SUBJECTPAGENAME}}}}/testcases</>|/testcases]] subpages{{<tvar|6>#switch:{{NAMESPACE}}</>|<tvar|7>Module</>=.|<tvar|8>#default</>=&#32;or in your own [[<tvar|9>Special:MyLanguage/Help:Subpages#Use of subpages</>|user subpage]].}}</translate><br />
<translate><!--T:1--> The tested changes can then be added to this page in one single edit.</translate><br />
<translate><!--T:4--> Please consider discussing any changes {{<tvar|1>#if:{{{2|}}}</>|at <tvar|2>[[{{trim|{{{2}}}}}]]</>|on the [[<tvar|3>{{#switch:{{SUBPAGENAME}}|doc|sandbox={{TALKSPACE}}:{{BASEPAGENAME}}|#default={{TALKPAGENAME}}}}</>|talk page]]}} before implementing them.</translate><br />
}}<br />
| #default=<br />
{{#invoke:Template translation|renderTranslatedTemplate|template=Template:High-risk|noshift=1|uselang={{int:lang}}}}<br />
}}<noinclude><br />
{{Documentation|content=<br />
<br />
This is the {{tl|high-risk}} message box. It is meant to be put at the top of the documentation page on the most high-use (high-risk) templates and Lua modules (the template detects the name space), i.e., for templates used on a large number of pages<br />
<br />
'''''Note:''''' It is normal that some of the links in the message box are red.<br />
<translate><br />
=== Usage === <!--T:5--><br />
</translate><br />
The template can be used as is. But it can also take some parameters:<br />
<br />
* First parameter is the number of pages.<br />
* Second parameter is the name of some other talk page if you want discussion to be made there instead. But a better option might be to redirect the talkpage of your template to that other talkpage.<br />
<br />
<translate><br />
===Examples=== <!--T:6--><br />
</translate><br />
<pre><br />
{{high-risk| 30,000+ | Project:Current issues}}<br />
</pre><br />
<br />
{{high-risk| 30,000+ | Project:Current issues}}<br />
<br />
<pre><br />
{{high-risk| 30,000+ }}<br />
</pre><br />
<br />
{{high-risk| 30,000+ }}<br />
<br />
<pre><br />
{{high-risk| | Project:Current issues}}<br />
</pre><br />
<br />
{{high-risk| | Project:Current issues}}<br />
<br />
The full code for a /doc page top may look like this:<br />
<br />
<pre><br />
{{documentation subpage}}<br />
<!-- Categories go where indicated at the bottom of this page, please; interwikis go to Wikidata (see also: [[Wikipedia:Wikidata]]). --><br />
{{high-risk| 30,000+ }}<br />
</pre><br />
<br />
<translate><br />
=== Technical details === <!--T:7--><br />
</translate><br />
The [[{{translatable}}/sandbox|/sandbox]] and [[{{translatable}}/testcases|/testcases]] links are the standard names for such subpages. If those pages are created then the green /doc box for the template will detect them and link to them in its heading. For instance see the top of this documentation.<br />
<br />
<translate><br />
=== See also === <!--T:8--><br />
</translate><br />
* {{tl|intricate template}} – For the intricate, i.e., complex templates.<br />
* {{tl|pp-template}} – The protection template that usually is put on high-risk templates.<br />
* {{tl|used in system}} – For templates used in the user interface.<br />
<br />
}}<br />
</noinclude></div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=Template:Documentation&diff=3002Template:Documentation2021-01-18T16:40:33Z<p>Flying-sausages: 1 revision imported: Imported anchor templates from mediawiki</p>
<hr />
<div><noinclude><br />
<languages/><br />
</noinclude><includeonly>{{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}</includeonly><noinclude><br />
{{documentation|content=<br />
<br />
{{Lua|Module:Documentation}}<br />
<translate><!--T:12--> This template automatically displays a documentation box like the one you are seeing now, of which the content is sometimes transcluded from another page.</translate><br />
<translate><!--T:13--> It is intended for pages which are [[<tvar|1>Special:MyLanguage/Help:Transclusion</>|transcluded]] in other pages, i.e. templates, whether in the template namespace or not.</translate><br />
<br />
<translate><br />
==Usage== <!--T:2--><br />
<br />
===Customizing display=== <!--T:3--><br />
<br />
<!--T:4--><br />
Overrides exist to customize the output in special cases:<br />
</translate><br />
* <nowiki>{{</nowiki>documentation{{!}}'''heading'''=<nowiki>}}</nowiki> - <translate><!--T:5--> change the text of the "documentation" heading.</translate> <translate><!--T:10--> If this is set to blank, the entire heading line (including the first [edit] link) will also disappear.</translate><br />
<br />
<translate><br />
==Rationale== <!--T:6--><br />
</translate><br />
<translate><!--T:7--> This template allows any page to use any documentation page, and makes it possible to protect templates while allowing anyone to edit the template's documentation, categories, and interwiki links.</translate><br />
<translate><!--T:8--> It also reduces server resources by circumventing a [[w:Wikipedia:Template limits|technical limitation of templates]] (see a [[<tvar|1>:en:Special:Diff/69888944</>|developer's explanation]]).</translate><br />
<br />
<translate><br />
==See also== <!--T:9--><br />
</translate><br />
* <translate><!--T:14--> [[w:Template:Documentation subpage]]</translate><br />
* {{tim|Documentation}}<br />
* <translate><!--T:11--> [[w:Wikipedia:Template documentation]]</translate><br />
<br />
}}<br />
[[Category:Formatting templates{{#translation:}}|Template documentation]]<br />
[[Category:Template documentation{{#translation:}}| ]]<br />
</noinclude><includeonly>{{#if:{{{content|}}}|<br />
[[Category:Template documentation pages{{#translation:}}]]<br />
}}</includeonly></div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=Template:Visible_anchor&diff=3000Template:Visible anchor2021-01-18T16:40:33Z<p>Flying-sausages: 1 revision imported: Imported anchor templates from mediawiki</p>
<hr />
<div>{{#if:{{{2|}}}|<span id="{{{2}}}"></span>}}<!--<br />
-->{{#if:{{{3|}}}|<span id="{{{3}}}"></span>}}<!--<br />
-->{{#if:{{{4|}}}|<span id="{{{4}}}"></span>}}<!--<br />
-->{{#if:{{{5|}}}|<span id="{{{5}}}"></span>}}<!--<br />
-->{{#if:{{{6|}}}|<span id="{{{6}}}"></span>}}<!--<br />
-->{{#if:{{{7|}}}|<span id="{{{7}}}"></span>}}<!--<br />
-->{{#if:{{{8|}}}|<span id="{{{8}}}"></span>}}<!--<br />
-->{{#if:{{{9|}}}|<span id="{{{9}}}"></span>}}<!--<br />
-->{{#if:{{{10|}}}|<span id="{{{10}}}"></span>}}<!--<br />
-->{{#if:{{{1|}}}|<span id="{{{1}}}">{{{text|{{{1}}}}}}</span>}}<!--<br />
-->{{#if:{{{11|}}}|<span class="error">[[Template:Visible anchor]]: too many anchors, maximum is 10.</span>}}<noinclude><br />
<br />
{{Documentation}}<br />
<!-- PLEASE ADD CATEGORIES AND INTERWIKIS TO THE /doc SUBPAGE, THANKS --><br />
</noinclude></div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=Template:Shortcut&diff=2998Template:Shortcut2021-01-18T16:40:33Z<p>Flying-sausages: 1 revision imported: Imported anchor templates from mediawiki</p>
<hr />
<div><languages/><br />
<onlyinclude>{{#switch:<translate></translate><br />
| =<br />
<div style="{{#switch: {{dir|{{pagelang}}|left|right}}<br />
| right= float: right; clear: right; margin: 0 0 0.5em 0.5em;<br />
| left= float: left; clear: left; margin: 0 0 0.5em 0.5em;<br />
}} background: #ccff99; padding: 5px 8px; border-radius: 10px; font-size: 85%; text-align: center;"><translate><!--T:5--> {{PLURAL:<tvar|1>{{#if:{{{5|}}}|5|{{#if:{{{4|}}}|4|{{#if:{{{3|}}}|3|{{#if:{{{2|}}}|2|1}}}}}}}}</>|shortcut|shortcuts}}:</translate> <!--<br />
If there is only one, show "shortcut: FOO", other wise "shortcuts:<br />FOO<br />BAR.."<br />
-->{{#if: {{{1|}}} | {{#if: {{{2|}}} | <br /> }} [[{{{1|}}}|'''{{{1|}}}''']] }}<!--<br />
-->{{#if: {{{2|}}} | <br />[[{{{2|}}}|'''{{{2|}}}''']] }}<!--<br />
-->{{#if: {{{3|}}} | <br />[[{{{3|}}}|'''{{{3|}}}''']] }}<!--<br />
-->{{#if: {{{4|}}} | <br />[[{{{4|}}}|'''{{{4|}}}''']] }}<!--<br />
-->{{#if: {{{5|}}} | <br />[[{{{5|}}}|'''{{{5|}}}''']] }}<!--<br />
--></div><br />
| #default=<br />
{{#invoke:Template translation|renderTranslatedTemplate|template=Template:Shortcut|noshift=1}}<br />
}}</onlyinclude><br />
{{clear}}<br />
{{Documentation|content=<br />
<translate><br />
== Usage == <!--T:1--><br />
</translate><br />
{{Shortcut|RL2}}<br />
<pre>{{Shortcut|RL2}}</pre><br />
<br />
{{-}}<br />
{{Shortcut|RL2|RL/V2SPEC}}<br />
<pre>{{Shortcut|RL2|RL/V2SPEC}}</pre><br />
<br />
{{-}}<br />
{{Shortcut|a|b|c|d|e}}<br />
<pre>{{Shortcut|a|b|c|d|e}}</pre><br />
<br />
<translate><br />
<!--T:2--><br />
Supports up to 5 shortcuts.<br />
</translate><br />
}}<br />
[[Category:Utility templates{{#translation:}}|{{PAGENAME}}]]</div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=Template:Anchor&diff=2996Template:Anchor2021-01-18T16:40:33Z<p>Flying-sausages: 1 revision imported: Imported anchor templates from mediawiki</p>
<hr />
<div><!--<br />
-->{{#if:{{{ 1|}}}|<span id="{{anchorencode:{{{ 1|}}}}}"></span><!--<br />
-->{{#if:{{{ 2|}}}|<span id="{{anchorencode:{{{ 2|}}}}}"></span><!--<br />
-->{{#if:{{{ 3|}}}|<span id="{{anchorencode:{{{ 3|}}}}}"></span><!--<br />
-->{{#if:{{{ 4|}}}|<span id="{{anchorencode:{{{ 4|}}}}}"></span><!--<br />
-->{{#if:{{{ 5|}}}|<span id="{{anchorencode:{{{ 5|}}}}}"></span><!--<br />
-->{{#if:{{{ 6|}}}|<span id="{{anchorencode:{{{ 6|}}}}}"></span><!--<br />
-->{{#if:{{{ 7|}}}|<span id="{{anchorencode:{{{ 7|}}}}}"></span><!--<br />
-->{{#if:{{{ 8|}}}|<span id="{{anchorencode:{{{ 8|}}}}}"></span><!--<br />
-->{{#if:{{{ 9|}}}|<span id="{{anchorencode:{{{ 9|}}}}}"></span><!--<br />
-->{{#if:{{{10|}}}|<span id="{{anchorencode:{{{10|}}}}}"></span><!--<br />
-->{{#if:{{{11|}}}<br />
|<span class="error">[[Template:Anchor]] (or Anchors): too many anchors, maximum is ten</span><!--<br />
-->}}<!--<br />
-->}} }} }} }} }} }} }} }} }} }}<noinclude><br />
{{Documentation|content=<br />
{{high-use|5000}}<br />
== Usage ==<br />
See [[w:Template:Anchor]] for documentation.<br />
<br />
This version of the anchor template cannot be substituted. To insert an anchor without the template, use <code><nowiki><span id="Anchor name"></span></nowiki></code>.<br />
<br />
[[Category:Templates{{#translation:}}]]<br />
<templatedata><br />
{<br />
"description": {<br />
"en": "Define link target(s) to a section or element within current page",<br />
"de": "Linkziel(e) zu einem Abschnitt oder einem Element innerhalb der aktuellen Wiki-Seite vereinbaren"<br />
},<br />
"params": {<br />
"1": {<br />
"label": {<br />
"en": "Anchor",<br />
"de": "Anker"<br />
},<br />
"description": {<br />
"en": "Fragment ID",<br />
"de": "Fragmentbezeichner"<br />
},<br />
"type": "line",<br />
"required": true<br />
},<br />
"2": {<br />
"label": {<br />
"en": "Second anchor",<br />
"de": "Zweiter Anker"<br />
},<br />
"description": {<br />
"en": "Further fragment ID",<br />
"de": "Weiterer Fragmentbezeichner"<br />
},<br />
"required": false,<br />
"suggested": false,<br />
"inherits": "1"<br />
},<br />
"3": {<br />
"label": {<br />
"en": "Further anchor",<br />
"de": "Weiterer Anker"<br />
},<br />
"inherits": "2"<br />
},<br />
"4": {<br />
"label": { },<br />
"inherits": "3" },<br />
"5": { "inherits": "4" },<br />
"6": { "inherits": "4" },<br />
"7": { "inherits": "4" },<br />
"8": { "inherits": "4" },<br />
"9": { "inherits": "4" },<br />
"10": { "inherits": "4" },<br />
"11": { "inherits": "4" }<br />
},<br />
"format": "inline"<br />
}<br />
</templatedata><br />
}}<br />
</noinclude></div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=Sandbox&diff=2994Sandbox2021-01-18T16:29:50Z<p>Flying-sausages: </p>
<hr />
<div>'''This is for creating pages and making edits as well as to view changes before you push anything to live. Also please CLEAN UP AFTER YOUR SELF'''<br />
<br />
{{anchor|sct1}}<br />
## Section1<br />
<br />
{{vanchor|sct2}}<br />
## Section 2<br />
<br />
## Section 3<br />
{{shortcut|sct3}}</div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=System_status&diff=2601System status2020-12-02T21:58:11Z<p>Flying-sausages: /* Radarr */</p>
<hr />
<div>== System ==<br />
=== Health ===<br />
==== Overview ====<br />
====== Radarr ======<br />
<section begin=radarr_system_status_health_overview /><br />
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.<br />
<section end=radarr_system_status_health_overview /><br />
====== Sonarr ======<br />
<section begin=sonarr_system_status_health_overview /><br />
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.<br />
<section end=sonarr_system_status_health_overview /><br />
====== Lidarr ======<br />
<section begin=lidarr_system_status_health_overview /><br />
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.<br />
<section end=lidarr_system_status_health_overview /><br />
====== Readarr ======<br />
<section begin=readarr_system_status_health_overview /><br />
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.<br />
<section end=readarr_system_status_health_overview /><br />
==== System Warnings ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_system_warnings /><br />
* <span id="update-to-net-core-version">'''[[#update-to-net-core-version|Update to .NET Core version]]'''</span><br />
** 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.<br />
** Fixing Docker installs<br />
*** Re-pull your container<br />
** Fixing Standalone installs<br />
*** This should only happen on Linux hosts. <span style="color:#ff0000">'''Do not install .net core runtime or SDK from microsoft.'''</span> To remedy, download the correct build for your architecture: <br />
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64]<br />
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64]<br />
****[https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br />
***<span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br />
*** '''Delete your existing binaries' (contents or folder of /opt/Radarr)''' and replace with the contents of the <code>.tar.gz</code> you just downloaded.<br />
***<span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br />
**** Update your startup script to call <code>Radarr</code> instead of calling it with mono like <code>mono --debug Radarr.exe</code>. In other words you want, as an example, <code>/opt/Radarr/Radarr</code> and '''not''' <code>mono --debug /opt/Radarr/Radarr</code>.<br />
*** If Radarr doesn’t start, ensure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br />
** Managed/tooled installs<br />
*** For instructions for Swizzin installs, please read the [https://swizzin.ltd/applications/radarr/#migrating-to-v3-on-net-core Swizzin Docs article]<br />
*** For instructions on Whatbox, please see the [https://whatbox.ca/wiki/Radarr#radarr_v3_(unstable) WB Wiki article]<br />
*<span id="Mono_version_is_less_than_3_10_upgrade_for_improved_stability">'''[[#Mono_version_is_less_than_3_10_upgrade_for_improved_stability|Mono version is less than 3.10, upgrade for improved stability]]'''</span><br />
** 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.<br /><br />
** Mono version 4.x and higher are also available and provides a better experience on certain platforms.<br />
** See "Update to .NET Core version above"<br />
*<span id="New_update_is_available">'''[[#New_update_is_available|New update is available]]'''</span><br />
** 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 -&gt; Updates page is probably a good starting point.<br />
**''(This warning will not appear if your current version is less than 14 days old)''<br />
*<span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#Cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br />
** 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.<br />
*<span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''[[#Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br />
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br />
** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br />
** This means Radarr will be unable to update itself without risking data-loss.<br />
** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br />
*<span id="Branch_is_for_a_previous_version">'''[[#Branch_is_for_a_previous_version|Branch is for a previous version]]'''</span><br />
** 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.<br />
**'''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.<br />
*<span id="Could_not_connect_to_signalR">'''[[#Could_not_connect_to_signalR|Could not connect to signalR]]'''</span><br />
** 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.<br />
** 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:<br />
*::<code>proxy_http_version 1.1;</code><br />
*::<code>proxy_set_header Upgrade $http_upgrade;</code><br />
*::<code>proxy_set_header Connection $http_connection;</code><br />
** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br />
** See https://github.com/aspnet/AspNetCore/issues/17081<br />
** For apache reverse proxy you need to add to the configuration:<br />
*::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br />
*::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br />
*::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br />
* <span id="missing-root-folder">'''[[#missing-root-folder|Missing Root Folder]]'''</span><br />
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available. <br />
*** 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<br />
*** Easiest way to find this is to go to the Movies (Library) Tab and create a custom filter with the old root folder path and then mass edit these movies to the new path.<br />
<section end=radarr_system_status_health_system_warnings /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_system_warnings /><br />
* <span id="Currently_installed_Net_Framework_is_old_and_unsupported">'''[[#Currently_installed_Net_Framework_is_old_and_unsupported|Currently installed .Net Framework is old and unsupported]]</span>'''<br />
** 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.<br />
** 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.<br />
* <span id="Currently_installed_Net_Framework_is_supported_but_upgrading_is_recommended">'''[[#Currently_installed_Net_Framework_is_supported_but_upgrading_is_recommended|Currently installed .Net Framework is supported but upgrading is recommended]]'''</span><br />
** 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.<br />
** 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.<br />
* <span id="Currently_installed_mono_version_is_old_and_unsupported">'''[[#Currently_installed_mono_version_is_old_and_unsupported|Currently installed mono version is old and unsupported]]'''</span><br />
** 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.<br /><br />
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br />
** The upgrade procedure for Mono varies per platform.<br />
* <span id="Currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''[[#Currently_installed_mono_version_is_supported_but_upgrading_is_recommended|Currently installed mono version is supported but upgrading is recommended]]'''</span><br />
** 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.<br />
** The upgrade procedure for Mono varies per platform.<br />
* <span id="New_update_is_available">'''[[#New_update_is_available|New update is available]]'''</span><br />
** 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 -&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.<br />
** ''(This warning will not appear if your current version is less than 14 days old)''<br />
* <span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''[[#Cannot_install_update_because_startup_folder_is_not_writable_by_the_user|Cannot install update because startup folder is not writable by the user]]'''</span><br />
** 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.<br />
* <span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''[[#Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update|Updating will not be possible to prevent deleting AppData on Update]]'''</span><br />
**Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br />
** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br />
** This means Sonarr will be unable to update itself without risking data-loss.<br />
** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br />
<section end=sonarr_system_status_health_system_warnings /><br />
<br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_system_warnings /><br />
Text<br />
<section end=lidarr_system_status_health_system_warnings /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_system_warnings /><br />
Text<br />
<section end=readarr_system_status_health_system_warnings /><br />
<br />
<br />
==== Download Clients ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_download_clients /><br />
* <span id="no_download_client_is_available>'''[[#no_download_client_is_available|No download client is available]]'''</span><br />
** 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 -&gt; Download Client.<br />
* <span id="unable-to-communicate-with-download-client">'''[[#unable-to-communicate-with-download-client|Unable to communicate with download client]]'''</span><br />
** 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.<br />
** This is typically due to improperlly configured download client. Things you can typically check:<br />
*** Your download clients IP Address if its on the same bare metal machien this is typically <code>127.0.0.1</code><br />
*** 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.<br />
*** 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.<br />
* <span id="Download_clients_are_unavailable_due_to_failure">'''[[#Download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br />
** 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.<br />
** You should inspect System-&gt;Logs to see what the reason is for the failures.<br />
** If you no longer use this download client, disable it in Radarr to prevent the errors.<br />
* <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span><br />
** 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.<br />
** ''(Completed Download Handling is enabled by default for new users.)''<br />
* <span id="docker-bad-remote-path-mapping">'''[[#docker-bad-remote-path-mapping|Docker bad remote path mapping]]'''</span><br />
** This error is typically associated with bad docker paths within either your download client or Radarr<br />
*** An example of this would be:<br />
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code><br />
**** Radarr: <code>Download Path: /data:/mnt/user/downloads</code><br />
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.<br />
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.<br />
**** Team Radarr is a big fan of simply using <code>/data</code>.<br />
***** Download client: <code>/data:/mnt/user/data</code><br />
***** Radarr: <code>/data:/mnt/user/data</code><br />
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."<br />
*** 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.<br />
<section end=radarr_system_status_health_download_clients /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_download_clients /><br />
* <span id="No_download_client_is_available">'''[[#No_download_client_is_available|No download client is available]]'''</span><br />
** 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 -&gt; Download Client.<br />
*<span id="unable-to-communicate-with-download-client">'''[[#unable-to-communicate-with-download-client|Unable to communicate with download client]]'''</span><br />
** 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.<br />
* <span id="Download_clients_are_unavailable_due_to_failure">'''[[#Download_clients_are_unavailable_due_to_failure|Download clients are unavailable due to failure]]'''</span><br />
** 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.<br />
** You should inspect System-&gt;Logs to see what the reason is for the failures.<br />
** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br />
* <span id="Enable_Completed_Download_Handling_or_configure_Drone_Factory">'''[[#Enable_Completed_Download_Handling_or_configure_Drone_Factory|Enable Completed Download Handling or configure Drone Factory]]'''</span><br />
** Sonarr requires Completed Download Handling or a properly configured Drone Factory to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br />
** ''(Completed Download Handling is enabled by default for new users.)''<br />
<section end=sonarr_system_status_health_download_clients /><br />
<br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_download_clients /><br />
Text<br />
<section end=lidarr_system_status_health_download_clients /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_download_clients /><br />
Text<br />
<section end=readarr_system_status_health_download_clients /><br />
<br />
==== Completed/Failed Download Handling ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_complete_failed_download_handling /><br />
* <span id="Completed_Download_Handling_is_disabled">'''[[#Completed_Download_Handling_is_disabled|Completed Download Handling is disabled]]'''</span><br />
** ''(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.)''<br />
** 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.<br />
** 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.<br />
** 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)<br /><br />
** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.<br /><br />
** 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.<br />
** 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 -&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.<br />
<section end=radarr_system_status_health_complete_failed_download_handling /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_complete_failed_download_handling /><br />
* <span id="Completed_Download_Handling_is_disabled">'''[[#Completed_Download_Handling_is_disabled|Completed Download Handling is disabled]]'''</span><br />
**''(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.)''<br />
** 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.<br />
** 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.<br />
** If you wish to enable Completed Download Handling you should verify the following:<br />
*** '''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.<br />
*** 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.<br />
*** 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)<br /><br />
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.<br />
** 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 -&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.<br />
<section end=sonarr_system_status_health_complete_failed_download_handling /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_complete_failed_download_handling /><br />
Text<br />
<section end=lidarr_system_status_health_complete_failed_download_handling /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_complete_failed_download_handling /><br />
Text<br />
<section end=readarr_system_status_health_complete_failed_download_handling /><br />
<br />
<br />
==== Indexers ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_indexers /><br />
* <span id="No_indexers_are_enabled">'''[[#No_indexers_are_enabled|No indexers are enabled]]'''</span><br />
** Radarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br />
* <span id="Enabled_indexers_do_not_support_searching">'''[[#Enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span><br />
** 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.<br />
* <span id="Indexers_are_unavailable_due_to_failures">'''[[#Indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br />
** 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).<br />
** 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.<br />
** You can prevent the warning by disabling the affected indexer.<br />
** 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.<br />
<section end=radarr_system_status_health_indexers /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_indexers /><br />
* <span id="No_indexers_are_enabled">'''[[#No_indexers_are_enabled|No indexers are enabled]]'''</span><br />
** Sonarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br />
* <span id="Enabled_indexers_do_not_support_searching">'''[[#Enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''</span><br />
** 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.<br />
* <span id="Indexers_are_unavailable_due_to_failures">'''[[#Indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span><br />
** 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).<br /><br />
** 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.<br />
** You can prevent the warning by disabling the affected indexer.<br />
**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.<br />
<section end=sonarr_system_status_health_indexers /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_indexers /><br />
Text<br />
<section end=lidarr_system_status_health_indexers /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_indexers /><br />
Text<br />
<section end=readarr_system_status_health_indexers /><br />
<br />
==== Folders ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_folders /><br />
* <span id="Missing_root_folder">'''[[#Missing_root_folder|Missing root folder]]'''</span><br />
** This message may appear if a previous root folder is no longer used. To remove old root folders:<br />
*** Begin adding a new Movie* by searching for a name, but do not submit<br />
*** In the 'Path' dropdown, select 'Add a different path'<br />
*** Click the cross at the end of a row to remove the unused path<br />
** Note - if the folder has been removed from the operating system, you will need to recreate the folder in the operating system, and restart Radarr, or else you will not be able to select it from the dropdown box. After that you can remove the path from the operating system.<br />
** The message will continue to appear until all movies have their root folder updated to the new root folder. To change the root folder for other movies, visit the movies editor.<br />
*** NB: I thought Radarr was for Movies and not Series<br />
<section end=radarr_system_status_health_folders /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_folders /><br />
* <span id="Missing root folder">'''[[#Missing root folder|Missing root folder]]'''</span><br />
** This message may appear if a previous root folder is no longer used. To remove old root folders:<br />
**# Begin adding a new Series by searching for a name, but do not submit<br />
**# In the 'Path' dropdown, select 'Add a different path'<br />
**# Click the cross at the end of a row to remove the unused path<br />
** Note - if the folder has been removed from the operating system, you will need to recreate the folder in the operating system, and restart Sonarr, or else you will not be able to select it from the dropdown box. After that you can remove the path from the operating system.<br />
** The message will continue to appear until all series have their root folder updated to the new root folder. To change the root folder for other series, visit the series editor.<br />
<section end=sonarr_system_status_health_folders /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_folders /><br />
Text<br />
<section end=lidarr_system_status_health_folders /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_folders /><br />
Text<br />
<section end=readarr_system_status_health_folders /><br />
<br />
==== Media ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_media /><br />
* <span id="Movie was removed from TMDb">'''[[#Movie was removed from TMDb|Movie was removed from TMDb]]'''</span><br />
** The specific movie is linked to a TMDbId that was deleted from TMDb. This may mean that the movie was either removed from the DB, was a duplicate, or was re-assigned a new ID for some reason. Deleted movies will not receive any info updates and should be corrected by the user to ensure continued functionality.<br /><br />
** 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<br />
<section end=radarr_system_status_health_media /><br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_media /><br />
* <span id="Series_Removed_from_TheTVDB">'''[[#Series_Removed_from_TheTVDB|Series Removed from TheTVDB]]'''</span><br />
** 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.<br />
<section end=sonarr_system_status_health_media /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_media /><br />
Text<br />
<section end=lidarr_system_status_health_media /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_media /><br />
Text<br />
<section end=readarr_system_status_health_media /><br />
<br />
=== Disk Space ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_disk_space /><br />
* This section will show you available disk space<br />
** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br />
<section end=radarr_system_status_disk_space /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_disk_space /><br />
Text<br />
<section end=sonarr_system_status_disk_space /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_disk_space /><br />
Text<br />
<section end=lidarr_system_status_disk_space /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_disk_space /><br />
Text<br />
<section end=readarr_system_status_disk_space /><br />
<br />
=== About ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_about /><br />
This will tell you about your current install of Radarr<br />
<section end=radarr_system_status_about /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_about /><br />
Text<br />
<section end=sonarr_system_status_about /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_about /><br />
Text<br />
<section end=lidarr_system_status_about /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_about /><br />
Text<br />
<section end=readarr_system_status_about /><br />
<br />
=== More Info ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_more_info /><br />
* Home page: [https://radarr.video Radarr's home page]<br />
* Discord: [https://discord.gg/r5wJPt9 Join our discord]<br />
* Wiki: [https://wiki.servarr.com You're here already]<br />
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]<br />
* Source: [https://github.com/Radarr/Radarr Github]<br />
* Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]<br />
<section end=radarr_system_status_more_info /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_more_info /><br />
Text<br />
<section end=sonarr_system_status_more_info /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_more_info /><br />
Text<br />
<section end=lidarr_system_status_more_info /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_more_info /><br />
Text<br />
<section end=readarr_system_status_more_info /><br />
<br />
=== Templates ===</div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=System_status&diff=2430System status2020-11-29T16:44:42Z<p>Flying-sausages: /* Radarr */ Change URLs to point to `master`, move shared bullets above</p>
<hr />
<div>== System ==<br />
=== Health ===<br />
==== Overview ====<br />
====== Radarr ======<br />
<section begin=radarr_system_status_health_overview /><br />
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.<br />
<section end=radarr_system_status_health_overview /><br />
<br />
====== Sonarr ======<br />
<section begin=sonarr_system_status_health_overview /><br />
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.<br />
<section end=sonarr_system_status_health_overview /><br />
====== Lidarr ======<br />
<section begin=lidarr_system_status_health_overview /><br />
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.<br />
<section end=lidarr_system_status_health_overview /><br />
====== Readarr ======<br />
<section begin=readarr_system_status_health_overview /><br />
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.<br />
<section end=readarr_system_status_health_overview /><br />
<br />
==== System Warnings ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_system_warnings /><br />
* <span id="update-to-net-core-version">'''Update to .NET Core version'''</span><br />
** 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.<br />
** Fixing Docker installs<br />
*** Re-pull your container<br />
** Fixing Standalone installs<br />
*** This should only happen on linux hosts. To remedy, download the correct build for your architecture: <br />
**** [https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 x64] <br />
**** [https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm64 arm64] <br />
**** [https://radarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=arm arm]<br />
*** <span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br />
*** '''Delete your existing binaries''' and replace with the contents of the <code>.tar.gz</code> you just downloaded. <br />
*** <span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br />
**** Update your startup script to call <code>Radarr</code> instead of <code>mono --debug Radarr.exe</code><br />
*** If Radarr doesn’t start make sure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br />
* <span id="Mono_version_is_less_than_3_10_upgrade_for_improved_stability">'''Mono version is less than 3.10, upgrade for improved stability'''</span><br />
** 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.<br /><br />
** Mono version 4.x and higher are also available and provides a better experience on certain platforms.<br />
** See "Update to .NET Core version above"<br />
* <span id="New_update_is_available">'''New update is available'''</span><br />
** 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 -&gt; Updates page is probably a good starting point.<br />
** ''(This warning will not appear if your current version is less than 14 days old)''<br />
* <span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''Cannot install update because startup folder is not writable by the user'''</span><br />
** 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.<br />
* <span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''Updating will not be possible to prevent deleting AppData on Update'''</span><br />
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br />
** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br />
** This means Radarr will be unable to update itself without risking data-loss.<br />
** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br />
* <span id="Branch_is_for_a_previous_version">'''Branch is for a previous version'''</span><br />
** 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.<br />
** '''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.<br />
* <span id="Could_not_connect_to_signalR">'''Could not connect to signalR'''</span><br />
** 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.<br />
** 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: <br />
*::<code>proxy_http_version 1.1;</code><br />
*::<code>proxy_set_header Upgrade $http_upgrade;</code><br />
*::<code>proxy_set_header Connection $http_connection;</code><br />
** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br />
** See https://github.com/aspnet/AspNetCore/issues/17081<br />
** For apache reverse proxy you need to add to the configuration:<br />
*::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br />
*::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br />
*::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br />
<section end=radarr_system_status_health_system_warnings /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_system_warnings /><br />
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.<br />
* '''Currently installed .Net Framework is old and unsupported'''<br />
** 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.<br />
** 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.<br />
* <span id="Currently_installed_Net_Framework_is_supported_but_upgrading_is_recommended">'''Currently installed .Net Framework is supported but upgrading is recommended '''</span><br />
** 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.<br />
** 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.<br />
* <span id="Currently_installed_mono_version_is_old_and_unsupported">'''Currently installed mono version is old and unsupported'''</span><br />
** 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.<br /><br />
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br />
** The upgrade procedure for Mono varies per platform.<br />
* <span id="Currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''Currently installed mono version is supported but upgrading is recommended'''</span><br />
** 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.<br />
** The upgrade procedure for Mono varies per platform.<br />
* <span id="New_update_is_available">'''New update is available'''</span><br />
** 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 -&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.<br />
** ''(This warning will not appear if your current version is less than 14 days old)''<br />
* <span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''Cannot install update because startup folder is not writable by the user'''</span><br />
** 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.<br />
* <span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''Updating will not be possible to prevent deleting AppData on Update'''</span><br />
**Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br />
** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br />
** This means Sonarr will be unable to update itself without risking data-loss.<br />
** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br />
<section end=sonarr_system_status_health_system_warnings /><br />
<br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_system_warnings /><br />
Text<br />
<section end=lidarr_system_status_health_system_warnings /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_system_warnings /><br />
Text<br />
<section end=readarr_system_status_health_system_warnings /><br />
<br />
<br />
==== Download Clients ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_download_clients /><br />
* <span id="no_download_client_is_available>'''No download client is available'''</span><br />
** 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 -&gt; Download Client.<br />
** Unable to communicate with download client<br />
** 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.<br />
* <span id="Download_clients_are_unavailable_due_to_failure">'''Download clients are unavailable due to failure'''</span><br />
** 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.<br />
** You should inspect System-&gt;Logs to see what the reason is for the failures.<br />
** If you no longer use this download client, disable it in Radarr to prevent the errors.<br />
* <span id="enable_complete_download_handling">'''Enable Completed Download Handling'''</span><br />
** 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.<br />
** ''(Completed Download Handling is enabled by default for new users.)''<br />
<section end=radarr_system_status_health_download_clients /><br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_download_clients /><br />
* <span id="No_download_client_is_available">'''No download client is available'''</span><br />
** 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 -&gt; Download Client.<br />
** Unable to communicate with download client ====<br />
** 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.<br />
* <span id="Download_clients_are_unavailable_due_to_failure">'''Download clients are unavailable due to failure'''</span><br />
** 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.<br />
** You should inspect System-&gt;Logs to see what the reason is for the failures.<br />
** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br />
* <span id="Enable_Completed_Download_Handling_or_configure_Drone_Factory">'''Enable Completed Download Handling or configure Drone Factory'''</span><br />
** Sonarr requires Completed Download Handling or a properly configured Drone Factory to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br />
** ''(Completed Download Handling is enabled by default for new users.)''<br />
<section end=sonarr_system_status_health_download_clients /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_download_clients /><br />
Text<br />
<section end=lidarr_system_status_health_download_clients /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_download_clients /><br />
Text<br />
<section end=readarr_system_status_health_download_clients /><br />
<br />
<br />
==== Drone Factory ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_drone_factory /><br />
* Drone Factory<br />
** Drone Factory folder does not exist<br />
*** If you configure Radarr to use a Drone Factory the specified folder must exist. Please ensure that it indeed exists, or disable the Drone Factory.<br />
*** ''(You might want to consider using Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients.)''<br />
** Unable to write to Drone Factory folder <br />
*** You configured Radarr to use a Drone Factory, however Radarr was unable to creates a test file, this indicates permission issues. Please verify that the user Radarr runs under has the appropriate permissions.<br />
** Drone Factory is deprecated<br />
*** '''Please don’t panic.'''<br />
*** The Drone Factory is unreliable in various situations and has been replaced by Completed Download Handling and external API calls over a year ago. This functionality will be removed in a future major version of Radarr and should no longer be used. ''Please note that the Drone Factory periodic scan functionality will not be removed via an automatic update, but rolled into an future backward-incompatible v3 major release which in most cases will require manual installation.''<br />
*** For occasional manual downloads use Wanted-&gt;Manual Import. It’ll allow you to select a directory and optionally review the parsing results before actually importing. Useful for the occasional manual download that isn’t handled automatically.<br />
*** If the download client is on a remote machine, consider using remote mounts in combination with Settings-&gt;Download Clients-&gt;Remote Path Mapping to make Radarr aware of the mount. Alternatives are available.<br />
*** Please disable the Drone Factory:<br />
**** Go to Settings-&gt;Download Clients<br />
**** Enable Advanced Settings in the top left<br />
**** Make sure the Drone Factory field is empty<br />
**** Make sure the Drone Factory Interval field is set to 0<br />
**** Save settings<br />
<section end=radarr_system_status_health_drone_factory /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_drone_factory /><br />
Text<br />
<section end=sonarr_system_status_health_drone_factory /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_drone_factory /><br />
Text<br />
<section end=lidarr_system_status_health_drone_factory /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_drone_factory /><br />
Text<br />
<section end=readarr_system_status_health_drone_factory /><br />
<br />
<br />
==== Completed/Failed Download Handling ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_complete_failed_download_handling /><br />
* <span id="Completed_Download_Handling_is_disabled">'''Completed Download Handling is disabled'''</span><br />
** ''(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.)''<br />
** 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.<br />
** 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.<br />
** 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)<br /><br />
** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.<br /><br />
** 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.<br />
** 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 -&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.<br />
* <span id="Download_Client_has_history_items_in_Drone_Factory_conflicting_with_Completed_Download_Handling">'''Download Client has history items in Drone Factory conflicting with Completed Download Handling '''</span><br />
** The Download Client put finished downloads inside the Drone Factory even though Completed Download Handling is configured. This could potentially cause both Completed Download Handling and the Drone Factory logic to import the same download simultaneously. To avoid conflicts Radarr will ignore those downloads during it’s Completed Download Handling logic, leaving it to be handled by the Drone Factory. This is a suboptimal situation since this effectively disabled Completed Download Handling.<br />
** Resolution: Configure the Drone Factory to use a different folder.<br />
'''''TODO: Reword'''''<br />
<br />
<section end=radarr_system_status_health_complete_failed_download_handling /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_complete_failed_download_handling /><br />
* <span id="Completed_Download_Handling_is_disabled">'''Completed Download Handling is disabled'''</span><br />
** ''(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.)''<br />
** 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.<br />
** 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.<br />
** If you wish to enable Completed Download Handling you should verify the following:<br />
*** '''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.<br />
*** 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.<br />
*** 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)<br /><br />
** You should reconfigure Sonarr to use a different Drone Factory Folder or disable it altogether.<br /><br />
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.<br />
** 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 -&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.<br />
* <span id="Download_Client_has_history_items_in_Drone_Factory_conflicting_with_Completed_Download_Handling">'''Download Client has history items in Drone Factory conflicting with Completed Download Handling'''</span><br />
** The Download Client put finished downloads inside the Drone Factory even though Completed Download Handling is configured. This could potentially cause both Completed Download Handling and the Drone Factory logic to import the same download simultaneously. To avoid conflicts Sonarr will ignore those downloads during it's Completed Download Handling logic, leaving it to be handled by the Drone Factory. This is a suboptimal situation since this effectively disabled Completed Download Handling.<br />
** Resolution: Configure the Drone Factory to use a different folder.<br />
** '''''TODO: Reword'''''<br />
<section end=sonarr_system_status_health_complete_failed_download_handling /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_complete_failed_download_handling /><br />
Text<br />
<section end=lidarr_system_status_health_complete_failed_download_handling /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_complete_failed_download_handling /><br />
Text<br />
<section end=readarr_system_status_health_complete_failed_download_handling /><br />
<br />
<br />
==== Indexers ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_indexers /><br />
* <span id="No_indexers_are_enabled">'''No indexers are enabled'''</span><br />
** Radarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br />
* <span id="Enabled_indexers_do_not_support_searching">'''Enabled indexers do not support searching''' </span><br />
** 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.<br />
* <span id="Indexers_are_unavailable_due_to_failures">'''Indexers are unavailable due to failures'''</span><br />
** 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).<br />
** 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.<br />
** You can prevent the warning by disabling the affected indexer.<br />
** 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.<br />
<section end=radarr_system_status_health_indexers /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_indexers /><br />
* <span id="No_indexers_are_enabled">'''No indexers are enabled'''</span><br />
** Sonarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br />
* <span id="Enabled_indexers_do_not_support_searching">'''Enabled indexers do not support searching'''</span><br />
** 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.<br />
* <span id="Indexers_are_unavailable_due_to_failures">'''Indexers are unavailable due to failures'''</span><br />
** 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).<br /><br />
** 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.<br />
** You can prevent the warning by disabling the affected indexer.<br />
**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.<br />
<section end=sonarr_system_status_health_indexers /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_indexers /><br />
Text<br />
<section end=lidarr_system_status_health_indexers /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_indexers /><br />
Text<br />
<section end=readarr_system_status_health_indexers /><br />
<br />
<br />
==== Folders ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_folders /><br />
* <span id="Missing_root_folder">'''Missing root folder'''</span><br />
** This message may appear if a previous root folder is no longer used. To remove old root folders:<br />
*** Begin adding a new Movie* by searching for a name, but do not submit<br />
*** In the 'Path' dropdown, select 'Add a different path'<br />
*** Click the cross at the end of a row to remove the unused path<br />
** Note - if the folder has been removed from the operating system, you will need to recreate the folder in the operating system, and restart Radarr, or else you will not be able to select it from the dropdown box. After that you can remove the path from the operating system.<br />
** The message will continue to appear until all movies have their root folder updated to the new root folder. To change the root folder for other movies, visit the movies editor.<br />
*** NB: I thought Radarr was for Movies and not Series<br />
<section end=radarr_system_status_health_folders /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_folders /><br />
* <span id="Missing root folder">'''Missing root folder'''</span><br />
** This message may appear if a previous root folder is no longer used. To remove old root folders:<br />
**# Begin adding a new Series by searching for a name, but do not submit<br />
**# In the 'Path' dropdown, select 'Add a different path'<br />
**# Click the cross at the end of a row to remove the unused path<br />
** Note - if the folder has been removed from the operating system, you will need to recreate the folder in the operating system, and restart Sonarr, or else you will not be able to select it from the dropdown box. After that you can remove the path from the operating system.<br />
** The message will continue to appear until all series have their root folder updated to the new root folder. To change the root folder for other series, visit the series editor.<br />
<section end=sonarr_system_status_health_folders /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_folders /><br />
Text<br />
<section end=lidarr_system_status_health_folders /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_folders /><br />
Text<br />
<section end=readarr_system_status_health_folders /><br />
<br />
==== Media ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_media /><br />
* <span id="Movie was removed from TMDb">'''Movie was removed from TMDb'''</span><br />
** The specific movie is linked to a TMDbId that was deleted from TMDb. This may mean that the movie was either removed from the DB, was a duplicate, or was re-assigned a new ID for some reason. Deleted movies will not receive any info updates and should be corrected by the user to ensure continued functionality.<br /><br />
** 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<br />
<section end=radarr_system_status_health_media /><br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_media /><br />
* <span id="Series_Removed_from_TheTVDB">'''Series Removed from TheTVDB'''</span><br />
** 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.<br />
<section end=sonarr_system_status_health_media /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_media /><br />
Text<br />
<section end=lidarr_system_status_health_media /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_media /><br />
Text<br />
<section end=readarr_system_status_health_media /><br />
<br />
=== Disk Space ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_disk_space /><br />
* This section will show you available disk space<br />
** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br />
<section end=radarr_system_status_disk_space /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_disk_space /><br />
Text<br />
<section end=sonarr_system_status_disk_space /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_disk_space /><br />
Text<br />
<section end=lidarr_system_status_disk_space /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_disk_space /><br />
Text<br />
<section end=readarr_system_status_disk_space /><br />
<br />
=== About ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_about /><br />
This will tell you about your current install of Radarr<br />
<section end=radarr_system_status_about /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_about /><br />
Text<br />
<section end=sonarr_system_status_about /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_about /><br />
Text<br />
<section end=lidarr_system_status_about /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_about /><br />
Text<br />
<section end=readarr_system_status_about /><br />
<br />
=== More Info ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_more_info /><br />
* Home page: [https://radarr.video Radarr's home page]<br />
* Discord: [https://discord.gg/r5wJPt9 Join our discord]<br />
* Wiki: [https://wiki.servarr.com You're here already]<br />
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]<br />
* Source: [https://github.com/Radarr/Radarr Github]<br />
* Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]<br />
<section end=radarr_system_status_more_info /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_more_info /><br />
Text<br />
<section end=sonarr_system_status_more_info /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_more_info /><br />
Text<br />
<section end=lidarr_system_status_more_info /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_more_info /><br />
Text<br />
<section end=readarr_system_status_more_info /><br />
<br />
=== Templates ===</div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=System_status&diff=2428System status2020-11-29T16:37:50Z<p>Flying-sausages: Add docker-specific flow</p>
<hr />
<div>== System ==<br />
=== Health ===<br />
==== Overview ====<br />
====== Radarr ======<br />
<section begin=radarr_system_status_health_overview /><br />
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.<br />
<section end=radarr_system_status_health_overview /><br />
<br />
====== Sonarr ======<br />
<section begin=sonarr_system_status_health_overview /><br />
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.<br />
<section end=sonarr_system_status_health_overview /><br />
====== Lidarr ======<br />
<section begin=lidarr_system_status_health_overview /><br />
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.<br />
<section end=lidarr_system_status_health_overview /><br />
====== Readarr ======<br />
<section begin=readarr_system_status_health_overview /><br />
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.<br />
<section end=readarr_system_status_health_overview /><br />
<br />
==== System Warnings ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_system_warnings /><br />
* <span id="update-to-net-core-version">'''Update to .NET Core version'''</span><br />
** Docker installs<br />
*** Re-pull your container<br />
** Standalone installs<br />
*** 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.<br />
*** This should only happen on linux hosts. To remedy, download the correct build for your architecture: <br />
**** [https://radarr.servarr.com/v1/update/nightly/updatefile?os=linux&runtime=netcore&arch=x64 x64] <br />
**** [https://radarr.servarr.com/v1/update/nightly/updatefile?os=linux&runtime=netcore&arch=arm64 arm64] <br />
**** [https://radarr.servarr.com/v1/update/nightly/updatefile?os=linux&runtime=netcore&arch=arm arm]<br />
*** <span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br />
*** '''Delete your existing binaries''' and replace with the contents of the <code>.tar.gz</code> you just downloaded. <br />
*** <span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br />
**** Update your startup script to call <code>Radarr</code> instead of <code>mono --debug Radarr.exe</code><br />
*** If Radarr doesn’t start make sure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br />
* <span id="Mono_version_is_less_than_3_10_upgrade_for_improved_stability">'''Mono version is less than 3.10, upgrade for improved stability'''</span><br />
** 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.<br /><br />
** Mono version 4.x and higher are also available and provides a better experience on certain platforms.<br />
** See "Update to .NET Core version above"<br />
* <span id="New_update_is_available">'''New update is available'''</span><br />
** 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 -&gt; Updates page is probably a good starting point.<br />
** ''(This warning will not appear if your current version is less than 14 days old)''<br />
* <span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''Cannot install update because startup folder is not writable by the user'''</span><br />
** 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.<br />
* <span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''Updating will not be possible to prevent deleting AppData on Update'''</span><br />
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br />
** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br />
** This means Radarr will be unable to update itself without risking data-loss.<br />
** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br />
* <span id="Branch_is_for_a_previous_version">'''Branch is for a previous version'''</span><br />
** 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.<br />
** '''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.<br />
* <span id="Could_not_connect_to_signalR">'''Could not connect to signalR'''</span><br />
** 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.<br />
** 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: <br />
*::<code>proxy_http_version 1.1;</code><br />
*::<code>proxy_set_header Upgrade $http_upgrade;</code><br />
*::<code>proxy_set_header Connection $http_connection;</code><br />
** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br />
** See https://github.com/aspnet/AspNetCore/issues/17081<br />
** For apache reverse proxy you need to add to the configuration:<br />
*::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br />
*::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br />
*::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br />
* <span id="Please upgrade to the .NET Core version of Radarr">'''Please upgrade to the .NET Core version of Radarr'''</span><br />
** If using docker linuxserver/radarr....are you updating radarr inside the container? if, Yes, then stop doing that. docker container should never be upgraded inside the container, remove it and pull a new one.<br />
<section end=radarr_system_status_health_system_warnings /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_system_warnings /><br />
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.<br />
* '''Currently installed .Net Framework is old and unsupported'''<br />
** 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.<br />
** 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.<br />
* <span id="Currently_installed_Net_Framework_is_supported_but_upgrading_is_recommended">'''Currently installed .Net Framework is supported but upgrading is recommended '''</span><br />
** 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.<br />
** 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.<br />
* <span id="Currently_installed_mono_version_is_old_and_unsupported">'''Currently installed mono version is old and unsupported'''</span><br />
** 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.<br /><br />
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br />
** The upgrade procedure for Mono varies per platform.<br />
* <span id="Currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''Currently installed mono version is supported but upgrading is recommended'''</span><br />
** 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.<br />
** The upgrade procedure for Mono varies per platform.<br />
* <span id="New_update_is_available">'''New update is available'''</span><br />
** 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 -&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.<br />
** ''(This warning will not appear if your current version is less than 14 days old)''<br />
* <span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''Cannot install update because startup folder is not writable by the user'''</span><br />
** 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.<br />
* <span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''Updating will not be possible to prevent deleting AppData on Update'''</span><br />
**Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br />
** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br />
** This means Sonarr will be unable to update itself without risking data-loss.<br />
** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br />
<section end=sonarr_system_status_health_system_warnings /><br />
<br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_system_warnings /><br />
Text<br />
<section end=lidarr_system_status_health_system_warnings /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_system_warnings /><br />
Text<br />
<section end=readarr_system_status_health_system_warnings /><br />
<br />
<br />
==== Download Clients ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_download_clients /><br />
* <span id="no_download_client_is_available>'''No download client is available'''</span><br />
** 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 -&gt; Download Client.<br />
** Unable to communicate with download client<br />
** 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.<br />
* <span id="Download_clients_are_unavailable_due_to_failure">'''Download clients are unavailable due to failure'''</span><br />
** 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.<br />
** You should inspect System-&gt;Logs to see what the reason is for the failures.<br />
** If you no longer use this download client, disable it in Radarr to prevent the errors.<br />
* <span id="enable_complete_download_handling">'''Enable Completed Download Handling'''</span><br />
** 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.<br />
** ''(Completed Download Handling is enabled by default for new users.)''<br />
<section end=radarr_system_status_health_download_clients /><br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_download_clients /><br />
* <span id="No_download_client_is_available">'''No download client is available'''</span><br />
** 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 -&gt; Download Client.<br />
** Unable to communicate with download client ====<br />
** 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.<br />
* <span id="Download_clients_are_unavailable_due_to_failure">'''Download clients are unavailable due to failure'''</span><br />
** 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.<br />
** You should inspect System-&gt;Logs to see what the reason is for the failures.<br />
** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br />
* <span id="Enable_Completed_Download_Handling_or_configure_Drone_Factory">'''Enable Completed Download Handling or configure Drone Factory'''</span><br />
** Sonarr requires Completed Download Handling or a properly configured Drone Factory to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br />
** ''(Completed Download Handling is enabled by default for new users.)''<br />
<section end=sonarr_system_status_health_download_clients /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_download_clients /><br />
Text<br />
<section end=lidarr_system_status_health_download_clients /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_download_clients /><br />
Text<br />
<section end=readarr_system_status_health_download_clients /><br />
<br />
<br />
==== Drone Factory ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_drone_factory /><br />
* Drone Factory<br />
** Drone Factory folder does not exist<br />
*** If you configure Radarr to use a Drone Factory the specified folder must exist. Please ensure that it indeed exists, or disable the Drone Factory.<br />
*** ''(You might want to consider using Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients.)''<br />
** Unable to write to Drone Factory folder <br />
*** You configured Radarr to use a Drone Factory, however Radarr was unable to creates a test file, this indicates permission issues. Please verify that the user Radarr runs under has the appropriate permissions.<br />
** Drone Factory is deprecated<br />
*** '''Please don’t panic.'''<br />
*** The Drone Factory is unreliable in various situations and has been replaced by Completed Download Handling and external API calls over a year ago. This functionality will be removed in a future major version of Radarr and should no longer be used. ''Please note that the Drone Factory periodic scan functionality will not be removed via an automatic update, but rolled into an future backward-incompatible v3 major release which in most cases will require manual installation.''<br />
*** For occasional manual downloads use Wanted-&gt;Manual Import. It’ll allow you to select a directory and optionally review the parsing results before actually importing. Useful for the occasional manual download that isn’t handled automatically.<br />
*** If the download client is on a remote machine, consider using remote mounts in combination with Settings-&gt;Download Clients-&gt;Remote Path Mapping to make Radarr aware of the mount. Alternatives are available.<br />
*** Please disable the Drone Factory:<br />
**** Go to Settings-&gt;Download Clients<br />
**** Enable Advanced Settings in the top left<br />
**** Make sure the Drone Factory field is empty<br />
**** Make sure the Drone Factory Interval field is set to 0<br />
**** Save settings<br />
<section end=radarr_system_status_health_drone_factory /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_drone_factory /><br />
Text<br />
<section end=sonarr_system_status_health_drone_factory /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_drone_factory /><br />
Text<br />
<section end=lidarr_system_status_health_drone_factory /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_drone_factory /><br />
Text<br />
<section end=readarr_system_status_health_drone_factory /><br />
<br />
<br />
==== Completed/Failed Download Handling ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_complete_failed_download_handling /><br />
* <span id="Completed_Download_Handling_is_disabled">'''Completed Download Handling is disabled'''</span><br />
** ''(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.)''<br />
** 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.<br />
** 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.<br />
** 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)<br /><br />
** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.<br /><br />
** 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.<br />
** 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 -&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.<br />
* <span id="Download_Client_has_history_items_in_Drone_Factory_conflicting_with_Completed_Download_Handling">'''Download Client has history items in Drone Factory conflicting with Completed Download Handling '''</span><br />
** The Download Client put finished downloads inside the Drone Factory even though Completed Download Handling is configured. This could potentially cause both Completed Download Handling and the Drone Factory logic to import the same download simultaneously. To avoid conflicts Radarr will ignore those downloads during it’s Completed Download Handling logic, leaving it to be handled by the Drone Factory. This is a suboptimal situation since this effectively disabled Completed Download Handling.<br />
** Resolution: Configure the Drone Factory to use a different folder.<br />
'''''TODO: Reword'''''<br />
<br />
<section end=radarr_system_status_health_complete_failed_download_handling /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_complete_failed_download_handling /><br />
* <span id="Completed_Download_Handling_is_disabled">'''Completed Download Handling is disabled'''</span><br />
** ''(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.)''<br />
** 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.<br />
** 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.<br />
** If you wish to enable Completed Download Handling you should verify the following:<br />
*** '''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.<br />
*** 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.<br />
*** 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)<br /><br />
** You should reconfigure Sonarr to use a different Drone Factory Folder or disable it altogether.<br /><br />
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.<br />
** 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 -&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.<br />
* <span id="Download_Client_has_history_items_in_Drone_Factory_conflicting_with_Completed_Download_Handling">'''Download Client has history items in Drone Factory conflicting with Completed Download Handling'''</span><br />
** The Download Client put finished downloads inside the Drone Factory even though Completed Download Handling is configured. This could potentially cause both Completed Download Handling and the Drone Factory logic to import the same download simultaneously. To avoid conflicts Sonarr will ignore those downloads during it's Completed Download Handling logic, leaving it to be handled by the Drone Factory. This is a suboptimal situation since this effectively disabled Completed Download Handling.<br />
** Resolution: Configure the Drone Factory to use a different folder.<br />
** '''''TODO: Reword'''''<br />
<section end=sonarr_system_status_health_complete_failed_download_handling /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_complete_failed_download_handling /><br />
Text<br />
<section end=lidarr_system_status_health_complete_failed_download_handling /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_complete_failed_download_handling /><br />
Text<br />
<section end=readarr_system_status_health_complete_failed_download_handling /><br />
<br />
<br />
==== Indexers ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_indexers /><br />
* <span id="No_indexers_are_enabled">'''No indexers are enabled'''</span><br />
** Radarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br />
* <span id="Enabled_indexers_do_not_support_searching">'''Enabled indexers do not support searching''' </span><br />
** 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.<br />
* <span id="Indexers_are_unavailable_due_to_failures">'''Indexers are unavailable due to failures'''</span><br />
** 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).<br />
** 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.<br />
** You can prevent the warning by disabling the affected indexer.<br />
** 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.<br />
<section end=radarr_system_status_health_indexers /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_indexers /><br />
* <span id="No_indexers_are_enabled">'''No indexers are enabled'''</span><br />
** Sonarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br />
* <span id="Enabled_indexers_do_not_support_searching">'''Enabled indexers do not support searching'''</span><br />
** 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.<br />
* <span id="Indexers_are_unavailable_due_to_failures">'''Indexers are unavailable due to failures'''</span><br />
** 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).<br /><br />
** 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.<br />
** You can prevent the warning by disabling the affected indexer.<br />
**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.<br />
<section end=sonarr_system_status_health_indexers /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_indexers /><br />
Text<br />
<section end=lidarr_system_status_health_indexers /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_indexers /><br />
Text<br />
<section end=readarr_system_status_health_indexers /><br />
<br />
<br />
==== Folders ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_folders /><br />
* <span id="Missing_root_folder">'''Missing root folder'''</span><br />
** This message may appear if a previous root folder is no longer used. To remove old root folders:<br />
*** Begin adding a new Movie* by searching for a name, but do not submit<br />
*** In the 'Path' dropdown, select 'Add a different path'<br />
*** Click the cross at the end of a row to remove the unused path<br />
** Note - if the folder has been removed from the operating system, you will need to recreate the folder in the operating system, and restart Radarr, or else you will not be able to select it from the dropdown box. After that you can remove the path from the operating system.<br />
** The message will continue to appear until all movies have their root folder updated to the new root folder. To change the root folder for other movies, visit the movies editor.<br />
*** NB: I thought Radarr was for Movies and not Series<br />
<section end=radarr_system_status_health_folders /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_folders /><br />
* <span id="Missing root folder">'''Missing root folder'''</span><br />
** This message may appear if a previous root folder is no longer used. To remove old root folders:<br />
**# Begin adding a new Series by searching for a name, but do not submit<br />
**# In the 'Path' dropdown, select 'Add a different path'<br />
**# Click the cross at the end of a row to remove the unused path<br />
** Note - if the folder has been removed from the operating system, you will need to recreate the folder in the operating system, and restart Sonarr, or else you will not be able to select it from the dropdown box. After that you can remove the path from the operating system.<br />
** The message will continue to appear until all series have their root folder updated to the new root folder. To change the root folder for other series, visit the series editor.<br />
<section end=sonarr_system_status_health_folders /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_folders /><br />
Text<br />
<section end=lidarr_system_status_health_folders /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_folders /><br />
Text<br />
<section end=readarr_system_status_health_folders /><br />
<br />
==== Media ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_media /><br />
* <span id="Movie was removed from TMDb">'''Movie was removed from TMDb'''</span><br />
** The specific movie is linked to a TMDbId that was deleted from TMDb. This may mean that the movie was either removed from the DB, was a duplicate, or was re-assigned a new ID for some reason. Deleted movies will not receive any info updates and should be corrected by the user to ensure continued functionality.<br /><br />
** 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<br />
<section end=radarr_system_status_health_media /><br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_media /><br />
* <span id="Series_Removed_from_TheTVDB">'''Series Removed from TheTVDB'''</span><br />
** 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.<br />
<section end=sonarr_system_status_health_media /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_media /><br />
Text<br />
<section end=lidarr_system_status_health_media /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_media /><br />
Text<br />
<section end=readarr_system_status_health_media /><br />
<br />
=== Disk Space ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_disk_space /><br />
* This section will show you available disk space<br />
** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br />
<section end=radarr_system_status_disk_space /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_disk_space /><br />
Text<br />
<section end=sonarr_system_status_disk_space /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_disk_space /><br />
Text<br />
<section end=lidarr_system_status_disk_space /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_disk_space /><br />
Text<br />
<section end=readarr_system_status_disk_space /><br />
<br />
=== About ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_about /><br />
This will tell you about your current install of Radarr<br />
<section end=radarr_system_status_about /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_about /><br />
Text<br />
<section end=sonarr_system_status_about /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_about /><br />
Text<br />
<section end=lidarr_system_status_about /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_about /><br />
Text<br />
<section end=readarr_system_status_about /><br />
<br />
=== More Info ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_more_info /><br />
* Home page: [https://radarr.video Radarr's home page]<br />
* Discord: [https://discord.gg/r5wJPt9 Join our discord]<br />
* Wiki: [https://wiki.servarr.com You're here already]<br />
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]<br />
* Source: [https://github.com/Radarr/Radarr Github]<br />
* Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]<br />
<section end=radarr_system_status_more_info /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_more_info /><br />
Text<br />
<section end=sonarr_system_status_more_info /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_more_info /><br />
Text<br />
<section end=lidarr_system_status_more_info /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_more_info /><br />
Text<br />
<section end=readarr_system_status_more_info /><br />
<br />
=== Templates ===</div>Flying-sausageshttps://wikiold.servarr.com/index.php?title=System_status&diff=2426System status2020-11-29T16:34:22Z<p>Flying-sausages: /* Radarr */ Move .net core to its own major bullet to make it more obvious what to look at whn you follow the anchor</p>
<hr />
<div>== System ==<br />
=== Health ===<br />
==== Overview ====<br />
====== Radarr ======<br />
<section begin=radarr_system_status_health_overview /><br />
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.<br />
<section end=radarr_system_status_health_overview /><br />
<br />
====== Sonarr ======<br />
<section begin=sonarr_system_status_health_overview /><br />
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.<br />
<section end=sonarr_system_status_health_overview /><br />
====== Lidarr ======<br />
<section begin=lidarr_system_status_health_overview /><br />
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.<br />
<section end=lidarr_system_status_health_overview /><br />
====== Readarr ======<br />
<section begin=readarr_system_status_health_overview /><br />
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.<br />
<section end=readarr_system_status_health_overview /><br />
<br />
==== System Warnings ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_system_warnings /><br />
* <span id="update-to-net-core-version">'''Update to .NET Core version'''</span><br />
** 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.<br />
** This should only happen on linux hosts. To remedy, download the correct build for your architecture: <br />
*** [https://radarr.servarr.com/v1/update/nightly/updatefile?os=linux&runtime=netcore&arch=x64 x64] <br />
*** [https://radarr.servarr.com/v1/update/nightly/updatefile?os=linux&runtime=netcore&arch=arm64 arm64] <br />
*** [https://radarr.servarr.com/v1/update/nightly/updatefile?os=linux&runtime=netcore&arch=arm arm]<br />
** <span style="color:#ff0000">'''Back-Up your existing configuration'''</span> before the next step.<br />
** '''Delete your existing binaries''' and replace with the contents of the <code>.tar.gz</code> you just downloaded. <br />
** <span style="color:#ff0000">'''DO NOT JUST EXTRACT THE DOWNLOAD OVER THE TOP OF YOUR EXISTING BINARIES.<br> YOU MUST DELETE THE OLD ONES FIRST'''.</span> <br />
*** Update your startup script to call <code>Radarr</code> instead of <code>mono --debug Radarr.exe</code><br />
** If Radarr doesn’t start make sure you have the dependencies listed [https://docs.microsoft.com/en-us/dotnet/core/install/dependencies?tabs=netcore31&pivots=os-linux here] installed.<br />
* <span id="Mono_version_is_less_than_3_10_upgrade_for_improved_stability">'''Mono version is less than 3.10, upgrade for improved stability'''</span><br />
** 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.<br /><br />
** Mono version 4.x and higher are also available and provides a better experience on certain platforms.<br />
** See "Update to .NET Core version above"<br />
* <span id="New_update_is_available">'''New update is available'''</span><br />
** 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 -&gt; Updates page is probably a good starting point.<br />
** ''(This warning will not appear if your current version is less than 14 days old)''<br />
* <span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''Cannot install update because startup folder is not writable by the user'''</span><br />
** 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.<br />
* <span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''Updating will not be possible to prevent deleting AppData on Update'''</span><br />
** Radarr detected that AppData folder for your Operating System is located inside the directory that contains the Radarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br />
** Please look at System -&gt; Info to see the current AppData &amp; Startup directories.<br />
** This means Radarr will be unable to update itself without risking data-loss.<br />
** If you’re on linux, you’ll probably have to change the home directory for the user that is running Radarr and copy the current contents of the <code>~/.config/Radarr</code> directory to preserve your database.<br />
* <span id="Branch_is_for_a_previous_version">'''Branch is for a previous version'''</span><br />
** 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.<br />
** '''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.<br />
* <span id="Could_not_connect_to_signalR">'''Could not connect to signalR'''</span><br />
** 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.<br />
** 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: <br />
*::<code>proxy_http_version 1.1;</code><br />
*::<code>proxy_set_header Upgrade $http_upgrade;</code><br />
*::<code>proxy_set_header Connection $http_connection;</code><br />
** Make sure you <span style="color:#ff0000">'''do not'''</span> include <code>proxy_set_header Connection "Upgrade";</code> as suggested by the nginx documentation. <span style="color:#ff0000">'''THIS WILL NOT WORK'''</span><br />
** See https://github.com/aspnet/AspNetCore/issues/17081<br />
** For apache reverse proxy you need to add to the configuration:<br />
*::<code>Include /etc/apache2/mods-available/proxy_wstunnel.load</code><br />
*::<code>ProxyPass "/socket" "ws://127.0.0.1:7878/socket"</code><br />
*::<code>ProxyPassReverse "/socket" "ws://127.0.0.1:7878/socket"</code><br />
<section end=radarr_system_status_health_system_warnings /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_system_warnings /><br />
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.<br />
* '''Currently installed .Net Framework is old and unsupported'''<br />
** 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.<br />
** 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.<br />
* <span id="Currently_installed_Net_Framework_is_supported_but_upgrading_is_recommended">'''Currently installed .Net Framework is supported but upgrading is recommended '''</span><br />
** 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.<br />
** 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.<br />
* <span id="Currently_installed_mono_version_is_old_and_unsupported">'''Currently installed mono version is old and unsupported'''</span><br />
** 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.<br /><br />
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.<br />
** The upgrade procedure for Mono varies per platform.<br />
* <span id="Currently_installed_mono_version_is_supported_but_upgrading_is_recommended">'''Currently installed mono version is supported but upgrading is recommended'''</span><br />
** 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.<br />
** The upgrade procedure for Mono varies per platform.<br />
* <span id="New_update_is_available">'''New update is available'''</span><br />
** 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 -&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.<br />
** ''(This warning will not appear if your current version is less than 14 days old)''<br />
* <span id="Cannot_install_update_because_startup_folder_is_not_writable_by_the_user">'''Cannot install update because startup folder is not writable by the user'''</span><br />
** 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.<br />
* <span id="Updating_will_not_be_possible_to_prevent_deleting_AppData_on_Update">'''Updating will not be possible to prevent deleting AppData on Update'''</span><br />
**Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be <code>C:\ProgramData</code> for Windows and, <code>~/.config</code> for linux.<br /><br />
** Please look at System -&gt; About to see the current AppData &amp; Startup directories.<br />
** This means Sonarr will be unable to update itself without risking data-loss.<br />
** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.<br />
<section end=sonarr_system_status_health_system_warnings /><br />
<br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_system_warnings /><br />
Text<br />
<section end=lidarr_system_status_health_system_warnings /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_system_warnings /><br />
Text<br />
<section end=readarr_system_status_health_system_warnings /><br />
<br />
<br />
==== Download Clients ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_download_clients /><br />
* <span id="no_download_client_is_available>'''No download client is available'''</span><br />
** 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 -&gt; Download Client.<br />
** Unable to communicate with download client<br />
** 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.<br />
* <span id="Download_clients_are_unavailable_due_to_failure">'''Download clients are unavailable due to failure'''</span><br />
** 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.<br />
** You should inspect System-&gt;Logs to see what the reason is for the failures.<br />
** If you no longer use this download client, disable it in Radarr to prevent the errors.<br />
* <span id="enable_complete_download_handling">'''Enable Completed Download Handling'''</span><br />
** 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.<br />
** ''(Completed Download Handling is enabled by default for new users.)''<br />
<section end=radarr_system_status_health_download_clients /><br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_download_clients /><br />
* <span id="No_download_client_is_available">'''No download client is available'''</span><br />
** 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 -&gt; Download Client.<br />
** Unable to communicate with download client ====<br />
** 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.<br />
* <span id="Download_clients_are_unavailable_due_to_failure">'''Download clients are unavailable due to failure'''</span><br />
** 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.<br />
** You should inspect System-&gt;Logs to see what the reason is for the failures.<br />
** If you no longer use this download client, disable it in Sonarr to prevent the errors.<br />
* <span id="Enable_Completed_Download_Handling_or_configure_Drone_Factory">'''Enable Completed Download Handling or configure Drone Factory'''</span><br />
** Sonarr requires Completed Download Handling or a properly configured Drone Factory to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.<br />
** ''(Completed Download Handling is enabled by default for new users.)''<br />
<section end=sonarr_system_status_health_download_clients /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_download_clients /><br />
Text<br />
<section end=lidarr_system_status_health_download_clients /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_download_clients /><br />
Text<br />
<section end=readarr_system_status_health_download_clients /><br />
<br />
<br />
==== Drone Factory ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_drone_factory /><br />
* Drone Factory<br />
** Drone Factory folder does not exist<br />
*** If you configure Radarr to use a Drone Factory the specified folder must exist. Please ensure that it indeed exists, or disable the Drone Factory.<br />
*** ''(You might want to consider using Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients.)''<br />
** Unable to write to Drone Factory folder <br />
*** You configured Radarr to use a Drone Factory, however Radarr was unable to creates a test file, this indicates permission issues. Please verify that the user Radarr runs under has the appropriate permissions.<br />
** Drone Factory is deprecated<br />
*** '''Please don’t panic.'''<br />
*** The Drone Factory is unreliable in various situations and has been replaced by Completed Download Handling and external API calls over a year ago. This functionality will be removed in a future major version of Radarr and should no longer be used. ''Please note that the Drone Factory periodic scan functionality will not be removed via an automatic update, but rolled into an future backward-incompatible v3 major release which in most cases will require manual installation.''<br />
*** For occasional manual downloads use Wanted-&gt;Manual Import. It’ll allow you to select a directory and optionally review the parsing results before actually importing. Useful for the occasional manual download that isn’t handled automatically.<br />
*** If the download client is on a remote machine, consider using remote mounts in combination with Settings-&gt;Download Clients-&gt;Remote Path Mapping to make Radarr aware of the mount. Alternatives are available.<br />
*** Please disable the Drone Factory:<br />
**** Go to Settings-&gt;Download Clients<br />
**** Enable Advanced Settings in the top left<br />
**** Make sure the Drone Factory field is empty<br />
**** Make sure the Drone Factory Interval field is set to 0<br />
**** Save settings<br />
<section end=radarr_system_status_health_drone_factory /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_drone_factory /><br />
Text<br />
<section end=sonarr_system_status_health_drone_factory /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_drone_factory /><br />
Text<br />
<section end=lidarr_system_status_health_drone_factory /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_drone_factory /><br />
Text<br />
<section end=readarr_system_status_health_drone_factory /><br />
<br />
<br />
==== Completed/Failed Download Handling ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_complete_failed_download_handling /><br />
* <span id="Completed_Download_Handling_is_disabled">'''Completed Download Handling is disabled'''</span><br />
** ''(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.)''<br />
** 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.<br />
** 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.<br />
** 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)<br /><br />
** You should reconfigure Radarr to use a different Drone Factory Folder or disable it altogether.<br /><br />
** 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.<br />
** 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 -&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.<br />
* <span id="Download_Client_has_history_items_in_Drone_Factory_conflicting_with_Completed_Download_Handling">'''Download Client has history items in Drone Factory conflicting with Completed Download Handling '''</span><br />
** The Download Client put finished downloads inside the Drone Factory even though Completed Download Handling is configured. This could potentially cause both Completed Download Handling and the Drone Factory logic to import the same download simultaneously. To avoid conflicts Radarr will ignore those downloads during it’s Completed Download Handling logic, leaving it to be handled by the Drone Factory. This is a suboptimal situation since this effectively disabled Completed Download Handling.<br />
** Resolution: Configure the Drone Factory to use a different folder.<br />
'''''TODO: Reword'''''<br />
<br />
<section end=radarr_system_status_health_complete_failed_download_handling /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_complete_failed_download_handling /><br />
* <span id="Completed_Download_Handling_is_disabled">'''Completed Download Handling is disabled'''</span><br />
** ''(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.)''<br />
** 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.<br />
** 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.<br />
** If you wish to enable Completed Download Handling you should verify the following:<br />
*** '''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.<br />
*** 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.<br />
*** 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)<br /><br />
** You should reconfigure Sonarr to use a different Drone Factory Folder or disable it altogether.<br /><br />
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.<br />
** 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 -&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.<br />
* <span id="Download_Client_has_history_items_in_Drone_Factory_conflicting_with_Completed_Download_Handling">'''Download Client has history items in Drone Factory conflicting with Completed Download Handling'''</span><br />
** The Download Client put finished downloads inside the Drone Factory even though Completed Download Handling is configured. This could potentially cause both Completed Download Handling and the Drone Factory logic to import the same download simultaneously. To avoid conflicts Sonarr will ignore those downloads during it's Completed Download Handling logic, leaving it to be handled by the Drone Factory. This is a suboptimal situation since this effectively disabled Completed Download Handling.<br />
** Resolution: Configure the Drone Factory to use a different folder.<br />
** '''''TODO: Reword'''''<br />
<section end=sonarr_system_status_health_complete_failed_download_handling /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_complete_failed_download_handling /><br />
Text<br />
<section end=lidarr_system_status_health_complete_failed_download_handling /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_complete_failed_download_handling /><br />
Text<br />
<section end=readarr_system_status_health_complete_failed_download_handling /><br />
<br />
<br />
==== Indexers ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_indexers /><br />
* <span id="No_indexers_are_enabled">'''No indexers are enabled'''</span><br />
** Radarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br />
* <span id="Enabled_indexers_do_not_support_searching">'''Enabled indexers do not support searching''' </span><br />
** 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.<br />
* <span id="Indexers_are_unavailable_due_to_failures">'''Indexers are unavailable due to failures'''</span><br />
** 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).<br />
** 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.<br />
** You can prevent the warning by disabling the affected indexer.<br />
** 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.<br />
<section end=radarr_system_status_health_indexers /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_indexers /><br />
* <span id="No_indexers_are_enabled">'''No indexers are enabled'''</span><br />
** Sonarr requires indexers to be able to discover new releases. Please read the wiki on instructions how to add indexers.<br />
* <span id="Enabled_indexers_do_not_support_searching">'''Enabled indexers do not support searching'''</span><br />
** 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.<br />
* <span id="Indexers_are_unavailable_due_to_failures">'''Indexers are unavailable due to failures'''</span><br />
** 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).<br /><br />
** 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.<br />
** You can prevent the warning by disabling the affected indexer.<br />
**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.<br />
<section end=sonarr_system_status_health_indexers /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_indexers /><br />
Text<br />
<section end=lidarr_system_status_health_indexers /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_indexers /><br />
Text<br />
<section end=readarr_system_status_health_indexers /><br />
<br />
<br />
==== Folders ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_folders /><br />
* <span id="Missing_root_folder">'''Missing root folder'''</span><br />
** This message may appear if a previous root folder is no longer used. To remove old root folders:<br />
*** Begin adding a new Movie* by searching for a name, but do not submit<br />
*** In the 'Path' dropdown, select 'Add a different path'<br />
*** Click the cross at the end of a row to remove the unused path<br />
** Note - if the folder has been removed from the operating system, you will need to recreate the folder in the operating system, and restart Radarr, or else you will not be able to select it from the dropdown box. After that you can remove the path from the operating system.<br />
** The message will continue to appear until all movies have their root folder updated to the new root folder. To change the root folder for other movies, visit the movies editor.<br />
*** NB: I thought Radarr was for Movies and not Series<br />
<section end=radarr_system_status_health_folders /><br />
<br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_folders /><br />
* <span id="Missing root folder">'''Missing root folder'''</span><br />
** This message may appear if a previous root folder is no longer used. To remove old root folders:<br />
**# Begin adding a new Series by searching for a name, but do not submit<br />
**# In the 'Path' dropdown, select 'Add a different path'<br />
**# Click the cross at the end of a row to remove the unused path<br />
** Note - if the folder has been removed from the operating system, you will need to recreate the folder in the operating system, and restart Sonarr, or else you will not be able to select it from the dropdown box. After that you can remove the path from the operating system.<br />
** The message will continue to appear until all series have their root folder updated to the new root folder. To change the root folder for other series, visit the series editor.<br />
<section end=sonarr_system_status_health_folders /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_folders /><br />
Text<br />
<section end=lidarr_system_status_health_folders /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_folders /><br />
Text<br />
<section end=readarr_system_status_health_folders /><br />
<br />
==== Media ====<br />
===== Radarr =====<br />
<section begin=radarr_system_status_health_media /><br />
* <span id="Movie was removed from TMDb">'''Movie was removed from TMDb'''</span><br />
** The specific movie is linked to a TMDbId that was deleted from TMDb. This may mean that the movie was either removed from the DB, was a duplicate, or was re-assigned a new ID for some reason. Deleted movies will not receive any info updates and should be corrected by the user to ensure continued functionality.<br /><br />
** 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<br />
<section end=radarr_system_status_health_media /><br />
===== Sonarr =====<br />
<section begin=sonarr_system_status_health_media /><br />
* <span id="Series_Removed_from_TheTVDB">'''Series Removed from TheTVDB'''</span><br />
** 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.<br />
<section end=sonarr_system_status_health_media /><br />
===== Lidarr =====<br />
<section begin=lidarr_system_status_health_media /><br />
Text<br />
<section end=lidarr_system_status_health_media /><br />
===== Readarr =====<br />
<section begin=readarr_system_status_health_media /><br />
Text<br />
<section end=readarr_system_status_health_media /><br />
<br />
=== Disk Space ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_disk_space /><br />
* This section will show you available disk space<br />
** In docker this can be tricky as it will typically show you the available space w/in your Docker image<br />
<section end=radarr_system_status_disk_space /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_disk_space /><br />
Text<br />
<section end=sonarr_system_status_disk_space /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_disk_space /><br />
Text<br />
<section end=lidarr_system_status_disk_space /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_disk_space /><br />
Text<br />
<section end=readarr_system_status_disk_space /><br />
<br />
=== About ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_about /><br />
This will tell you about your current install of Radarr<br />
<section end=radarr_system_status_about /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_about /><br />
Text<br />
<section end=sonarr_system_status_about /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_about /><br />
Text<br />
<section end=lidarr_system_status_about /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_about /><br />
Text<br />
<section end=readarr_system_status_about /><br />
<br />
=== More Info ===<br />
==== Radarr ====<br />
<section begin=radarr_system_status_more_info /><br />
* Home page: [https://radarr.video Radarr's home page]<br />
* Discord: [https://discord.gg/r5wJPt9 Join our discord]<br />
* Wiki: [https://wiki.servarr.com You're here already]<br />
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/radarr here]<br />
* Source: [https://github.com/Radarr/Radarr Github]<br />
* Feature Requests: Got as great idea drop it [https://github.com/Radarr/Radarr/issues here]<br />
<section end=radarr_system_status_more_info /><br />
<br />
==== Sonarr ====<br />
<section begin=sonarr_system_status_more_info /><br />
Text<br />
<section end=sonarr_system_status_more_info /><br />
==== Lidarr ====<br />
<section begin=lidarr_system_status_more_info /><br />
Text<br />
<section end=lidarr_system_status_more_info /><br />
==== Readarr ====<br />
<section begin=readarr_system_status_more_info /><br />
Text<br />
<section end=readarr_system_status_more_info /><br />
<br />
=== Templates ===</div>Flying-sausages