aptalca

There is a pending PR to make it work safely in bridge mode. Should be merged soon.

It needs a newer version of nginx that is not yet released for alpine stable. When it is released, or image will use it.

No, what I mean is, the docker image is only able to pull either the stable (public) releases or plexpass versions. Go to the Plex website, hit download and you'll see a toggle switch for plexpass. With it on and off, you'll see two versions listed. Those are the latest versions this image supports. Not ones that are posted on the forums.

The docker image doesn't support alpha or preview images, only stable and plexpass

Either your ip or your port forwarding is incorrect. Letsencrypt servers get a response, but it's not from the letsencrypt container.

Plex website lists 1.14 as the latest release

Set the version variable to that version number

You do see the issue, right? Unraid gui runs on port 80? You gotta use a different port for letsencrypt

I believe your port 80 is forwarded to your unraid gui at the moment

Well there is your issue. Plex was never set up. You didn't claim your server. Until then it will block reverse proxy connections.

Is Plex all set up and running? Also that's not the nginx log. That's part of a docker log of a container

Is your Plex container name "plex"?

Supported dns providers are listed in the readme. Godaddy is not one of them

How did you set it up? Post your proxy conf and we'll take a look

What are you doing exactly and what are you experiencing?

Not easily, nginx comes from the alpine package repo. We are currently on the latest stable, 3.8, which uses libressl, which doesn't yet support TLS 1.3. However, the edge build of nginx is using openssl 1.1.1, which supports TLS 1.3. When 3.9 stable of alpine is released, it should support TLS 1.3 with nginx. Or you _could_ try and install nginx from the edge repo inside the container but we don't support it, so don't come to us if you try and have issues.

Linuxserver version does not use the claim code. Did you set it up with host networking? and are you trying to connect to it while on the same subnet? If not, you may have to use the ssh tunnel method described on plex website, troubleshooting guide.

Version variable is for the plex version, not container tag. And you need to use the long plex version (10 digits or so). The docker image tag on the other hand gets added to the end of the image name ie. linuxserver/plex:124

Check the tags tab, not builds

If you do http validation, port 80 is required on the wan. If you do dns validation, you don't need port 80

Yup, when connecting container to container, remember to use the container port, not the host

We have a new build of couchpotato and we are looking for testers. This is a multi-arch build, meaning x86_64, arm and aarch64 builds are all hosted in the same repo and when you pull latest, your system should automatically get the correct arch. They also use our new build system. If you're willing to test, please first back up your existing config folder, then replace the image linuxserver/couchpotato in container settings with lspipepr/couchpotato and save. Then let us know here if it all goes well. Following successful tests, these builds will be published in the original repo. Thanks

Not sure about ddns but duckdns let's you have any sub-subdomain below yours. So if you put in yoursubdomain.duckdns.org as the URL in letsencrypt and put in speedtest as the SUBDOMAINS your cert will cover speedtest.yoursubdomain.duckdns.org as well as yoursubdomain.duckdns.org. In nginx, there is already an example for cp on how you can reverse proxy a subdomain. Use that and it should work. When you use the subfolder method, the recommended way is to match the location (speedtest here) to the base url. But if there is no base url for your application, this get complicated as you experienced. Subdomain method doesn't require a base url

You can proxy via subdomain

Syncing disks is happening inside the container. Did you map your unraid disks or protected array locations in the container? If not, it shouldn't touch the array at all. Check your container settings and make sure that /mnt is not mapped. I remember there was talk a while back that unraid was going to add /mnt mapping by default to all newly created containers. Can't remember if that ended up happening or not.