docker-openvpn VS openvpn-pihole

J'ai trouvé pour openvpn ces deux: [https://hub.docker.com/r/kylemanna/openvpn [https://hub.docker.com/r/linuxserver/openvpn-as DMAM

Else - https://github.com/kylemanna/docker-openvpn

I'm fighting a weird issue plaguing both a friend and myself. I'm using the kylemanna/openvpn docker container on the server side and whatever OpenVPN client there is on clients.

I'm using the latest kylemanna/openvpn container for the server, running on Debian 11 x86_64.

Talking with some contacts I have, right now the big ask is for secure VPNs. If you can host a server (location should be outside the US and other western countries so CSPs may by your best option) that would perhaps be the best. OpenVPN is a solid choice and there are docker images you can use to readily deploy: https://github.com/kylemanna/docker-openvpn a solution.

3 . Clone the project from this repo (https://github.com/kylemanna/docker-openvpn) with this command

When I look into vpn servers, I find easy installers, which directly work on linux (e.g. angristan/wireguard-install) or also vpns, which operate from docker (like kylemanna/docker-openvpn). Then there are options, where multiple things are included, like firezone or this. I am not so sure how well they integrate with my reverse proxy and some seem to be much more complicated than others.

I know that tunneler supports OpenVPN, so I imagine I could use kylemanna/openvpn but I can't figure out how to set it up...

I'm trying to setup an openvpn docker container in a one to many setup. I know there exist already solutions but I'm kind of scared that it hasn't been updated in a year (OpenVPN Docker Container).

I setup a openvpn-pihole docker combo container onto my cloud VPS, which has a public static IP. Pihole must run behind VPN and I am only interested in dns queries, in other terms I don't want my internet traffic get routed by the VPN server. I read everywhere that I should comment out this line in the server.conf file (and I did do):

if you know how to create and maintain an open vpn server of course the self-hosted solution is better, any other vpn provider can use your data beyond your knowing, big problem is that they host servers all over the world so in its "vpn server" they have deferent rules from the country that they are located, so if we speak about personal integrity you can host your service in Europe where the gdpr is very restricted about personal data. If you are open to suggestions about the server provider I recommend you hertzner. For me personal for everyday use I use my self-hosted open-vpn/ pihole(inside the vpn with docker) and for multimedia consumption, I use proton vpn to have access to content from all over the world.