aptalca

https://github.com/linuxserver/docker-plex#application-setup This is linked to in the first post here

If you set the version parameter to public instead of latest, it will stay on 1.14 which is the latest public release. It's in the readme

We don't really recommend it for security reasons, but if you really want to, you can edit one of the existing ones and use the unraid ip and port in the proxy_pass directive to proxy via the subdomain method

I started hitting the transcoder issue as well. The reason I didn't notice it before is because it works fine on mp4. But mkvs cause a transcoder error. Since it works for mp4s I'm convinced it's the new Plex server 1.15 and not docker related. Tag 168 is unable to update to 1.15 (due to change in package location on Plex servers) and that's why it works fine. EDIT: some mkvs play fine, I'm at a loss. Most likely plex transcoder issues. They do use a newer ffmpeg build in 1.15

Most of our images don't update apps inside the container so not updating the image for a month is ok. But for apps that update inside the container like this plexpass version, you should make sure you are always on the latest image, otherwise it may break (like it did this time but could have been a lot worse)

Judging by that log, you need to update your plex image/container

I didn't notice any issues on my end and had a bunch of users streaming happily over the last few days. No complaints so far.

Umm, that's a no. In bridge mode, connection goes from whatever network unraid uses, to the docker network, to the container through mapped ports, and inside the container it goes to the tun device. The tun device is not exposed to the host. I assure you my unraid knows nothing about a tun device and I have no problems connecting to vpn inside the container. Like I said before, you should test it instead of just hypothesizing.

Definitely a plex issue and you should ask on their forums

Likely the symlinks got messed up during the restore process. How exactly did you restore?

Kind of an advanced trick so don't expect any further support from me, but you could potentially use a separate dns server like pi-hole where you would tell eero to use that as a custom dns. Pi-hole is more configurable. It seems this guy did just that: https://discourse.pi-hole.net/t/redirect-dyndns-conditionally-no-nat-loopback-owncloud/2846

To add to j0nnymoe's comment, even if you nuke and start over you'll hit the same issue again. Letsencrypt servers cannot reach your container via port 80 so they can't validate ownership

Are you sure you're looking in the right place? That log entry is from Jan 19th What does your docker log say after changing the subdomains?

In due time

You set the transcode location in Plex gui settings

Dns via container name doesn't handle uppercase. It has to be all lowercase. You need to change the container name to bitwarden

For anyone who's having issues with openvpn on unraid 6.7 rc, switch it to run in bridge networking, remove the INTERFACE variable setting or set it to eth0 (default) and map the ports 943 and 9443 for tcp and 1194 for udp

Ask on the Plex forums. It could be a Plex server but only they would know

Did you restore your letsencrypt app data from a backup or did you copy it to a different location over the last couple of months? If so, the method you used messed up the symlinks and copied the actual files so now certbot/letsencrypt is not happy. You can change one of the parameters in the container settings to force it to revoke and delete the old cert and create a new one. Adding a subdomain should do it.

Do you mean in the unraid gui? No, you won't see the tun interface in the unraid gui because the interface is inside the container. Vpn knows where to go because you are mapping ports. It goes through the docker bridge network on the host. Did you actually try connecting or are you hypothesizing?

What do you mean by route never got added to the network?

Check the logs under letsencrypt folder to see why the renewals failed the last 30 nights

He didn't say "I'm your daddy" so I'll go with Vader

Baby squid

Make sure you're using the global api key and not the other one. It's a bit confusing to get to global the api key on the cloudflare interface. Also make sure that you're copying and pasting correctly and not missing or introducing characters