Giter Site home page Giter Site logo

docker-jackett's Introduction

linuxserver.io

Blog Discord Discourse Fleet GitHub Open Collective

The LinuxServer.io team brings you another container release featuring:

  • regular and timely application updates
  • easy user mappings (PGID, PUID)
  • custom base image with s6 overlay
  • weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

Find us at:

  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!
  • Discord - realtime support / chat with the community and the team.
  • Discourse - post on our community forum.
  • Fleet - an online web interface which displays all of our maintained images.
  • GitHub - view the source for all of our repositories.
  • Open Collective - please consider helping us by either donating or contributing to our budget

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

Jackett works as a proxy server: it translates queries from apps (Sonarr, SickRage, CouchPotato, Mylar, etc) into tracker-site-specific http queries, parses the html response, then sends results back to the requesting software. This allows for getting recent uploads (like RSS) and performing searches. Jackett is a single repository of maintained indexer scraping & translation logic - removing the burden from other apps.

jackett

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/jackett:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture Available Tag
x86-64 amd64-<version tag>
arm64 arm64v8-<version tag>
armhf

Application Setup

The web interface is at <your-ip>:9117 , configure various trackers and connections to other apps there. More info at Jackett.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

docker-compose (recommended, click here for more info)

---
services:
  jackett:
    image: lscr.io/linuxserver/jackett:latest
    container_name: jackett
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - AUTO_UPDATE=true #optional
      - RUN_OPTS= #optional
    volumes:
      - /path/to/jackett/data:/config
      - /path/to/blackhole:/downloads
    ports:
      - 9117:9117
    restart: unless-stopped
docker run -d \
  --name=jackett \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e AUTO_UPDATE=true `#optional` \
  -e RUN_OPTS= `#optional` \
  -p 9117:9117 \
  -v /path/to/jackett/data:/config \
  -v /path/to/blackhole:/downloads \
  --restart unless-stopped \
  lscr.io/linuxserver/jackett:latest

Parameters

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Parameter Function
-p 9117 WebUI
-e PUID=1000 for UserID - see below for explanation
-e PGID=1000 for GroupID - see below for explanation
-e TZ=Etc/UTC specify a timezone to use, see this list.
-e AUTO_UPDATE=true Allow Jackett to update inside of the container (currently recommended by Jackett and enabled by default)
-e RUN_OPTS= Optionally specify additional arguments to be passed.
-v /config Where Jackett should store its config file.
-v /downloads Path to torrent blackhole.

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

User / Group Identifiers

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker Mods

Docker Mods Docker Universal Mods

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info

  • Shell access whilst the container is running:

    docker exec -it jackett /bin/bash
  • To monitor the logs of the container in realtime:

    docker logs -f jackett
  • Container version number:

    docker inspect -f '{{ index .Config.Labels "build_version" }}' jackett
  • Image version number:

    docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/jackett:latest

Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

Via Docker Compose

  • Update images:

    • All images:

      docker-compose pull
    • Single image:

      docker-compose pull jackett
  • Update containers:

    • All containers:

      docker-compose up -d
    • Single container:

      docker-compose up -d jackett
  • You can also remove the old dangling images:

    docker image prune

Via Docker Run

  • Update the image:

    docker pull lscr.io/linuxserver/jackett:latest
  • Stop the running container:

    docker stop jackett
  • Delete the container:

    docker rm jackett
  • Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)

  • You can also remove the old dangling images:

    docker image prune

Image Update Notifications - Diun (Docker Image Update Notifier)

tip: We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-jackett.git
cd docker-jackett
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/jackett:latest .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 31.05.24: - Rebase to Alpine 3.20.
  • 11.03.24: - Rebase to Alpine 3.19. Deprecate development tag as upstream is publishing nightly stable releases.
  • 11.07.23: - Rebase to Alpine 3.18.
  • 01.07.23: - Deprecate armhf. As announced here
  • 13.02.23: - Add icu-data-full to address ICU issue with Cyrillic character sets.
  • 11.02.23: - Rebase to Alpine 3.17, migrate to s6v3.
  • 10.05.22: - Rebase to Ubuntu Focal.
  • 24.05.20: - Allow user to optionally enable auto updates.
  • 31.12.19: - Remove agressive startup chowning.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 10.03.19: - Switch to net-core builds of jackett, not dependant on mono and smaller images.
  • 11.02.19: - Add pipeline logic and multi arch.
  • 11.06.18: - Ensure root ownership of Jackett files.
  • 13.12.17: - Fix continuation lines.
  • 17.04.17: - Switch to using inhouse mono baseimage, ubuntu xenial based.
  • 09.02.17: - Rebase to alpine 3.5.
  • 29.10.16: - Call python2 from edge main to satisfy new mono dependency.
  • 14.10.16: - Add version layer information.
  • 22.09.16: - Remove autoupdate, tidy up Dockerfile.
  • 10.09.16: - Add layer badges to README.
  • 28.08.16: - Add badges to README.
  • 06.08.16: - Rebase to alpine linux for smaller image.
  • 25.01.16: - Initial Release.

docker-jackett's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docker-jackett's Issues

Problem NameResolutionFailure in jackett

