binhex

Sorry but there is very little I can suggest other than posing on Plex support and hoping somebody has an idea on how to fix it. Sent from my CLT-L09 using Tapatalk

thanks for this, i have confirmed your fix works so pushed it out and currently rebuilding the image.

that is a successful start, so similar questions to you as the last guy:- that looks like a successful start, questions for you:- 1. do you have proxy enabled in your web browser? 2. what is the ip address of the device running the web browser? 3. are you trying to access the ui via vpn, external or internal? 4. what is the 'network type' for this container?

you are attempting to setup port forwarding on an endpoint that does not support it, from your log:- 2021-07-29 03:04:13,743 DEBG 'start-script' stdout output: [warn] PIA endpoint 'us-atlanta.privacy.network' is not in the list of endpoints that support port forwarding, DL/UL speeds maybe slow [info] Please consider switching to one of the endpoints shown below change to one of the endpoints that is port forward enabled (see your log for a list).

i would be careful about doing that as you may inadvertently allow bad people in, but def check to see if there are any lan blocking rules in there that might be causing the issue, maybe crank the logging up on your router and see if you can spot anything.

thats very odd!, i just restarted my container and it kicked out the list no problems, can you try a restart of the container, if it still doesnt output then please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

that looks like a successful start, questions for you:- 1. do you have proxy enabled in your web browser? 2. what is the ip address of the device running the web browser? 3. are you trying to access the ui via vpn, external or internal?

hmm using the same openvpn file as privoxyvpn which you say works, should get you going, im assuming you havent actually tried restarting privoxyvpn though right?, maybe it will also fail on restart. in any case, please do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

hi guys, i have relaxed the restriction about adding in additional packages, you can now do this if required, see Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/code-server.md

yeah this will be probably due to minidlna app scanning for media changes and thus keeping your array drives spun up, im not aware of any setting to change this behaviour edit - you could try this, change this line in the file /config/minidlna.conf:- inotify=no save and restart the container, this will of course mean if you add media then it will not appear until you restart the container.

if you want to run as a different user then you need to use the PUID and PGID variables to change it, see the bottom of the readme.md:-https://github.com/binhex/arch-minidlna yeah this is common newbie mistake, you need to get your head around volume mappings in docker, see here for my explanation of it Q2:- https://github.com/binhex/documentation/blob/master/docker/faq/general.md so either change /media to be /mnt/user and then in minidlna set it to /media/podcasts or create another volume mapping that points at host path /mnt/user/podcasts and has a container path

I suspect latest tag works fine, the issue you had is that you had the old broken latest image cached on disk, you need to click on force update when switching back to latest. Sent from my CLT-L09 using Tapatalk

a new version of plex pass has been released and built guys, give it a whirl and see if it fixes the issue.

i would agree, def looks like a showstopper plex bug, be nice if they tested a bit more eh!. ok if you cant wait for the fix and want to get going again then please roll back, instructions here Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

thanks i was able to replicate the issue, i have fixed the problem so please pull down the image by doing a force update, please note you may still have to remove '/config/home/.MakeMKV' folder and then restart the container, after that you should be good.