Servarr - User contributions [en]

System status

2021-05-08T21:21:36Z

TRaSH: /* Radarr */

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

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

* <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>
** Radarr is written in .Net and requires Mono to run on very old ARM processors.
** Mono 5.8 is the absolute minimum for Radarr but Mono 5.20 is currently recommended and is the minimum requirement on nightly builds.
** The upgrade procedure for Mono varies per platform.

*<span id="currently_installed_sqlite_version_is_not_supported">'''[[#currently_installed_sqlite_version_is_not_supported|Currently installed SQLite version is not supported]]'''</span>
** Radarr stores its data in an SQLite database. The sqlite3 library installed on your system is too old. Radarr requires at least version 3.9.0.

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

*<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>
** 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.

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

*<span id="branch_is_for_a_previous_version">'''[[#branch_is_for_a_previous_version|Branch is for a previous version]]'''</span>
** 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.

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

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

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

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

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

*<span id="mediainfo_not_loaded">'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''</span>
** MediaInfo Library could not be loaded.

*<span id="ptp_settings_old">'''[[#ptp_settings_old|PTP Indexer Settings Out of Date]]'''</span>
** The following PassThePopcorn indexers have deprecated settings and should be updated.

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

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

<section end=radarr_system_status_health_system_warnings />

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

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

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

* <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>
** 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 />
** Mono 5.4 is the absolute minimum for Sonarr v3 but Mono 5.20 is currently recommended.
** The upgrade procedure for Mono varies per platform.

* <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>
** Sonarr uses the .Net Framework which Mono implements for your system. We need to build Sonarr against the lowest supported version still used by our users. Upgrading to newer versions allows us to build against newer versions and use new Framework features.
** The upgrade procedure for Mono varies per platform.

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

* <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>
** 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.

* <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>
** 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 />
** Please look at System -> About to see the current AppData & Startup directories.
** This means Sonarr will be unable to update itself without risking data-loss.
** If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the <code>~/.config/Sonarr</code> directory to preserve your database.
* <span id="package_maintainer_message">'''[[#package_maintainer_message|Package Maintainer Message]]'''</span>
** Please refer to the specific message your package maintainer is indicating to you. This is not a Sonarr issue. For additional information, refer to your package maintainer. Your package maintainer can be found in System -> Status -> About. Note that this includes docker and your package maintainer is whomever maintains your docker image.

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

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

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

*<span id="mediainfo_not_loaded">'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''</span>
** MediaInfo Library could not be loaded.

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

<section end=sonarr_system_status_health_system_warnings />

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

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

*<span id="mono_version_is_less_than_5_8_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_8_upgrade_for_improved_stability|Mono version is less than 5.8, upgrade for improved stability]]'''</span>
** Lidarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.
** See "Update to .NET Core version above"

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

*<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>
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

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

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

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

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

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

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

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

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

*<span id="mediainfo_not_loaded">'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''</span>
** MediaInfo Library could not be loaded.

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

<section end=lidarr_system_status_health_system_warnings />

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

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

*<span id="mono_version_is_less_than_5_2_upgrade_for_improved_stability">'''[[#mono_version_is_less_than_5_2_upgrade_for_improved_stability|Mono version is less than 5.2, upgrade for improved stability]]'''</span>
** Readarr is written in .Net and requires Mono to run. Versions of 3.10 and above resolved various stability issues we experienced in the past and is considered the minimum supported version.
** Mono version 5.x and higher are also available and provides a better experience on certain platforms.
** See "Update to .NET Core version above"

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

*<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>
** This means Lidarr will be unable to update itself. You’ll have to update Lidarr manually or set the permissions on Lidarr Startup directory (the installation directory) to allow Lidarr to update itself.

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

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

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

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

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

*<span id="mediainfo_not_loaded">'''[[#mediainfo_not_loaded|MediaInfo Library Could not be Loaded]]'''</span>
** MediaInfo Library could not be loaded.

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

<section end=readarr_system_status_health_system_warnings />

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

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

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

* <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span>
** Radarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span>
** This error is typically associated with bad docker paths within either your download client or Radarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Radarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished movie is in <code>/downloads</code>. Radarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Radarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Radarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Radarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/movies</code> and since you used <code>/data</code> in Radarr when the download client tells Radarr it's done Radarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/movies</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/hardlinks How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

