gluetun VS ovpn-admin

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki

I've been using this myself for managing two different OpenVPN setups, https://github.com/flant/ovpn-admin it's fairly basic but it does the job and generates .ovpn files for the clients. I'm building it and running it with docker, one for each vpn network.

I use both Wireguard (primary) and OpenVPN(secondary) to access my homelab. I really like the ease of management of WGDashboard for Wireguard and so went looking for something similar for OpenVPN and ran into ovpn-admin which I am running on a docker container. It works well, but I am struggling with a major issue: enabling local LAN access.

Based on this idea I want to add pihole service in the docker-compose file. I added the service like so: yaml pihole: container_name: pihole image: pihole/pihole:latest depends_on: - "openvpn" # ports: # - "53:53/tcp" # - "53:53/udp" # - "67:67/udp" # - "8081:80/tcp" env_file: - ./pihole/.env environment: TZ: 'Europe/Athens' # Change that with your timezone WEBPASSWORD: 'askdlasjd32r2fweasfq' DNS1: 1.1.1.1 # CloudFlare ServerIP: 172.19.2.1 # https://github.com/Simonwep/openvpn-pihole/blob/master/docker-compose.yml volumes: - './pihole/etc-pihole/:/etc/pihole/' - './pihole/etc-dnsmasq.d/:/etc/dnsmasq.d/' cap_add: - NET_ADMIN networks: npm_backend: ipv4_address: 172.19.2.1 # from npm-backend network restart: unless-stopped

This March, we've introduced ovpn-admin — a simple web interface to manage OpenVPN users, their certificates & routes in Linux. It is Open Source with its backend written in Go and frontend based on Vue.js.

Not sure how this all will work with Mikotiks, though. Because the admin panel should have access to the certificates and run on Mikrotik, but the OpenVPN there is quite limited (the things you've mentioned)… If you're really into it, it would be great to see a relevant issue, so other people can support, we can discuss all details and don't forget about it :-)