aptalca

That help notice only applies to incoming connections to the container. So the docker container will be accessible only on the ports that you map. But outgoing connections are not restricted. You will connect to openvpn-as container on port 1194 or 9443 (incoming), which you will map, and then the connection will go from openvpn-as to unraid (outgoing).

Please don't recommend users to do that. And if you do that yourself, don't expect any support from us. The container itself does all of those steps correctly and automatically. Just follow the steps in the readme, set it up with bridge networking and it works.

A programming language

Plex does automatic backups of its database every three days. Their website/forum has instructions on how to restore

Check your Plex server log. Likely corrupt database

Go to the address https://serverip:port for the client interface. Without "/admin" at the end. That interface is set up in the admin gui and is enabled by default. More info on openvpn-as website

Reproduced them. There are two separate issues. The issue of nginx not starting is fixed in the next update. Still looking into the luajit error, but it seems to only affect lua, nothing else.

I can't reproduce the error. Please list the reverse proxy configs you enabled or any specific changes you made to your nginx or site configs

Google nginx tcp stream proxy. It's very easy and straightforward.

No. But you can create a second container with a different name and set that up with the other duckdns account. But why do you need that many if they all point to the same IP?

Use the extra domains variable for the second domain

You're assuming something is listening on those ports. That assumption is incorrect in your situation. Only during validation, port 80 is listening. After it fails, nothing is listening as nginx is not started.

Read the image description and check out our blog article: https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/

Hey guys, I'm just gonna drop this here. It's a new starter guide with a bunch of examples we published: https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/

For something internal only, you can use our nginx image. You can drop the web files into folder www and set the default site conf accordingly.

That only works with subdomains confs, not subfolder

No, that's the logic built in. You can do "ls *.conf" to see the active ones. How is tab completion difficult? It's the first part of the naming scheme that's unique per app, and it matches the conf before the .sample And how frequently do you edit them honestly?

If the reverse proxy is already set up via container name as dns hostname, you can remove the 8989 port mapping

Instructions in the readme

Ok, as a test, stop the letsencrypt container. Then set up the regular nginx container with the same exact port mappings as letsencrypt. See if you can reach the container using your domain name at both ports 80 and 443

Nginx doesn't run until it gets a cert

Post your container settings

Check the ip on duckdns, if correct, check your port mapping

Could it be browser cache? There shouldn't be duplicates unless there are two Plex servers are running with the same name but different server ids.

So basically you did everything but read the official documentation? See here for the most accurate info: https://hub.docker.com/r/linuxserver/openvpn-as Or here: https://github.com/linuxserver/docker-openvpn-as You may have missed the cap add statement. If it still doesn't work after that, check the logs (both the docker log and the log folder under config folder)