2 minutes ago, wgstarks said:

The Prowlarr docker allows for certain health checks. If you are not familiar with the process I would recommend just using the defaults (leave the fields blank).

It does not allow me to apply and start the container without something being there

Edited July 17, 2025Jul 17 by Sinister

1 hour ago, Sinister said:

It does not allow me to apply and start the container without something being there

What repository is that from?

I suspect you are trying to install some docker other than binhex-prowlarr (maybe linuxserver’s prowlarr). If that’s the case you can go to the listing for that docker in the apps tab and click the “Support” link. It will take you to the proper support forum.

If I’m wrong my apologies and perhaps @binhex can assist you.

Looks like a recent change that wasn't meant to be set to required.
Either those 2 variables should be set to Required=no, or removed completely.

Edited July 17, 2025Jul 17 by tjb_altf4

2 hours ago, tjb_altf4 said:

Looks like a recent change that wasn't meant to be set to required.
Either those 2 variables should be set to Required=no, or removed completely.

My bad, they should be set to required=no, I shall fix this up shortly.

EDIT - done.

7 hours ago, Sinister said:

It does not allow me to apply and start the container without something being there

To work aorund your issue you can either wait a couple of hours for the templates to update and create it again from Community Applications (CA), or toggle 'advanced view' (top right), click on edit for the healthcheck env vars and set the dropdown to 'required' as 'no' and save, like so, do the same for both healthheck env vars:

5 hours ago, wgstarks said:

If I’m wrong my apologies and perhaps @binhex can assist you.

FYI - It's new functionality, primarily aimed at detecting internet outage and potentially (if set by the user) allowing the container to auto restart, this can also come in handy when sharing the network of another container, such as VPN containers.

1 hour ago, binhex said:

FYI - It's new functionality, primarily aimed at detecting internet outage and potentially (if set by the user) allowing the container to auto restart, this can also come in handy when sharing the network of another container, such as VPN containers.

Is there info somewhere for the possible values? I’d like to add the variables to my container.

13 minutes ago, wgstarks said:

Is there info somewhere for the possible values? I’d like to add the variables to my container.

The value for both can be literally anything you want (thus no default), if you want to monitor the application then you could do something like:

# this will mark the container as unhealthy if the process name Prowlarr is not found (crash)
HEALTHCHECK_COMMAND = pgrep Prowlarr
HEALTHCHECK_ACTION = exit 1

The above would mean you would need to keep an eye on the health of the container, if it becomes 'unhealthly' then you would need to manually restart the container, so if you want something more automated then you could do the following:

# this will stop the container if prowlarr dies.
HEALTHCHECK_COMMAND = pgrep Prowlarr
HEALTHCHECK_ACTION = kill 1 # will kill pid 1 and thus the container will stop) 

# Note: If you want the container to auto restart then set in the extra parameters --restart=always

You could even extend this and send yourself a message via something like ntfy if the process dies:

HEALTHCHECK_COMMAND = pgrep Prowlarr
HEALTHCHECK_ACTION = curl -s -d "Prowlarr is down, restarting container..." "ntfy.sh/<my ntfy topic>" ; kill 1

So as you can see its quite flexible, it all depends on what you want to monitor and what action you want to take.

The default is to monitor internet connectivity and if the internet connection goes down for the container then mark it as unhealthy (exit 1).

Note: The Prowlarr image has not been rebuilt for a while due to lack of new releases and thus the new healthcheck functionality i have built in will not be there, so the above env var's will not do anything until a new image is pushed out (new prowlarr version)

I would want to monitor the VPN connection and restart the container on failure, possibly after a time delay. I’ll wait for the container update.

Is this a feature you plan to add to all your containers eventually?

2 minutes ago, wgstarks said:

Is this a feature you plan to add to all your containers eventually?

Its already code complete and pushed, it just requires a rebuild of the image, so this will naturally roll out as new releases are pushed out and the image is rebuilt.

I am running Unraid 7.1.4:

• binhex-delugevpn without internal ports or other changes. Privoxy enabled via PIA on 8118

• prowlarr running with indexers proxied to port 8118.

• prowlarr proxy set to same settings as indexer so I can do searches from within prowlarr. I have ignored my local IP in the proxy settings as well.

Testing via curl ifconfig.io in the console for delugevpn shows the vpn ip address I expect.

Testing in the console for prowlarr shows my public ip address.

Why doesn't prowlarr console show the vpn address to confirm it is configured as expected? I was hoping to do the same proxy settings with all the arrs.

If this isn't expected behavior, any ideas how to fix?

17 hours ago, danimal_0119 said:

Why doesn't prowlarr console show the vpn address to confirm it is configured as expected?

This is expected behavior, see Q18 in the faq:

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Any news on when it will be updated to V2 (2.0.5.5160)? TrashGuides and indexers are recommending we update to v2 ASAP due to breaking changes.

14 minutes ago, iZChae said:

Any news on when it will be updated to V2 (2.0.5.5160)? TrashGuides and indexers are recommending we update to v2 ASAP due to breaking changes.

