[Support] Linuxserver.io - Jackett


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
Link to comment
  • 1 month later...

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
Link to comment

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) ?

Link to comment
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.

Link to comment
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

Link to comment
  • 2 weeks later...
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

Link to comment
  • 1 month later...
  • 3 weeks later...
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
Link to comment
  • 2 weeks later...

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
Link to comment
  • 2 months later...
On 10/11/2018 at 5:23 PM, devalias said:

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

 

I'm getting the SSL error, and none of my trackers are working with Jackett. I have seen a few updates since this problem started, and none have fixed it.

 

I couldn't get this above method to work.

 

Deleting the proxy URL in the Jackett settings allows everyting to work, but obviously it would be better if this traffic went through a proxy... Maybe I'll try another Jackett docker.

Link to comment
9 hours ago, III_D said:

Deleting the proxy URL in the Jackett settings allows everyting to work, but obviously it would be better if this traffic went through a proxy... Maybe I'll try another Jackett docker.

if you are using a socks proxy then its currently broken (and worst still, ip leaking according to comment in ui), see here:-

 

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

 

and here (proxy causes mem leak)

 

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

Edited by binhex
Link to comment
  • 3 weeks later...
On 4/3/2019 at 6:51 AM, tjb_altf4 said:

If PIA sock5 is broken, you could always spin up PrivoxyVPN and proxy to your pia vpn.

That's how my jackett has been setup for quite some time, albeit with DelugeVPN, but same same.

 

Thanks tjb! The fix for me was in this response, but I did not understand it at first, so I will clarify for others.

 

Yes, using the SOCKS5 proxy feature within Jackett (and Sonarr, and Radarr...) DIRECTLY, ie. using the credentials for PIA within each of these dockers, was broken. It had previously caused persistent memory leaks, and more recently caused Jackett to stop working altogether due to SSL errors.

 

The fix: within the excellent (thanks Binhex!) DelugeVPN there is a built-in Privoxy feature (ENABLE_PRIVOXY = yes). Enabling this, and then pointing each of the other dockers to use that http proxy, fixes both the SSL error and also the memory leaks.

 

SpaceinvaderOne has a good Youtube video on how to set up Privoxy https://www.youtube.com/watch?v=2MNqonB86ec

 

Thanks guys

III_D 

Link to comment
  • 2 weeks later...

I'm having this weird issue for quite some time. Says the indexers are not available in sonarr or Radarr, it fixes on its own, but I noticed this weird errors in the jackett logs. Is this normal?

 

at Jackett.Common.Indexers.BaseWebIndexer.ResultsForQuery(TorznabQuery query) in /home/appveyor/projects/jackett/src/Jackett.Common/Indexers/BaseIndexer.cs:line 815
at Jackett.Common.Services.IndexerManagerService.TestIndexer(String name) in /home/appveyor/projects/jackett/src/Jackett.Common/Services/IndexerManagerService.cs:line 222
at Jackett.Server.Controllers.IndexerApiController.Test() in /home/appveyor/projects/jackett/src/Jackett.Server/Controllers/IndexerApiController.cs:line 128
at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync()
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter()
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync()
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync()
at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
at Jackett.Server.Middleware.CustomExceptionHandler.Invoke(HttpContext httpContext) in /home/appveyor/projects/jackett/src/Jackett.Server/Middleware/CustomExceptionHandler.cs:line 29

Link to comment
2 hours ago, gacpac said:

I'm having this weird issue for quite some time. Says the indexers are not available in sonarr or Radarr, it fixes on its own, but I noticed this weird errors in the jackett logs. Is this normal?

 

at Jackett.Common.Indexers.BaseWebIndexer.ResultsForQuery(TorznabQuery query) in /home/appveyor/projects/jackett/src/Jackett.Common/Indexers/BaseIndexer.cs:line 815
at Jackett.Common.Services.IndexerManagerService.TestIndexer(String name) in /home/appveyor/projects/jackett/src/Jackett.Common/Services/IndexerManagerService.cs:line 222
at Jackett.Server.Controllers.IndexerApiController.Test() in /home/appveyor/projects/jackett/src/Jackett.Server/Controllers/IndexerApiController.cs:line 128
at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync()
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter()
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync()
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync()
at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
at Jackett.Server.Middleware.CustomExceptionHandler.Invoke(HttpContext httpContext) in /home/appveyor/projects/jackett/src/Jackett.Server/Middleware/CustomExceptionHandler.cs:line 29

I think I fixed it. 

 

Looks like this docker doesn't have Microsoft .NET library by default so I checked in the github for Jackett and installed from there.

 

"Install on Linux (AMDx64) "

On most operating systems all the required dependencies will already be present. In case they are not, you can refer to this page https://docs.microsoft.com/en-us/dotnet/core/linux-prerequisites?tabs=netcore2x#linux-distribution-dependencies

 

If someone is having the same issue I opened the command line and ran this commands

1.  apt-get update

2. apt-get install libunwind-dev

3. wget https://dot.net/v1/dotnet-install.sh

 

When it's done restart the container and errors no more. 

 

Link to comment
1 minute ago, Squid said:

Just so you know, you will have to redo those steps whenever you update the container.

I thought about it 🤣 But I had to get rid of the annoying message. 

 

Maybe this could be fixed in a next build? Unless I need to do something on my end. 

Link to comment
On 5/5/2019 at 4:21 PM, Squid said:

Just so you know, you will have to redo those steps whenever you update the container.

I just updated the docker today and I'm not getting the errors. Looks like they fixed it on this release. 

Thanks everyone :D

Link to comment

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.