![]() If your client supports multiple feeds it's recommended to add each indexer directly instead of using the all indexer. ![]() It will query all configured indexers and return the combined results. The Jackett readme.md makes the disadvantages clear but they don't sound like a deal breaker:Ī special "all" indexer is available at /api/v2.0/indexers/all/results/torznab What is your reasoning behind the "Absolutely do not use the /all"? Did I make an integration error somewhere in here? I've read all of the relevant threads I could find on Jackett integration into Sonarr but this one has me stumped. When I complete the same search manually from Jackett, the search returns results as expected. Sometimes, if I wait a few seconds and reclick on the search button from the previous search, the UI is populated with the relevant search results. There are no noticeable errors in the Jackett or Sonarr logs. However in the Jackett logs, I can see the query going to Jackett and Jackett returning results. When I click on search in Sonarr, the UI waits a few moment and then returns a "No results found". This integration tests successfully before being saved when setting up the Sonarr index. Sonarr was setup to use a single Jackett Index as described in this post: REDDIT LINK ![]() ![]() There is no additional complexity to this integration other than mapping to ports in the 3xxxx range. Sonarr and Jackett are deployed in Docker on a Kubernetes cluster. It also looks like I have other issues in my configuration to solve for. Once I switched it, it was working as expected. I had added my indexer as Usenet which was incorrect. Solved the issue based on some keyword searches I got from teh automod (Awesome bot!). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |