docker-prowlarr VS Prowlarr

Gotcha. I was going by Linuxserver's documentation on it since i mainly use their images.

# https://github.com/linuxserver/docker-prowlarr prowlarr: image: lscr.io/linuxserver/prowlarr:develop container_name: prowlarr environment: - PUID=13004 - PGID=13000 - UMASK=002 - TZ=${TIMEZONE} volumes: - ${ROOT_DIR}/docker/prowlarr-config:/config ports: - 9696:9696 restart: unless-stopped ``` From my googling I thought it might be a permissions issue but after checking that doesn't seem to be the case.

Wireguard VPN and Prowlerr

Prowlarr

Prowlarr for index management

I have it running in a docker container. I use the LinuxServer image. The image is well documented and gives docker run and docker-compose examples. It is still in beta stage, can contain bugs.

Prowlarr: Integrates content providers with Sonarr and Radarr.

Just use https://github.com/Prowlarr/Prowlarr. Thank me later.

I'm going to mention this first though because it's very important (and will save you a ton of repetition) to set up Prowlarr first to manage your indexers: https://github.com/Prowlarr/Prowlarr.

I use prowlarr to manage my trackers and cross-seed to automatically cross seed downloaded torrents.

Release available at: https://github.com/Prowlarr/Prowlarr/releases

Jackett (or Prowlarr as mentioned above) API middleware/proxy for trackers https://github.com/Jackett/Jackett https://github.com/Prowlarr/Prowlarr

Prowlarr: (A replacement for Jackett from the Arr team)

cool. It's currently gathering data, it may take a few hours to reproduce the issue. It seems it has no specific trigger to it, and all the arrs are affected. Seems a clone of this https://github.com/Prowlarr/Prowlarr/issues/435