![]() ![]() This may be an issue with the indexer or your indexer category settings. The specific error will be be an HTTP 400 from *Arr stating Query successful, but no results in the configured categories were returned from your indexer.In other words, if you're syncing to an App and your indexer's empty query does not return results with any release within the categories configured for the App then it will be unable to add the indexer to *Arr. The most common cause for this is that the *Arrs only accept indexers whose test queries return results containing at least one of the configured categories.Indexers will not be attempted to be synced if the specific Categories supported by the Indexer are not selected in Settings => Application => => Sync Categories (Advanced Settings) and logs will not show any indication of a sync attempt.A given indexer will only be synced to Sonarr "Supported" Categories can be selected as an advanced setting on a per app basis.If an indexer supports only TV categories it will not be synced to Lidarr, Radarr, and Readarr.Indexers are synced based on the capabilities/categories they claim to support.Only in instances where an App and Indexer have matching tags or no tags at all will an indexer be synced to an app.Prowlarr only syncs if Add and Remove or Full Sync is enabled for the app.¶ Prowlarr will not sync X Indexer to App Sonarr v2 (fka nzbdrone) is not supported by Prowlarr nor supported in general and has been end-of-life since March 2021.Press Save again to trigger a force save.Follow then standard steps to add the indexer noting thr following changes.See TRaSH's Guides on "How to setup Flaresolverr" for more details ¶ How can I add an indexer that is down or not functional? A Flaresolverr proxy is disabled if no tags are used. ![]() The tags must match & Cloudflare must be detected for Flaresolverr to be used.
0 Comments
Leave a Reply. |