[Support] binhex - Jackett


binhex

276 posts in this topic Last Reply

Recommended Posts

New to Jackett due to the tightening of iptables issue. Am I correct in assuming that if my indexer isn’t listed then this docker is of no use or could I still use it to route download clients thru? Using nzbplanet for nzb’s and rarbg for torrents.
 
On a side note, I was using Privoxy to route Sonarr, Radarr and Lidarr thru DelugeVPN. Adding the “Additional_Ports” variable for these dockers to DelugeVPN and ignoring my server’s IP address has restored the download client connection to DelugeVPN but not NZBgetVPN. Assuming I can’t make the same changes to NZBgetVPN because a docker update would be required to recognize the Additional Ports variable? Is there a fix to get NZBgetVPN working similar to DelugeVPN or should I bite the bullet and bind these containers to DelugeVPN?

I ended up adding all of the download apps in the delugeVPN network, including NzbGet (the non-VPN version from binhex). I am seeing slower download speeds for nzbget this way, but at least it’s working and all apps can talk to each other again.
Binhex is working on a secure solution to allow apps inside the VPN network to talk to apps outside it, so it might be possible to run NzbGet on the outside again in the future.
Your only other option is to configure sonarr/radarr to talk to NzbGet on the internal docker ip, e.g. 172.x.x.x, but beware that the actual up is dynamic for each container and may change on restarts.

Edit: yeah jackett is of no use for NZB’s, you need to set them up as separate indexers in radarr/sonarr. Which shouldn’t be a problem, both apps should talk to the internet freely over the VPN tunnel

Edit2: sorry ignore the first bit of my reply, you’re using privoxy, not network binding. Sorry for the confusion.
Link to post
  • Replies 275
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

im on it guys, looks like there has been a switch to .net core which requires changes to the code which ive now done, new image now building

I pushed my luck a bit more as i got a little friendly with one of the dev's on Jackett and mentioned him in another one of my open enhancements, this one is to automatically disable index sites when

a feature i created an issue for in 2017 is now going to be in the next build, yay!, and in my opinion its a good un', it allows for logical grouping of index sites, so you will be able to hit aggrega

Posted Images

Hey @binhex, Wondering if you can help me. I have had the delugeVPN working fine and still running fine with PIA(confirmed by setting up proxy on laptop and still getting VPN IP address). Jackett has been passed through delugeVPN container for quite a while and no issues until this past weekend where I am not sure what changed. My server for the most part is automated so I never really login other than to maybe sonarr/radarr to queue a download if something isnt automated.

 

The issue is Jackett seems to have stopped working, its not connecting to the GUI and on sonarr and radarr it cant search the indexer I had setup. If I remove the extra parameters(--net=container:binhex-delugevpn) pushing it through the delugeVPN container and set it back to bridge then it connects to the GUI fine so seems the container is working. 

I tried clearing the appdata files and starting fresh with Jackett but I am not sure what else to try. I am not sure why the GUI refuses to work now through the delugeVPN container. Any ideas?

Edited by chris7r
Link to post
1 hour ago, chris7r said:

The issue is Jackett seems to have stopped working, its not connecting to the GUI and on sonarr and radarr it cant search the indexer I had setup. If I remove the extra parameters(--net=container:binhex-delugevpn) pushing it through the delugeVPN container and set it back to bridge then it connects to the GUI fine so seems the container is working. 

this is not a jackett issue, look at the 'recommended post' on the delugevpn support thread on how to fix this.

Link to post
3 hours ago, binhex said:

this is not a jackett issue, look at the 'recommended post' on the delugevpn support thread on how to fix this.

Cheers thanks mate will look into delugevpn support thread then. much appreciated

Link to post

Hi Binhex, I have just noticed that my weekly show hadn't downloaded along with a couple of movies etc. I went and checked my radarr and sonarr to test the indexer, but the indexer within jackett seems to have stopped working in the last couple of days.

 

Unraid is up to date, as are all dockers, haven't changed anything on the network or within the settings of the dockers, unraid etc.

 

I changed the nordvpn openvpn file within the deluge openvpn folder as these seem to expire sometimes, thats what I thought was the problem with no downloads going initially.

 

I checked the logs of jackett and there is this message, looks like some file permission setting? Not sure if this is what is causing the issue but its in the logs anyway:

 

2021-03-13 18:17:56,258 DEBG 'jackett' stderr output:
realpath(/usr/lib/jackett/) failed: Operation not permitted

realpath(/usr/lib/jackett/) failed: Operation not permitted

