ddns-updater VS gluetun

Setup https://github.com/qdm12/ddns-updater to keep you IP address updated for your Google DNS record. This is only need for inbound access while you are remote so that your DNS record is updated if you IP address changes.

Do you mean something like ddns-updater?

This assumes you have your DynDNS mechanism set up by any means other than the Fritz!Box internals (for example, I use this docker image, in combination with my cloudflare managed domain to achieve DDNS behavior). This means that the Fritz!Box needs to be reachable with the domain you intend to use for your VPN connection. For example, I use vpn...

SOLVED: Thanks to some of the suggestions here I realized the WAN IP wasn't actually changing. The DDNS updater I use: https://github.com/qdm12/ddns-updater uses a bunch of different sources, both http and DNS to determine the current public IP. At lease one of the http sources was no longer working and I have no idea how the DNS sources are supposed to know what my current IP is, that doesn't make sense to me.

I use ddns-updater.

Take a look at qdm12/ddns-updater

Use https://github.com/qdm12/ddns-updater. You can buy a standard domain, and this will keep it pointed at your IP.

if youre public IP isnt static, you will need a dns-updater too.

Use a dynamic DNS service like noip.com. You either use one of their domains like myusername.someDDNScompany.com or you use your own domain. Then you run software like ddns_updater on a raspberry pi or a docker container on your NAS that periodically checks and updates the DNS record with your current home IP.

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