Web interface error on adding indexer

Help & Support
#1

Sonarr version (exact version):
docker container linuxserver/sonarr which is Sonarr Ver. 2.0.0.4949
OS:
Docker (with Ubuntu Xenial as a base)
((Debug logs)):
17-8-22 15:49:01.3|Debug|Torznab|Downloading Feed http://jackett:9117/torznab/all?t=tvsearch&cat=5030,5040&extended=1&apikey=(removed)&offset=0&limit=100
17-8-22 15:49:01.5|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:
– No results were returned from your indexer, please check your settings.
17-8-22 15:49:01.5|Debug|Api|[POST] /api/indexer/test: 400.BadRequest (328 ms)
Description of issue:
When manually curling the jackett api from my sonarr server, it returns results:

root@6ba2f47d12e1:/config/logs# curl http://jackett:9117/torznab/all?apikey=jwwys3yc0ax0olheftmb8dbhhekv7cb3 | head -100
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0 <?xml version="1.0" encoding="UTF-8"?>  0 --:--:--  0:00:11 --:--:--     0
<rss version="1.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:torznab="http://torznab.com/schemas/2015/feed">
  <channel>
    <atom:link href="http://jackett:9117/" rel="self" type="application/rss+xml" />
    <title>AggregateSearch</title>
    <description>This feed includes all configured trackers</description>
    <link>http://127.0.0.1/</link>
    <lanuage>en-us</lanuage>
    <category>search</category>
    <image>
      <url>http://jackett:9117/logos/aggregateindexer.png</url>
      <title>AggregateSearch</title>
      <link>http://127.0.0.1/</link>
      <description>AggregateSearch</description>
    </image>
    <item>
      <title>Game.of.Thrones.S07E06.1080p.WEBRip.x264.LEGENDADO-WWW.BLUDV.COM.mkv</title>
      <guid>https://torrentz2.eu/0111c660685693c4b7d8afbdfb5aae4121feb453</guid>
      <comments>https://torrentz2.eu/0111c660685693c4b7d8afbdfb5aae4121feb453</comments>
      <pubDate>Tue, 22 Aug 2017 15:31:07 +0100</pubDate>
      <size>1955594240</size>
(and so on)

But looking at the debugging logs, it’s trying to run the following command, which gives me this output:

root@6ba2f47d12e1:/config/logs# curl http://jackett:9117/torznab/all?t=tvsearch&cat=5030,5040&extended=1&offset=0&limit=100&apikey=jwwys3yc0ax0olheftmb8dbhhekv7cb3
[1] 491
[2] 492
[3] 493
[4] 494
[5] 495
root@6ba2f47d12e1:/config/logs# "Incorrect API key"
[1]   Done                    curl http://jackett:9117/torznab/all?t=tvsearch
[2]   Done                    cat=5030,5040
[3]   Done                    extended=1
[4]-  Done                    offset=0
[5]+  Done                    limit=100

If I then remove t=tvsearch&cat=5030,5040&extended=1&offset=0&limit=100& from the command, it returns results.

Does anyone have an idea of where I’m going wrong here?

#2

It looks like Jackett is having a hard time parsing the API Key when there are other query params.
Do you have the same issue if you use an individual feed instead of the aggregate feed?

#3

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.