realpath(/usr/lib/jackett/) failed: Operation not permitted

realpath(/usr/lib/jackett/) failed: Operation not permitted

realpath(/usr/lib/jackett/) failed: Operation not permitted

realpath(/usr/lib/jackett/) failed: Operation not permitted

realpath(/usr/lib/jackett/) failed: Operation not permitted

 

 

Then on sonarr I have:

 

2021-03-13 18:58:37,195 DEBG 'sonarr' stdout output:
[Warn] SonarrErrorPipeline: Invalid request Validation failed:

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

 

On radarr I am getting the same:

 

2021-03-13 18:59:38,107 DEBG 'radarr' stdout output:
[Warn] RadarrErrorPipeline: Invalid request Validation failed:

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

 

My Jackett is setup as follows:

 

image.png.44ba61f3252ef79710a6845cb3352cc2.png

 

Any help in diagnosing would be appreciated :)

 

Thank you

Link to post

This thread has been very helpful getting Jackett setup for me. I've moved Radarr and Jackett behind my delugevpn container an now seem to be having issues getting Jackett to connect to indexers. I'm assuming this is a simple setup issue i overlooked. Hopefully someone can save my hours of searching.

Radarr and Jackett can connect - used "localhost" in applicable fields

Added port 9117 to VPN_INPUT and created additional port in DelugeVPN per SpaceInvaderOne

This might be Q26 but i don't quite understand what is being stated here.

 

Edit 1: In case anyone stumbles across this with the same problem i was able to get some indexers on my list to connect by using local host as the Proxy URL. This only works after typing in "http://localhost". see second screen shot of fix. Some indexers are not connecting still so i supect there is a VPN block which is discussed elsewhere. I will update this post when i get them working. 

image.png.9f45bce6c031853267e122c0e9084b97.png

supervisord - Copy.log

 

Edit 2 Screenshot

image.png.863e3df37d69198343f73ccb5f68faf9.png

Edited by Jayg37
Link to post
  • 1 month later...

a feature i created an issue for in 2017 is now going to be in the next build, yay!, and in my opinion its a good un', it allows for logical grouping of index sites, so you will be able to hit aggregated named groups, as opposed to having to use the 'all' group, for anybody interested here is my feature request:-

 

https://github.com/Jackett/Jackett/issues/2185

Link to post
  • 2 weeks later...

I pushed my luck a bit more as i got a little friendly with one of the dev's on Jackett and mentioned him in another one of my open enhancements, this one is to automatically disable index sites when they are offline - link to the enhancement:- https://github.com/Jackett/Jackett/issues/3292#issuecomment-841484694

 

So the reason i wanted the ability for inders to be disabled is that if you have one or more indexers goes offline then this can block all index sites from being contacted via the metadata downloaders (e.g. sonarr/radarr, etc), as the aggregated 'all' list contacts each index site in turn before returning the result to the metadata downloader. 

 

So how do you use this feature?, simple you add in additional filters to the api feed for the metadata downloader, an example:-

 

http://<your servers ip>:<your host port>/api/v2.0/indexers/tag:tv+type:public+lang:en+test:passed/results/torznab

 

so in the above example this will filter for indexers with tags tv AND type public AND language english AND test passed, the important bit being the end 'test', this is where it filters based on only indexers that have passed, failed index sites will not be tried until they pass the tests again.

 

want to see which index sites are marked as failed?, issue this from web browser:-

 

http://<your servers ip>:<your host port>/api/v2.0/indexers/test:failed/results?apikey=<your jackett api key>

 

I hope you like the enhancement as much as i do, already getting value from this as two of my indexers went temporarily offline 🙂

  • Like 1
  • Thanks 1
Link to post
  • 2 weeks later...

Is there a tutorial somewhere on how to setup jackett to route through a VPN? I have PIA, and Deluge goes through it. But one of the sites jackett searches for me is Nyaa for anime. For the past 3 days I am getting an error 429 too many requests. Not sure what triggered this as I haven't downloaded anything except a couple of episodes in the time frame. I can still access the site through the browser when I turn on the VPN client. So I was hoping to just set up jackett to use the VPN so I can still get my anime. 

Link to post
1 minute ago, jebusfreek666 said:

Is there a tutorial somewhere on how to setup jackett to route through a VPN? I have PIA, and Deluge goes through it. But one of the sites jackett searches for me is Nyaa for anime. For the past 3 days I am getting an error 429 too many requests. Not sure what triggered this as I haven't downloaded anything except a couple of episodes in the time frame. I can still access the site through the browser when I turn on the VPN client. So I was hoping to just set up jackett to use the VPN so I can still get my anime. 