i've restarted the nas where the container is stored, at the reboot i have my jackett docker, i can access the webui, but with avery test i try to do (check for update also) give me a NameResolutionFailure error in mono
i've tried to check from inside the machine if i could check the network, but ping is not present also i'm not very expert in docker and i don't know what to do

from what i can see the network config seems ok:
inside the container: mount
/dev/md1 on /etc/resolv.conf type ext4 (rw,relatime,stripe=48,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /etc/hostname type ext4 (rw,relatime,stripe=48,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /etc/hosts type ext4 (rw,relatime,stripe=48,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)

and from the hosts os:
cat /etc/resolv.conf
nameserver 8.8.4.4
nameserver 8.8.8.8
nameserver 2001:4860:4860::8888

Host OS: Asustor ADM 3.2.5
Docker: 18.03.1-ce
Portainer: 1.20.0 (only gui to manage docker)

the container is connected to bridge network in docker, i can access to the 9117 port so network works but not all

if you need more information help me to understand how to get there

EDIT: after restarting docker manually now it seems to works again...

add --NoUpdates command line flag

Starting with version v0.8.676 jackett has a new command line option --NoUpdates which will prevent any kind of self updates. I suggest you add it to the docker init options to prevent the 100% CPU bug (See #34).

Rasberry PI docker "exec format error"

linuxserver.io

I am running HASSIO on my Rasberry Pi3B+ and with portainer for docker. When I launch jackett I get:

standard_init_linux.go:190: exec user process caused "exec format error"

What could be the culprit ?

100% cpu usage (1 core) until restarted

| Host OS | LimeTech unRAID 6.3.5 |
| Template | screenshot link |
| Docker log | log link |

I'm seeing 100% cpu usage (which is 100% of the total 400%, since I have 4 cores) when Jackett is running for a while. I'm seeing this issue since I've installed Jackett (4-5 months or something). It happens around twice a week I think.

A friend of mine is also seeing this issue, so it's not limitted to my setup.

The only way to stop Jackett from using up to 100% cpu is to restart the docker container in the unRAID GUI. I've also found out that when its running at 100% cpu, other dockers, like Transmission, cannot find leechers/peers anymore, so Jackett is really hanging.

ServerConfig.json gets overwritten every time docker image is updated

Recently whenever I pull the latest version of this docker image and restart it, my ServerConfig.json file is getting overwritten with a seemingly default one. I'm losing my specific settings such as the APIKey and BasePathOverride that are preventing other containers from accessing this one.

My ServerConfig.json is stored on my Host's drive that I'm mapping to /config of this container.

I just noticed this happening in the last few weeks or so. Previously whenever this docker image got updated my config was untouched.

new version of jackett

A new version is released. Is it possible to create a new tag and release a new version version of docker.
Tks a lot

Test failed for isohunt: An error occurred while sending the request: Error: TrustFailure (Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED at /tmp/buildd/mono-5.0.1.1/external/boringssl/ssl/handshake_client.c:1132)

Docker container under Arch Linux

Created with: sudo docker create --name=jackett -v /home/docker/jackett/config:/config -v /home/docker/jackett/downloads:/downloads -e PGID=617 -e PUID=617 -e TZ=Europe/Lisbon -p 9117:9117 --restart=unless-stopped linuxserver/jackett

Can't connect to the majority of trackers with a similar message.

Jackett Crashes after a couple of days

I am not sure what to provide here as the docker logs arnt showing any errors, but every few days my sonarr/radarr installation tells me my jackett-based indexers arnt working. When I go look at jackett's UI everything seems ok except the "test" function just sits endlessly.

Once I restart the jackett container everything works again normally. Is this a known issue? Is there anything I can provide to help? Thanks!

unRAID 6.3.2

jackett

Automatic builds on every release using outdated tag

Thanks for this docker.

Due to github API's handling of pre-releases this line in your dockerfile pulls the wrong tag if it is marked as pre-release.

Would probably be better to use https://api.github.com/repos/Jackett/Jackett/tags for pulling tags.
If you do not want to use pre-releases for the main tag, could you alternatively provide a dev tag for the bleeding edge and limit automatic builds of the main tag to new releases?

Right now every tagged (pre-)release in the Jackett repo triggers a build of the main tag, using the same outdated v0.9.41, as v0.10.x releases are tagged as pre-releases.

Unable to create custom definitions

I'd like to create a custom definition for a site not supplied, but the /definitions/ folder is held within the container itself. Is it possible to map /definitions/ to a virtual folder so new sites can be added?

Integrate OpenVPN

Would it be possible to add OpenVPN support to this? Something similar to this repo.

This would allow retrieval of sites that would otherwise be blocked by ISPs, etc etc.

Error adding tracker with username and password

Am trying to add a tracker with username and password and I get a error message, a tracker without username/password am able to add.
OS: Windows 10, USER: abc, ID:911 . Docker images is made by the commands from readme
I open a console with that user and am able to create a file > touch filename
Looking in explorer i can see the files being created and the mount is good..

03-12 00:10:26 Error Exception in Configure System.Security.Cryptography.CryptographicException: Data protection failed. ---> System.Security.Cryptography.CryptographicException: Improperly protected user's key pairs in '/config/.mono/keypairs'.
at Mono.Security.Cryptography.KeyPairPersistence.get_UserPath () [0x0010d] in :0
at Mono.Security.Cryptography.KeyPairPersistence.get_Filename () [0x0006c] in :0
at Mono.Security.Cryptography.KeyPairPersistence.Load () [0x00000] in :0
at System.Security.Cryptography.RSACryptoServiceProvider.Common (System.Security.Cryptography.CspParameters p) [0x0000c] in :0
at System.Security.Cryptography.RSACryptoServiceProvider..ctor (System.Int32 dwKeySize, System.Security.Cryptography.CspParameters parameters) [0x00023] in :0
at Mono.Security.Cryptography.ManagedProtection.GetKey (System.Security.Cryptography.DataProtectionScope scope) [0x0003d] in <4e846e5e073e42a59beb6f5f871cf0f1>:0
at Mono.Security.Cryptography.ManagedProtection.Protect (System.Byte[] userData, System.Byte[] optionalEntropy, System.Security.Cryptography.DataProtectionScope scope) [0x00156] in <4e846e5e073e42a59beb6f5f871cf0f1>:0
at System.Security.Cryptography.ProtectedData.Protect (System.Byte[] userData, System.Byte[] optionalEntropy, System.Security.Cryptography.DataProtectionScope scope) [0x00030] in <4e846e5e073e42a59beb6f5f871cf0f1>:0
--- End of inner exception stack trace ---
at System.Security.Cryptography.ProtectedData.Protect (System.Byte[] userData, System.Byte[] optionalEntropy, System.Security.Cryptography.DataProtectionScope scope) [0x00051] in <4e846e5e073e42a59beb6f5f871cf0f1>:0
at Jackett.Services.ProtectionService.ProtectDefaultMethod (System.String plainText) [0x0006a] in :0
at Jackett.Services.ProtectionService.Protect (System.String plainText) [0x00011] in :0
at Jackett.Models.IndexerConfig.ConfigurationData.ToJson (Jackett.Services.IProtectionService ps, System.Boolean forDisplay) [0x00139] in :0
at Jackett.Indexers.BaseIndexer.SaveConfig () [0x00000] in :0
at Jackett.Indexers.BaseIndexer+c__asyncC.MoveNext () [0x0003d] in :0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in :0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in :0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in :0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in :0
at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in :0
at Jackett.Indexers.RevolutionTT+c__async0.MoveNext () [0x0023f] in :0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in :0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in :0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in :0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in :0
at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () [0x00000] in :0
at Jackett.Controllers.AdminController+c__async4.MoveNext () [0x00167] in :0

How to set this up on Windows

Can anyone give a layman's explanation for how to set this up on Windows? I keep seeing Linux explanations all over the web (for the past couple of hours)

I'd like to set up Jackett, change the save and log directory - and open the Web UI.

I used this guide and backtracked once, and I couldn't figure out how to set custom Windows locations, and I'm not able to access the UI.

I used the docker ps command to output this info:

PS C:\WINDOWS\system32> docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9f34df13993d linuxserver/jackett "/init" 25 minutes ago Up 25 minutes 9117/tcp, 0.0.0.0:50169->50169/tcp jackett

jenkins webhook integration broken

Hi,

the webhook to h**ps://ci.linuxserver.io/generic-webhook-trigger/invoke which should trigger new jenkins job runs when a new jackett release is released is failing with the following response:

{"status":"ok","data":{"triggerResults":{"ANY":"Did not find any jobs to trigger! The user invoking /generic-webhook-trigger/invoke must have read permission to any jobs that should be triggered. You may try adding http://user:passw@url... or configuring and passing an authentication token like ...trigger/invoke?token=TOKENHERE"}}}

Update to last

Hi I use this image to run Jackett, and I can find a way to update to the last jackette releases.

I use Debian 9 and I run Jackett Version 0.10.455.0 but v0.10.467 is up.

Thk

docker-jackett chowns mounted directories/volumes unnecessarily?

docker-jackett seems to unnecessarily “chown” mounted directories to the docker-jackett container PUID?

For example, when the docker-jackett container is started, it changes the owner of say directory X (a mounted directory in the container) to the PUID of the docker-jackett container, yet this same directory maybe also used by other docker containers (say docker-container-B) as well... this results in a strange situation where, if docker-container-B starts after the docker-jackett container and then writes to the same directory, all files are owned in the directory by docker-jackett PUID?

Using Synology Docker...

Image size is 500 mb

Does this image really need to be this big? Can we use alpine or something else lightweight instead?

Update to v0.7.1557

It will be useful if you upgrade the jackett version to at least the version v0.7.1557. Several trackers have change since.

Thanks you.

Taking a long time for docker to start.

linuxserver.io

I recently restarted my host and noticed the only thing that didn't come back up was the Jackett instance in docker. I removed it and recreated it and it took 30 minutes to an hour to start on a fresh install of the docker instance.

Ubuntu 16.04

sudo docker run -d --restart always -h jackett --name jackett -v /config:/config -v /media/Downloads:/downloads -e PGID=1001 -e PUID=111 -e TZ=America/Chicago -p 9117:9117 linuxserver/jackett:latest

[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------

User uid:    111
User gid:    1001
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...

Thanks, team linuxserver.io

Jackett starts okay, runs for a while, crashes. Recreating does not fix.

I run it in a container on an Ubuntu system along with related apps, none of which have issues. I have seen a similar bug here and the suggestion is to repull/update the image, but that hasn't worked for more than a couple hours at a time, if even.

Host OS: Ubuntu 18.04

Command line users, your run/create command, GUI/Unraid users, a screenshot of your template settings.

docker create
--name=jackett
-v /home/[redacted]/.config/Jackett:/config
-v /tmp/torrents/:/downloads
-e PGID=1000 -e PUID=1000
-e TZ="Los Angeles"
-v /etc/localtime:/etc/localtime:ro
-p 9117:9117
--restart unless-stopped
linuxserver/jackett

Docker log output, docker log

Repeated exceptions.

dockerlog.txt

Mention if you're using symlinks on any of the volume mounts.

Don't believe so. Should all be direct. Device it's writing to is external USB drive mounted under /media.

Thanks, team linuxserver.io

The log file attached is the same whether the Jackett or Docker log file.

Error: SecureChannelFailure (One or more errors occurred.) when adding IPTorrents as an indexer

When attempting to add IPTorrents as an indexer, I get the following error on screen: https://i.imgur.com/HXmawm0.png

In the logs I get the following stack trace:

	11-18 23:53:19 Error System.Net.Http.HttpRequestException: An error occurred while sending the request ---> System.Net.WebException: Error: SecureChannelFailure (One or more errors occurred.) ---> System.AggregateException: One or more errors occurred. ---> System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> Mono.Btls.MonoBtlsException: Ssl error:10000417:SSL routines:OPENSSL_internal:SSLV3_ALERT_ILLEGAL_PARAMETER
  at /build/mono-5.4.1.6/external/boringssl/ssl/tls_record.c:462
  at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x00038] in <50d80b08c1a5449282b22aedf03ce925>:0
  at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status) [0x0003c] in <50d80b08c1a5449282b22aedf03ce925>:0
  at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream:ProcessHandshake (Mono.Net.Security.AsyncOperationStatus)
  at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in <50d80b08c1a5449282b22aedf03ce925>:0
  at Mono.Net.Security.AsyncProtocolRequest+<ProcessOperation>d__24.MoveNext () [0x000ff] in <50d80b08c1a5449282b22aedf03ce925>:0
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <62f5937022004555807e6c57c33f6684>:0
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <62f5937022004555807e6c57c33f6684>:0
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <62f5937022004555807e6c57c33f6684>:0
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <62f5937022004555807e6c57c33f6684>:0
  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <62f5937022004555807e6c57c33f6684>:0
  at Mono.Net.Security.AsyncProtocolRequest+<StartOperation>d__23.MoveNext () [0x0008b] in <50d80b08c1a5449282b22aedf03ce925>:0
   --- End of inner exception stack trace ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <62f5937022004555807e6c57c33f6684>:0
  at Mono.Net.Security.MobileAuthenticatedStream+<ProcessAuthentication>d__47.MoveNext () [0x00254] in <50d80b08c1a5449282b22aedf03ce925>:0
   --- End of inner exception stack trace ---
  at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00011] in <62f5937022004555807e6c57c33f6684>:0
  at System.Threading.Tasks.Task.Wait (System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00043] in <62f5937022004555807e6c57c33f6684>:0
  at System.Threading.Tasks.Task.Wait () [0x00000] in <62f5937022004555807e6c57c33f6684>:0
  at Mono.Net.Security.MobileAuthenticatedStream.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x0000d] in <50d80b08c1a5449282b22aedf03ce925>:0
  at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) [0x0007b] in <50d80b08c1a5449282b22aedf03ce925>:0
  at System.Net.WebConnection.CreateStream (System.Net.HttpWebRequest request) [0x00073] in <50d80b08c1a5449282b22aedf03ce925>:0
   --- End of inner exception stack trace ---

