Jump to content
linuxserver.io

[Support] Linuxserver.io - Jackett

137 posts in this topic Last Reply

Recommended Posts

43 minutes ago, CHBMB said:
1 hour ago, methanoid said:
REQ: New icon that works in both LIGHT and DARK themes wink.png

Feel free to find one and submit it.....

 

errr I did.. two years ago in this thread  ;-)  https://raw.githubusercontent.com/sdesbure/docker-containers/master/images/jackett-icon.png 

 

jackett-icon.png  Dunno why it looks white if I view that image in Chrome tab... 

Edited by methanoid

Share this post


Link to post

FYI, I was getting a lot of failed tests with the trackers. Errors indicated that it was an SSL issue. I did some digging and ran the following commands:

wget https://curl.haxx.se/ca/cacert.pem
cert-sync --user ./cacert.pem

 

It imported 132 new certificates and now all is good. Posting here to hopefully save someone else a headache.

 

Great work LinuxServer btw!

  • Like 1
  • Upvote 1

Share this post


Link to post

Is there a way to weigh the results from jackett?

 

For example.. I've got a private tracker, I would want that preferred over a public tracker..

Private-ShownameEp1 - 10 seeders - weight 10+1(1 being my preferred number) 

vs

Public-ShownameEp1 - 2 seeders - weight 2+0

 

Does this make sense or am I just asking in a profoundly stupid way?😕

 

I know theres already ways to prefer those with a minimum limit of seeders, but what about prioritizing results from A(priv) vs B(pub) ?

Share this post


Link to post
3 hours ago, tbonedude420 said:

Is there a way to weigh the results from jackett?

 

For example.. I've got a private tracker, I would want that preferred over a public tracker..

Private-ShownameEp1 - 10 seeders - weight 10+1(1 being my preferred number) 

vs

Public-ShownameEp1 - 2 seeders - weight 2+0

 

Does this make sense or am I just asking in a profoundly stupid way?😕

 

I know theres already ways to prefer those with a minimum limit of seeders, but what about prioritizing results from A(priv) vs B(pub) ?

you need to ask this on the jackett github page.

 

we don't make the app itself, we just package it in a docker image.

Share this post


Link to post
On 6/28/2018 at 4:41 PM, Av8or1ab said:

FYI, I was getting a lot of failed tests with the trackers. Errors indicated that it was an SSL issue. I did some digging and ran the following commands:


wget https://curl.haxx.se/ca/cacert.pem
cert-sync --user ./cacert.pem

 

It imported 132 new certificates and now all is good. Posting here to hopefully save someone else a headache.

 

Great work LinuxServer btw!

This didnt work for me. I added the commands above to the console for Jackett but the error remained SSL error.

Ended up using couch potato also by LinuxServer which doesnt require Jackett to work

Share this post


Link to post
On 6/29/2018 at 1:41 AM, Av8or1ab said:

FYI, I was getting a lot of failed tests with the trackers. Errors indicated that it was an SSL issue. I did some digging and ran the following commands:


wget https://curl.haxx.se/ca/cacert.pem
cert-sync --user ./cacert.pem

 

It imported 132 new certificates and now all is good. Posting here to hopefully save someone else a headache.

 

Great work LinuxServer btw!

This had a bunch of things to update, but still seem to be getting issues unfortunately. Perhaps mine is something different.

For those not 100% what to do:

  • I SSH'd into my unraid server (can probably use the 'console' in the webUI if it works for you)
  • Got the hash of the running container: docker ps | grep jackett
  • Got a shell in that container: docker exec -it 756ff4e65268 bash
  • Downloaded the CA bundle as above: wget https://curl.haxx.se/ca/cacert.pem
  • Weirdly, it wouldn't work like this, so had to rename with .crt: mv cacert.pem cacert.crt
  • Then I could import as above: cert-sync --user cacert.crt

This gave me a whole pile of output as it imported the new certificates. When I ran it again, this is what the output looks like if it had nothing to update:

root@756ff4e65268:/tmp# cert-sync --user cacert.crt
Mono Certificate Store Sync - version 5.14.0.177
Populate Mono certificate store from a concatenated list of certificates.
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.

Importing into legacy user store:
I already trust 132, your new list has 132
Import process completed.

Importing into BTLS user store:
I already trust 132, your new list has 132
Import process completed.

I restarted the Jackett container to make sure it was using the updated certificates, but I still see a bunch of errors in my logs, and the tests fail:

 

at Jackett.Server.Middleware.CustomExceptionHandler+<Invoke>d__3.MoveNext () [0x0008a] in <01c04986aa9e4ce994ffbe35ff12148b>:0 Jackett.Common.IndexerException: Exception (eztv): No route to host ---> System.Net.Http.HttpRequestException: An error occurred while sending the request ---> System.Net.WebException: Error: ConnectFailure (No route to host) ---> System.Net.Sockets.SocketException: No route to host

Share this post


Link to post

Anyone else having problems with radarr & sonarr connecting to Jackett?

 

Edit: ignore - somehow my API key changed

Edited by DZMM

Share this post


Link to post

There is an apparent memory leak associated with the Mono version of Jackett. On my unraid server I end up hitting 100% memory usage after a few days. This affects more than just Jackett (Radarr, Sonarr etc), and one proposed solution is to switch to the .netcore version of Jackett. Is that possible with this docker?

 

Source: https://github.com/Jackett/Jackett/issues/4088

Share this post


Link to post
On 12/30/2018 at 9:12 AM, Nem said:

There is an apparent memory leak associated with the Mono version of Jackett. On my unraid server I end up hitting 100% memory usage after a few days. This affects more than just Jackett (Radarr, Sonarr etc), and one proposed solution is to switch to the .netcore version of Jackett. Is that possible with this docker?

 

Source: https://github.com/Jackett/Jackett/issues/4088

The leak is getting quite bad - I'm having to restart a couple of times a day to avoid problems.  I'm probably going to have to write a quick script to do hourly in case I forget

  • Upvote 1

Share this post


Link to post
Posted (edited)
docker stats jackett

Jackett has been up for about 12hrs at this stage, seems excessive for what it needs to do.

image.thumb.png.9bd9ba25920a0fac20f093d736521535.png

 

15 min after a docker restart and with a few queries through the webUI.

image.thumb.png.d47440a8bea016fd78e578f7fb43c6e2.png

 

Edited by tjb_altf4

Share this post


Link to post

I can't seem to get the proxy setting to work, even without my privoxy docker running the jacket requests are still successful, I have -e "RUN_OPTS"="--ProxyConnection=192.168.10.10:8118" under the advanced section in jackets docker settings.

 

Seems like I had to set it on the dockers web page and apply server setting which added the following lines to my ServerConfig file

 

  "ProxyUrl": "192.168.10.10",
  "ProxyType": 0,
  "ProxyPort": 8118,
  "ProxyUsername": "",
  "ProxyPassword": "",
  "ProxyIsAnonymous": true

Edited by Spies

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now