Sonarr - Unable to connect to indexer, check the log for more details

QuickBox Support
#31

Did this get resolved? Even after a removal i keep getting this error in sonarr?
NzbDrone.Common.Http.HttpException: HTTP request failed: [401:Unauthorized] [GET] at [https://xx.xx.xx.xx/jackett/torznab/tvchaosuk/api?t=tvsearch&cat=5030,5040&extended=1&apikey=xxxxxxxxxxxxxxxxxxxxxx&offset=0&limit=100]
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x001a1] in :0
at NzbDrone.Core.Indexers.HttpIndexerBase1[TSettings].FetchIndexerResponse (NzbDrone.Core.Indexers.IndexerRequest request) [0x00058] in <16f9d0ac1b4b4545a818312139cdf850>:0 at NzbDrone.Core.Indexers.HttpIndexerBase1[TSettings].FetchPage (NzbDrone.Core.Indexers.IndexerRequest request, NzbDrone.Core.Indexers.IParseIndexerResponse parser) [0x00000] in <16f9d0ac1b4b4545a818312139cdf850>:0
at NzbDrone.Core.Indexers.HttpIndexerBase`1[TSettings].TestConnection () [0x00024] in <16f9d0ac1b4b4545a818312139cdf850>:0

401 Unauthorized

Unauthorized

This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.

Apache/2.4.18 (Ubuntu) Server at xx.xx.xx.xx Port 443 Close
#32

For a handful of users this works for connecting the 2 just fine:

#33

jackett is communicating over https, if i change to http it shows connection refused. The only thing that i can think of is this seems be failing is due to using htaccess and sonarr not being able to handle that request correctly

#34

It is happening due to the port forwarding as it is not listening on port 443. Another issue could be the fact that it is requesting auth before access. So you may need to remove the require auth bits from those two applications apache configs.

#35

I have never had to mess with the auth bits…just use “http://localhost:9117” in place of the http://host.domain.com/ portion. You can’t just take the URL out of Jackett as is because it will not work. It requires taking that url and modifying it for Sonarr.

#36

Correct, the auth bits are just another measure for anyone that thinks one way or another. As you stated, http://localhost:{port} is the only way I have ever been able to connect the 2.

#37

Im running the current version as installed today. No matter what i put in i get the same style of output.
https://xx.xx.xx.xx:9117/torznab/iptorrents
http://xx.xx.xx.xx:9117/torznab/iptorrents
https://xx.xx.xx.xx:9117/jackett/torznab/iptorrents
http://xx.xx.xx.xx:9117/jackett/torznab/iptorrents

#38

Two points here:

  1. No https, its http
  2. you need ‘localhost’ and not xx.xx.xx.xx

use it EXACTLY as we have it.

#39

sorry im putting in xx.xx to mask my ip.
ok you win that worked… im an idiot! once i have this all running expect a donation. This is fantastic work!

1 Like
#40

You’re not an idiot… @RXWatcher just has that way of being smarter than the rest of us :stuck_out_tongue:

#41

That maybe true… however ill stand by my comment of being an idiot! Setting up everything again in a day has melted my brain. Ive run a seedbox that i built from scratch a couple of years ago and never messed with it too much. i wanted this as it just has nearly everything without messing with it too heavily and keeping the OS clean

#42

I’m not smarter…I’m just a very seasoned linux admin…like 30 years working on unix-linux.

the apps(if setup correctly) should all listen on ‘localhost’ and not a public IP. It’s a security measure. They can only be accessed on the server itself via that port which is http so insecure. If you want to connect to the actual port of 9117, you’d need to do it from the actual server via VNC or X2Go…by entering localhost here, its saying that my local app(Sonarr) is going to talk to Jackett(also local) via the localhost(127.0.0.1) on that port. It works because they are both local to the server. It never goes against the public IP and thus bypasses the proxy stuff.

#43

I had this issue as well. Except I’m using Jackett on my seedbox, talking to Sonarr on my local server. Thus I am using my domain name. I can only make this work with HTTP, auth disabled and specifying 9117 (don’t worry, I set a Jackett password).

Is it possible to use HTTPS? I want to make sure the data is passed securely.

#44

Hi,
I have the same problem. I tested with this differents addresses (IP adresse, localhost, http, https) but it don’t work.
Do you have some issues ?
PS : I have a question : why Jackett give me this link to integrate for sonarr / Radarr:
https://MY_SERVER_IP/jackett/api/v2.0/indexers/yggtorrent/results/torznab/

#45

Hello @Neibaf

Ygg has changed their website URL, so even if the interaction between Sonarr/Radarr and Jackett was functionnal, you should not have any result :slight_smile:

As we need to do when are facing of this kind of issue, you need to create a new issue directly on Jackett github to tell teme to correct the issue : https://github.com/Jackett/Jackett/issues/2215.

PS : the issue was already created, please use the search bar (/autoflogging)

I can grab results from Jackett with this torznab URL : http://localhost:9117/torznab/YourIndexer

#46

The problem is that Sonarr/Radarr return me a error :
Unable to connect to indexer: HTTP request failed: [401:Unauthorized] [GET] at [https://MY.DOMAIN.COM/jackett/api/v2.0/indexers/yggtorrent/results/torznab/api?t=caps&apikey=MyAPIKey]
and the errors ars same for http, https, IP adress, Domain name address and localhost

#47

Did you try this URL with a working indexer : http://localhost:9117/torznab/YourIndexer ?

#48

yes, same error

#49

Weird.

Could you please show us the result of these commands :

  • netstat -an | grep 9117 | grep LISTEN
  • cat /etc/apache2/sites-enabled/jackett.conf (remove your username after “require user” when you paste the result here please)
#50

I have uninstall sonarr/radarr and jackett for this moment.
I tried again it next week.