Generally Quality Trumps All
The current logic can be found here.
As of 2021-07--8 the logic is as follows
CAUTION:If lists are done improperly they will absolutely wreck your library with a bunch of trash you have no intention of watching. So make sure of what you're importing before you click save.
Readarr uses .NET Core and a new webserver. In order for SignalR to work, the UI buttons to work, database changes to take, and other items. It requires the following addition to the location block for Readarr:
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
Make sure you
do not include
proxy_set_header Connection "Upgrade"; as suggested by the nginx documentation.
THIS WILL NOT WORK
If you are using a CDN like Cloudflare ensure websockets are enabled to allow websocket connections.
This will not install the bits from that branch immediately, it will happen during the next update.
master - - (Default/Stable): It has been tested by users on the develop and nightly branches and it’s not known to have any major issues. On GitHub, this is the
master branch. Readarr does not yet have a stable release.
develop - - (Beta): This is the testing edge. Released after tested in nightly to ensure no immediate issues. New features and bug fixes released here first. Readarr does not yet have a beta release.
Warning: You may not be able to go back to
masterafter switching to this branch. On GitHub, this is a snapshot of the
developbranch at a specific point in time.
nightly- - (Alpha/Unstable): The bleeding edge. Released as soon as code is committed and passed all automated tests. Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update. This version is updated immediately.
Warning: You may not be able to go back to
developafter switching to this branch. On GitHub, this is the
:nightlyto the end of your container tag depending on who makes your builds.
|hotio||no stable release yet||no beta release yet||
nightly, but then update the Docker container itself (possibly downgrading to an older version).
You can (almost) always increase your risk.
mastercan go to
developcan go to
masterfor your given build.
Error parsing column 45 (Language=31 - Int64)or other similar database errors around missing columns or tables.
Readarr uses both Alt Titles and Translations for parsing and searching. Search will use the Original Title, English Title, and Translated Title from whatever languages you have preferred (in profile and CFs). Parsing should look for a match in all Translations and Alt Titles.
To get a book in a foreign language set your Profile Language to Original (Book's Original Language), a specific language for that profile, or any and use custom formats to determine which language to grab.
Note that this does not include any indexer languages specified as multi.
Sometimes you can get a problem that authors that are imported from your lists, gets imported with the root path set to “C:” or other weird paths.
This is a known issue for when the root path is either not setup during the creation of the list, or if the root path has been deleted after the list was created. Note that this problem can still occur even if the list is
edited and the correct root path is set.
Use the Mass Editor to fix paths of existing authors.
Check if you have Completed Download Handling - Remove turned on. (This does not work if you are using rtorrent.)
If you are using deluge make sure auto-managed is turned on. And that torrents get paused when they reach specified seeding quota.
Raspbian has a version of libseccomp2 that is too old to support running a docker container based on Ubuntu 20.04, which both hotio and LinuxServer use as their base. You either need to use
--privileged, update libseccomp2 from Ubuntu or get a better OS (We recommend Ubuntu 20.04 arm64)
Managed to fix the issue by installing the backport from debian repo. Generally not recommended to use backport in blanket upgrade mode. Installation of a single package may be ok but may also cause issues. So got to understand what you are doing.
Steps to fix:
First ensure you are running Raspbian buster e.g using
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
If you are using buster:
echo "deb <http://deb.debian.org/debian> buster-backports main" | sudo tee /etc/apt/sources.list.d/buster-backports.list
sudo apt update && sudo apt-get -t buster-backports install libseccomp2
Lists never were nor are intended to be
add it now they are
hey I want this, add it eventually tools.
You can trigger a list refresh manually, script it and trigger it via the API, or add the books directly to Readarr.
This change was due to not have our server get killed by people updating lists every 10 minutes.
No, nor should you through any SQL hackery. The refresh books task queries the upstream Servarr proxy and checks to see if the metadata for each book (ids, cast, summary, rating, translations, alt titles, etc.) has updated compared to what is currently in Readarr. If necessary, it will then update the applicable books.
A common complaint is the Refresh task causes heavy I/O usage. One setting that can cause issues is "Rescan Author Folder after Refresh". If your disk I/O usage spikes during a Refresh then you may want to change the Rescan setting to
Manual. Do not change this to
Never unless all changes to your library (new books, upgrades, deletions etc) are done through Readarr. If you delete book files manually or a third party program, do not set this to
No. With a single Readarr instance, you can have either one or the other, but not both. If you want both, you would need to run two separate instances of Readarr (much like some people run 2 instances of Sonarr or Radarr for 1080p and 4K versions of their media).
No. In general Calibre offers some further enhancement, such as the ability to auto-convert ebooks to another format specific to your e-reader's capabilities, and also to connect to that e-reader. But if you weren't running Calibre prior to installing Readarr, then it's probably going to be of limited added benefit to you to install it, and it's a very large program.
Unless you're in a repressive country like China, Australia or South Africa, your torrent client is typically the only thing that needs to be behind a VPN. Because the VPN endpoint is shared by many users, you can and will experience rate limiting, DDOS protection, and ip bans from various services each software uses.
In other words, putting the *Arrs (Lidarr, Radarr, Readarr, and Sonarr) behind a VPN can and will make the applications unusable in some cases due to the services not being accessible. To be clear it is not a matter if VPNs will cause issues with the Arrs, but when: image providers will block you and cloudflare is in front of most of arr servers (updates, metadata, etc.) and liable to block you too
In addition, some private trackers ban for browsing from a VPN, which is how Jackett works. In some cases (i.e. certain UK ISPs) it may be needed to use a VPN for public trackers, in which case you should then be putting only Jackett behind the VPN. However, you should not do that if you have private trackers without checking their rules first. Many private trackers will ban you for using or accessing them (i.e. using Jackett) via a VPN.
/all endpoint is convenient, but that is its only benefit. Everything else is potential problems, so adding each tracker individually is recommended.
May 2021 Update: It is likely Radarr support will be phased out for the jackett
/all endpoint in the future due to the fact it only causes issues.
/all endpoint has no advantages (besides reduced management overhead), only disadvantages:
Adding each indexer separately It allows for fine tuning of categories on a per indexer basis, which can be a problem with the
/all end point if using the wrong category causes errors on some trackers. In Readarr, each indexer is limited to 1000 results if pagination is supported or 100 if not, which means as you add more and more trackers to Jackett, you're more and more likely to clip results. Finally, if one of the trackers in
/all returns an error, Sonarr will disable it and now you do not get any results.
This is expected. This is how the Torrent Process works.