[https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* <span id="downloads_in_root_folder">'''[[#downloads_in_root_folder|Downloading into Root Folder]]'''</span>
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Radarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* <span id="bad_download_client_settings>'''[[#bad_download_client_settings|Bad Download Client Settings]]'''</span>
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* <span id="bad_remote_path_mapping">'''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''</span>
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* <span id="permissions_error">'''[[#permissions_error|Permissions Error]]'''</span>
** Radarr or the user radarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''</span>
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''</span>
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end=radarr_system_status_health_download_clients />

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

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

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

* <span id="downloads_in_root_folder">'''[[#downloads_in_root_folder|Downloading into Root Folder]]'''</span>
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Sonarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* <span id="bad_download_client_settings>'''[[#bad_download_client_settings|Bad Download Client Settings]]'''</span>
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* <span id="bad_remote_path_mapping">'''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''</span>
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Sonarr/V3/Sonarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information.]

* <span id="permissions_error">'''[[#permissions_error|Permissions Error]]'''</span>
** Sonarr or the user sonarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''</span>
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''</span>
** Check your logs for more info; Refer to our Troubleshooting Guides
<section end="sonarr_system_status_health_download_clients" />

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

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

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

* <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span>
** Lidarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span>
** This error is typically associated with bad docker paths within either your download client or Lidarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Lidarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Lidarr when its complete that the finished song is in <code>/downloads</code>. Lidarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Lidarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Lidarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Lidarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/audio</code> and since you used <code>/data</code> in Lidarr when the download client tells Lidarr it's done Lidarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/audio</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* <span id="downloads_in_root_folder">'''[[#downloads_in_root_folder|Downloading into Root Folder]]'''</span>
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Lidarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* <span id="bad_download_client_settings>'''[[#bad_download_client_settings|Bad Download Client Settings]]'''</span>
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* <span id="bad_remote_path_mapping">'''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''</span>
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* <span id="permissions_error">'''[[#permissions_error|Permissions Error]]'''</span>
** Lidarr or the user lidarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''</span>
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''</span>
** Check your logs for more info; Refer to our Troubleshooting Guides

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

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

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

* <span id="enable_complete_download_handling">'''[[#enable_complete_download_handling|Enable Completed Download Handling]]'''</span>
** Readarr requires Completed Download Handling to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
** ''(Completed Download Handling is enabled by default for new users.)''

* <span id="docker_bad_remote_path_mapping">'''[[#docker_bad_remote_path_mapping|Docker bad remote path mapping]]'''</span>
** This error is typically associated with bad docker paths within either your download client or Readarr
*** An example of this would be:
**** Download client: <code>Download Path: /downloads:/mnt/user/downloads</code>
**** Readarr: <code>Download Path: /data:/mnt/user/downloads</code>
**** Within this example the download client places its downloads into <code>/downloads</code> and therefore tells Radarr when its complete that the finished book is in <code>/downloads</code>. Readarr then comes along and says "Okay, cool, let me check in <code>/downloads</code>" Well, inside Readarr you did not allocate a <code>/downloads</code> path you allocated a <code>/data</code> path so it throws this error.
**** The easiest fix for this is '''CONSISTENCY''' if you use one scheme in your download client, use it across the board.
**** Team Readarr is a big fan of simply using <code>/data</code>.
***** Download client: <code>/data:/mnt/user/data</code>
***** Readarr: <code>/data:/mnt/user/data</code>
***** Now within the download client you can specify where in <code>/data</code> you'd like to place your downloads, now this varies depending on the client but you should be able to tell it "Yeah download client place my files into." <code>/data/torrents (or usenet)/books</code> and since you used <code>/data</code> in Readarr when the download client tells Readarr it's done Readarr will come along and say "Sweet, I have a <code>/data</code> and I also can see <code>/torrents (or usenet)/books</code> all is right in the world."
*** There are many great write ups by some very talented people one on our wiki [[Docker Guide]] and the other by TRaSH with his [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ How To Set Up Hardlinks and Atomic-Moves] Now these guides place heavy emphasis on Hardlinks and Atomic moves, but the general concept of containers and how path mapping works is the core of these discussions.

* <span id="downloads_in_root_folder">'''[[#downloads_in_root_folder|Downloading into Root Folder]]'''</span>
** You're downloading directly into your root folder. This frequently causes issues and is not advised. To fix this change your download client so it is not placing downloads within your root folder. Please note that this check looks at all [[Readarr Settings#Root Folders|defined/configured root folders]] added not only root folders currently in use.

* <span id="bad_download_client_settings>'''[[#bad_download_client_settings|Bad Download Client Settings]]'''</span>
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map.

* <span id="bad_remote_path_mapping">'''[[#bad_remote_path_mapping|Bad Remote Path Mapping]]'''</span>
** The location your download client is downloading files to is causing problems. Check the logs for further information. This may be permissions or attempting to go from windows to linux or linux to windows without a remote path map. [https://trash-guides.info/Radarr/V3/Radarr-remote-path-mapping/ See TRaSH's Remote Path Guide for more information. The link is for Radarr, but the same concept applies.]

* <span id="permissions_error">'''[[#permissions_error|Permissions Error]]'''</span>
** Readarr or the user readarr is running as cannot access the location your download client is downloading files to. This is typically a permission issue.

* <span id="remote_path_file_removed">'''[[#remote_path_file_removed|Remote File was removed part way through processing]]'''</span>
** A file accessible via a remote path map appears to have been removed prior to processing completing.

* <span id="remote_path_import_failed">'''[[#remote_path_import_failed|Remote Path is Used and Import Failed]]'''</span>
** Check your logs for more info; Refer to our Troubleshooting Guides

<section end=readarr_system_status_health_download_clients />

==== Completed/Failed Download Handling ====
===== Radarr =====
<section begin=radarr_system_status_health_complete_failed_download_handling />
* <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span>
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Radarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Radarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=radarr_system_status_health_complete_failed_download_handling />

===== Sonarr =====
<section begin=sonarr_system_status_health_complete_failed_download_handling />
* <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span>
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Sonarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the
<section end=sonarr_system_status_health_complete_failed_download_handling />

===== Lidarr =====
<section begin=lidarr_system_status_health_complete_failed_download_handling />
* <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span>
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Lidarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Lidrr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=lidarr_system_status_health_complete_failed_download_handling />

===== Readarr =====
<section begin=readarr_system_status_health_complete_failed_download_handling />
* <span id="completed_download_handling_is_disabled">'''[[#completed_download_handling_is_disabled|Completed Download Handling is disabled]]'''</span>
**''(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)''
** It’s recommended to use Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients. With it, Readarr will only import a download once the download client reports it as ready.
** If you wish to enable Completed Download Handling you should verify the following: * '''Warning''': Completed Download Handling only works properly if the download client and Readarr are on the same machine since it gets the path to be imported directly from the download client otherwise a remote map is needed.
<section end=readarr_system_status_health_complete_failed_download_handling />

==== Indexers ====
===== Radarr =====
<section begin=radarr_system_status_health_indexers />
* <span id="no_indexers_available_with_automatic_search_enabled_radarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_radarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Radarr will not provide any automatic search results]]'''</span>
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*<span id="no_indexers_available_with_rss_sync_enabled_radarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_radarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Radarr will not grab new releases automatically]]'''</span>
** So Radarr uses the RSS feed to pick up new releases as they come along. More info on that [[Radarr FAQ#How does Radarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span>
** Radarr requires indexers to be able to discover new releases. [[Radarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span>
** 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.
* <span id="no_indexers_available_with_interactive_search_enabled">'''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' </span>
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span>
** Errors occurs while Radarr tried to use one of your indexers. To limit retries, Radarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Radarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Radarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=radarr_system_status_health_indexers />

===== Sonarr =====
<section begin=sonarr_system_status_health_indexers />
* <span id="no_indexers_available_with_automatic_search_enabled_sonarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_sonarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Sonarr will not provide any automatic search results]]'''</span>
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*<span id="no_indexers_available_with_rss_sync_enabled_sonarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_sonarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Sonarr will not grab new releases automatically]]'''</span>
** So Sonarr uses the RSS feed to pick up new releases as they come along. More info on that [[Sonarr FAQ#How does Sonarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span>
** Sonarr requires indexers to be able to discover new releases. [[Sonarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]'''</span>
** 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.
* <span id="no_indexers_available_with_interactive_search_enabled">'''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' </span>
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span>
** Errors occurs while Sonarr tried to use one of your indexers. To limit retries, Sonarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Sonarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Sonarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=sonarr_system_status_health_indexers />
===== Lidarr =====
<section begin=lidarr_system_status_health_indexers />
* <span id="no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_lidarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Lidarr will not provide any automatic search results]]'''</span>
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*<span id="no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_lidarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Lidarr will not grab new releases automatically]]'''</span>
** So Lidarr uses the RSS feed to pick up new releases as they come along. More info on that [[Lidarr FAQ#How does Lidarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span>
** Lidarr requires indexers to be able to discover new releases. [[Lidarr_Settings#Indexers|Please read the wiki on instructions how to add indexers]].
* <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span>
** None of the indexers you have enabled support searching. This means Lidarr will only be able to find new releases via the RSS feeds. But searching for music (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* <span id="no_indexers_available_with_interactive_search_enabled">'''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' </span>
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span>
** Errors occurs while Lidarr tried to use one of your indexers. To limit retries, Lidarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Lidarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Lidarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=lidarr_system_status_health_indexers />
===== Readarr =====
<section begin=readarr_system_status_health_indexers />
* <span id="no_indexers_available_with_automatic_search_enabled_readarr_will_not_provide_any_automatic_search_results">'''[[#no_indexers_available_with_automatic_search_enabled_readarr_will_not_provide_any_automatic_search_results|No indexers available with automatic search enabled, Readarr will not provide any automatic search results]]'''</span>
** Simply put you do not have any of your indexers set to allow automatic searches
*** Go into Settings > Indexers, select an indexer you'd like to allow Automatic Searches and then click save.
*<span id="no_indexers_available_with_rss_sync_enabled_readarr_will_not_grab_new_releases_automatically">'''[[#no_indexers_available_with_rss_sync_enabled_readarr_will_not_grab_new_releases_automatically|No indexers available with RSS sync enabled, Readarr will not grab new releases automatically]]'''</span>
** So Readarr uses the RSS feed to pick up new releases as they come along. More info on that [[Readarr FAQ#How does Readarr work?|here]]
** To correct this issue go to Settings > Indexers, select an indexer you have and enable RSS Sync
* <span id="no_indexers_are_enabled">'''[[#no_indexers_are_enabled|No indexers are enabled]]'''</span>
** Readarr requires indexers to be able to discover new releases. [[Readarr_Settings#Indexers|Please read the wiki on instructions how to add indexers.]]
* <span id="enabled_indexers_do_not_support_searching">'''[[#enabled_indexers_do_not_support_searching|Enabled indexers do not support searching]]''' </span>
** None of the indexers you have enabled support searching. This means Readarr will only be able to find new releases via the RSS feeds. But searching for books (either Automatic Search or Manual Search) will never return any results. Obviously, the only way to remedy it is to add another indexer.
* <span id="no_indexers_available_with_interactive_search_enabled">'''[[#no_indexers_available_with_interactive_search_enabled|No indexers avaiable with Interactive Search Enabled"]]''' </span>
** None of the indexers you have enabled support interactive searching. This means the application will only be able to find new releases via the RSS feeds or an automatic search.
* <span id="indexers_are_unavailable_due_to_failures">'''[[#indexers_are_unavailable_due_to_failures|Indexers are unavailable due to failures]]'''</span>
** Errors occurs while Readarr tried to use one of your indexers. To limit retries, Readarr will not use the indexer for an increasing amount of time (up to 24h).
** This mechanism is triggered if Readarr was unable to get a response from the indexer (could be dns, connection, authentication or indexer issue), or unable to fetch the nzb/torrent file from the indexer. Please inspect the logs to determine what kind of error causes the problem.
** You can prevent the warning by disabling the affected indexer.
** Run the Test on the indexer to force Readarr to recheck the indexer, please note that the Health Check warning will not always disappear immediately.
<section end=readarr_system_status_health_indexers />

==== Folders ====
===== Radarr =====
<section begin=radarr_system_status_health_folders />
* <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span>
** This error is typically identified if a Movie is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the movie that is still using the old root folder and edit it to the correct root Folder
***# Easiest way to find this is to go to the Movies (Library) Tab
***# Create a custom filter with the old root folder path
***# Select mass edit on the top bar and from the '''Root Paths''' drop down select the new root path that you want these movies to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the movie folders to '<root path>' ?''' This will also state '''This will also rename the movie folder per the movie folder format in settings.''' Simply select No if the you do not want Radarr to move your files
<section end=radarr_system_status_health_folders />
===== Sonarr =====
<section begin=sonarr_system_status_health_folders />
* <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span>
** This error is typically identified if a series is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the series that is still using the old root folder and edit it to the correct root folder
***# Go to the Series > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these series to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the series folders to '<root path>'?''' Simply select No if the you do not want Sonarr to move your files
* <span id="import_list_missing_root_folder">'''[[#import_list_missing_root_folder|Import List missing root folder]]'''</span>
** This error is typically identified if a list is looking for a root folder but that root folder is no longer available.
**#Go to Settings > Import Lists
**#Edit the import lists that were mentioned in the health check
**#Save
<section end=sonarr_system_status_health_folders />
===== Lidarr =====
<section begin=lidarr_system_status_health_folders />
* <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span>
** This error is typically identified if an artist is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the artist that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these artists to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the artist folders to '<root path>'?''' Simply select No if the you do not want Lidarr to move your files
<section end=lidarr_system_status_health_folders />
===== Readarr =====
<section begin=readarr_system_status_health_folders />
* <span id="missing_root_folder">'''[[#missing_root_folder|Missing root folder]]'''</span>
** This error is typically identified if an author is looking for a root folder but that root folder is no longer available.
*** If you would like to remove this warning simply find the author that is still using the old root folder and edit it to the correct root folder
***# Go to the Library > Mass Editor Tab
***# Create a custom filter with the old root folder path
***# Once the series have been found find the '''Root Paths''' drop down and select the new root path that you want these authors to be moved to.
***# Next you'll receive a pop-up that states '''Would you like to move the author folders to '<root path>'?''' Simply select No if the you do not want Readarr to move your files
<section end=readarr_system_status_health_folders />

==== Media ====
===== Radarr =====
<section begin=radarr_system_status_health_media />
* <span id="movie_was_removed_from_tmdb">'''[[#movie_was_removed_from_tmdb|Movie was removed from TMDb]]'''</span>
** The movie is linked to a TMDb Id that was deleted from TMDb, usually because it was a duplicate, wasn't a movie or changed ID for some other reason. Deleted movies will not receive any updates and should be corrected by the user to ensure continued functionality. Remove the movie from Radarr without deleting the files, then try to re-add it. If it doesn't show up in a search, check Radarr because it might be a TV miniseries like Stephen King's It.<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

* <span id="lists_are_unavailable_due_to_failures">'''[[#lists_are_unavailable_due_to_failures|Lists are unavailable due to failures]]'''</span>
** Typically this simply means that Radarr is no longer able to communicate via API or via logging in to your chosen list provider. Your best bet if the problem persists is to contact them in order to rule them out, as their systems maybe overloaded from time to time.
<section end=radarr_system_status_health_media />
===== Sonarr =====
<section begin=sonarr_system_status_health_media />
* <span id="series_removed_from_thetvdb">'''[[#series_removed_from_thetvdb|Series Removed from TheTVDB]]'''</span>
** The affected series were removed from TheTVDB, this usually happens because it is a duplicate or considered part of a different series. To correct you will need to remove the affected series and add the correct series.
<section end=sonarr_system_status_health_media />
===== Lidarr =====
<section begin=lidarr_system_status_health_media />
Text
<section end=lidarr_system_status_health_media />
===== Readarr =====
<section begin=readarr_system_status_health_media />
Text
<section end=readarr_system_status_health_media />

=== Disk Space ===
==== Radarr ====
<section begin=radarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=radarr_system_status_disk_space />
==== Sonarr ====
<section begin=sonarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=sonarr_system_status_disk_space />
==== Lidarr ====
<section begin=lidarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=lidarr_system_status_disk_space />
==== Readarr ====
<section begin=readarr_system_status_disk_space />
* This section will show you available disk space
** In docker this can be tricky as it will typically show you the available space within your Docker image
<section end=readarr_system_status_disk_space />

=== About ===
==== Radarr ====
<section begin=radarr_system_status_about />
This will tell you about your current install of Radarr
<section end=radarr_system_status_about />
==== Sonarr ====
<section begin=sonarr_system_status_about />
This will tell you about your current install of Radarr
<section end=sonarr_system_status_about />
==== Lidarr ====
<section begin=lidarr_system_status_about />
This will tell you about your current install of Lidarr
<section end=lidarr_system_status_about />
==== Readarr ====
<section begin=readarr_system_status_about />
This will tell you about your current install of Readarr
<section end=readarr_system_status_about />

=== More Info ===
==== Radarr ====
<section begin=radarr_system_status_more_info />
* Home Page: [https://radarr.video Radarr's home page]
* Wiki: [https://wiki.servarr.com/Radarr You're here already]
* Reddit: [https://reddit.com/r/radarr r/radarr]
* Discord: [https://radarr.video/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/radarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Radarr/Radarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Radarr/Radarr/issues here]
<section end=radarr_system_status_more_info />
==== Sonarr ====
<section begin=sonarr_system_status_more_info />
* Home page: [https://sonarr.tv Sonarr's home page]
* Forums: [https://forums.sonarr.tv Sonarr Forums]
* Discord: [https://discord.gg/M6BvZn5 Join our discord]
* Reddit: [https://reddit.com/r/sonarr r/sonarr]
* Twitter: [https://twitter.com/sonarrtv @sonarrtv]
* IRC: [https://webchat.freenode.net/?channels=#sonarr #sonarr on Freenode]
* Wiki: [https://wiki.servarr.com/sonarr You're here already]
* Donations: If you're feeling generous and would like to donate [https://sonarr.tv/donate click here]
* Source: https://github.com/Sonarr/Sonarr Github]
* Feature Requests: Got a great idea drop it on Github [https://github.com/Sonarr/Sonarr/issues here]
<section end=sonarr_system_status_more_info />
==== Lidarr ====
<section begin=lidarr_system_status_more_info />
* Home page: [https://lidarr.audio Lidarr's home page]
* Wiki: [https://wiki.servarr.com/Lidarr You're here already]
* Reddit: [https://reddit.com/r/lidarr r/lidarr]
* Discord: [https://lidarr.audio/discord Join our discord]
* Donations: If you're feeling generous and would like to donate [https://opencollective.com/lidarr click here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/lidarr/Lidarr/ Github]
* Feature Requests: Got a great idea drop it on GitHub [https://github.com/Lidarr/Lidarr/issues here]
<section end=lidarr_system_status_more_info />
==== Readarr ====
<section begin=readarr_system_status_more_info />
* Home page: [https://readarr.com Readarr's home page]
* Wiki: [https://wiki.servarr.com/Readarr You're here already]
* Reddit: [https://reddit.com/r/readarr r/readarr]
* Discord: [https://readarr.com/discord Join our discord]
* Donations: If you're feeling generous and would like to donate click [https://opencollective.com/readarr here]
* Donations to Sonarr: If you're feeling generous and would like to donate to the project that started it all [https://sonarr.tv/donate click here]
* Source: [https://github.com/Readarr/Readarr Github]
* Feature Requests: Got a great idea drop it [https://github.com/Readarr/Readarr/issues click here]
<section end=readarr_system_status_more_info />

=== Templates ===

Radarr Quick Start Guide

2021-05-08T21:20:04Z

TRaSH: /* Importing */

= Setup Guide =

In this guide we will try to explain the basic setup you need to do to get started with Radarr.

For a more detailed few of all the setting check [[Radarr_Settings|Radarr ->Settings]]
We will cover the following options.

Please note that within the screenshots and GUI settings in <code>orange</code> are advanced options, so you'll need to enable those to make them visible.
-----

After installation and starting up, you open a browser and go to http://ip_where_installed:7878

[[File:radarr-start.png|frameless|none|900px|900px|alt=radarr-start|radarr-start]]

== Media Management ==
<small>[[#Media Management|anchor]]</small>

First we’re going to take a look at the <code>Media Management</code> settings where we can setup our preferred naming and file management settings.

<code>Settings</code> => <code>Media Management</code>

[[File:radarr-settings-mm.png|frameless|none|900px|alt=radarr-settings-mm|radarr-settings-mm]]

=== Movie Naming ===
<small>[[#Movie Naming|anchor]]</small>

[[File:radarr-settings-mm-movie-naming.png|frameless|none|900px|alt=radarr-settings-mm-movie-naming|radarr-settings-mm-movie-naming]]

# Enable/Disable Renaming of your movies (as opposed to leaving the names that are currently there or as they were when you downloaded them).
# If you want illegal characters replaced or removed (<code>\ / : * ? " < > | ~ # % & + { }</code>).
# This setting will dictate how Radarr handles colons within the movie file.
# Here you will select the naming convention for the actual movie files.
# ''(Advanced Option) This is where you will set the naming convention for the folder that contains the video file.''

:If you want a recommended naming scheme and examples take a look [https://trash-guides.info/Radarr/V3/Radarr-recommended-naming-scheme/ TRaSH's Recommended Naming Schemes].

=== Importing ===
<small>[[#Importing|anchor]]</small>

[[File:radarr-settings-mm-importing.png|frameless|none|900px|alt=radarr-settings-mm-importing|radarr-settings-mm-importing]]

# ''(Advanced Option) Enable <code>Use Hardlinks instead of Copy</code> more info how and why with examples [https://trash-guides.info/hardlinks TRaSH's Hardlinks Guide].''
# ''(Advanced Option) Import matching extra files (subtitles, nfo, etc) after importing a file.''

=== File Management ===
<small>[[#File Management|anchor]]</small>

[[File:radarr-settings-mm-fm.png|frameless|none|900px|alt=radarr-settings-mm-fm|radarr-settings-mm-fm]]

# Movies deleted from disk are automatically unmonitored in Radarr.
#* You may want to delete a movie but do not want Radarr to re-download the movie. You would use this option.
# ''(Advanced Option) Designate a location for deleted files to go to (just in case you want to retrieve them before the bin is taken out).''
# ''(Advanced Option) This is how old a given file can be before it is deleted permanently.''

=== Root Folders ===
<small>[[#Root Folders|anchor]]</small>

[[File:radarr-settings-mm-root-folder.png|frameless|none|900px|alt=radarr-settings-mm-root-folder|radarr-settings-mm-root-folder]]

Here we will add the root folder that Radarr will be using to import your existing organized media library and where Radarr will be importing (copy/hardlink/move) your media after your download client has downloaded it.

NOTE:

<blockquote>Your download client download to a download folder and Radarr imports it to your media folder (final destination) that your media server uses.

<span style="color:#ff0000"><big>'''Your download folder and media folder can’t be the same location !!!'''</big></span>
</blockquote>
Don’t forget to save your changes

== Profiles ==
<small>[[#Profiles|anchor]]</small>

<code>Settings</code> => <code>Profiles</code>

[[File:radarr-settings-profiles.png|frameless|none|900px|alt=radarr-settings-profiles|radarr-settings-profiles]]

Here you’ll be allowed to set profiles for which you can have for the quality of movie you’re looking to download
Here you'll be allowed to set profiles for the quality of movie you're looking to download

More info [https://wiki.servarr.com/Radarr_Settings#Profiles Settings -> Profiles].

We recommend you to create your own profiles and only select the Quality Sources you actually want.

To see what the difference is between the Quality Sources look [https://wiki.servarr.com/Radarr_Settings#Qualities_Defined at our Quality Definitions].

== Quality ==
<small>[[#Quality|anchor]]</small>

<code>Settings</code> => <code>Quality</code>

[[File:radarr-settings-quality.png|frameless|none|900px|alt=radarr-settings-quality|radarr-settings-quality]]

Here you’re able to change/fine tune the min and max size of your wanted media files (when using usenet keep in mind the RAR/PAR2 files)

If you need some help with what to use for a Quality Settings check [https://trash-guides.info/Radarr/V3/Radarr-Quality-Settings-File-Size/ TRaSH's size recommendations] for a tested example.

== Indexers ==
<small>[[#Indexers|anchor]]</small>

<code>Settings</code> => <code>Indexers</code>

[[File:radarr-settings-indexers.png|frameless|none|900px|alt=radarr-settings-indexers|radarr-settings-indexers]]

Here you’ll be adding the indexer/tracker that you’ll be using to actually download any of your files.

Once you’ve clicked the <code>+</code> button to add a new indexer you’ll be presented with a new window with many different options. For the purposes of this wiki Radarr considers both Usenet Indexers and Torrent Trackers as “Indexers”.

There are two sections here: Usenet and Torrents. Based upon what download client you’ll be using you’ll want to select the type of indexer you’ll be going with.

More information on Indexers and Trackers can be found [https://wiki.servarr.com/Definitions#Indexers.2FTrackers on our definitions page]

== Download Clients ==
<small>[[#Download Clients|anchor]]</small>

<code>Settings</code> => <code>Download Clients</code>

[[File:radarr-settings-download-clients.png|frameless|none|900px|alt=radarr-settings-download-clients|radarr-settings-download-clients]]

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

* Usenet
*# Radarr will send a download request to your client, and associate it with a label or category name that you have configured in the download client settings.
*#* Examples: movies, tv, series, music, ect.
*# Radarr will monitor your download clients active downloads that use that category name. It monitors this via your download client’s API.
*# When the download is completed, Radarr will know the final file location as reported by your download client. This file location can be almost anywhere, as long as it is somewhere separate from your media folder and accessible by Radarr
*# Radarr will scan that completed file location for files that Radarr can use. It will parse the file name to match it against the requested media. If it can do that, it will rename the file according to your specifications, and move it to the specified media location.
*# Leftover files from the download will be sent to your trash or recycling.
* BitTorrent - If you’re downloading using a BitTorrent client, the process is slightly different:
*# Completed files are left in their original location to allow you to seed the file (ratio or time can be adjusted in the download client or from within Radarr under the specific download client). When files are imported to your media folder by default Radarr will copy the file, which uses twice the disk space.
*# An advanced option to hardlink can be enabled (Settings > Media Management > Importing) which will attempt to hardlink the media to your Series folder. A hardlink will allow not use any additional disk space. If the hardlink creation fails, Radarr will fall back to the default behavior and copy the file.
*# If the “Completed Download Handling - Remove” option is enabled in Radarr’s settings, Radarr} will delete the original file and torrent from your client, but only if the client reports that seeding is complete and torrent is stopped.

== How to import your existing organized media library ==
<small>[[#How to import your existing organized media library|anchor]]</small>

After setting up your profiles/quality sizes and added your indexers and download client(s) it’s time to import your existing organized media library.

<code>Movies</code>

[[File:radarr-movies.png|frameless|none|900px|alt=radarr-movies|radarr-movies]]

Select <code>Import Existing Movies</code> or select <code>Import</code> from the sidebar.

=== Import movies ===
<small>[[#Import movies|anchor]]</small>

[[File:radarr-movies-import.png|frameless|none|900px|alt=radarr-movies-import|radarr-movies-import]]

Select the root path you added earlier [[#root-folders| in the root folders section.]]

==== Importing Existing Media ====
<small>[[#Importing Existing Media|anchor]]</small>

[[File:radarr-importing-existing.png|frameless|none|900px|alt=radarr-importing-existing|radarr-importing-existing]]

Depending how well you got your existing movie folders named Radarr will try to match it with the correct movie as seen at Nr.5 If all your movies are in a single directrly follow this [https://wiki.servarr.com/Radarr_Tips_and_Tricks#Create_a_Folder_for_Each_Movie guide]

<ol style="list-style-type: decimal;">
<li><p>Your movie folder name.</p></li>
<li><p>How you want the movie to be added to Radarr.</p>
<blockquote><ul>
<li>Yes = Radarr will monitor the RSS feed for the movie in your library that you do not have (yet) or upgrade the existing movie to a better quality.</li>
<li>No = Radarr will not monitor the RSS feed, any upgrades or new movies will be ignored and have to be manually done.</li>
</ul>
</blockquote></li>
<li><p>When will Radarr consider a movie is available.</li>
<blockquote>
<ul>
<li>'''Announced''': Radarr shall consider movies available as soon as they are added to Radarr. This setting is ''recommended'' if you have good private trackers (or really good public ones, e.g. rarbg.to) that do not have fakes.</li>
<li>'''InCinemas''': Radarr shall consider movies available as soon as movies they hit cinemas. This option is ''not recommended''.</li>
<li>'''Physical / Web''': Radarr shall consider movies available as soon as the Blu-ray is released. This option is ''recommended'' if your indexers contain fakes often.</li>
</ul>
</blockquote>
<li><p>Select your preferred profile to use.</p></li>
<li><p>What Radarr thinks the movie matched for. (if you got to many wrong matched you might need to name your folders better).</p></li>
<li><p>Mass select Monitor status.</p></li>
<li><p>Mass select Minimum Availability.</p></li>
<li><p>Mass select Quality Profile.</p></li>
<li><p>Start Importing your existing media library.</p></li></ol>

==== No match found ====
<small>[[#No match found|anchor]]</small>

If you’re getting a error like this

[[File:radarr-importing-existing-no-match.png|frameless|none|900px|alt=radarr-importing-existing-no-match|radarr-importing-existing-no-match]]

Then you probably made a mistake with your movie folder naming.

To fix this issue you can try the following

Expand the error message

[[File:radarr-importing-existing-no-match-expand.png|frameless|none|900px|alt=radarr-importing-existing-no-match-expand|radarr-importing-existing-no-match-expand]]

and check on the [https://www.themoviedb.org/ themoviedb] if the year or title matches. in this example you will notice that the year is wrong and you can fix it by changing the year and click on the refresh icon.

[[File:radarr-importing-existing-no-match-expand-refresh.png|frameless|none|900px|alt=radarr-importing-existing-no-match-expand-refresh|radarr-importing-existing-no-match-expand-refresh]]

Or you can just use the tmdb:id or imdb:id and then select the found movie if matched.

[[File:radarr-importing-existing-no-match-expand-tmdb.png|radarr-importing-existing-no-match-expand-tmdb]] [[File:radarr-importing-existing-no-match-expand-imdb.png|radarr-importing-existing-no-match-expand-imdb]]

==== Fix faulty folder name after import ====
<small>[[#Fix faulty folder name after import|anchor]]</small>

[[File:radarr-wrong-folder-name.png|frameless|none|900px|alt=radarr-wrong-folder-name|radarr-wrong-folder-name]]

You will notice after the fix we did during the import that the folder name still has the wrong year in it. To fix this we’re going to do a little magic trick.

Go to you movie overview

<code>Movies</code>

On the top click on <code>Movie Editor</code>

[[File:radarr-movie-editor.png|frameless|none|900px|alt=radarr-movie-editor|radarr-movie-editor]]

After activating it you select the movie(s) from where you want to have the folder(s) to be renamed.

[[File:radarr-movie-editor-select.png|frameless|none|900px|alt=radarr-movie-editor-select|radarr-movie-editor-select]]

# If you want all your movie folders renamed to your folder naming scheme you set earlier [[#movie-naming|movie naming section]].
# Select the movie(s) from where you want to have the folder(s) to be renamed.
# Choose the same <code>Root Folder</code>

A new popup will be shown

[[File:radarr-movie-editor-move-files-yes.png|frameless|none|900px|alt=radarr-movie-editor-move-files-yes|radarr-movie-editor-move-files-yes]]

Select <code>Yes, Move the files</code>

Then Magic

[[File:radarr-correct-folder-name.png|frameless|none|900px|alt=radarr-correct-folder-name|radarr-correct-folder-name]]

As you can see the folder has been renamed to the correct year following your naming scheme.

== How to add a movie ==
<small>[[#How to add a movie|anchor]]</small>

After you imported your existing well organized media library it’s time to add the movies you want.

<code>Movies</code> => <code>Add New</code>

[[File:radarr-add-new.png|frameless|none|900px|alt=radarr-add-new|radarr-add-new]]

Type in the box the movie you want or use the tmdb:id or imdb:id.

When typing out the movie name you will see it will start showing you results.

[[File:radarr-movie-search.png|frameless|none|900px|alt=radarr-movie-search|radarr-movie-search]]

When you see the movie you want click on it.

[[File:radarr-movie-add.png|frameless|none|900px|alt=radarr-movie-add|radarr-movie-add]]

<ol style="list-style-type: decimal;">
<li><p>Radarr will add the Root Folder you’ve setup [[#root-folders|in the root folders section]]</p></li>
<li><p>How you want the movie to be added to Radarr.</p>
<blockquote><ul>
<li>Yes = Radarr will monitor the RSS feed for the movie in your library that you do not have (yet) or upgrade the existing movie to a better quality.</li>
<li>No = Radarr will not monitor the RSS feed, any upgrades or new movies will be ignored and have to be manually done.</li></ul>
</blockquote></li>
<li><p>When Radarr shall consider a movie is available..</p>
<blockquote><ul>
<li>'''Announced''': Radarr shall consider movies available as soon as they are added to Radarr. This setting is ''recommended'' if you have good private trackers (or really good public ones, e.g. rarbg.to) that do not have fakes.</li>
<li>'''InCinemas''': Radarr shall consider movies available as soon as movies they hit cinemas. This option is ''not recommended''.</li>
<li>'''Physical / Web''': Radarr shall consider movies available as soon as the Blu-ray is released. This option is ''recommended'' if your indexers contain fakes often.</li></ul>
</blockquote></li>
<li><p>Select your preferred profile to use.</p></li>
<li><p>Here you can add certain tags for advanced uasage.</p></li>
<li><p>Make sure you enable this if you want Radarr search for the missing movie when added to Radarr [https://wiki.servarr.com/Radarr_FAQ#How_does_Radarr_find_movies.3F more info]</p></li>
<li><p>Click on <code>Add Movie</code> to add the movie to Radarr.</p></li></ol>

That’s all, Folks....

Docker Guide

2021-05-08T21:17:36Z

TRaSH: /* Consistent and well planned paths */

=== The Best Docker Setup ===

'''TL; DR''': An [https://www.lexico.com/en/definition/eponymous eponymous] user per daemon and a shared group with a umask of <code>002</code>. Consistent path definitions between ''all'' containers that maintains the folder structure. Using one volume for Sonarr, Radarr and Lidarr so the download folder and library folder are on the same file system which makes hard links and instant moves possible. And most of all, ignore ''most'' of the Docker image’s path documentation!

'''Note: Many folks find [https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/ TRaSH's Hardlink Tutorial] helpful and easier to understand than this guide. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.'''

==== Introduction ====

This article will not show you specifics about the best Docker setup, but it describes an overview that you can use to make your own setup the best that it can be. The idea is that you run each docker container as its own user, with a shared group and consistent volumes so every container sees the same path layout. This is easy to say, but difficult to understand and explain.

==== Multiple users and a shared group ====

===== Permissions =====

Ideally, each software runs as its own user user and they’re all part of a shared group with folder permissions set to <code>775</code> (<code>drwxrwxr-x</code>) and files set to <code>664</code> (<code>-rw-rw-r--</code>), which is a umask of <code>002</code>. A sane alternative to this is a single shared user, which would use <code>755</code> and <code>644</code> which is a umask of <code>022</code>. You can restrict permissions even more by denying read from “other”, which would be a umask of <code>007</code> for a user per daemon or <code>077</code> for a single shared user. For a deeper explanation, try the Arch Linux wiki articles about [https://wiki.archlinux.org/index.php/File_permissions_and_attributes File permissions and attributes] and [https://wiki.archlinux.org/index.php/Umask Umask].

===== UMASK =====

Many docker images accept a <code>-e UMASK=002</code> environment variable and some software inside can be configured with a user, group and umask (NZBGet) or folder/file permission (Sonarr/Radarr). This will ensure that files and folders created by ''one'' can be read and written by the others. If you’re using existing folders and files, you’ll need to fix their current ownership and permissions too, but going forward they’ll be correct because you set each software up right.

===== PUID and PGID =====

Many docker images also take a <code>-e PUID=123</code> and <code>-e PGID=321</code> that lets you change the UID/GID used inside to that of an account on the outside. If you ever peak in, you’ll find that username is something like <code>abc</code>, <code>nobody</code> or <code>hotio</code>, but because it uses the UID/GID you pass in, on the outside it looks like the expected user. If you’re using storage from another system via NFS or CIFS, it will make your life easier if ''that'' system also has matching users and group. Perhaps let one system pick the UID/GIDs, then re-use those on the other system, assuming they don’t conflict.

===== Example =====

You run [https://github.com/Sonarr/Sonarr/releases Sonarr] using [https://github.com/hotio/docker-sonarr hotio/sonarr], you’ve created a <code>sonarr</code> user with uid <code>123</code> and a shared group <code>media</code> with gid <code>321</code> which the <code>sonarr</code> user is a member of. You configure the Docker image to run with <code>-e PUID=123 -e PGID=321 -e UMASK=002</code>. Sonarr also lets you configured user, group as well as folder and file permissions. The previous settings should negate these, but you could configure them if you wanted. Folders would be <code>775</code>, files <code>664</code> and the user/group are a little tricky because ''inside'' the container, they have a different name. Maybe <code>abc</code> or <code>nobody</code>. I’d leave all these blank unless you find you need them for some reason.

==== Single user and optional shared group ====

Another popular and arguably easier option is a single, shared user. Perhaps even ''your'' user. It isn’t as secure and doesn’t follow best practices, but in the end it is easier to understand and implement. The UMASK for this is <code>022</code> which results in <code>755</code> (<code>drwxr-xr-x</code>) for folders and <code>644</code> (<code>-rw-r--r--</code>) for files. The group no longer really matters, so you’ll probably just use the group named after the user. This does make it harder to share with ''other'' users, so you may still end up wanting a UMASK of <code>002</code> even with this setup.

==== Ownership and permissions of /config ====

Don’t forget that your <code>/config</code> volume will ''also'' need to have correct ownership and permissions, usually the daemon’s user and that user’s group like <code>sonarr:sonarr</code> and a umask of <code>022</code> or <code>077</code> so ''only'' that user has access. In a single user setup, this would of course be the one user you’ve chosen.

==== Consistent and well planned paths ====

'''Note: Many folks find [https://trash-guides.info/hardlinks TRaSH's Hardlink Tutorial] helpful and easier to understand than this guide. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.'''

The easiest and most important detail is to create unified path definitions across all the containers.

If you’re wondering why hard links aren’t working or why a simple move is taking far longer than it should, this section explains it. The paths you use on the ''inside'' matter. Because of how Docker’s volumes work, passing in two volumes such as the commonly suggested <code>/tv</code> and <code>/downloads</code> makes them look like two file systems, even if they aren’t. This means hard links won’t work ''and'' instead of an instant move, a slower and more io intensive copy + delete is used. If you have multiple download clients because you’re using torrents and usenet, having a single <code>/downloads</code> path means they’ll be mixed up. Because the Radarr in one container will ask the NZBGet in its own container where files are, using the same path in both means it will all just work. If you don’t, you’d need to fix it with a remote path map.

So pick ''one'' path layout and use it for all of them. I’m a fan of <code>/data</code>, but there are other great names like <code>/shared</code>, <code>/media</code> or <code>/dvr</code>. If this can be the same on the outside ''and'' inside, your setup will be simpler: one path to remember or if integrating docker and native software. But if not, that’s fine too. For example, Synology might use <code>/Volume1/data</code> and unRAID might use <code>/mnt/user/data</code> on the outside, but <code>/data</code> on the inside is fine.

It is also important to remember that you’ll need to setup or re-configure paths in the software running ''inside'' these Docker containers. If you change the paths for your download client, you’ll need to edit its settings to match. If you change your library path, you’ll need to change those settings in Sonarr, Radarr, Lidarr and/or Plex.

===== Examples =====

What matters here is the general structure, not the names. You are free to pick folder names that make sense to you. And there are other ways of arranging things too. For example, you’re not likely to download and run into conflicts of identical releases between usenet and torrents, so you ''could'' put both in <code>/data/downloads/{movies|music|tv}</code> folders. Downloads don’t even have to be sorted into subfolders either, since movies, music and tv will rarely conflict.

This example <code>data</code> folder has subfolders for torrents and usenet and each of these have subfolders for tv, movie and music downloads to keep things neat. The <code>media</code> folder has nicely named <code>tv</code>, <code>movies</code> and <code>music</code> subfolders, this is your library and what you’d pass to Plex, Kodi, or Emby.

<pre>data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv</pre>
The path for each Docker container can be as specific as needed while still maintaining the correct structure:

====== Torrents ======

<pre>data
└── torrents
├── movies
├── music
└── tv</pre>
Torrents only needs access to torrent files, so pass it <code>-v /host/data/torrents:/data/torrents</code>. In the torrent software settings, you’ll need to reconfigure paths and you can sort into subfolders like<code>/data/torrents/{tv|movies|music}</code>.

====== Usenet ======

<pre>data
└── usenet
├── movies
├── music
└── tv</pre>
Usenet only needs access to usenet files, so pass it <code>-v /host/data/usenet:/data/usenet</code>. In the usenet software settings, you’ll need to reconfigure paths and you can sort into subfolders like<code>/data/usenet/{tv|movies|music}</code>.

====== Media Server ======

<pre>data
└── media
├── movies
├── music
└── tv</pre>
Plex/Emby only needs access to your media library, so pass <code>-v /host/data/media:/data/media</code>, which can have any number of subfolders like <code>movies</code>, <code>kids movies</code>, <code>tv</code>, <code>documentary tv</code> and/or <code>music</code> as sub folders.

====== Sonarr, Radarr and Lidarr ======

<pre>data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv</pre>
Sonarr, Radarr and Lidarr get everything using <code>-v /host/data:/data</code> because the ''download'' folder(s) and ''media'' folder will look like and ''be'' one file system. Hard links will work and moves will be atomic, instead of copy + delete.

===== Issues =====

There are a couple minor issues with not following the Docker image’s suggested paths.

The biggest is that volumes defined in the <code>Dockerfile</code> will get created if they’re not specified, this means they’ll pile up as you delete and re-create the containers. If they end up with data in them, they can consume space unexpectedly and likely in an unsuitable place. You can find a [https://old.reddit.com/r/usenet/wiki/docker#wiki_prune_docker cleanup command] in the helpful commands section below. This could also be mitigated by passing in an empty folder for all the volumes you don’t want to use, like <code>/data/empty:/movies</code> and <code>/data/empty:/downloads</code>. Maybe even put a file named <code>DO NOT USE THIS FOLDER</code> inside, to remind yourself.

Another problem is that some images are pre-configured to use the documented volumes, so you’ll need to change settings in the software inside the Docker container. Thankfully, since configuration persists outside the container this is a one time issue. You might also pick a path like <code>/data</code> or <code>/media</code> which some images already define for a specific use. It shouldn’t be a problem, but will be a little more confusing when combined with the previous issues. In the end, it is worth it for working hard links and fast moves. The consistency and simplicity are welcome side effects as well.

If you use the latest version of the abandoned [https://github.com/Sperryfreak01/RadarrSync RadarrSync] to synchronize two Radarr instances, it ''depends'' on mapping the ''same'' path inside to a different path on the outside, for example <code>/movies</code> for one instance would point at <code>/data/media/Movies</code> and the other at <code>/data/media/Movies 4k</code>. This breaks ''everything'' you’ve read above. There is no good solution, you either use the old version which isn’t as good, do your mapping in a way that is ugly and breaks hard links or just don’t use it at all.

==== Running containers using ====

===== Docker-compose =====

This is the best option for most users, it lets you control and configure many containers and their interdependence in one file. A good starting place is docker’s own [https://docs.docker.com/compose/gettingstarted/ Get started with Docker Compose]. You can use [https://composerize.com composerize] or [https://old.reddit.com/r/usenet/wiki/docker#wiki_get_docker-compose red5d/docker-autocompose]to convert <code>docker run</code> commands into a single <code>docker-compose.yml</code> file.

The below is ''not'' a complete working example! The containers only have PID, UID, UMASK and example paths defined to keep it simple.

<pre># sonarr
Sonarr:
image: "hotio/sonarr"
volumes:
- /path/to/config/sonarr:/config
- /host/data:/data
environment:
- PUID=111
- PGID=321
- UMASK=002

# deluge
Deluge:
image: binhex/arch-delugevpn
volumes:
- /path/to/config/deluge:/config
- /host/data/torrents:/data/torrents
environment:
- PUID=222
- PGID=321
- UMASK=002

# sabnzbd
SABnzbd:
image: binhex/arch-sabnzbd
volumes:
- /path/to/config/sabnzbd:/config
- /host/data/usenet:/data/usenet
environment:
- PUID=333
- PGID=321
- UMASK=002

# plex
Plex:
image: binhex/arch-plex
volumes:
- /path/to/config/plex:/config
- /host/data/media:/data/media

environment:
- PUID=444
- PGID=321
- UMASK=002</pre>
====== Update all images and containers ======

<pre>docker-compose pull
docker-compose up -d</pre>
====== Update individual image and container ======

<pre>docker-compose pull NAME
docker-compose up -d NAME</pre>
===== Docker Run =====

Like the Docker Compose example above, the following <code>docker run</code> commands are stripped down to ''only'' the PUID, PGID, UMASK and volumes in order to act as an obvious example.

<pre># sonarr
docker run -v /path/to/config/sonarr:/config \
-v /host/data:/data \
-e PUID=111 -e PGID=321 -e UMASK=002 \
hotio/sonarr

# deluge
docker run -v /path/to/config/deluge:/config \
-v /host/data/torrents:/data/torrents \
-e PUID=222 -e PGID=321 -e UMASK=002 \
binhex/arch-delugevpn

# sabnzbd
docker run -v /path/to/config/sabnzbd:/config \
-v /host/data/usenet:/data/usenet \
-e PUID=333 -e PGID=321 -e UMASK=002 \
binhex/arch-sabnzbd

# plex
docker run -v /path/to/config/plex:/config \
-v /host/data/media:/data/media \
-e PUID=444 -e PGID=321 -e UMASK=002 \
binhex/arch-plex</pre>
===== Systemd =====

I don’t run a full Docker setup, so I manage my few Docker containers with individual systemd service files. It standardizes control and makes dependencies simpler for both native and docker services. The generic example below can be adapted to any container by adjusting or adding the various values and options.

<pre># /etc/systemd/system/thing.service
[Unit]
Description=Thing
Requires=docker.service
After=network.target docker.service

[Service]
ExecStart=/usr/bin/docker run --rm \
--name=thing \
-v /path/to/config/thing:/config \
-v /host/data:/data
-e PUID=111 -e PGID=321 -e UMASK=002 \
nobody/thing

ExecStop=/usr/bin/docker stop -t 30 thing

[Install]
WantedBy=default.target</pre>
==== Helpful commands ====

===== List running containers =====

<pre>docker ps</pre>
===== Shell ''inside'' a container =====

<pre>docker exec -it CONTAINER_NAME /bin/bash</pre>
For more information, see the [https://docs.docker.com/engine/reference/commandline/exec/ docker exec] documentation.

===== Prune docker =====

<pre>docker system prune --all --volumes</pre>
Remove unused containers, networks, volumes, images and build cache. As the WARNING this command gives says, this will remove all of the previously mentioned items for anything not in use by a running container. In a correctly configured environment, this is fine. But be aware and proceed cautiously the first time. See the [https://docs.docker.com/engine/reference/commandline/system_prune/ docker system prune] documentation for more details.

===== Get docker run command =====

Getting the <code>docker run</code> command from GUI managers can be hard, this docker image makes it easy for a running container ([https://stackoverflow.com/questions/32758793/how-to-show-the-run-command-of-a-docker-container source]).

<pre>docker run --rm -v /var/run/docker.sock:/var/run/docker.sock assaflavie/runlike CONTAINER_NAME</pre>
===== Get docker-compose =====
Additionally, you may check out [https://trash-guides.info/Misc/how-to-provide-a-docker-compose/ TRaSH's Guide for docker-compose]

Getting a <code>docker-compose.yml</code> from running instances is possible with [https://hub.docker.com/r/red5d/docker-autocompose red5d/docker-autocompose], in case you’ve already started your containers with <code>docker run</code> or <code>docker create</code> and want to change to <code>docker-compose</code> style. It is also great for sharing your settings with others, since it doesn’t matter what management software you’re using. The last argument(s) are your container names and you can pass in as many as needed at the same time. The first container name is required, more are optional. You can see container names in the '''NAMES''' column of `docker ps`, they're usually set by you or might be generated based on the image like <code>binhex-qbittorrent</code>. It is ''not'' the image name, like <code>binhex/arch-qbittorrentvpn</code>.

<pre>docker run --rm -v /var/run/docker.sock:/var/run/docker.sock red5d/docker-autocompose CONTAINER_NAME [ANOTHER_CONTAINER_NAME] ... [ONE_MORE_CONTAINER_NAME]</pre>

===== Troubleshoot networking =====

Most Docker images don’t have many useful tools in them for troubleshooting, but you can [https://success.docker.com/article/troubleshooting-container-networking attach a network troubleshooting type image] to an existing container to help with that.

<pre>docker run -it --rm --network container:CONTAINER_NAME nicolaka/netshoot</pre>
===== Recursively chown user and group =====

<pre>chown -R user:group /some/path/here</pre>
===== Recursively chmod to 775/664 =====

<pre>chmod -R a=,a+rX,u+w,g+w /some/path/here
^ ^ ^ ^ adds write to group
| | | adds write to user
| | adds read to all and execute to all folders (which controls access)
| sets all to `000`</pre>
===== Find UID/GID for user =====

<pre>id <username></pre>

===== Examine files for hard links =====
<pre>ls -alhi
42207934 -rw-r--r-- 2 user group 0 Sep 11 11:55 hardlink
42207936 -rw-r--r-- 1 user group 0 Sep 11 11:55 nohardlinks
42207934 -rw-r--r-- 2 user group 0 Sep 11 11:55 original
</pre>

<pre>stat original
File: original
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 803h/2051d Inode: 42207934 Links: 2
Access: (0644/-rw-r--r--) Uid: ( 1000/ user) Gid: ( 1001/ group)
Access: 2020-09-11 11:55:43.803327144 -0500
Modify: 2020-09-11 11:55:43.803327144 -0500
Change: 2020-09-11 11:55:49.706660476 -0500
Birth: 2020-09-11 11:55:43.803327144 -0500
</pre>

==== Interesting docker images ====

* [https://hub.docker.com/r/rasmunk/sshfs rasmunk/sshfs] let you create an sshfs volume, ''perfect'' for a seedbox setup using a remote mount instead of sync. Better documentation, including examples can be found at the github [https://github.com/rasmunk/docker-volume-sshfs rasmunk/docker-volume-sshfs] repository. This is a more recently maintained fork of [https://hub.docker.com/p/vieux/sshfs vieux/sshfs].
* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/sonarr sonarr], [https://hub.docker.com/r/hotio/radarr radarr] and [https://hub.docker.com/r/hotio/lidarr lidarr] images let you run the built in version ''or'' specify an alternative via environment variable. The documentation and Dockerfile also don’t make any poor path suggestions. Images are automatically updated 2x in 1 hour if upstream changes are found. Hotio also builds our Pull Requests which may be useful for testing.
* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/ombi ombi], [https://hub.docker.com/r/hotio/jackett jackett], [https://hub.docker.com/r/hotio/nzbhydra2 nzbhydra2] and [https://hub.docker.com/r/hotio/bazarr bazarr] are useful too, but don’t really require any special permissions or paths.
* [https://hub.docker.com/u/hotio hotio’s] [https://hub.docker.com/r/hotio/unpackerr unpackerr] is useful for packed torrent extraction across a variety of torrent clients where unpacking is lacking or missing entirely.
* [https://hub.docker.com/u/binhex binhex’s] [https://hub.docker.com/r/binhex/arch-qbittorrentvpn/ qbittorrent], [https://hub.docker.com/r/binhex/arch-delugevpn/ deluge] and [https://hub.docker.com/r/binhex/arch-rtorrentvpn/ rtorrent] are popular torrent clients with built in VPN support. For usenet, there is [https://hub.docker.com/r/binhex/arch-sabnzbd/ sabnzbd] and [https://hub.docker.com/r/binhex/arch-nzbget/ nzbget].
* [https://hub.docker.com/u/binhex binhex’s] [https://hub.docker.com/r/binhex/arch-sonarr/ sonarr], [https://hub.docker.com/r/binhex/arch-radarr/ radarr] and [https://hub.docker.com/r/binhex/arch-lidarr/ lidarr] images suggest default paths that don’t allow for hard linking, instead follow the process described above and pass in a single volume.
* [https://hub.docker.com/u/linuxserver linuxserver.io’s] images have images for a ''lot'' of software and they’re well maintained.
* [https://hub.docker.com/r/pyouroboros/ouroboros pyouroboros/ouroboros] or [https://hub.docker.com/r/containrrr/watchtower containrrr/watchtower] automatically update your running Docker containers to the latest available image. These are not recommended if you use Docker Compose.

==== Custom Docker Network and DNS ====

One interesting feature of a [https://docs.docker.com/network/network-tutorial-standalone/#use-user-defined-bridge-networks custom Docker network] is that it gets its own DNS server. If you create a bridge network for your containers, you can use their hostnames in your configuration. For example, if you <code>docker run --network=isolated --hostname=deluge binhex/arch-deluge</code> and <code>docker run --network=isolated --hostname=radarr binhex/arch-radarr</code>, you can then configure the Download Client in Radarr to point at just <code>deluge</code> and it’ll work ''and'' communicate on its own private network. Which means if you wanted to be even more secure, you could ''stop'' forwarding that port too. If you put your reverse proxy container on the same network, you can even stop forwarding the web interface ports and make them even more secure.

==== Common Problems ====

===== Correct ''outside'' paths, incorrect ''inside'' paths =====

Many people read this and think they understand, but they end up seeing the outside path correctly to something like <code>/data/usenet</code>, but then they miss the point and set the ''inside'' path to <code>/downloads</code> still.

===== Running Docker containers as root or changing users around =====

If you find yourself running your containers as <code>root:root</code>, you’re doing something wrong. If you’re not passing in a UID and GID, you’ll be using whatever the default is for the image and ''that'' will be unlikely to line up with a reasonable user on your system. And if you’re changing the user and group your Docker containers are running as, you’ll probably end up with permissions issues on folders like the <code>/config</code> folder which will likely have files and folders in them that got created the first time with the UID/GID you used the first time.

===== Running Docker containers with umask 000 =====

If you find yourself setting a UMASK of <code>000</code> (which is 777 for folders and 666 for files), you’re ''also'' doing something wrong. It leaves your files and folders read/write to ''everyone'', which is poor Linux hygiene.

==== Getting Help ====

Need some help? For real time, chat style support try the [https://discord.gg/xyRwnyB Sonarr] or [https://radarr.video/discord Radarr] Discord servers. If you prefer forum style support, make a post in [http://reddit.com/r/sonarr /r/sonarr] or [http://reddit.com/r/radarr /r/radarr].

Template:Installation

2021-02-06T08:38:15Z

TRaSH: /* Synology */

<noinclude>
<templatedata>
{
"params": {
"ARRNAME": {
"description": "Name of the ARR",
"example": "Radarr",
"type": "string",
"required": true,
"default": "Fake Radarr"
},
"RunArrCommandLinux": {
"description": "Command to Start & Run ARR Linux",
"example": "./opt/Radarr/Radarr -nobrowser -data=/home/radarr/.config/Radarr/",
"type": "string",
"required": true
},
"RunArrCommandOSX": {
"description": "Command to Start & Run ARR OSX",
"example": "./opt/Radarr/Radarr -nobrowser -data=/home/radarr/.config/Radarr/",
"type": "string",
"required": true
},
"ArrExecutableNameWin": {
"description": "Executable Name for Windows",
"example": "Radarr.exe",
"type": "string",
"required": true
},
"ArrDownloadLink": {
"description": "Link to the Arr Downloads",
"type": "url",
"required": true
},
"ArrLinuxAutoStart": {
"description": "Autostart file instructions",
"required": true
},
"ARRPORT": {
"description": "Port number for the ARR",
"example": "Radarr: 7878, Sonarr: 8989, Lidarr: 8686, Readarr: 8787",
"type": "number",
"default": "7878",
"required": true
},
"ARRNAME2": {
"description": "Used for lowercase ARR names, this is not a required field only used if needed",
"example": "radarr, sonarr, lidarr, readarr",
"type": "string"
}
},
"paramOrder": [
"ARRNAME",
"RunArrCommandLinux",
"RunArrCommandOSX",
"ArrExecutableNameWin",
"ArrDownloadLink",
"ArrLinuxAutoStart",
"ARRPORT",
"ARRNAME2"
],
"description": "This template is expressly for the steps and processes of installing all the various ARR software on multiple different platforms"
}
</templatedata>
</noinclude>

= Installing =
== Windows ==

== OSX ==
{{#lst::Installation Misc|{{{ARRNAME2}}}_osx_big_sur_installation}}

== Linux ==

=== Debian / Ubuntu ===
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.

{{#lst::Installation Misc|{{{ARRNAME2}}}_linux_ubuntu_NetCore_manual_installation}}

==== Mono Install ====
{{#lst::Installation Misc|{{{ARRNAME2}}}_linux_ubuntu_repository_installation}}

===== Manual Install (Mono) =====
Manual Installs need to have dependencies installed first.

Mono:
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb https://download.mono-project.com/repo/ubuntu stable-focal main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list
sudo apt update && sudo apt install mono-devel
Curl
sudo apt install curl
Mediainfo:
sudo apt install mediainfo
sqlite3:
sudo apt install sqlite3

Now download the newest mono version release of {{{ARRNAME}}}:
wget --content-disposition '{{{ARRPackageFileMono}}}'

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

You can start {{{ARRNAME}}} with the following command:
/usr/bin/mono --debug /opt/{{{ARRNAME}}}/{{{ARRNAME}}}.exe -nobrowser

=== Auto Start Using Systemd ===
Most modern Linux distributions have switched to systemd, which involves a simple unit service file which gets enabled and started. It is important to remember that in Linux, capitalization matters. <code>User</code> account names and <code>Group</code> names are typically all lowercase, as are the directory structures mapped to them as part of the home directory.

==== Preparing the Unit Service File ====
Several items may need to be changed to match your installation:

# <code>User</code> should match the service account that {{{ARRNAME2}}} will run as.
# <code>Group</code> should match the service account group that {{{ARRNAME2}}} will run as.
# <code>ExecStart</code> has several items that should match your installation <code>/opt/{{{ARRNAME}}}/{{{ARRNAME}}}</code>
## Executable Path Default location is <code>/opt/{{{ARRNAME}}}/{{{ARRNAME}}}</code>, but you may need to update if you installed {{{ARRNAME}}} elsewhere.
## 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.
## 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.

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.

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>.

{{#lst::Installation Misc|{{{ARRNAME2}}}_installation_unit_service_file}}

==== Verify Directory Permissions ====
Ensure the <code>User</code> that will be running {{{ARRNAME}}} has access to both the executable directory and data directory.
Running the command <code>ls -lad /directory/</code> will show the permissions for that folder.
Example:
$ ls -lad /opt/{{{ARRNAME}}}
drwxr-xr-x 6 {{{ARRNAME2}}} {{{ARRNAME2}}} 24576 Nov 28 21:30 /opt/{{{ARRNAME}}}/
$ ls -lad /home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/
drwxr-xr-x 6 {{{ARRNAME2}}} {{{ARRNAME2}}} 24576 Nov 28 21:30 /home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/

==== Enabling and starting the Unit Service File ====
Once you have created <code>{{{ARRNAME}}}.service</code>, you will want to enable the service:
sudo systemctl enable {{{ARRNAME}}}.service

You are now ready to start {{{ARRNAME}}}. You can do so with the <code>start</code> command:
sudo systemctl start {{{ARRNAME}}}.service

If you want to verify {{{ARRNAME}}} is running, you can run the <code>status</code> command:
$ sudo systemctl status {{{ARRNAME}}}.service
● {{{ARRNAME}}}.service - {{{ARRNAME}}}Service
Loaded: loaded (/usr/lib/systemd/system/{{{ARRNAME}}}.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2017-03-07 10:23:44 PST; 5min ago
Main PID: 19978 ({{{ARRNAME}}})
Tasks: 16 (limit: 4915)
Memory: 114.6M
CPU: 9.331s
CGroup: /system.slice/{{{ARRNAME}}}.service
└─19978 /opt/{{{ARRNAME}}}/{{{ARRNAME}}} -nobrowser -data=/home/{{{ARRNAME2}}}/.config/{{{ARRNAME}}}/
Mar 07 10:23:44 apollo systemd[1]: Started {{{ARRNAME}}} Service.
=== NGINX Reverse Proxy ===
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.

(Link to NGINX Install Wiki Page)

Create a text file named {{{ARRNAME}}}.conf and place it in your default NGINX App directory, typically <code>/etc/nginx/conf.d/apps</code>
# {{{ARRNAME}}} Reverse Proxy
# Be sure to set your Base-URL in {{{ARRNAME}}}
location /{{{ARRNAME2}}} {
proxy_pass http://127.0.0.1:{{{ARRPORT}}}/{{{ARRNAME2}}};
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_http_version 1.1;
proxy_no_cache $cookie_session;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
# Allow the {{{ARRNAME}}} API
location /{{{ARRNAME2}}}/api { auth_request off;
proxy_pass http://127.0.0.1:{{{ARRPORT}}}/{{{ARRNAME2}}}/api;
}
}
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.

Once you have saved the file, test your NGINX config:
sudo nginx -t
Which should show this:
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Now you can have NGINX reload it's configuration to use the new file:
sudo nginx -s reload
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>
The URL base can be set here: https://wiki.servarr.com/{{{ARRNAME}}}_Settings#Host

== NAS ==
=== FreeNAS ===
=== Qnap ===
=== Synology ===
* 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].
* This guide works directly with docker-compose as this is typically a much better/faster way to get you up and running
<br><center>'''NOTE:'''</center>
If your Synology doesn't support dockers you will need to look at the packages that are fully maintained by the Synology community.
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.

== Docker ==

== Docker on unRAID ==
* Installation of {{{ARRNAME}}} is quite simple when it comes to unRAID as they have made installing Docker containers a breeze.
<ol style="list-style-type: decimal;">
<li><p>Simply head on over to the community applications store on the top bar of your browser. <br /></p></li>
[[File:unraid-install1.png|frameless|750px|alt=Community Applications|Communitty Applications]]
<li><p>In the search field type in {{{ARRNAME}}}<br />
</p></li>
<li><p>Select which docker image you would like to install. There are several to choose from<br />
</p></li>
[[File:{{{ARRNAME}}}-unraid-install.png|frameless|none|750px|alt=Installation Options|Installation Options]]
<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 />
</p></li>
<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>
<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>
<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>
[[File:unraid-install3.png|frameless|750px|alt=Toggle Advanced|Toggle Advanced]]
<ol>
<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 />
</p></li>
<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 />
</p></li>
<li><p> From here you will want to fill out all pertinant information:<br />
</p></li>
<ol>
<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 />
</p></li>
<li><p>'''Container Path:''' This will be the path that {{{ARRNAME}}} will see inside the container <code>/data</code> is a favorite<br />
</p></li>
<li><p>'''Host Path:''' This is the path to the host (unRAID) machine, This will be <code>/mnt/user/<Your User Share></code><br />
</p></li>
<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>
<li><p> The last three items '''Default Value:''', '''Access Mode"''', and '''Description:''' Can be left alone.<br />
</p></li>
<li><p> Click '''ADD'''<br />
</p></li>
[[File:unraid-install4.png|frameless|750px|alt=Add New path|Add New Path]]
</ol>
<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 />
</p></li>
<li><p> Click '''APPLY'''<br />
</p></li>
</ol>
<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 />
</p></li>
<li><p> Click '''DOCKER''' on the top row of your browser.<br />
</p></li>
<li><p> Now all you will need to do is simply left click on your newly created container and select '''WebUI'''.<br />
</p></li>
[[File:unraid-install2.png|frameless|none|250x240px|alt=Select WebUI|Select WebUI]]
<li><p> Now a new browser tab should show up with {{{ARRNAME}}} running in all its glory. '''ENJOY'''<br />
</p></li>
</ol>

Sonarr FAQ

2021-01-30T11:47:56Z

TRaSH: /* Preferred Words FAQs */

== How does Sonarr find episodes? ==
<span id="how_does_Sonarr_find_episodes"><small>[[#how_does_Sonarr_find_episodes|anchor]]</small></span><br>

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

== Why didn’t Sonarr grab an episode I was expecting? ==
<span id="Why_didnt_Sonarr_grab_an_episode_i_was_expecting"><small>[[#Why_didnt_Sonarr_grab_an_episode_i_was_expecting|anchor]]</small></span><br>

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

== How are possible downloads compared? ==
<span id="how_are_possible_downloads_compared"><small>[[#how_are_possible_downloads_compared|anchor]]</small></span><br>
'''Generally Quality Trumps All'''

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

== Preferred Words FAQs ==
<span id="Preferred_Words_FAQs"><small>[[#Preferred_Words_FAQs|anchor]]</small></span><br>

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

How are preferred words included in renaming?

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

For Radarr you can make use of the `{Custom Formats}` token in your renaming scheme. and you need to enable it in your Custom Format
take a look [https://trash-guides.info/Radarr/V3/Radarr-recommended-naming-scheme/ HERE] for a recommended naming scheme examples for Radarr.

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

== How does Sonarr handle scene numbering issues (American Dad!, etc)? ==
<span id="how_does_sonarr_handle_scene_numbering_issues"><small>[[#how_does_sonarr_handle_scene_numbering_issues|anchor]]</small></span><br>

* '''How Sonarr handles scene numbering issues'''
** Sonarr relies on [http://thexem.de/ TheXEM], a community driven site that lets users create mappings of shows that the scene (the people that post the files) and TheTVDB (which typically follows the network’s numbering). There are a number of shows on there already, but its easy to add another and typically the changes are accepted within a couple days (if they’re correct). TheXEM is used to correct differences in episode numbering (disagreement whether an episode is a special or not) as well as season number differences, such as episodes being released as S10E01, but TheTVDB listing that same episode as S2017E01.
* '''Problematic Shows'''
** This by no means is an all inclusive list of shows that have known issues with scene mapping however, these are the big ones that come to mind while writing this.
** Typical Issue: Scene numbering does not match TVDb numbering so Sonarr doesn't work. Well enter XEM which creates a map for Sonarr to look at.
*** Scene releases double episodes in a single file since that is how they air but TVDb marks each episode individually.
*** Scene uses a year for the season S2010 and TVDb uses S01.
** [http://thexem.de XEM] works in most cases and keeps it running smooth without you ever knowing. However as with most things, there will always be a _black sheep_ and in this case there is a list of them.
** This is a list of the known shows and how/why they're **fu...** Problematic!
*** American Dad
*** Arrested Development
*** Mythbusters
*** Paw Patrol
**** Double episode files vs single episode TVDb but also not all episodes are doubles so the map can get added wrong pointing to which ones are singles vs doubles
*** Pawn Stars
*** Pokemon
**** On TheXem, [http://thexem.de/xem/show/4638 pokemon] is tracking *dubbed* episodes. So if you want subbed episodes, you might be out of luck.
* '''Possible resolutions:'''
# TVDb adds alternate ordering to the API (Current status: They say v4 but dont count on it to work or be stable based on the history of v3)
# XEM adds a map to allow for alternate orders that sonarr can use (Current status: Unlikely)
# Sonarr allows for disabling of XEM maps when doing manual searches (Current status: Unlikely)
* '''Sonarr side effects:'''
** On top of the issues with the shows already, Sonarr also has some odd behavior so you may just need to overlook this as well. Example:
** American Dad is currently on S17 based on TVDb or S16 based on Scene at the time of this writing. So searching in sonarr for season 17 will '''only''' return S16 results because of the XEM map. If you have a tracker with S17 episodes (because they use P2P and not Scene), you are SOL & sonarr will never see them or find them. Right click > Save as on the torrent and add it manually is your <u>solution</u>. However here is the odd part, if you use tags and you add it to your client with a tag that Sonarr looks for, it will see the episodes and when they download it '''will''' automatically import them to S17. So it wont find S17 because it is mapped to S16 but it will import S17 to S17 even though it is mapped to S16. Cant explain it & never got an answer for it so enjoy the inconsistent logic as it will save you having to import it.
* '''Final thouhgs:'''
** This may or may not happen on other shows but we have only tested it on this one. Main point, if you have any issues related to these shows you're kind of out of luck and just have to deal with it. It is something that is constantly being worked on and discussed as it is a pain for us as well as much as it is for you.

== Why can’t Sonarr import episode files for series X? / Why can’t Sonarr find releases for series X? ==
<span id="why_cant_sonarr_import_episode_files_for_series_x_why_cant_sonarr_find_releases_for_series_x"><small>[[#why_cant_sonarr_import_episode_files_for_series_x_why_cant_sonarr_find_releases_for_series_x|anchor]]</small></span><br>

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

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

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

''Again, do not request a mapping for Anime; use XEM for that.''

== Sonarr grabbed a release, why can’t it import it? ==
<span id="sonarr_grabbed_a_release_why_cant_it_import_it"><small>[[#sonarr_grabbed_a_release_why_cant_it_import_it|anchor]]</small></span><br>

The reason it was able to grab the release in the first place was because the indexer returned the tv rage ID for the series and Sonarr was able to match it to that, but that ID is not available during import, so it fails.

== I see that feature/bug X was fixed, why can’t I see it? ==
<span id="i_see_that_feature_bug_x_was_fixed_why_cant_i_see_it"><small>[[#i_see_that_feature_bug_x_was_fixed_why_cant_i_see_it"|anchor]]</small></span><br>

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

== Episode Progress - How is it calculated? ==
<span id="episode_progress_-_how_is_it_calculated"><small>[[#episode_progress_-_how_is_it_calculated|anchor]]</small></span><br>

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

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

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

== How do I access Sonarr from another computer? ==
<span id="how_do_I_access_sonarr_from_another_computer"><small>[[#how_do_I_access_sonarr_from_another_computer|anchor]]</small></span><br>

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

== Why doesn’t Sonarr automatically search for missing episodes? ==
<span id="why_doesnt_sonarr_automatically_search_for_missing_episodes"><small>[[#why_doesnt_sonarr_automatically_search_for_missing_episodes|anchor]]</small></span><br>

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

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

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

== Why does Sonarr refresh series information so frequently? ==
<span id="why_does_sonarr_refresh_series_information_so_frequently"><small>[[#why_does_sonarr_refresh_series_information_so_frequently|anchor]]</small></span><br>

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

== Why is there a number next to Activity? ==
<span id="why_is_there_a_number_next_to_activity"><small>[[#why_is_there_a_number_next_to_activity|anchor]]</small></span><br>

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

== I see log messages for shows I don’t have/don’t want ==
<span id="i_see_log_messages_for_shows_i_don_t_have_dont_want"><small>[[#i_see_log_messages_for_shows_i_don_t_have_dont_want|anchor]]</small></span><br>

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

== Seeding torrents aren’t deleted automatically ==
<span id="seeding_torrents_arent_deleted_automatically"><small>[[#seeding_torrents_arent_deleted_automatically|anchor]]</small></span><br>

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

== Why can’t I add a new series? ==
<span id="why_cant_i_add_a_new_series"><small>[[#why_cant_i_add_a_new_series|anchor]]</small></span><br>

* In the event that TheTVDB is unavailable Sonarr is unable to get search results and you will be unable to add any new series by searching. You may be able to add a new series by TheTVDB ID if you know what it is, the UI explains how to add it by an ID.

== Why can’t I add a new series when I know the TVDB ID? ==
<span id="why_cant_i_add_a_new_series_when_i_know_the_tvdb_id"><small>[[#why_cant_i_add_a_new_series_when_i_know_the_tvdb_id|anchor]]</small></span><br>

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

== Sonarr won't work on Big Sur ==
<span id="sonarr_wont_work_on_big_sur"><small>[[#sonarr_wont_work_on_big_sur|anchor]]</small></span><br>

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

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

System status

2020-11-29T16:40:50Z

TRaSH: /* Radarr */

System status

2020-11-29T16:36:37Z

TRaSH: /* Radarr */

Settings Custom Formats

2020-11-28T14:14:28Z

TRaSH: /* Import/Export */

'''Yes, I'm aware Sonarr does not have CFs but a man can dream cant he'''

== Custom Formats ==
<section begin=radarr_settings_custom_formats />
Custom formats have been reworked significantly in Radarr V3. They are now calculated on-the-fly instead of being stored in the database, so they update as soon as you change the definitions.
<section end=radarr_settings_custom_formats />

=== Conditions ===
==== Radarr ====
<section begin=radarr_settings_custom_formats_conditions />
All conditions have two possible modifiers:

* <code>Negate</code> - the match is inverted, so the condition is satisfied if and only if the non-negated condition is not satisfied
* <code>Required</code> - only applies to formats with more than one condition of the same type and changes the matching rules for type groups. Enabling this option means that this specific condition must be satisfied for the whole custom format to apply regardless of if another condition of the same type would otherwise satisfy the type group.

The conditions are:
* <code>Release Title</code> - This is a regular expression matched against the release title and, after download, the filename on disk
* <code>Edition</code> - This tag is matched against any Editions Radarr may parse. You can put any value Radarr will try to match that against what it parsed (case-insensitive).
* <code>Language</code> - This language is matched against any language(s) Radarr parses. All languages previously selectable in profiles work here.
* <code>Indexer Flag</code> - This tag is matched against any Indexer Flags Radarr may parse.
* <code>Source</code> - The source where a release was ripped from.
* <code>Resolution</code> - The resolution parsed from either the release name or media info (if available).
* <code>Quality Modifier</code> - Quality Modifier sets things like Telescene, Telesync, Remux, Regional. It just disambiguates a given source and resolution pair when there are multiple quality types that can apply
* <code>Size</code> - This is matched against the release size. The release size is converted to gigabytes and compared against the values min and max.
<section end=radarr_settings_custom_formats_conditions />

==== Sonarr ====

==== Lidarr ====

==== Readarr ====

=== Profiling Settings and Ranking ===
==== Radarr ====
<section begin=radarr_settings_custom_formats_profiling_settings_and_ranking />
The overhaul has scrapped the linear ranking system in favor of a scoring system assigning points to releases to allow more multi-dimensional preferences. The cutoff has been replaced by a stopping score where upgrading stops once a release with this desired score has been downloaded. The "None" format is replaced simply with a score of zero while the checkboxes controlling rejection or acceptance of matched releases is now controlled by the Minimum Custom Format Score. Custom formats that match with undesirable attributes should be given a negative score to lower their appeal. Outright rejections should be given a negative score low enough that even if all of the other formats with positive scores were added, the score would still fall below the minimum.
<section end=radarr_settings_custom_formats_profiling_settings_and_ranking />
==== Sonarr ====

==== Lidarr ====

==== Readarr ====

=== Import/Export ===
<section begin=radarr_settings_custom_formats_import_export />
Please see [https://trash-guides.info/Radarr/V3/How-to-importexport-Custom-Formats-and-truly-make-use-of-it/ TRaSH's Guides] for a guide. However, one is able to import and export custom formats.
<section end=radarr_settings_custom_formats_import_export />

=== Community Custom Formats ===
==== Radarr ====
<section begin=radarr_community_custom_formats />
* Please see our [[Radarr Tips and Tricks]] section
<section end=radarr_community_custom_formats />
==== Sonarr ====

==== Lidarr ====

==== Readarr ====

=== Templates ===

Radarr Tips and Tricks

2020-11-27T20:59:28Z

TRaSH: /* TRaSH's Custom Formats */

== TRaSH's Custom Formats ==
[https://trash-guides.info/Radarr/ TRaSH's Guides]

== Importing IMDb lists into TMDb ==

This is a guide for importing a list from IMDb into The Movie Database. This can be useful for large lists, due to IMDb’s RSS feeds not supporting the entire list.

# [https://www.imdb.com/registration/signin Log into your IMDb account].
# Open the list you would like to import into TMDb.
# Scroll to the bottom, just before the comments, and click the “Export this list” button, as shown below: [[File:Importing-IMDb-lists-into-TMDb1.png|Click the “Export this list” button]]
# [https://www.themoviedb.org/login Log into your TMDb account].
# [https://www.themoviedb.org/account/ Go to your account page on TMDb (by clicking your username)].
# Click the “Import List” button on the left side-bar as shown below:

[[File:Importing-IMDb-lists-into-TMDb2.png|Click the “Import List” button]]

<ol start="7" style="list-style-type: decimal;">
<li>Click “Select Files…” and navigate to the downloaded CSV file from IMDb:</li></ol>

[[File:Importing-IMDb-lists-into-TMDb3.png|thumb|none|alt=Click “Select Files…”|Click “Select Files…”]]

<ol start="8" style="list-style-type: decimal;">
<li><p>Choose the destination list as shown in the image above.</p></li>
<li><p>Click import, and wait to be notified of the import completion.</p></li></ol>

== Create a Folder for Each Movie ==

=== Windows & Linux ===

==== Filebot ====

[http://www.filebot.net/ Filebot] is a fantastic utility for getting your movies organized in a way that Radarr can successfully parse. Version 4.7.9’s [https://sourceforge.mirrorservice.org/f/project/fi/filebot/filebot/FileBot_4.7.9/FileBot_4.7.9_x64.msi 64 bit] and [https://sourceforge.mirrorservice.org/f/project/fi/filebot/filebot/FileBot_4.7.9/FileBot_4.7.9_x86.msi 32 bit] can still be downloaded free from a SourceForge [https://sourceforge.mirrorservice.org/f/project/fi/filebot/filebot/FileBot_4.7.9/ mirror], but there are also paid versions in the [https://www.microsoft.com/en-us/store/p/filebot/9nblggh52t9x?cid=filebot2 Windows] and [https://itunes.apple.com/us/app/filebot/id905384638?mt=12&uo=6&at=1l3vupy&ct=filebot2 Apple] stores. On Linux, your distribution of choice may have a package for it, like in [https://aur.archlinux.org/packages/filebot/ Arch’s AUR package] or <code>.deb</code> files for Debian/Ubuntu from their [http://www.filebot.net/#download download page]. It has both a GUI and a CLI, so should satisfy almost everyone.

There is great help available, including their [http://www.filebot.net/naming.html format expressions] page. My personal suggestion is to use something like <code>{ny}\{fn}</code> ''if'' your files include useful details like quality, edition and/or group ''or'' <code>{ny}/{ny} [{dim[0] >= 1280 ? 'Bluray' : 'DVD'}-{vf}]</code> if they don’t, which would yield <code>Movie (Year)/Movie (Year) [Bluray-1080p]</code> or <code>Movie (Year)/Movie (Year) [DVD-480p]</code> for example. Instead of <code>Bluray</code>, you could also use <code>WEBDL</code> if you’d rather your collection be considered that.

To keep this pattern for future movies, you should set:

Settings -> Media Management (Advanced Settings Shown) -> Movie Naming * File: <code>{Movie CleanTitle} {(Release Year)} {Edition Tags} {[Quality Title]}</code> * Folder: <code>{Movie CleanTitle} {(Release Year)}</code>

Note: You can replace the spaces above with <code>.</code> or <code>_</code> if you prefer that naming format.

=== Windows ===

==== Files 2 Folder ====

I used a program called [http://www.dcmembers.com/skwire/download/files-2-folder/ Files 2 Folder] to make my movie library visible for import into Radarr, extract the zip to your computer and run the .exe as administrator, then click yes to add it to your right click menu.

# Browse to your movie folder
# Select all files and right click to bring up the menu
# Press the files 2 folder option in the menu [[File:Create-a-Folder-for-Each-Movie1.jpg]]
# Wait for the box to appear, ONLY CLICK THE SECOND OPTION [[File:Create-a-Folder-for-Each-Movie2.png]]
# Each movie will be in its’ own folder. [[File:Create-a-Folder-for-Each-Movie3.jpg]]

=== Linux ===

<pre>cd /path/to/your/movies/files/
find . -maxdepth 1 -type f -iname "*.mkv" -exec sh -c 'mkdir "${1%.*}" ; mv "${1%}" "${1%.*}" ' _ {} \;</pre>
==== Windows & Linux ====

This script will place movies and TV episodes on folders<br />
Files are not modifed or renamed only moved to folders.

Usage:: ./movie&TV2folder.py /path/movies/ (Movie 1 (year) , Movie)<br />
Usage:: ./movie&TV2folder.py /path/tv/ ( tv folders: Tile 1, Title 2 )<br />
Type of files:

Movies: (scans 1 folder deep - i.e. not recursive)<br />
All files bellow would be moved to folder: ./Movie Title (2017)<br />
Movie Title (2017) 1080p.mkv<br />
Movie Title (2017) anything else.*<br />
Movie Title (2017).*<br />
Movie Title.mkv –> '''would not be moved, since missing (year)'''

Series: (scans 2 folders deep)<br />
All files bellow would be moved to folder: ./Season 04/<br />
Farscape - S04E01.mkv<br />
Farscape - S04E01-E02.mkv<br />
Farscape - S04E01<br />
S04E01 - Farscape - group.mkv<br />
Daily Show S2014E20 - would be moved to ./Season 2014/

Additional rules:<br />
On OS error: retry operation 3 times with 1 second delay between attempts.<br />
If move fails it continue with other files.

https://github.com/ajkis/scripts/blob/master/other/movie-tv2folder.py

== Custom Post Processing Scripts ==
If you’re looking to trigger a custom script in your download client to tell Radarr when to update, you can find more details here. Scripts are added to Radarr via the [[Radarr Settings#Connections|Connect Settings]] page.

=== Overview ===

Radarr can execute a custom script when new movies are imported or a movie is renamed and depending on which action occurred, the parameters will be different. They are passed to the script through environment variables which allows for more flexibility in what is sent to the script and in no particular order.

=== Environment Variables ===

===== On Grab =====

{| class="wikitable"
!width="50%"| Environment Variable
!width="50%"| Details
|-
| radarr_eventtype
| Grab
|-
| radarr_download_client
| NZB/Torrent downloader client
|-
| radarr_download_id
| The hash of the torrent/NZB file downloaded (used to uniquely identify the download in the download client)
|-
| radarr_movie_id
| Internal ID of the movie
|-
| radarr_movie_imdbid
| IMDb ID for the movie
|-
| radarr_movie_in_cinemas_date
| Cinema release date
|-
| radarr_movie_physical_release_date
| Physical release date
|-
| radarr_movie_title
| Title of the movie
|-
| radarr_movie_tmdbid
| TMDb ID for the movie
|-
| radarr_movie_year
| Release year of the movie
|-
| radarr_release_indexer
| Indexer where the release was grabbed
|-
| radarr_release_quality
| Quality name from Radarr
|-
| radarr_release_qualityversion
| 1 is the default, 2 for proper, 3+ could be used for anime versions
|-
| radarr_release_releasegroup
| Release Group, will not be set if it is unknown
|-
| radarr_release_size
| Size of the release reported by the indexer
|-
| radarr_release_title
| NZB/Torrent title
|}

===== On Download/On Upgrade =====

{| class="wikitable"
!width="50%"| Environment Variable
!width="50%"| Details
|-
| radarr_eventtype
| Download
|-
| radarr_download_id
| The hash of the torrent/NZB file downloaded (used to uniquely identify the download in the download client)
|-
| radarr_isupgrade
| <code>True</code> when an existing file is upgraded, otherwise <code>False</code>
|-
| radarr_movie_id
| Internal ID of the movie
|-
| radarr_movie_imdbid
| IMDb ID for the movie
|-
| radarr_movie_in_cinemas_date
| Cinema release date
|-
| radarr_movie_physical_release_date
| Physical release date
|-
| radarr_movie_path
| Full path to the movie ( /Movie (Year)/ )
|-
| radarr_movie_title
| Title of the movie
|-
| radarr_movie_tmdbid
| TMDb ID for the movie
|-
| radarr_movie_year
| Release year of the movie
|-
| radarr_moviefile_id
| Internal ID of the movie file
|-
| radarr_moviefile_relativepath
| Path to the movie file relative to the movie’ path
|-
| radarr_moviefile_path
| Full path to the movie file ( /Movie (Year)/Movie (Year).mkv )
|-
| radarr_moviefile_quality
| Quality name from Radarr
|-
| radarr_moviefile_qualityversion
| 1 is the default, 2 for proper, 3+ could be used for anime versions
|-
| radarr_moviefile_releasegroup
| Release group, will not be set if it is unknown
|-
| radarr_moviefile_scenename
| Original release name
|-
| radarr_moviefile_sourcepath
| Full path to the movie file that was imported
|-
| radarr_moviefile_sourcefolder
| Full path to the folder the movie file was imported from
|}

===== On Rename =====

{| class="wikitable"
! Environment Variable
! Details
|-
| radarr_eventtype
| Rename
|-
| radarr_movie_id
| Internal ID of the movie
|-
| radarr_movie_imdbid
| IMDb ID for the movie
|-
| radarr_movie_in_cinemas_date
| Cinema release date
|-
| radarr_movie_path
| Full path to the movie
|-
| radarr_movie_physical_release_date
| Physical release date
|-
| radarr_movie_title
| Title of the movie
|-
| radarr_movie_tmdbid
| TMDb ID for the movie
|-
| radarr_movie_year
| Release year of the movie
|}

=== Specific usage tips ===

==== LINUX / UNIX Scripts ====

Remember to always add a [https://en.wikipedia.org/wiki/Shebang_(Unix) shebang] and make your scripts executable with [https://en.wikipedia.org/wiki/Chmod chmod].

Sample bash script to echo environmental variables

<pre>#!/bin/bash
RADARRENVLOG="/pathtoalog.log"

if [[ $radarr_eventtype == "Grab" ]] ; then
echo "
radarr_download_client = $radarr_download_client // NZB/Torrent downloader client
radarr_download_id = $radarr_download_id // The hash of the torrent/NZB file downloaded (used to uniquely identify the download in the download client)
radarr_movie_id = $radarr_movie_id // Internal ID of the movie
radarr_movie_imdbid = $radarr_movie_imdbid // IMDb ID for the movie
radarr_movie_in_cinemas_date = $radarr_movie_in_cinemas_date // Cinema release date
radarr_movie_physical_release_date = $radarr_movie_physical_release_date // Physical release date
radarr_movie_title = $radarr_movie_title // Title of the movie
radarr_movie_tmdbid = $radarr_movie_tmdbid // TMDb ID for the movie
radarr_movie_year = $radarr_movie_year // Release year of the movie
radarr_release_indexer = $radarr_release_indexer // Indexer where the release was grabbed
radarr_release_quality = $radarr_release_quality // Quality name from Radarr
radarr_release_qualityversion = $radarr_release_qualityversion // 1 is the default, 2 for proper, 3+ could be used for anime versions
radarr_release_releasegroup = $radarr_release_releasegroup // Release Group, will not be set if it is unknown
radarr_release_size = $radarr_release_size // Size of the release reported by the indexer
radarr_release_title = $radarr_release_title // NZB/Torrent title" >> $RADARRENVLOG
fi
if [[ $radarr_eventtype == "Download" ]] ; then
echo "
radarr_download_id = $radarr_download_id // The hash of the torrent/NZB file downloaded (used to uniquely identify the download in the download client)
radarr_isupgrade = $radarr_isupgrade // `True` when an existing file is upgraded, otherwise `False`
radarr_movie_id = $radarr_movie_id // Internal ID of the movie
radarr_movie_imdbid = $radarr_movie_imdbid // IMDb ID for the movie
radarr_movie_in_cinemas_date = $radarr_movie_in_cinemas_date // Cinema release date
radarr_movie_physical_release_date = $radarr_movie_physical_release_date // Physical release date
radarr_movie_path = $radarr_movie_path // Full path to the movie ( /Movie (Year)/ )
radarr_movie_title = $radarr_movie_title // Title of the movie
radarr_movie_tmdbid = $radarr_movie_tmdbid // TMDb ID for the movie
radarr_movie_year = $radarr_movie_year // Release year of the movie
radarr_moviefile_id = $radarr_moviefile_id // Internal ID of the movie file
radarr_moviefile_relativepath = $radarr_moviefile_relativepath // Path to the movie file relative to the movie' path
radarr_moviefile_path = $radarr_moviefile_path // Full path to the movie file ( /Movie (Year)/Movie (Year).mkv )
radarr_moviefile_quality = $radarr_moviefile_quality // Quality name from Radarr
radarr_moviefile_qualityversion = $radarr_moviefile_qualityversion // 1 is the default, 2 for proper, 3+ could be used for anime versions
radarr_moviefile_releasegroup = $radarr_moviefile_releasegroup // Release group, will not be set if it is unknown
radarr_moviefile_scenename = $radarr_moviefile_scenename // Original release name
radarr_moviefile_sourcepath = $radarr_moviefile_sourcepath // Full path to the movie file that was imported
radarr_moviefile_sourcefolder = $radarr_moviefile_sourcefolder // Full path to the folder the movie file was imported from" >> $RADARRENVLOG
fi
if [[ $radarr_eventtype == "Rename" ]] ; then
echo "
radarr_movie_id = $radarr_movie_id // Internal ID of the movie
radarr_movie_imdbid = $radarr_movie_imdbid // IMDb ID for the movie
radarr_movie_in_cinemas_date = $radarr_movie_in_cinemas_date // Cinema release date
radarr_movie_path = $radarr_movie_path // Full path to the movie
radarr_movie_physical_release_date = $radarr_movie_physical_release_date // Physical release date
radarr_movie_title = $radarr_movie_title // Title of the movie
radarr_movie_tmdbid = $radarr_movie_tmdbid // TMDb ID for the movie
radarr_movie_year = $radarr_movie_year // Release year of the movie" >> $RADARRENVLOG
fi</pre>
==== PHP ====

The information from Radarr will not be added to <math display="inline">_ENV as one might expect but should be included in the [</math>_SERVER variable](https://secure.php.net/manual/en/reserved.variables.server.php). A sample script to use this information to convert a file can be found [https://gist.github.com/karbowiak/7fb38d346e368edc9d1a here]. #### PowerShell #### Sample script using the Radarr environment variables to create EDL files for all episodes is [https://gist.github.com/RedsGT/e1b5f28e7b5b81e1e45378151e73ba5c here].

Sample script to have Plex scan destination folder only and “analyze deeply” the file. PSQLite needed to query the plex DB. Adjust folder locations to match your setup.

<pre lang="powershell"># This script will add the movie to plex and scan the destination folder (it will not scan the entire library)
# C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe\PowerShell.exe -ExecutionPolicy Bypass "C:\Users\Server\Desktop\radarrcustom.ps1"

$movie_path = $env:radarr_movie_path
#PSQlite location
Import-Module C:\Users\Server\Desktop\scripts\PSSQLite
#set file locations
$logfile = "C:\Users\Server\Desktop\radarrimport.txt"
$database = "C:\Users\Server\AppData\Local\Plex Media Server\Plug-in Support\Databases\com.plexapp.plugins.library.db"
$plexscanner = "C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Scanner.exe"
#set your plex library ID
$libraryid = 0
#If you have multiple root folders and library IDs you can set them like so
#If ($movie_path -like '*Movies Release\*' ) { $libraryid = 19 }

#Scan the movie folder
& "$plexscanner" --scan --refresh --section $libraryid --directory $movie_path
write-output """$plexscanner"" --scan --refresh --section $libraryid --directory $movie_path" | add-content $logfile

sleep 20

#Query the plex db for the item ID
$likemoviepath = $movie_path + "%"
$query = "SELECT mi.metadata_item_id FROM media_parts mp LEFT JOIN media_items mi on mp.media_item_id=mi.id WHERE mp.file LIKE '$likemoviepath'"
$itemid = Invoke-SqliteQuery -Query $query -DataSource $database
$itemid = $itemid.metadata_item_id

#Analyze the ItemID
& "$plexscanner" --analyze --item $itemid
write-output """$plexscanner"" --analyze --item $itemid" | add-content $logfile

sleep 20

#Analyze deeply the item ID
& "$plexscanner" --analyze-deeply --item $itemid
write-output """$plexscanner"" --analyze-deeply --item $itemid" | add-content $logfile</pre>
==== Reverse Symlinking ====

When using private trackers, it is imperative to continue seeding. By using this script <code>on Download</code> and <code>on Upgrade</code> moves the media to your root movie folder as set in Radarr, and will create a symlink in the original download location so you can continue to seed.

Symlinking is preferable over hardlinking in most cases as the root movie folder can be on a seperate drive or nfs mount, where hardlinks are impossible.

<pre lang="sh">#!/bin/bash

PERMPATH="$radarr_moviefile_path"
LINKPATH="$radarr_moviefile_sourcepath"

if [[ -f "$LINKPATH" ]]; then
sleep 1
else
exit 1
fi

ORIGFILESIZE=$(stat -c%s "$LINKPATH")
PERMFILESIZE=$(stat -c%s "$PERMPATH")

sleep 30

while [[ $PERMFILESIZE != $ORIGFILESIZE ]]; do
sleep 60
PERMFILESIZE=$(stat -c%s "$PERMPATH")
done

if [[ $PERMFILESIZE == $ORIGFILESIZE ]]; then
# Save current time stamps to prevent radarr from identifying our simlink as new, and double-processing it
LINKDIR=$(dirname "$LINKPATH")
FOLDER_DATE=$(date -r "$LINKDIR" +@%s.%N)
FILE_DATE=$(date -r "$LINKPATH" +@%s.%N)

rm "$LINKPATH"
ln -s "$PERMPATH" "$LINKPATH"

touch --no-create --no-dereference --date "$FILE_DATE" "$LINKPATH"
touch --no-create --no-dereference --date "$FILE_DATE" "$PERMPATH"
touch --no-create --no-dereference --date "$FOLDER_DATE" "$LINKDIR"
fi</pre>
A quick way to test scripts is to create a testing environment using the movie “Test (2013)”.

<pre>mkdir -p ~/test && cd ~/test && touch "Test (2013).nfo" "Test (2013).por.srt" "Test (2013).por.forced.srt" "Test (2013).eng.srt" "Test (2013).mkv" && cp -R ~/test /path/to/folder/to/import</pre>
or in bash:

<pre>mkdir -p ~/test && cd ~/test && touch "Test (2013)."{nfo,por.srt,por.forced.srt,eng.srt,mkv} && cp -R ~/test /path/to/folder/to/import</pre>
This way you can manually import this movie and trigger the script. You can just run it again to repopulate the files.

== Installing multple Radarrs on Windows ==

This guide will show you how to run multiple instances of Radarr on Windows using only one base installation. This guide was put together using Windows 10; if you are using a previous version of Windows (7, 8, etc.) you may need to adjust some things. This guide also assumes that you have installed Radarr to the default directory, and your second instance of Radarr will be called Radarr-4K. Feel free to change things to fit your own installations, though.

=== Prerequisites ===

* You must have Radarr already installed. It is ''highly'' recommended that you use [https://github.com/Radarr/Radarr/releases the latest installer.exe file].
* You must have [http://nssm.cc NSSM (Non-Sucking Service Manager)] installed. To install, download the latest release (2.24 at the time of writing) and copy either the 32-bit or 64-bit nssm.exe file to C:/windows/system32. (If you aren’t sure if you have a 32-bit or 64-bit system, check Settings > System > About > System type.)

=== Configuring Radarr ===

<ol style="list-style-type: decimal;">
<li><p>Open a Command Prompt administrator window. (To run as an admin, right click on the Command Prompt icon and choose “Run as administrator.”)</p></li>
<li><p>If Radarr is running, stop the service by running <code>nssm stop Radarr</code> in Command Prompt.</p></li>
<li><p>Now we have to edit the existing Radarr instance to explicitly point to its data directory. The default command is as follows:</p>
<p><code>sc config Radarr binpath= "C:\ProgramData\Radarr\bin\Radarr.exe -data=C:\ProgramData\Radarr"</code></p></li></ol>

This command tells the original instance of Radarr to explicitly use C:for its data directory. If you didn’t use the default Radarr install, or if your data folder is somewhere else, you may have to change your paths here.

=== Creating Radarr-4K ===

<ol start="4" style="list-style-type: decimal;">
<li>Create a new folder where you’d like Radarr-4K to live. I prefer all my instances in the same place, so my new folder is C:-4K.</li>
<li>Back in Command Prompt, create the new Radarr-4K service using <code>nssm install Radarr-4K</code>. A popup window will open where you can type your parameters for the new instance. For this example, we will use the following:
<ul>
<li>'''Path:''' C:.exe</li>
<li>'''Startup directory:''' C:</li>
<li>'''Arguments:''' -data=C:-4K</li></ul>
</li></ol>

Note that '''Arguments''' points to the ''new'' folder created in step 4. This is crucial, as it keeps all the data files from both instances in separate locations.

<ol start="6" style="list-style-type: decimal;">
<li>Click ''Install service''. The window should close and the service will now be available to run.</li></ol>

=== Configuring Radarr-4K ===

<ol start="7" style="list-style-type: decimal;">
<li><p>Next we’ll need to configure the new service to use its own port, the entry for which is in a config.xml file. This file is created when you first run the service, so start up Radarr-4K with <code>nssm start Radarr-4K</code> in Command Prompt.</p></li>
<li><p>Navigate to your new data directory (C:-4K in this case) to see if the config.xml file is there. If it is, go ahead and stop Radarr-4K with <code>nssm stop Radarr-4K</code>. (Don’t worry, we’ll be starting it back up in a second.)</p></li>
<li><p>Open the config.xml file using your preferred text editor. There should only be a handful of lines, but the important one is <code><Port>7878</Port></code>.</p></li></ol>

Since the first Radarr instance will occupy port 7878, the second instance must use another available port, like 7879 or 17878. I prefer the latter, so I changed the line to <code><Port>17878</Port></code>. Don’t change anything else.

<ol start="9" style="list-style-type: decimal;">
<li>After you’ve set a new port, save the file and close your text editor.</li>
<li>With both services fully installed and properly configured, you can now start them:
<ul>
<li><code>nssm start Radarr</code> (accessible via http://ip_address:7878)</li>
<li><code>nssm start Radarr-4K</code> (accessible via http://ip_address:17878)</li></ul>
</li></ol>

==== Notes ====

* Though this tutorial was tested using Command Prompt, it should work with Windows Terminal as well. But, if you’re feeling cautious, just go with Command Prompt.
* A previous version of this installation guide encouraged users to copy Radarr’s config.xml file to Radarr-4K’s data directory. However, you’ll run into trouble with this method, especially if you have authentication enabled. I’d recommend starting with a clean config.xml file, created when you start the service for the first time (Step 7).
* If one Radarr instance is updated, both instances will shutdown and only the updated one will start again. To fix this, you will have to manually start the other instance, or you may want to look into using the below powershell script to address the problem until an official solution is found.

=== Port Checker and Restarter PowerShell Script ===

When you use two Radarr instances and one of it is updating, it will kill both instances ( by killing all running radarr.console.exe ). Only the one which is updating will come back online.

To keep both online i made a powershell script which i run as a scheduled task.

It checks the ports and if one is not online, it will (re-)start the scheduled task to launch radarr.

Create a new File and name it <code>RadarrInstancesChecker.ps1</code> with the below code.

Create a scheduled task which triggers on launch and set it to repeat every 5 or 10mins. - Trigger: - On launch - Repeat every 5 or 10 mins - Action: - Launch Application/Programm - Enter <code>powershell</code> as programm - Add your script as argument: <code>-File D:\RadarrInstancesChecker.ps1</code>

Adjust ur pathes, ip, ports and scheduled task names.

RadarrInstancesChecker.ps1

<pre>################################################################################################
### RadarrInstancesChecker.ps1 ###
################################################################################################
### Keeps multiple Radarr Instances up by checking the port ###
### Please use Radarr´s Discord or Reddit for support! ###
### https://github.com/Radarr/Radarr/wiki/Installing-Multiple-Instances-of-Radarr-on-Windows ###
################################################################################################
### Version: 1.1 ###
### Updated: 2020-10-22 ###
### Author: reloxx13 ###
################################################################################################

### SET YOUR CONFIGURATION HERE ###
# Set your host ip and port correctly and use your service or scheduledtask names!

# (string) The type how Radarr is starting
# "Service" (default) Service process is used
# "ScheduledTask" Task Scheduler is used
$startType = "Service"

# (bool) Writes the log to C:\Users\YOURUSERNAME\log.txt when enabled
# $false (default)
# $true
$logToFile = $false

$instances = @(
[pscustomobject]@{ # Instance 1
Name='Radarr-V3'; # (string) Service or Task name (default: Radarr-V3)
IP='192.168.178.12'; # (string) Server IP where Radarr runs (default: 192.168.178.12)
Port='7873'; # (string) Server Port where Radarr runs (default: 7873)
}
[pscustomobject]@{ # Instance 2
Name='Radarr-4K'; # (string) Service or Task name (default: Radarr-V3)
IP='192.168.178.12'; # (string) Server IP where Radarr runs (default: 192.168.178.12)
Port='7874'; # (string) Server Port where Radarr runs (default: 7874)
}
# If needed you can add more instances here...
# [pscustomobject]@{ # Instance 3
# Name='Radarr-3D'; # (string) Service or Task name (default: Radarr-3D)
# IP='192.168.178.12'; # (string) Server IP where Radarr runs (default: 192.168.178.12)
# Port='7875'; # (string) Server Port where Radarr runs (default: 7875)
# }
)

### DONT CHANGE ANYTHING BELOW THIS LINE ###

###
# This function will write to a log file or in console output
###
function Write-Log {
#Will write to C:\Users\YOURUSERNAME\log.txt

Param(
$Message,
$Path = "$env:USERPROFILE\log.txt"
)

function TS {Get-Date -Format 'hh:mm:ss'}

#Console output
Write-Output "[$(TS)]$Message"

#File Output
if($logToFile){
"[$(TS)]$Message" | Tee-Object -FilePath $Path -Append | Write-Verbose
}
}

Write-Log "START ====================="

$instances | ForEach-Object {
Write-Log "Check $($_.Name) $($_.IP):$($_.Port)"

$PortOpen = ( Test-NetConnection $_.IP -Port $_.Port -WarningAction SilentlyContinue ).TcpTestSucceeded

if (!$PortOpen) {
Write-Log "Port $($_.Port) is closed, restart $($startType) $($_.Name)!"

if($startType -eq "Service"){
Get-Service -Name $_.Name | Stop-Service
Get-Service -Name $_.Name | Start-Service
}
elseif($startType -eq "ScheduledTask"){
Get-ScheduledTask -TaskName $_.Name | Stop-ScheduledTask
Get-ScheduledTask -TaskName $_.Name | Start-ScheduledTask
}
else{
Write-Log "[ERROR] STARTTYPE UNKNOWN! USE Service or ScheduledTask !"
}
}else{
Write-Log "Port $($_.Port) is open!"
}
}

Write-Log "END ====================="</pre>

Definitions

2020-11-26T17:13:27Z

TRaSH: /* Video Qualities */

=== Download Protocols ===
* <code>Usenet</code> - (USEr NETwork) A public access network on the Internet that provides group discussions and group email. It is a giant, dispersed bulletin board that is maintained by volunteers who provide news and mail feeds to other nodes. All Usenet content is "NetNews," and a running collection of messages about a subject is a "newsgroup."
:'''Note:''' This is typically a paid service with a direct connection to the servers containing the data you're wishing to acquire. The connections can be quite fast and typically can saturate any home download connection. <br> For more information about Usenet and discussions about them we'd recommend you look at [https://www.reddit.com/r/usenet/ r/usenet]

* <code>Torrents</code> - In the BitTorrent file distribution system, a torrent file or meta-info file is a computer file that contains metadata about files and folders to be distributed, and usually also a list of the network locations of trackers, which are computers that help participants in the system find each other and form efficient distribution groups called swarms. A torrent file acts like a table of contents (index) that allows computers to find information through the use of a Bittorrent client. A torrent file gives addresses identifying computers that can send parts of the requested file.
:'''Note:''' Torrents in of them selves are completely innocuous and is simply a file sharing system. To share a file between two people is free. However, the service for finding the files (Trackers) and the computers that are hosting them can lead to a cost however there are may Trackers that are completely free to use. Torrent speeds are limited to the amount of seeders in a swarm. <br> For more information about Torrents and discussions about them we'd recommend you look at [https://www.reddit.com/r/torrents/ r/torrents]

=== Indexers/Trackers ===
==== Usenet ====
* <code>Indexers</code> - Usenet indexing sites allow you to search Usenet for specific posts. Some display the newsgroup and full subjects of each post matching the search criteria. Others allow you to download an NZB file which contains information about each post that your download client can use to automatically download the files. Indexes typically have a fee (usually to help cover server costs)that is typically paid yearly (some have an unlimited membership). <br> For more information about Indexers and discussions about them we'd recommend you look at [https://reddit.com/r/indexers r/indexers]

==== Torrents ====
* <code>Trackers</code> - Torrent trackers are servers that keep track of the peers who are available at the moment to offer you the requested files. These are a special type of servers that help in better communication between torrent clients and peers to speed up downloads.
** <code>Seeders</code> - Seeders are people who have a complete copy of the file. Seeders are only uploading because they already have the file finished, so there's no reason to download it.
** <code>Leechers</code> - Leechers are people with an incomplete copy of the file. Due to the nature of torrents, you are always sharing the part of the file that you have downloaded. So you are always uploading to others while you download the file yourself.
** <code>Ratio</code> - The ratio of what you have uploaded versus downloaded. Calculated as uploaded quantity / downloaded quantity.

=== Seedboxes ===

=== Common File Containers ===
*<code>MKV</code> - An MKV file is a video file saved in the Matroska multimedia container format. It supports several types of audio and video codecs and may include .SRT, .SSA, .USF (Universal Subtitle Format), or VobSub subtitles. MKV files are typically used for storing short video clips, TV shows, and movies.

*<code>MP4</code> - An MP4 file is a multimedia file commonly used to store a movie or video clip. It may also contain subtitles or images. MP4 is short for MPEG-4 Part 14, which is a container format based on the QuickTime File Format (QTFF) used by .MOV and .QT files

*<code>MP3</code> - An MP3 file is an audio file saved in a compressed audio format developed by the Moving Picture Experts Group (MPEG) that uses "Layer 3" audio compression (MP3). It is most commonly used to store music, but may also contain other types of audio content, such as a lecture, sermon, audiobook, or podcast.

*<code>AAC</code> - Compressed audio file similar to an .MP3 file, but offers several performance improvements; examples include a higher coding efficiency for both stationary and transient signals, a simpler filterbank, and better handling of frequencies above 16 kHz; maintains quality nearly indistinguishable from the original audio source.

*<code>OGG</code> - An OGG file is a compressed audio file that uses free, unpatented Ogg Vorbis audio compression. It is similar to an .MP3 file, but sounds better than an MP3 file of equal size, and may include song metadata, such as artist information and track data. OGG files are supported by many software music players and some portable music players.

*<code>FLAC</code> - A FLAC file is an audio file compressed in the Free Lossless Audio Codec (FLAC) format, which is an open source lossless audio compression format. It is similar to an .MP3 file, but is compressed without any loss in quality or loss of any original audio data.

For a list of different video containers and its capabilities click [https://en.wikipedia.org/wiki/Comparison_of_video_container_formats#Video_coding_formats_support HERE]

For a list of different audio containers and its capabilities click
[https://en.wikipedia.org/wiki/Comparison_of_video_container_formats#Audio_coding_formats_support HERE]

=== Bitrates ===
<section begin=bitrates />
Bitrate, as the name implies, describes the rate at which bits are transferred from one location to another. In other words, it measures how much data is transmitted in a given amount of time. Bitrate is commonly measured in bits per second (bps), kilobits per second (Kbps), or megabits per second (Mbps). For example, a DSL connection may be able to download data at 768 kbps, while a Firewire 800 connection can transfer data up to 800 Mbps.

Bitrate can also describe the quality of an audio or video file. For example, an MP3 audio file that is compressed at 192 Kbps will have a greater dynamic range and may sound slightly more clear than the same audio file compressed at 128 Kbps. This is because more bits are used to represent the audio data for each second of playback. Similarly, a video file that is compressed at 3000 Kbps will look better than the same file compressed at 1000 Kbps. Just like the quality of an image is measured in resolution, the quality of an audio or video file is measured by the bitrate.
<section end=bitrates />

=== Scene Naming ===
<section begin=scene naming />
* <code>PROPER</code> - means there was a problem with the previous release. Downloads tagged as PROPER shows that the problems have been fixed in that release. This is done by a Group that did not release the original.
* <code>REPACK</code> - means there was a problem with the previous release and is corrected by the original Group. Downloads tagged as REPACK shows that the problems have been fixed in that release. This is done by a Group that did release the original.
<section end=scene naming />

=== Qualities ===
==== Video Qualities ====
<section begin=video-qualities />

<section begin=Unknown />*<code>Unknown</code> - Self Explanatory<section end=Unknown />

*<code>WORKPRINT</code> - A workprint of a film generally contains timecode and usually has watermarks from the studio involved in the production of the film. These "proxy" copies of a film often go between the editorial and visual effects departments of the film crew. A workprint may be of any resolution, but are generally lower quality versions of the film used to show progress on the editorial or post-production process. Therefore, these may not be at all the same as a theatrical version of the film, and may be missing many of the visual effects or audio that end up making it to the theatrical release.

*<code>CAM</code> - is a theater rip usually done with a digital video camera. A mini tripod is sometimes used, but a lot of the time this won't be feasible, so the camera may shake. Seating placement isn't always ideal, and it might be filmed from an awkward angle. If cropped properly, this is hard to tell unless there's text on the screen, but a lot of times these are left with triangular borders on the top and bottom of the screen. Sound is taken from the onboard microphone of the camera, and especially in comedies, laughter can often be heard during the film. Due to these factors picture and sound quality are usually quite poor, but sometimes we're lucky, and the theater will be fairly empty and a fairly clear signal will be heard.

*<code>TELESYNC</code> - is the same spec as a CAM except it uses an external audio source (most likely an audio jack in the chair for the disabled). A direct audio source does not guarantee good quality audio, as a lot of background noise can interfere. Sometimes a telesync is filmed in an empty cinema or from the projection booth with a professional camera, giving better picture quality. Quality ranges drastically. A high percentage of telesyncs are CAMs that have been mislabeled.

*<code>TELECINE</code> - A telecine machine copies the film digitally from the reels. Sound and picture should be very good, but due to the equipment and cost involved telecines are fairly uncommon. Generally, the film will be in correct aspect ratio, although 4:3 telecines have existed. TC should not be confused with TimeCode, which is a visible counter on screen throughout the film.

*<section begin=REGIONAL /><code>REGIONAL</code> - <--------------------- Needs definition<section end=REGIONAL />

*<code>DVDSCR</code> - A pre-release DVD often sent to awards judges and various other places for promotional use. A screener is supplied on a DVD or other large enough media. The main draw back is a “ticker” (a message that scrolls past at the bottom of the screen, with the copyright and anti-copy telephone number). Also, if the screener contains any serial numbers, or any other markings that could lead to the source of the tape, these will have to be blocked, usually with a black mark over the section. This is sometimes only for a few seconds, but unfortunately on some copies this will last for the entire film, and some can be quite big. Depending on the equipment used, screener quality can range from excellent to very poor. Usually transferred to SVCD, DivX/XviD, or MP4.

<section begin=SDTV />*<code>SDTV</code> - Post air rips from an analog source (usually cable television or OTA standard definition). The image quality is generally good (for the resolution) and they are usually encoded in DivX/XviD or MP4.<section end=SDTV />

<section begin=DVD />*<code>DVD</code> - A re-encode of the final released DVD9. If possible this is released PRE retail. It should be excellent quality (for the resolution). DVDrips are usually released in DivX/XviD or MP4.<section end=DVD />

*<code>DVD-R</code> - Same as DVD, but re-compressed to fit a single-layer DVD (generally reduces the original source bitrate by half, so the source material may have already been compressed from the original DVD copy and has been compressed a third time by the ripper).

<section begin=WEBDL-480p />*<code>WEBDL-480p</code> - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 480p (SD) quality. <section end=WEBDL-480p />

<section begin=WEBRip-480p />*<code>WEBRip-480p</code> - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 480p (SD) quality.<section end=WEBRip-480p />

<section begin=Bluray-480p />*<code>Bluray-480p</code> - A re-encode of the final released Blu-ray, downscaled to 480p resolution (720x480 @ 16:9, any other Aspect Ratio may be a different resolution). If possible this is released PRE retail. It should be excellent quality for the resolution. Bitrates may vary, but these are generally encoded to DivX, XviD, or AVC and offer the tradeoff of a small perceived quality reduction over the original source while drastically reducing filesize. These are generally MKV or MP4, but some DivX/XviD are around as well which use AVI.<section end=Bluray-480p />

*<code>Bluray-576p</code> - Same as Bluray-480p, but in 576p (720x576). 576p is the standard PAL resolution for SDTV (although some manufacturers represent HDTV as anything above 480p, 576p offers barely any perceived quality increase over 480p). Bitrates may vary, but these are generally encoded to AVC or HEVC and offer the tradeoff of a small perceived quality reduction over the original source while drastically reducing filesize. These are generally MKV or MP4 container.

<section begin=HDTV-720p />*<code>HDTV-720p</code> - A re-encode of the final released Blu-ray, but broadcast over HD cable or satellite (1280x720 @ 16:9, any other aspect ratio may be a different resolution). It may be modified for runtime or content depending on the network it came from. This is released usually several months after a retail release, but sometimes upscaled versions of a Standard Definition film are released on cable channels such as STARZ or HBO, and they would be the only HD copies of that specific film available. These are generally MKV or MP4.<section end=HDTV-720p />

*<code>WEBDL-720p</code> - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 720p quality.

<section begin=WEBRip-720p />*<code>WEBRip-720p</code> - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 720p quality.<section end=WEBRip-720p />

<section begin=Bluray-720p />*<code>Bluray-720p</code> - A re-encode of the final released Blu-ray, downscaled to 720p resolution (1280x720 @ 16:9, any other aspect ratio may be a different resolution). If possible this is released PRE retail. It should be excellent quality for the resolution. Bitrates may vary, but these are generally encoded to AVC or HEVC and offer the tradeoff of a small perceived quality reduction over the original source while drastically reducing filesize. These are generally MKV or MP4 container.<section end=Bluray-720p />

<section begin=HDTV-1080p />*<code>HDTV-1080p</code> - A re-encode of the final released Blu-ray, but broadcast over HD cable or satellite (1920x1080 @ 16:9, any other aspect ratio may be a different resolution). It may be modified for runtime or content depending on the network it came from. This is released usually several months after a retail release, but sometimes upscaled versions of a Standard Definition film are released on cable channels such as STARZ or HBO, and they would be the only HD copies of that specific film available. These are generally MKV or MP4 container.<section end=HDTV-1080p />

<section begin=WEBDL-1080p />*<code>WEBDL-1080p</code> - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 1080p quality.<section end=WEBDL-1080p />

<section begin=WEBRip-1080p />*<code>WEBRip-1080p</code> - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 1080p quality.<section end=WEBRip-1080p />

<section begin=Bluray-1080p />*<code>Bluray-1080p</code> - A re-encode of the final released Blu-ray, at its native 1080p resolution (1920x1080 @ 16:9, any other aspect ratio may be a different resolution). If possible this is released PRE retail. It should be excellent quality and the same resolution as the source. Bitrates may vary, but these are generally encoded to AVC or HEVC and offer the tradeoff of a small perceived quality reduction over the original source while slightly reducing filesize. These are generally MKV or MP4 container.<section end=Bluray-1080p />

<section begin=1080p Remux />*<code>Remux-1080p</code> - A remux is a rip of a Blu-ray or HD DVD disc to another container format or just stripping the disc of menus and bonus material while keeping the contents of its audio and video streams intact (also keeping the current codecs), guaranteeing the exact 1:1 movie quality as on original disc. This is at 1080p quality.<section end=1080p Remux />

<section begin=HDTV-2160p />*<code>HDTV-2160p</code> - TVRip is a capture source from an capture card. HDTV stands for captured source from HD television. With an HDTV source, the quality can sometimes even surpass DVD. Movies in this format are starting to grow in popularity. Some advertisement and commercial banner can be seen on some releases during playback. This is at 2160p (4K) quality.<section end=HDTV-2160p />

<section begin=WEBDL-2160p />*<code>WEBDL-2160p</code> - WEB-DL (P2P) refers to a file losslessly ripped from a streaming service, such as Netflix, Amazon Video, Hulu, Crunchyroll, Discovery GO, BBC iPlayer, etc., or downloaded via an online distribution website such as iTunes. The quality is quite good, since they are not reencoded. The video (H.264 or H.265) and audio (AC3/AAC) streams are usually extracted from the iTunes or Amazon Video and remuxed into a MKV container without sacrificing quality. An advantage with these releases is that, like BD/DVDRips, they usually have no onscreen network logos. These are nearly as good as a Blu-ray source but can suffer from audio lag or visual artifacts from the adaptive bitrate of streaming services. If a ripper's internet connection drops to a point where the bitrate lowers, the source bitrate could change dynamically, causing variations in picture quality. Most releases that suffer from an extreme amount of visual artifacts are NUKED and a PROPER is generally released to fix any wild variations in adaptive bitrate. This will be in 2160p (4K) quality.<section end=WEBDL-2160p />

<section begin=WEBRip-2160p />*<code>WEBRip-2160p</code> - In a WEB-Rip (P2P), the file is often extracted using the HLS or RTMP/E protocols and remuxed from a TS, MP4 or FLV container to MKV. This will be in 2160p (4k) quality.<section end=WEBRip-2160p />

<section begin=Bluray-2160p />*<code>Bluray-2160p</code> - A re-encode of the final released Blu-ray, at its native 21600p resolution (3840x2160 @ 16:9, any other aspect ratio may be a different resolution). 4K versions of films that are released in generally HEVC codec and could be either 8-bit or 10-bit color reproduction or from an HDR source. slightly reducing filesize. These are generally MKV or MP4 container.<section end=Bluray-2160p />

<section begin=2160p-Remux />*<code>Remux-2160p</code> - A remux is a rip of a Blu-ray or HD DVD disc to another container format or just stripping the disc of menus and bonus material while keeping the contents of its audio and video streams intact (also keeping the current codecs), guaranteeing the exact 1:1 movie quality as on original disc. This is at 2160p (4K) quality.<section end=2160p-Remux />

*<code>BR-DISK</code> - The original Blu-ray disc, with it's AVC/HEVC folder structure and no change in container format. Some media players are unable to deal with these, but they are generally used for archival purposes. The original Blu-ray disc content is unmodified. Most of the time, these have been run through an HDCP decryption process already via the ripper. Sometimes they are still encrypted.
<section end=video-qualities />

==== Audio Qualities ====
<section begin=audio-qualities />
*<code>AAC-192</code> - An AAC file with a 192 kbps bitrate
*<code>AAC-256</code> - An AAC file with a 256 kbps bitrate
*<code>AAC-320</code> - An AAC file with a 320 kbps bitrate
*<code>AAC-VBR</code> - An AAC file with a variable bitrate
*<code>ALAC</code> - Audio file created with the Apple Lossless Audio Codec (ALAC); used for storing digital music losslessly without losing any sound quality from the original audio data; differs from lossy audio codecs such as AAC.
*<code>APE</code> - Audio file compressed using Monkey's Audio lossless compression algorithm; includes error detection and support for tags that store information about audio files; sometimes created with .CUE files to comprise an audio CD image.
<section begin=FLAC />*<code>FLAC</code> - A FLAC file is an audio file compressed in the Free Lossless Audio Codec (FLAC) format, which is an open source lossless audio compression format. It is similar to a .MP3 file, but is compressed without any loss in quality or loss of any original audio data.<section end=FLAC />
*<code>FLAC 24bit</code> - A FLAC file with 24-bit encoding, allowing a much wider dynamic range than CD, and sampling rates all the way up to 192kHz
*<code>MP3-8</code> - A MP3 file with a 8 kbps bitrate
*<code>MP3-16</code> - A MP3 file with a 16 kbps bitrate
*<code>MP3-24</code> - A MP3 file with a 24 kbps bitrate
*<code>MP3-32</code> - A MP3 file with a 32 kbps bitrate
*<code>MP3-40</code> - A MP3 file with a 40 kbps bitrate
*<code>MP3-48</code> - A MP3 file with a 48 kbps bitrate
*<code>MP3-56</code> - A MP3 file with a 56 kbps bitrate
*<code>MP3-64</code> - A MP3 file with a 64 kbps bitrate
*<code>MP3-80</code> - A MP3 file with a 80 kbps bitrate
*<code>MP3-96</code> - A MP3 file with a 96 kbps bitrate
*<code>MP3-112</code> - A MP3 file with a 112 kbps bitrate
*<code>MP3-128</code> - A MP3 file with a 128 kbps bitrate
*<code>MP3-160</code> - A MP3 file with a 160 kbps bitrate
*<code>MP3-192</code> - A MP3 file with a 192 kbps bitrate
*<code>MP3-224</code> - A MP3 file with a 224 kbps bitrate
*<code>MP3-256</code> - A MP3 file with a 256 kbps bitrate
<section begin=MP3-320 />*<code>MP3-320</code> - An MP3 file with a 320 kbps bitrate<section end=MP3-320 />
*<code>MP3-VBR-V0</code> - An MP3 file with a variable bitrate (version 0)
*<code>MP3-VBR-V2</code> - An MP3 file with a variable bitrate (version 2)
*<code>OGG Vorbis Q5</code> - An OOG file with an 160 kbps bitrate
*<code>OGG Vorbis Q6</code> - An OOG file with a 192 kbps bitrate
*<code>OGG Vorbis Q7</code> - An OOG file with a 224 kbps bitrate
*<code>OGG Vorbis Q8</code> - An OOG file with a 256 kbps bitrate
*<code>OGG Vorbis Q9</code> - An OOG file with a 320 kbps bitrate
*<code>OGG Vorbis Q10</code> - An OOG file with a 500 kbps bitrate
*<code>Unknown</code> - Self Explanatory
*<code>WavPack</code> - WavPack compresses high-quality audio to between thirty and seventy percent and supports both mono and stereo audio ranging from 8 to 32 bits. Typically these are audio files in an <code>.WV</code> container
*<code>WAV</code> - A WAV file is an audio file saved in the WAVE format, which is a standard digital audio file format utilized for storing waveform data. WAV files may contain audio recordings with different sampling rates and bitrates but are often saved in a 44.1 KHz, 16-bit, stereo format, which is the standard format used for CD audio.
*<code>WMA</code> - A WMA file is an audio file saved in the Advanced Systems Format (ASF) proprietary format developed by Microsoft. It contains Windows Media Audio and metadata objects such as the title, artist, album, and genre of the track. WMA files are similar to .MP3 files and primarily used for streaming music from the web.
<section end=audio-qualities />

==== eBook Qualities ====
<section begin=ebook-qualities />
*<code>Unknown</code> - Self Explanatory
*<code>PDF</code> - A PDF file is a multi-platform document created by Adobe Acrobat or another PDF application. The PDF format is commonly used for saving documents and publications in a standard format that can be viewed on multiple platforms. In many cases, PDF files are created from existing documents instead of from scratch. With that being said PDF isn't a book format it is originally designed as a printing format so a lot of features you'll find with other formats will not be available.
*<code>MOBI</code> - A MOBI file is an eBook saved in the MOBI format, a format originally used by the Mobipocket Reader but now supported by several different readers. It contains an eBook and may incorporate DRM copyright protection to prevent copying or unauthorized viewing. MOBI files are supported by various eReaders, tablets, PDAs, and desktop computer applications.
*<code>EPUB</code> - An EPUB file is a digital ebook saved in the EPUB format, an open XML-based format for digital books and publications. It provides a standard digital publication format for publishers and consumers. EPUB files can be viewed with supporting software programs and hardware devices, such as the Amazon Kindle and Barnes & Noble NOOK.
*<code>AZW3</code> - An AZW3 file is an eBook created in the Kindle Format 8 (KF8), Amazon's successor to the .AZW format. It supports newer features such as HTML5 and CSS3 support as well as many other formatting capabilities. AZW3 files often include DRM protection and are used as the download format for many Amazon eBooks.
<section end=ebook-qualities />

=== Indexer Flags ===

Torrent Indexers sometimes have torrents that, while they contain the same video, have other attributes that differentiate them. In Radarr, these are called Indexer Flags and you can do some cool stuff with them. See the table below, for a list of available flags and what they signify.

==== Uses ====

Indexer Flags can be used for multiple things in Radarr. Under Settings -> Indexers, you can e.g. specify that all releases with any indexer flag is preferred. This is useful, if you occasionally want to download a golden popcorn release over a normal encode.

If you want more control over indexer flags, there are two other options:

==== 1. Required Flags ====

In your indexer settings, you can specify, what exact flags are required, for a release to be downloaded for this indexer. This allows you to have a strict indexer only download freeleech torrents as an example. To require an indexer flag, look at the table below, take the flag name and put it in the corresponding field in your indexer’s settings.

==== 2. Custom Formats ====

'''(Radarr Only)'''
Indexer Flags can be used as Format Tags in a Custom Format. Check out the [[Radarr Settings#Custom Formats|Custom Formats]] section for more information.

==== Supported Flags ====

{|
!width="33%"| Flag Name
!width="33%"| Symbol
!width="33%"| Description
|-
| G_Freeleech
| ⬇⬇
| Sometimes, torrent sites set a torrent to be freeleech. This means, that the download of this torrent will not count towards your download quota or ratio. This is really useful, if you do not have the best ratio yet.
|-
| G_Halfleech
| ⇩⇩
| Similar to G_Freeleech, G_Halfleech signifies that only half of the size of this torrent will count towards your download quota or ratio.
|-
| G_DoubleUpload
| ⬆
| Similar to G_Freeleech, G_DoubleUpload signifies that any amount of data you upload via seeding is counted twice towards your upload quota and ratio. This is very useful, if you want to build up a ratio buffer.
|-
| PTP_Golden
| 🌟
| On PassThePopcorn, some torrents are given the Golden tag, when they meet certain encoding standards. These are usually the best encodes, with almost no perceptible quality loss. You can learn more on their wiki page.
|-
| PTP_Approved
| ✔
| On PassThePopcorn, some torrents are approved, when they meet the minimum standards for encoding (e.g. no low bitrates). See their wiki for more information.
|-
| HDB_Internal
| 🚪
| Releases on HDBits receive this tag, when the release was uploaded by one of the release groups of HDBits themselves.
|-
| AHD_Internal
| 🚪
| Releases on Awesome HD receive this tag, when the release was uploaded by one of the release groups of Awesome HD themselves.
|-
| G_Scene
| ☠
| This flag is applied to releases that are reported to be from a scene release group by your indexer.
|-
| G_Freeleech75
| ⇩⬇
| Similar to G_Freeleech, G_Freeleech75 signifies that only 25% of the size of this torrent will count towards your download quota or ratio.
|-
| G_Freeleech25
| ⇩
| Similar to G_Freeleech, G_Freeleech25 signifies that only 75% of the size of this torrent will count towards your download quota or ratio.
|}

Radarr Tips and Tricks

2020-09-27T21:02:45Z

TRaSH: /* TRaSH's Custom Formats */

=== TRaSH's Custom Formats ===
[https://github.com/TRaSH-/Tutorials-FAQ/blob/master/RadarrV3/Collection-of-Custom-Formats-for-RadarrV3.md Link to source document]
{{#github:RadarrV3/Collection-of-Custom-Formats-for-RadarrV3.md|TRaSH-/Tutorials-FAQ|master}}