binhex

That is actually a reasonably simple problem to fix, there is a script that is executed on startup of unraid, its located at '/boot/config/go' if the file doesnt exist then create it, then drop in whatever you want to run on startup, do note though you cannot directly run scripts from the usb key any more, if you need to do this then the go file will have to copy any scripts you want to run onto the os filesystem or array and then execute from there. why not keep things simple and use something like rsync?, you can run rsync either from unraid or from your backup server, it supports full mirroring, diffs or incremental so should suffice, and yes you would need to put in a bit of effort to work out the flags, but once set it should just chug along on its own with zero effort - its what i use for backing up from unraid to another device on my lan.

OK ended up reworking the script quite a bit, so audio (radio) support is now in, if you want to use it then pull down the new image and then add a new 'variable' to your container named 'AUDIO_SHOWS_NAME' to specify the name of the show, and if you want to use the show PID then add variable 'AUDIO_SHOWS_PID' (new users will have these already created).

you could stop the container then restore from backup /config/sonarr.db* and /config/logs.db* then start the container.

Is this container using a network of another container? if not then set this to no (the default).

Totally forgot about this!, i shall see if i can get some time in the next couple of days to add this in, should be simple enough.

You can specify the custom jar path as @deusxanime suggested, or you can roll back to a specific version of the docker image using a docker tag, see Q5. https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Sure, i need to document this, so SHARED_NETWORK variable is used when you are sharing the networking of another container, for example a VPN enabled container with this container. This sets up a monitor that checks the VPN containers network and if it goes down then it also shuts down this container. To be clear this is not related to any potential IP leakage, it is purely to ensure that the container will get correctly shutdown when the VPN container is shutdown to prevent the nasty UNRAID Web UI issue, where UNRAID has a hissy fit and keeps attempting to restart the container that was using the VPN network, and as the network no longer exists it keeps on restarting in a loop, this MAY be better handled in v7 (not tested), but i know it was definitely not handled correctly in prior versions of UNRAID. One final note on this, SHARED_NETWORK only works when sharing the network of one of my VPN enabled images, if you are using gluetun or anything else then it won't work and should be set to 'no'.

you need to dig into this, this does work, but there any some tweaks you may need to make depending on how you have deluge configured. I don't know too much about the tailscale integration that unraid does, and i have never used tailscale, having said that i have had some pointers from other people in this regards, Please see Q36 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

you cannot bind mount /home in the container, that already exists and contains scripts required for the container to operate correctly, why are you bind mounting /home instead of using /downloads or /data to store incomplete and completed downloads?.

Tis done, click 'check for updates' or do a 'force update'.

Looking at the error i think you either have one of the following:- 1. your minecraft bedrocks client is out of date - if using android ensure you pull from google play 2. you have an incompatible mod or similar - upgrade or remove 3. your world data is corrupt - restore from backup or create new world. If you truly do have the exact same error then you will need to do the same too.

Yes your path ending in MakeMKV is your HOST path, but you aren't on your host, you are inside a container, thus you use the container path that maps to your host path, which in this case is /media. Don't feel too bad, lots of people get tripped up on this in the beginning, once it clicks for you then it's easy, as this is the same for all docker containers.

from your screenshot:-

ok becaue you have both containers in the same network changing the host port will do nothing, the way out of this is to change the port that qbittorrent is using, not sabnzbd, as qbittorrent has the ability to change the container port and thus prevent the clash, to change the port see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

have you clicked on 'check for updates' at the bottom of the docker screen in unraid and then applied any updates?.

nothing stopping you setting the default output path to anything you want, makemkv/view/preferences.

This image was designed around the concept of bridge, as MACVLAN and IPVLAN were simply not available at the time, and thus bridge is your best bet for getting everything working. I did look into custom bridge some time ago and openvpn with a custom bridge did not permit access to the web ui for me, so i'm not sure how it did work for you. In any case, the image has not been rebuilt so i don't believe it's any change to the image that has caused the lack of access to the web ui, so i can only assume something on your system. So the TLDR is switch to bridge network and be happy, or try and work out what's changed on your system and revert it and see if you can use custom bridge again.

yeah do NOT edit that file, i will have a little think about the best way to achieve this, please can you post a link this in the support thread for the container so i don't forget.

See Q4 to rule it out:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md

sure, you can add as many paths as you want, just click edit and go to the botton click on add and add a new path then set the host path to point at the pool and give the container path a unique name and lastly point plex at the uniqe container path and add your media.

ive seen this a couple of times where the issue is actually cookie related, try accessing the second instance from a completely different browser to the first instance.

no idea im afraid, you would have to do some googling and asking in minecraft related forums, you might get some answers there.

From your log:- [Trace] DiskProviderBase: Directory '/config' isn't writable. No space left on device : '/config/sonarr_write_test.txt'

https://forums.unraid.net/topic/44141-support-binhex-plex/page/39/#findComment-1495123

See here:- https://forums.unraid.net/topic/155853-support-binhex-flaresolverr/page/2/#findComment-1478510