(there's a lot more to it, but it doesn't seem particularly helpful)

Host OS: macOS High Sierra, but also tested on a Synology NAS

Screenshot of Jackett settings: https://i.imgur.com/KLhCBRE.png

Jackett container freezes every 6-10 hours

Docker version: 18.06.1-ce
Jackett version: v0.10.97.0
Mono version: 5.14.0.177

Hi,
Every 5-8 hours my sonarr and radarr tells me that the jackett indexrs couldnt be found, I check and cannot access to webui jacket server.

If I enter the container it seams running.
I read the logs and cant find anything that points me in the good direction.

I have auto-update disabled.

The freezes are just random.
I have docker installed on Openmediavault.

Here i post the logs.

Hope you can help me.

Thanks

Jackett log:

log.txt

Alse sonarr log if it helps

sonarr.txt

HTTP 400 on every post request from the UI

Every post request sent to jackett results in a 400 error with an empty response.
I can't even turn on the enhanced logging as the post request to update the settings fails as well.

There are no logs after Jacketts successful start and loading of the indexers.

I also checked all file permissions, they are correctly being set to 1000 on the host.

Here's my docker-compose for it:

jackett:
    container_name: jackett
    image: "linuxserver/jackett"
    restart: always
    networks:
      - torrent
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Berlin
    ports:
      - 9117:9117
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ~/gits/sonarr/config:/config
      - ~/rtorrent/torrents:/downloads

