Can confirm that if you use @JMSolo solution here - Sonarr and jackett is working just fine.
Thanks JM for helping me out!
Hello guys, I have the same problem but manually specifying the port still doesn’t work for me. The server actively refuses connections on the jackett port (9117). Can anyone help? Thanks!
EDIT: nevermind, a reboot fixed it! 
AND IT WORKS!
I’m a bit confused… How do I remove the password protection from the reverse proxy exactly?
I’m having a similar issue and even with http://localhost:9117 used as my connection in sonarr it still refuses connection to jacket here’s an example
@maddawg2 was able to fix it via uninstalling Jackett, removing the ~/Jackett/ directory and reinstalling.
When you go into Jackett and copy the URL, does it contain a hostname or is it an IP? In @maddawg2’s case it was an IP.
I think that there is a thing when Jackett installs that it binds to the hostname via /etc/hosts and if thats off then it binds to an IP and if it’s an IP then the localhost doesnt work.
Yes it is an ip I’ll try reinstallling when I get home from work
I would also check your /etc/hosts to make sure its correct before reinstalling.
cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 hostname.domain.com hostname
Do not remove the following line, or various programs
that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
(main ip removed from here) .net ns513330
2607:5300:0060:70ec:: .net ns513330
Localhost seems to work when it comes to setting up sickrage or couchpotato etc etc so tbh I don’t know why it wouldn’t work here
I would try the uninstall, trash the Jackett dir and reinstall.
Okie dokie I’ll give it a shot never used sonarr before but hear it blows sickrage away so wanting to give it a shot
Wellllll, that’s stretching things a tad bit. The UI is much cleaner, however; their lack of supporting TV packs is why SickRage is still a go-to for most. Sonarr could (and more than likely will be) be a sure replacement in the future. I am still waiting for it to be a matter of aesthetic before I make the move.
1 Like
Maybe I won’t go to all the trouble just yet then sickrage is doing the job might still work on jackett though just as a way to keep my trackers in check
Sorry I just uninstall ed jacket but I can’t locate the jackett folder it’s not in my user folder and it’s not in /opt so I have no idea where it is but it’s definitely around somewhere because upon reinstall jackett all my settings persist
You should have two Jackett folders:
/home/user/.config/Jackett
/home/user/Jackett
i had the .config folder but not the user one
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
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
For a handful of users this works for connecting the 2 just fine:
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
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.