qbittorrent-natmap VS gluetun

# https://github.com/soxfor/qbittorrent-natmap

qbittorrent-natmap: # https://github.com/soxfor/qbittorrent-natmap image: ghcr.io/soxfor/qbittorrent-natmap:latest container_name: qbittorrent-natmap restart: unless-stopped volumes: - /var/run/docker.sock:/var/run/docker.sock:ro environment: - TZ=Etc/UTC - QBITTORRENT_SERVER=127.0.0.1 # - QBITTORRENT_PORT=8080 # - QBITTORRENT_USER=admin # - QBITTORRENT_PASS=adminadmin # - VPN_GATEWAY= - VPN_CT_NAME=gluetun - VPN_IF_NAME=tun # - CHECK_INTERVAL=300 # - NAT_LEASE_LIFETIME=300 network_mode: "service:gluetun" depends_on: qbittorrent: condition: service_started gluetun: condition: service_healthy

These ports change after every reboot and can only be manually inserted into my qBittorrent. Luckily someone wrote some code that automatically updates containerized versions of qBittorrent.

Using qBittorent-NatMap - would help with ExpressVPN (probably not)?

qBittorrent-NatMap - Automatically configures your qBittorrent container for proper port forwarding (big performance improvements)

It's a bit complex but I use a setup of three docker containers which all share the same networking. I use Gluetun (https://github.com/qdm12/gluetun) as the VPN client and qbittorrent as the torrent client (I use the linuxserver io image but any should qbittorrent client should work). For the port forwarding I use https://github.com/soxfor/qbittorrent-natmap which uses nat-pmp to request a port from ProtonVPN via the Gluetun interface and then automatically updates it in qbittorrent. Gluetun apparently supports Proton port forwarding by default and exposes the port via its API if you want to write your own script, but I couldn't get it to work and it uses openvpn. This setup uses a wireguard config on gluetun from Proton with nat-pmp enabled. I run this on a random weak decade old computer 24/7 but in a desktop environment you should be able to just run it on Docker desktop when you want to torrent. The docker compose file in the natmap repo gives a good idea of this docker stack.

I feel like the solution could involve https://github.com/soxfor/qbittorrent-natmap/pkgs/container/qbittorrent-natmap somehow, but the fact that I run the VPN connection on the router (rather than the NAS) means that I have no clue how to set it upt.

I just switched over myself and only did a quick test with natpmpc. While that works, on its own it isn't terribly practical. My long term goal is to get it working in a docker container which has proven more challenging. That said others seem to have been successful with this and I'm trying to adapt this: https://github.com/soxfor/qbittorrent-natmap

If your NAS supports Docker, you could use a combination of vpn container (gluetun), natpmp container (for port forwarding) and a qbittorrent container. I have it working on a raspberrypi

Since I couldn't find exact instructions for qBittorrent I decided to start something, that can be found here (github)

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