Some logs about the used versions:

12-13 22:36:50 Info Starting Jackett v0.10.504.0
12-13 22:36:50 Info Environment version: 4.0.30319.42000 (/usr/lib/mono/4.5)
12-13 22:36:50 Info OS version: Unix 4.9.0.8 (64bit OS) (64bit process)
12-13 22:36:50 Info ThreadPool MaxThreads: 800 workerThreads, 200 completionPortThreads
12-13 22:36:50 Info App config/log directory: /config/Jackett
12-13 22:36:50 Info issue: Ubuntu 16.04.5 LTS \n \l
12-13 22:36:50 Info mono version: 5.16.0.220 (tarball Mon Nov 26 17:22:46 UTC 2018)

Here's a screenshot of the failed request to enable enhanced logging:
https://vgy.me/JoVApx.png

Do you have any idea what might be going wrong?

Mono Error when start jackett since update 0.9.6.0

Hello
Since the last update to jackett (0.9.6.0), it does not start anymore and I have this error message:

07-23 00:13:40 Info Starting Jackett 0.9.6.0
07-23 00:13:40 Info Environment version: 4.0.30319.42000 (/usr/lib/mono/4.5)
07-23 00:13:40 Info OS version: Unix 3.10.105.0 (64bit OS) (64bit process)
07-23 00:13:40 Info ThreadPool MaxThreads: 400 workerThreads, 200 completionPortThreads
07-23 00:13:40 Info App config/log directory: /config/Jackett
07-23 00:13:40 Info issue: Ubuntu 16.04.3 LTS \n \l
07-23 00:13:40 Info mono version: 5.4.0.201 (tarball Fri Oct 13 21:51:45 UTC 2017)
07-23 00:13:40 Error A minimum Mono version of 5.8 is required. Please update to the latest version from http://www.mono-project.com/download/