most probably this is due to somebody who had previously used your currently allocated vpn ip spamming Nyaa, causing them to block that specific ip, you could try restarting the vpn container, this should give you a new ip and may (assuming nobody has abused that ip) get you through the block.

Link to post
2 hours ago, binhex said:

most probably this is due to somebody who had previously used your currently allocated vpn ip 

 

No, it currently is not set up to use a VPN and I want to set it up to use PIA. I get the error when I try to access Nyaa without any VPN.

Link to post
10 hours ago, jebusfreek666 said:

 

No, it currently is not set up to use a VPN and I want to set it up to use PIA. I get the error when I try to access Nyaa without any VPN.

sorry i was skim readng and it was early :-), ok so no vpn in play, does your isp allocate you a static ip or is it dhcp?.

Link to post
13 minutes ago, binhex said:

sorry i was skim readng and it was early :-), ok so no vpn in play, does your isp allocate you a static ip or is it dhcp?.

 

Fairly certain it is static. So I could probably just change the MAC of my router and it would go through. But I figured setting up the VPN would allow for a little more privacy. And since I already have it anyway with deluge, it would be no cost.

Link to post
On 12/3/2020 at 12:29 PM, binhex said:

nope its not normal but i havent had time to track down whats causing the increase in size, after some further investigation i found out its due to nuget caching, the next image will be smaller.

Has this been fixed? I got a warning notification that my docker.img is 21.5GB and one of the discrepancies I noticed is that the Jackett image is 980MB and the container 279MB, meaning a total of 1.26GB. Does that seem right?

Link to post
23 hours ago, KnifeFed said:

Jackett image is 980MB and the container 279MB, meaning a total of 1.26GB. Does that seem right?

sounds about right to me, keep in mind that size is the total size including all intermediate images that make up jackett, so the actual size of jackett when you pull down is about 250MB not 1.2GB.

Link to post
20 hours ago, binhex said:

sounds about right to me, keep in mind that size is the total size including all intermediate images that make up jackett, so the actual size of jackett when you pull down is about 250MB not 1.2GB.

Yeah, it's got a unique size of 369MB so I guess that's all good. Thanks for confirming.

Link to post
10 hours ago, francrouge said:

hi all i'm trying to add an rss feed in qbitorrent its not working at all.

 

so far i tried 3 rss feed.

 

dont know what to do 

image.png.36a9508875943b90b891135f952a9b9b.png

any help ? please  thx

i have this working, here is what my rss feed looks like for qbittorrent rss:-

http://<host ip>:<host port>/api/v2.0/indexers/all/results/torznab/api?apikey=<my api key from jackett ui>&t=search&cat=&q=

 

Link to post
1 hour ago, binhex said:

i have this working, here is what my rss feed looks like for qbittorrent rss:-


Hi yes i have the samething.

Can you tell me if there is another torrent docker working with rss or how can i test it ?

could it be qbitorrent that is not working good ?



http://<host ip>:<host port>/api/v2.0/indexers/all/results/torznab/api?apikey=<my api key from jackett ui>&t=search&cat=&q=

 

 

Link to post

@binhex I did try to reinstall qbitorrent from scratch still having the same issue.

 

Edit: I checked the qbitorrent logs and i can only see this on the rease it failed to add rss feed:

 

Reason: The connection to the remote server timed out

 

 

Any idea ?

 

thx

Edited by francrouge
Link to post

Anyone had any issues with the latest Jackett update? I'm getting the attached error.

 

I can run other docker updates no problem, it's just Jackett so far.

 

200687103_989915225151885_4114820253298093025_n.png

Edited by skwisgaarz
Link to post
6 minutes ago, skwisgaarz said:

Anyone had any issues with the latest Jackett update? I'm getting the attached error.

no issues here, i had latest update pending so just updated and didn't encounter any issue, so i would assume your problem is probably due to docker image corruption, best to ask on docker engine topic for resolving this:- https://forums.unraid.net/forum/58-docker-engine/

Link to post
8 hours ago, francrouge said:

@binhex I did try to reinstall qbitorrent from scratch still having the same issue.

 

Edit: I checked the qbitorrent logs and i can only see this on the rease it failed to add rss feed:

 

Reason: The connection to the remote server timed out

 

 

Any idea ?

 

thx

if jackett is NOT running through qbittorrentvpn then you need to take a look at Q27. (hint application running on lan would be jackett):- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.