aptalca

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.

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

No worries. Let us know if we can improve the docs so they are clearer

I'm just wondering why you read the other image's readme and even quoted it here, but you didn't read our image's readme. All of what you quoted is also in our readme in different words

Holy moly, php7-pecl-imagick has a ton of dependencies and the size of all apps installed jump from 156MB to 233MB. So I'm not going to add it, but, you can create a file on your host called 90-config, with the following contents: #!/usr/bin/with-contenv bash apk add --no-cache php7-pecl-imagick and then map that file on the host to location in container: /etc/cont-init.d/90-config (add new path in container settings) That will install it during container start and will survive container recreation as long as the file on the host is still there

No idea why it's doing that. But if it is updating every so often, it should be fine.

Start from the beginning. Forget about the reverse proxy. Forward port 80 on your router to port 80. Check the docker log, make sure cert is retrieved. Then check the landing page

I'll look into adding it

Your server names aren't matching for 80 and 443, bw vs bitwarden

The way you set up your a record and cnames is correct. You just need to make sure that the a record remains up to date. You can use a docker image like ddclient to update it, or some routers can also do it. If you're doing dns validation, look into getting a wildcard cert and then you only need to create one cname for "*" without the quotes and you'll be good. Between the a record and that wildcard cname, your domain and all subdomains will be covered.

Is it using host networking or bridge? Nothing wrong in the docker log

Yeah, it's optional for default config but you specifically turned it on when you included the following two lines in your conf: auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; Either create the .htpasswd or comment those lines out. The error you're getting specifically says that nginx can't find the .htpasswd file

Did you create an .htpasswd file? The command to do so is in the image readme linked in the first post

It's probably the dns cache. You have to turn it off and wait a bit

Turn cloudflare proxy off. Click on the orange cloud and make sure it's gray

No. Nothing on the host ip can connect to macvlan. One user here tried putting openvpn on macvlan as well, in order to be able to connect to other containers on macvlan but he had other issues I believe. Don't recall the details, it was beyond my networking knowledge.

Spent about an hour digging through their scripts and their post install of their package to see what could be missing. Wasted time. Openvpn pulled the 2.7.2 release. We pushed an update to set latest back to 2.6.1. If you updated to 2.7.2 today, update again to go back to 2.6.1 and things should go back to normal.

Openvpn-as devops is a bit of a mess, really. They like to make significant (breaking) changes to their db and data through their package updates, but not during service start. With this docker image, we don't do in place package updates, we replace the package along with the docker image. So the changes within their package updater need to be made manually. That happened about a year ago as well. Essentially, you're seeing a version mismatch between the app and its data and unfortunately it's not something we can easily prevent in the future

There are 3 types, host, bridge, and macvlan. Macvlan is the only one with that restriction.

Check your port forwarding