But I have the 5.12 version of mono:

root @ mono1: / # cert-sync
Mono Certificate Store Sync - version 5.12.0.226
Populate Mono certificate store from a concatenated list of certificates.
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.
                                                                                                                  
Usage: cert-sync [--quiet] [--user] system-ca-bundle.crt
Where system-ca-bundle.crt is in PEM format

Thx for your help
Thierry

linuxserver.io

Synology DS6.2

07-23 00:13:40 Info Starting Jackett 0.9.6.0
07-23 00:13:40 Info Environment version: 4.0.30319.42000 (/usr/lib/mono/4.5)
07-23 00:13:40 Info OS version: Unix 3.10.105.0 (64bit OS) (64bit process)
07-23 00:13:40 Info ThreadPool MaxThreads: 400 workerThreads, 200 completionPortThreads
07-23 00:13:40 Info App config/log directory: /config/Jackett
07-23 00:13:40 Info issue: Ubuntu 16.04.3 LTS \n \l
07-23 00:13:40 Info mono version: 5.4.0.201 (tarball Fri Oct 13 21:51:45 UTC 2017)
07-23 00:13:40 Error A minimum Mono version of 5.8 is required. Please update to the latest version from http://www.mono-project.com/download/

Thanks, team linuxserver.io

Save Jackett settings in container

Hi, perhaps more of a question than an issue, perhaps more related to me being unfamiliar with Docker, too.

How does one retain the Jackett settings? Whenever I stop and restart the container (in my Synology), the Jackett config is gone. I can't find this information anywhere in the README nor documentation.

Thanks!

unable to pull your image

when I try docker pull linuxserver/jackett
it result an error

docker pull linuxserver/jackett
Using default tag: latest
latest: Pulling from linuxserver/jackett
4e2e76526c94: Already exists
9b420d767d74: Already exists
71becf26860f: Already exists
a3b46a5e0012: Already exists
703787483247: Already exists
4431a105bf56: Already exists
3e57e8ce0540: Already exists
140b510e4841: Already exists
00e44ad23245: Already exists
1aa29ca7bbe5: Extracting 4.524MB/4.524MB
09ccdb48553d: Download complete
failed to register layer: ApplyLayer exit status 1 stdout: stderr: Container ID 197121 cannot be mapped to a host ID

I run a bunch of image from linuxserver and others without any issue

the error is not present if I pull : linuxserver/jackett:90

A minimum Mono version of 5.8 is required

07-15 05:05:57 Info Starting Jackett 0.9.6.0                                                                                  
07-15 05:05:57 Info Environment version: 4.0.30319.42000 (/usr/lib/mono/4.5)                                                  
07-15 05:05:57 Info OS version: Unix 3.10.105.0 (64bit OS) (64bit process)                                                    
07-15 05:05:57 Info ThreadPool MaxThreads: 400 workerThreads, 200 completionPortThreads                                       
07-15 05:05:57 Info App config/log directory: /config/Jackett                                                                 
07-15 05:05:57 Info issue: Ubuntu 16.04.3 LTS \\n \\l                                                                           
07-15 05:05:57 Info mono version: 5.4.1.6 (tarball Wed Nov  8 20:37:08 UTC 2017)                                              
07-15 05:05:57 Error A minimum Mono version of 5.8 is required. Please update to the latest version from http://www.mono-project.com/download/                                                                                                              