Binhex's releases are automated, looks like the source arch package still needs to be updated.

Given 2.0.5.5160 is 3 days old, seems odd that not upgrading would create breaking changes... guessing the breaks are going to happen on the other *Arrs

18 minutes ago, iZChae said:

Any news on when it will be updated to V2 (2.0.5.5160)? TrashGuides and indexers are recommending we update to v2 ASAP due to breaking changes.

i see the issue, i had switched over upstream package name to add in arm suport but forgotten to update my python trigger script, this is now fixed and a new image has been manually pushed out, please update at your convienience.

Note:- As notes this is a major bump from v1 to v2 so there MAY be breaking changes here!.

16 minutes ago, tjb_altf4 said:

Binhex's releases are automated, looks like the source arch package still needs to be updated.

You were quite right i was targeting aur package prowlarr, i have now switched over to prowlarr-bin, its smaller and faster to build and allows me to push out an arm variant as well, so the new v2 image is now available.

3 hours ago, binhex said:

i see the issue, i had switched over upstream package name to add in arm suport but forgotten to update my python trigger script, this is now fixed and a new image has been manually pushed out, please update at your convienience.

Note:- As notes this is a major bump from v1 to v2 so there MAY be breaking changes here!.

Thank you for the quick turn around.

I am having an issue adding the Unraid Tailscale integration with my Prowlarr install. Prowlarr has been up and running for a long time with no issue. When I try to enable tailscale, it doesn't install, here is the log:

Executing Unraid Docker Hook for Tailscale

Detecting Package Manager...

Detected pacman Package Manager!

Installing packages...

Please wait...

ERROR: Installing packages!

:: Synchronizing package databases...

core downloading...

extra downloading...

error: failed retrieving file 'extra.db' from europe.archive.pkgbuild.com : Could not resolve host: europe.archive.pkgbuild.com

warning: fatal error from europe.archive.pkgbuild.com, skipping for the remainder of this transaction

error: failed retrieving file 'core.db' from europe.archive.pkgbuild.com : Failed to connect to europe.archive.pkgbuild.com port 443 after 4264 ms: Could not connect to server

error: failed retrieving file 'core.db' from america.archive.pkgbuild.com : Could not resolve host: america.archive.pkgbuild.com

warning: fatal error from america.archive.pkgbuild.com, skipping for the remainder of this transaction

error: failed retrieving file 'extra.db' from america.archive.pkgbuild.com : Failed to connect to america.archive.pkgbuild.com port 443 after 72 ms: Could not connect to server

error: failed retrieving file 'extra.db' from asia.archive.pkgbuild.com : Could not resolve host: asia.archive.pkgbuild.com

warning: fatal error from asia.archive.pkgbuild.com, skipping for the remainder of this transaction

error: failed retrieving file 'core.db' from asia.archive.pkgbuild.com : Failed to connect to asia.archive.pkgbuild.com port 443 after 72 ms: Could not connect to server

error: failed to synchronize all databases (failed to retrieve some files)

ERROR: Unraid Docker Hook script throw an error!

Starting container without Tailscale!

Starting container...

All my other Tailscale enable containers are fine. No idea how to move forward here.

13 hours ago, arkestler said:

I am having an issue adding the Unraid Tailscale integration with my Prowlarr install. Prowlarr has been up and running for a long time with no issue

pull down the latest image, this should fix the tailscale integration

9 hours ago, binhex said:

pull down the latest image, this should fix the tailscale integration

That did the trick! Thank you!

Hey Binhex, i was hoping to pull the latest dev build to add the new AnimeZ indexer but it doesn't look like you've got a tag for it. Do you plan on making a dev release tag?

https://github.com/Prowlarr/Prowlarr/tree/v2.3.4.5307

5 minutes ago, BlastMaster3000 said:

Hey Binhex, i was hoping to pull the latest dev build to add the new AnimeZ indexer but it doesn't look like you've got a tag for it. Do you plan on making a dev release tag?

https://github.com/Prowlarr/Prowlarr/tree/v2.3.4.5307

Sorry, nope, i only include latest releases to keep support down to a minimum.

I recently started getting a "bad parameter" execution error when I try to start the docker. I did recently update to 7.2.5 so don't know if it's maybe an issue with the latest stable release? I have the docker routed through binhex-delugevpn (I think I followed spaceinvader's video when I originally set it up), but it hasn't given me issues in the past.

tower-diagnostics-20260507-1829.zip

Edited May 8May 8 by jmcskis

1 minute ago, jmcskis said:

I recently started getting a "bad parameter" execution error when I try to start the docker. I did recently update to 7.2.5 so don't know if it's maybe an issue with the latest stable release? I have the docker routed through binhex-delugevpn (I think I followed spaceinvader's video when I originally set it up), but it hasn't given me issues in the past.

There have been multiple reports of this issue with multiple dockers after the 7.2.5 release. In my case I just have to change any setting and revert the change and apply the same settings I started with. Some people have reported that they actually had a port set to 0000 and they had to change it to the correct setting.