gluetun VS AriaNg

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

if you use a rss reader,you can try [rsshub](rsshub.app/). for example,you can subscribe "https://github.com/mayswind/AriaNg/releases.atom" in your rss reader,when AriaNG is released,you will be noticed in your reader.

I'm using Aria2 on my server: https://aria2.github.io/ and add the GUI from here: https://github.com/mayswind/AriaNg/releases Actually this is working for a long time and I'm pretty happy with this combination...

Another one is AriaNG, pretty nice interface to your aria2 instance. You can export your configuration so you don't need to log-in on a new device every time. If you're using an Android phone, you can try Aria2App to control your download server remotely.

On your host machine (RPi, desktop, old laptop), you would need to run your services (paperless-ng, anything else you feel like, e.g. filebrowser, navidrome, Jellyfin, qBittorrent, Aria2Ng) which (best practice) is to serve to localhost/127.0.0.1 and then you use nginx to connect localhost:port to sensible addresses on LAN or a small homepage, which are then forwarded to your router, which is then connected to dyndns.