Jackett starts, but after a day or two crashes [Restarting fixes it for sometime]

Host OS is: Ubuntu Server 18.04 x64
My docker-compose file snippet:

jackett:
    image: linuxserver/jackett
    container_name: jackett
    volumes:
     - /etc/localtime:/etc/localtime:ro
     - /opt/docker/appdata/jackett:/config
    ports:
     - 27027:9117
    expose:
     - "9117"
    environment:
     - PUID=111
     - GUID=113
     - TZ=Europe/Helsinki

Docker log can be found at: https://p.kapsi.fi/?2945f2222bde8140#fNVjksAEliw9hxaV3+7bGq77XIF0wLuDft1OUyTUTno=

This is fixed by just restarting the container usually, but I have no idea why it's happening to begin with.

Output of docker inspect -f '{{ index .Config.Labels "build_version" }}' jackett:

Linuxserver.io version:- 343 Build-date:- December-01-2018-19:36:28-UTC

Output of docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/jackett:

Linuxserver.io version:- 343 Build-date:- December-01-2018-19:36:28-UTC

Related issue: Jackett/Jackett#4283

Add the ability to set a proxy

Jackett has a command line option to use a proxy server but this is not currently exposed in the docker as a variable

-j, --ProxyConnection use proxy - e.g. 127.0.0.1:8888

Not starting up on a raspberry pi

I'm running this in a docker container on a raspberry pi 3 getting the following error in the logs when ever I start it up

standard_init_linux.go:190: exec user process caused "exec format error",
standard_init_linux.go:190: exec user process caused "exec format error",
standard_init_linux.go:190: exec user process caused "exec format error",
standard_init_linux.go:190: exec user process caused "exec format error",
standard_init_linux.go:190: exec user process caused "exec format error",
standard_init_linux.go:190: exec user process caused "exec format error",

the configuratoin is the follwoing

docker create --name=jackett
--restart=always
-v /home/docker/jackett/config:/config
-v /home/docker/jackett/downloads:/downloads
-e PGID=1000 -e PUID=1000
-e TZ=/etc/localtime:/etc/localtime:ro
-p 82:9117
linuxserver/jackett

the image
Linuxserver.io version:- 357 Build-date:- December-18-2018-19:13:59-UTC

Jackett not starting on Synology, access to the path "/config/Jackett" is denied

When using the linuxserver/jackett docker image on Synogoly, I'm getting high CPU usage, and Jackett isn't available on the port. Looking at the logs it says Access to the path \"/config/Jackett\" is denied..

Synology: DS218+

To create the docker container:

docker create \
  --name=jackett \
  -v /volume1/media/jackett/config:/config \
  -v /volume1/media/downloads:/downloads \
  -e PGID=1024 -e PUID=100 \
  -e TZ=Europe/Amsterdam \
  -p 9117:9117 \
  linuxserver/jackett

I've provided the -e PGID=1024 -e PUID=100 flags, and looking at the logs I see:

User uid:    100
User gid:    102

Could it have something to do with an incorrect gid, messing up the permissions?

Part of the logs:

-------------------------------------
          _     _ _
         | |___| (_) ___
         | / __| | |/ _ \
         | \__ \ | | (_) |
         |_|___/ |_|\___/
               |_|

Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------

