nordlynx VS gluetun

version: '3.8' services: nordlynx: image: bubuntux/nordlynx:latest container_name: nordlynx restart: unless-stopped healthcheck: test: ["CMD-SHELL", "curl https://api.nordvpn.com/vpn/check/full | grep '\"status\":\"Protected\"' && exit 0 || exit 1"] cap_add: - NET_ADMIN # Required sysctls: - net.ipv6.conf.all.disable_ipv6=1 ulimits: # Recommended for High bandwidth scenarios memlock: soft: -1 hard: -1 dns: - 192.168.0.250 - 192.168.0.251 networks: - bridge-lan ports: - 8082:8082 # qBittorrent - 6881:6881 # qBittorrent - 6881:6881/udp # qBittorrent environment: # Review https://github.com/bubuntux/nordlynx - PRIVATE_KEY=${PRIVATE_KEY} #required # Country Codes - https://github.com/azinchen/nordvpn/blob/master/COUNTRIES.md - QUERY=filters[country_id]=227&filters[servers_groups][identifier]=legacy_p2p&filters[servers_technologies][identifier]=wireguard_udp - NET_LOCAL=192.168.0.0/24 - TZ=${TZ} - PUID=${PUID} - PGID=${PGID}

I added the following env and the rest is pretty much the default from the gitHub (https://github.com/bubuntux/nordlynx)

I ended up using another NordVPN container (by the same author) and it is working pretty well now. 1g/1g sympatric internet gets about 20m/s download speed. I added the following env and the rest is pretty much the default from the gitHub (https://github.com/bubuntux/nordlynx) - ALLOWED_IPS=0.0.0.0/0 (maybe without this nordvpn is blocking everything?)

This is what I use. It works great, is easy to setup, and includes qbit in the template docker-compose file.

Please migrate to the NordLynx container (https://github.com/bubuntux/nordlynx)

I would check out https://github.com/bubuntux/nordlynx

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