aptalca

Alright ladies and gents, the rewrite for openvpn has been pushed to master and there is a new build on docker hub. You should be able to return to linuxserver/openvpn-as or update to 2.7.3 safely

Once we merge to master, I'll notify here so you can switch back to the "linuxserver/openvpn-as" image

Is that in host networking? If not, try host networking. If so, are you on the same network subnet? If not, you need to be. You can ssh tunnel to your host. See the "on a different network" heading at the bottom of this page: https://support.plex.tv/articles/200288586-installation/

You're confusing different tags. There are docker image tags, which are found on the docker hub page under tags. If you don't select a tag, "latest" is selected by default, which is what you're seeing for our image there, simply because you put in "linuxserver/plex" as your image in the container settings. If you change that to "linuxserver/plex:1.15.1.791-8bec0f76c-ls11", then you'll see "1.15.1.791-8bec0f76c-ls11" as the tag in that screenshot for our image. The other tag you're confused about is plex's version tag. Our image (different than the official plex image) supports updating to a custom version inside the container by setting an environment variable to a specific plex version. Other options are "latest", "public" and "docker". docker does no updates and you get the version that comes with that image. Public updates to the latest public release on container start and latest updates to the latest beta/plexpass on container start (as long as you're logged in with a plexpass account). Or you can set the version variable to a long plex version and it will update to that. The long plex version for the current stable is "1.15.2.793-782228f99". That's what you would need to enter in as the "VERSION" variable in container settings. Now as for the other variable for plex downloads, that's the url our image uses to download plex releases. With 1.15, that url changed. So if you enter in a 1.14 version, our image won't be able to download it from the new endpoint, so you need to override that url by passing in the url for old downloads, which is what I listed before. So if you want to update to a 1.15 version, don't specify that url. If you want to update to a 1.14 or earlier, you need to specify that url. I hope that's clear. If you simply want to use version 1.15.1.791-8bec0f76c, the easiest way would be to set the "VERSION" variable to "docker" so it doesn't do any updates during container start, and use the image "linuxserver/plex:1.15.1.791-8bec0f76c-ls11" so you'll use the image that comes with that version with no in container updates

What's the source media you're transcoding by the way? Is it h265? 4K? If so, even on a super fast cpu, it is very difficult to sw decode so your experience is perfectly normal

Thanks so much for the confirmation. We are now using the openvpn recommended backup and restore steps whenever the container is recreated. Hopefully this should alleviate any issues arising from version updates. Downside is, openvpn is installed on container start of a newly created container, which increases the overall space used (between the image and the container) by about 44MB due to duplication, but I think it's a worthwhile compromise.

I rewrote the openvpn-as setup steps to prevent breaking updates. Can I get a few volunteers to test going from 2.6.1 to 2.7.3? If you're interested, please first back up your app data, then change the image in your container settings to "lsiodev/openvpn-as" from "linuxserver/openvpn-as:2.6.1.ls11" and let us know here? It worked for my install but I may have had changed other things manually while tinkering. Thanks

Did you set the library path as /config as the readme says?

First of all, the additional variable is only needed if you're trying to go back to 1.14, not 1.15. Second, you're missing some digits in the version you are entering. It needs to be longer than that. Third, the "latest" you're seeing in that screenshot is for the docker image, not the version of Plex inside the image

You need to provide more info. Define "not working". What do you observe? And which steps did you do?

Also check the proxy.conf, which used to have a limiter a while back

Can you give this a try? https://github.com/linuxserver/reverse-proxy-confs/blob/21af09b2cd447939f8be549a73d9c88cb3646ef9/taisun.subdomain.conf.sample

I don't see how any of it relates to letsencrypt. The log snippet you posted shows one container trying to connect to the other directly via host ip. I don't see any proxying involved

Along with the version for 1.14blah, pass an environment variable where PLEX_DOWNLOAD="https://downloads.plex.tv/plex-media-server"

In other words you need to change the ports unraid gui uses (only the https one if you do dns validation)

Don't expect us to watch videos to figure out what you may or may not have done. Post what you did, your config, full logs, etc. and then we can try and figure what went wrong

That's right, open the container settings and modify the repository entry (which is the docker image)

PSA. It seems openvpn pushed another broken bin, tagged 2.7.3 I get the same error with it as I did with the previously pulled 2.7.2 While they/us try to figure it out, you can change your image to "linuxserver/openvpn-as:2.6.1-ls11" and it should work

you currently have the container set to 1200, host set to 1194 172.17.0.2 is the container IP, 192.168.1.8 is your host IP

other way around

I really didn't have the patience to read all of your posts, but let me tell you it is quite possible to access vpn through different ports. But you really need to understand how these things for together. That's why everyone's been telling you to read the docker faq. If you want to access it at port 1200, you can either 1) run it in bridge, don't change any ports in the openvpn-as gui, in container settings, map host port 1200 to container port 1194 with udp selected. Map any host port you like to container port 943 with tcp for the webgui. Leave the interface as eth0, or 2) run it in host networking, in the openvpn-as gui change the udp port to 1200. Set your interface to your ubraid network interface. With either of the above, set the vpn client to use port 1200 udp and that's it. Fyi, I'm accessing my vpn server on a different port than 1194 via the first option listed above If the above doesn't make any sense to you, then read up on docker port mapping and docker host vs bridge networking. Google is your friend.

Thanks for your generosity. Much appreciated.

You're confused about app settings and port mapping. When you tell openvpn-as to listen on port X, it is listening on that port inside the container, not on unraid. When you change port mapping in unraid gui, app has no idea about that change. The change is at the docker system level, not inside the container. You should read the docker FAQ here to better understand how that all works

Glad to hear it works Here's the donate link: https://www.linuxserver.io/donate Thanks