binhex

only two ways, either you edited the container and accidentally entered in a 1 instead of a 0 and didn't realise you were doing it (too much beer? 🙂 ) or you deleted the edited template and pulled it fresh from CA and forgot to change the LAN_NETWORK. in short there is NO way any of my code has access to your template, so it aint me 🙂

thanks, change in and image built, please pull down new image.

yep as i suspected incorrect LAN_NETWORK, from your log:- LAN_NETWORK defined as '192.168.1.0/24' see Q4 if you are struggling to define it correctly:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

You are out of date, 'check for updates' in unraid web ui and apply EDIT - Just checked and although the image is tagged as 0.2.0.1448 it is 0.2.0.1426, i can only assume a mess up upstream from me, i have re-tagged to kick off github action and can now confirm its now up to date, please pull down latest image.

thats a successful start, what is the ip of the machine running your web browser?.

yep its currently up to date with the latest prowlarr pre-release so not sure what versions you are seeing?.

bug in 4.4.0, revert to 4.3.9

im assuming by this you mean you are using a custom bridge right?, if so this is not supported, you need to switch it back to the default, which is simply 'Bridge'.

no idea whats causing the no such file or directory errors but the plexmediaserver is the name of the 'program' which kicked off the start of plex media server and is being managed by supervisord, for the errors you are best asking on the official plex forums.

you are best asking on the CA support thread for this, as this is not an issue with the template or the image.

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

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

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

yep that should work, if i were you though i would simply rename the radarr.db to something like radarr.db.old JUST incase you need it rather than deleting it.

look out for blocking DNS resolution, this runs on port 53 UDP, you must permit this.

are you running 4.4.0?, if so roll back to 4.3.9, 4.4.0 has multiple issues including category related problems. secondly you need to fix that path asap!, if you dont then you risk filling up your docker image file which will lead to other issues, do as @wgstarks suggests.

ok so just to confirm this, whats the lan ip of your unraid server and whats the ip of the machine you are running the web browser from when attempting to access the qbittorrent web ui?

link to reddit post, quite a good run down of the changes, note the current qbittorrent v4.4.0 incompatibilities!. https://www.reddit.com/r/radarr/comments/sgrsb3/new_stable_release_master_v4045909/

thanks for that!, you are the first user that has confirmed a successful upgrade (without restoring from backup), so it looks like any prior corruption in the db (probably due to earlier versions of radarr) will cause the migration to fail, so it is going to be a case of backup your config, cross your fingers, sacrifice a couple of goats in your back garden and then press the button!.

for what its worth, this is from the radarr wiki:-

the plan is somebody with this issue (i dont have it as i dont use this image personally) needs to post an issue on radarr's github repo so the radarr dev's are aware of it, give as much detail as possible, see my earlier post requesting this:- https://forums.unraid.net/topic/53807-support-binhex-radarr/?do=findComment&comment=1091945 just to be crystal clear here - the image is fine, if you start from a clean slate the container will start, its the upgrade of the db form the previous release to the now current release thats broken, this is out of my control.

@daan_SVK @Tolete looks like the upgrade of the db partially happened when you upgraded to the latest version of radarr leaving things in a broken state when you roll back, not great!. solution is to either wipe your db, go to latest and reimport everything (ideal but time consuming) or restore your config for radarr from backup.

Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

@haakony @marcoNLD this looks to be a coding issue where the radarr dev's have not correctly worked out how to upgrade the database from the previous release 3.2.2.5080 to the new release 4.0.4.5922, please raise an issue on their github repo:- https://github.com/Radarr/Radarr/issues/new/choose

they dont :-), this will be a change on the users side, @BernieFPV is now blocking name resolution for some reason causing the error:- running opnsense/pfsense/pi-hole?, if so check the logs and think back to any rule changes you recently made.