User uid:    100
User gid:    102
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
12-16 16:29:00 Error Top level exception Autofac.Core.DependencyResolutionException: An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = ServerService (ReflectionActivator), Services = [Jackett.Services.Interfaces.IServerService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = IndexerManagerService (ReflectionActivator), Services = [Jackett.Services.Interfaces.IIndexerManagerService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = IndexerConfigurationService (ReflectionActivator), Services = [Jackett.Services.Interfaces.IIndexerConfigurationService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = ConfigurationService (ReflectionActivator), Services = [Jackett.Services.Interfaces.IConfigurationService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An exception was thrown while invoking the constructor 'Void .ctor(ISerializeService, IProcessService, Logger, RuntimeSettings)' on type 'ConfigurationService'. ---> Could not create settings directory. Access to the path "/config/Jackett" is denied. (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) ---> Autofac.Core.DependencyResolutionException: An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = IndexerManagerService (ReflectionActivator), Services = [Jackett.Services.Interfaces.IIndexerManagerService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = IndexerConfigurationService (ReflectionActivator), Services = [Jackett.Services.Interfaces.IIndexerConfigurationService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = ConfigurationService (ReflectionActivator), Services = [Jackett.Services.Interfaces.IConfigurationService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An exception was thrown while invoking the constructor 'Void .ctor(ISerializeService, IProcessService, Logger, RuntimeSettings)' on type 'ConfigurationService'. ---> Could not create settings directory. Access to the path "/config/Jackett" is denied. (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) ---> Autofac.Core.DependencyResolutionException: An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = IndexerConfigurationService (ReflectionActivator), Services = [Jackett.Services.Interfaces.IIndexerConfigurationService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = ConfigurationService (ReflectionActivator), Services = [Jackett.Services.Interfaces.IConfigurationService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An exception was thrown while invoking the constructor 'Void .ctor(ISerializeService, IProcessService, Logger, RuntimeSettings)' on type 'ConfigurationService'. ---> Could not create settings directory. Access to the path "/config/Jackett" is denied. (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) ---> Autofac.Core.DependencyResolutionException: An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = ConfigurationService (ReflectionActivator), Services = [Jackett.Services.Interfaces.IConfigurationService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An exception was thrown while invoking the constructor 'Void .ctor(ISerializeService, IProcessService, Logger, RuntimeSettings)' on type 'ConfigurationService'. ---> Could not create settings directory. Access to the path "/config/Jackett" is denied. (See inner exception for details.) (See inner exception for details.) ---> Autofac.Core.DependencyResolutionException: An exception was thrown while invoking the constructor 'Void .ctor(ISerializeService, IProcessService, Logger, RuntimeSettings)' on type 'ConfigurationService'. ---> Could not create settings directory. Access to the path "/config/Jackett" is denied. (See inner exception for details.) ---> System.Exception: Could not create settings directory. Access to the path "/config/Jackett" is denied.

How to update jackett?

Hi,
I wanted to know if the bug in ticket #44 is still here.
There is some way to update jackett without dowloading the docket image again?

Indexer configuration is lost if container gets removed

If the jackett container gets removed/recreated the previous configuration can not be restored. You have to update the password fields for each of the indexer to get jackett working again.
See: Jackett/Jackett#361
Works great however with this image: https://github.com/tyler43636/unraid-jackett

Error message from docker logs:

Error Failed loading configuration for RandomIndexer, you must reconfigure this indexer System.Security.Cryptography.CryptographicException: Padding is invalid and cannot be removed.
  at System.Security.Cryptography.RijndaelManagedTransform.DecryptData (System.Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount, System.Byte[]& outputBuffer, Int32 outputOffset, PaddingMode paddingMode, Boolean fLast) <0x7f405e8430c0 + 0x00f88> in <filename unknown>:0
  at System.Security.Cryptography.RijndaelManagedTransform.TransformFinalBlock (System.Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount) <0x7f405e841a10 + 0x001d0> in <filename unknown>:0
  at System.Security.Cryptography.CryptoStream.FlushFinalBlock () <0x7f405e837c50 + 0x00044> in <filename unknown>:0
  at System.Security.Cryptography.CryptoStream.Dispose (Boolean disposing) <0x7f405e839720 + 0x00030> in <filename unknown>:0
  at System.IO.Stream.Close () <0x7f405e7c93d0 + 0x00019> in <filename unknown>:0
  at Jackett.Services.ProtectionService.UnProtectDefaultMethod (System.String plainText) <0x4197faf0 + 0x00318> in <filename unknown>:0
  at Jackett.Services.ProtectionService.UnProtect (System.String plainText) <0x4197fa70 + 0x00043> in <filename unknown>:0
  at Jackett.Models.IndexerConfig.ConfigurationData.LoadValuesFromJson (Newtonsoft.Json.Linq.JToken json, IProtectionService ps) <0x4197e000 + 0x002f5> in <filename unknown>:0
  at Jackett.Indexers.BaseIndexer.LoadFromSavedConfiguration (Newtonsoft.Json.Linq.JToken jsonConfig) <0x4196dbd0 + 0x0005f> in <filename unknown>:0
  at Jackett.Services.IndexerManagerService.InitIndexers () <0x4195fcf0 + 0x00216> in <filename unknown>:0

Massive log file size.

Jackett eats a good amount of space in log files.
Is it possible to add logrotate to jackett log files within the container?

Armhf version

Hi,

Could you please create an official armhf version? This pairs well with sonarr!

Thanks,
Jon

After a couple of days, jackett keeps restarting

linuxserver.io

Debian 8

 uname -a
Linux xxx.com 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux

Docker log:

02-28 12:19:35 Info Loading Cardigann definition /app/Jackett/Definitions/trancetraffic.yml 
02-28 12:19:35 Info Loading Cardigann definition /app/Jackett/Definitions/uhdbits.yml 
02-28 12:19:35 Info Loading Cardigann definition /app/Jackett/Definitions/ultrahdclub.yml 
02-28 12:19:35 Info Loading Cardigann definition /app/Jackett/Definitions/utorrents.yml 
02-28 12:19:35 Info Loading Cardigann definition /app/Jackett/Definitions/worldofp2p.yml 
02-28 12:19:35 Info Loading Cardigann definition /app/Jackett/Definitions/xtremezone.yml 
02-28 12:19:35 Info LibCurl init Ok 
02-28 12:19:35 Info LibCurl version libcurl/7.52.1 LibreSSL/2.4.4 zlib/1.2.8 libssh2/1.7.0 
02-28 12:19:35 Info Starting web server at http://*:9117/ 
02-28 12:19:36 Info set HttpListener.IgnoreWriteExceptions = true 
02-28 12:19:36 Error Address already in use: Most likely Jackett is already running. 
02-28 12:19:40 Info App config/log directory: /config/Jackett 
02-28 12:19:40 Info Starting Jackett 0.7.1090.0 
02-28 12:19:40 Info Environment version: 4.0.30319.42000 (/usr/lib/mono/4.5) 
02-28 12:19:40 Info OS version: Unix 3.16.0.4 (64bit OS) (64bit process) 
02-28 12:19:40 Info ThreadPool MaxThreads: 400 workerThreads, 400 completionPortThreads 
02-28 12:19:40 Info issue: Welcome to Alpine Linux 3.5 
02-28 12:19:40 Info mono version: 4.6.1 (Stable 4.6.1.5/ef43c15 Thu Oct 27 15:59:40 GMT 2016) 
02-28 12:19:40 Info Using HTTP Client: UnixLibCurlWebClient 
02-28 12:19:41 Info Loading Cardigann definitions from: /config/cardigann/definitions/ 
02-28 12:19:41 Info Loading Cardigann definitions from: /etc/xdg/cardigan/definitions/ 
02-28 12:19:41 Info Loading Cardigann definitions from: /app/Jackett/Definitions 
02-28 12:19:41 Info Loading Cardigann definition /app/Jackett/Definitions/2fast4you.yml 
02-28 12:19:42 Info Loading Cardigann definition /app/Jackett/Definitions/acidlounge.yml 

Just to note again, I see the issue of the port being used, but it makes no sense. Is supervisord just restarting after a couple of days for the sake of it?
Stopping the container and restart it, makes it work for the next couple of days (I don't know the exact number of days or hours.)

Not using symlinks afaik

PUID/PGID are being ignored

I am running a Jackett container under Synology.
I set both PUID and PGID, snippet from docker container inspect:
"Env": [
"PUID=1029",
"PGID=100",
"TZ=Asia/Tel_Aviv"
],

I also made sure the user exists:
$ id jackett
uid=1029(jackett) gid=100(users) groups=100(users)

But, when I look at the logs I see:
2018-03-22 12:47:10 | stdout | -------------------------------------
2018-03-22 12:47:10 | stdout | GID/UID
2018-03-22 12:47:10 | stdout | -------------------------------------
2018-03-22 12:47:10 | stdout |  
2018-03-22 12:47:10 | stdout | User uid:    0
2018-03-22 12:47:10 | stdout | User gid:    0
2018-03-22 12:47:10 | stdout | -------------------------------------

Libcurl failed to initialize

I've been using Jackett without issue for a long time, but recently it has stopped working after I updated the image.

Host OS: Synology DSM 6
Created using DSM docker manager

12-12 11:29:52 Info Adding aggregate indexer 
12-12 11:29:52 Warn Libcurl failed to initalize. Did you install it? 
12-12 11:29:52 Warn Debian: apt-get install libcurl4-openssl-dev 
12-12 11:29:52 Error Top level exception System.DllNotFoundException: libcurl
  at Jackett.Utils.Clients.UnixLibCurlWebClient.Init () [0x0008a] in <0f6344813a0d49efa2c0dd536a9ad71a>:0 
  at Jackett.Services.ServerService.Initalize () [0x003e0] in <0f6344813a0d49efa2c0dd536a9ad71a>:0 
  at JackettConsole.Program.Main (System.String[] args) [0x0058a] in <57581ca9af78422ab46352f25efa2bc3>:0 

I was able to resolve by executing apk add curl-dev inside the running container.

Cannot access API though CouchPotato or Torznab

I use:
Synology DSM 5.2

I run this command:
docker run --restart always --name jackett -h jackett -p 9117:9117 -d -v /volume1/docker/jackett/config:/config -v /volume1/docker/jackett/downloads:/downloads linuxserver/jackett:38

CouchPotato Error:
[hpotato.core.plugins.base] Failed opening url in TorrentPotato: http://192.168.10.8:9117/potato/avistaz?imdbid=tt4195368&search=Flying+Colors+2015&user=&passkey=xxx&search=Flying+Colors+2015&user=&passkey=xxx

Sonarr Error:
17-1-15 12:18:53.2|Warn|Torznab|Unable to connect to indexer

[v2.0.0.4472] System.Net.WebException: The request timed out
at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00065] in /spksrc/native/mono/work-native/mono-3.10.0/mcs/class/System/System.Net/HttpWebRequest.cs:971
at System.Net.HttpWebRequest.GetResponse () [0x0000e] in /spksrc/native/mono/work-native/mono-3.10.0/mcs/class/System/System.Net/HttpWebRequest.cs:985
at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x000fe] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:61

17-1-15 12:18:53.3|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:
-- Unable to connect to indexer, check the log for more details

Docker version 44 downloads old version of Jackett ( 0.7.1006.0 )

Jackett docker file version (Linuxserver.io version:- 44 Build-date:- February-10-2017-23:48:27-UTC) downloads old version of Jackett ( 0.7.1006.0 )

linuxserver.io

Ubuntu 16.04.2 LTS

sudo docker run --restart=always --name=jackett -v /docker/jackett/config:/config -v /docker/jackett/downloads:/downloads -e TZ=Europe/Prague -p 9117:9117 linuxserver/jackett

http://pastebin.com/VYjfg3FB

image hash:
sha256:e588088688699b02eeac469d8982a927981f4e1459f8c3661e97018db7edd82e

Thanks, team linuxserver.io

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.