binhex

Im unable to replicate this issue, i just tried from a clean configuration from CA and i can see from the log i get a start and if i go to the console of the container i can see the minidlna process is running, what am i missing here?

ive pushed out a new release, please pull down and let me know how you get on with it.

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.

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 1The 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=alwaysYou 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 1So 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)

Please revert back to latest and attach the /config/supervisord.log file

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.

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:

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

Hi all, the issue where the container is stopping MAY of been related to the introduction of healthchecking, this checks to see if the internet connection is operational, if not the container is marked as unhealthy and then set to shutdown the container. I have now relaxed this somewhat and if not configurd it will now simply mark the container as 'unhealthy' rather than exit, i have also introduced additional env vars to permit the user to decide what they want to healthcheck as well as the action they prefer - these env vars are new so you won't see these unless you add from CA again. So the TLDR is a new image has just been triggered by a new version of plex and this will include the above changes, so please pull down latest and give it a try and let me know.

in a word, no, a DNS leak would be your ISP allocated IP address is seen as the source ip when performing name resolution, as port 53 is not open for your LAN this is not possible, all DNS queries must be performed over the VPN tunnel and thus is leak proof.

simple, you change the port on the host side to be a non conflicting port number, for example 9119 (assuming 9119 is not in use by another container). i would suspect /mnt/disks/WDC... is not healthy or not mounted, check that you can write to it.

and that fixed the issue right?, if not follow my previous post, if that still fails then I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

Fix is in for the dos2unix.sh path issue: Go to unraid web ui/docker tab Toggle to 'advaned view (tp right) Click on 'force update' for qbittorrentvpn container and close window once downloaded Check logs and try accessing web ui.

Try changing NAME_SERVERS value to 1.1.1.1,1.0.0.1

ok that all checks out ok, can you try connecting using a different browser to rule out extension/plugin blocking, also try from another machine/device.

from your log:- 2025-07-10 16:39:29.980721 [info] VPN_PROV defined as 'pia' 2025-07-10 16:39:30.008887 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf 2025-07-10 16:39:30.041604 [info] VPN_REMOTE_SERVER defined as 'sjc-337-wg.whiskergalaxy.com' What the heck is whiskergalaxy.com?, that is not a PIA endpoint, are you using PIA VPN provider or not?.

fixed, please pull down latest.

nothing wrong in that log, all looks good, what is the ip address of the machine running the web browser?

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

that depends on the container path name you use for the bind mount for /tmp, if you named the CONTAINER path /transcode then you are set. as far as i can see, yep the rest looks ok.

I can see one issue, TRANS_DIR, this env var defines where transcodes get written to, you have defined it as /tmp, that means transcodes get written to the /tmp directory inside the container (not the host), if you want to transcode to ram then follow Q1:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md EDIT - Just spotted you also have Plex 'Transcoder temorary directory' set to /transcode, well that doesn't exist in your configuration (according to your screenshots).

i believe its now available as an option in unraid v7, sadly i cant tell you exactly where it is cos im still on v6, have a look at settings/docker in the unraid web ui it might be in there.

Are you using storage driver overlay2 for docker by any chance?, if so you probably are hitting this long standing bug/limitation:- https://github.com/docker/for-linux/issues/388

you aren't (you are running a cached old latest), please do as instructed above.

sounds like a unraid issue to me.