Gluetun and mullvad works for sure but, yes, you do need to modify some settings in the compose file. At least I did to get it work.
this post was submitted on 16 Jun 2026
27 points (100.0% liked)
Selfhosted
61126 readers
418 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
Yes my gluetun container is working properly, I just can't figure out how to edit the compose for the qbittorrent file to work behind gluetun. I've even exported a working qbittorrent app, uninstalled it, edited and uploaded a new compose file as a custom app but that doesn't seem to work for me.
This is a docker compose that I know works for qbittorrent behind gluetun.
I wonder if you are missing the "network_mode: service:gluetun" part?
qbittorrent:
image: lscr.io/linuxserver/qbittorrent:latest
container_name: qbittorrent2
network_mode: service:gluetun
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- WEBUI_PORT=9090
- TORRENTING_PORT=6882
volumes:
- /path/to/qbittorrent/appdata:/config
- /mnt/JellyFinContent/Data/torrents:/data/torrents #optional
# ports:
# - 9090:9090
# - 6882:6882
# - 6882:6882/udp
depends_on:
gluetun:
condition: service_healthy
restart: unless-stopped
If you can't modify the compose file, you can try editing the container with Portainer. There you can change the network of ~~gluetun~~ qbittorrent to "container" and select gluetun.
That's how I did it when I was running CasaOS.
THIS is what worked you are the goat thank you
Using zimaOS, Umbrel, and other "one click install" OSs are very locked down when you need a more "complex" setup.
Hence they appeal to newcomers in the selfhost space. But you'll soon realize that they get in your way.
It's preferable to learn docker, docker compose from scratch if you really like to tinker and just setup a vanilla Debian server with it. That way you will not be tied down when you later want to do more elaborated setups. You will feel rewarded afterwards.
However, it does take time. It's up to you if its worth it.
Even though I made a mistake. Happy to help!
Btw, I don't remember where, but the compose file do exist somewhere on the system.
If it helps, here's how I had my gluetun / transmission set up with mullvad (I've since moved to proton for port forwarding but I saved the mullvad config in case I needed to switch back):
services:
gluetun:
image: qmcgaw/gluetun:v3
container_name: gluetun
restart: always
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun:/dev/net/tun
volumes:
- ./volumes/gluetun:/gluetun
environment:
- TZ=America/New_York
# Mullvad
- VPN_SERVICE_PROVIDER=mullvad
- VPN_TYPE=wireguard
- SERVER_COUNTRIES=USA
- SERVER_CITIES=New York NY
- WIREGUARD_PRIVATE_KEY=
- WIREGUARD_ADDRESSES=x.x.x.x/32
- UPDATER_PERIOD=24h
- UPDATER_MIN_RATIO=0.1
- UPDATER_VPN_SERVICE_PROVIDERS=mullvad,privado,protonvpn
networks:
- default
- ingress
transmission:
image: linuxserver/transmission:latest
container_name: transmission
restart: always
network_mode: "service:gluetun"
environment:
- PUID=0
- PGID=0
- TZ=America/New_York
volumes:
- ./volumes/transmission:/config
- /volume1/Media:/media
flood:
image: jesec/flood:latest
container_name: flood-sidecar
restart: always
command: --port 3000
user: "0:0"
network_mode: "service:gluetun"
volumes:
- ./volumes/transmission:/config
- /volume1/Media:/media:ro
environment:
- TZ=America/New_York
- HOME=/config
labels:
- com.centurylinklabs.watchtower.enable=true
- "traefik.enable=true"
- "traefik.http.routers.flood.rule=Host(`flood.example.com`)"
- "traefik.http.services.flood.loadbalancer.server.port=3000"
- "traefik.http.routers.flood.entrypoints=websecure"
- "traefik.http.routers.flood.tls.certresolver=mytlschallenge"
# This example uses "Selective Authentication"
- "traefik.http.routers.flood.middlewares=oauth-middleware"
Idk how zimaos works, but the way to attach containers like this is with network_mode: "service:othercontainer" which might need them to be in the same compose file (the docs aren't clear).
Also note that you can't put any port mappings on a container using network_mode service, you have to put them on the other container that is handling networking since the first container is piggybacking off of the other and doesn't have its own networking.
Idk how zimaos works, but the way to attach containers like this is with
network_mode: "service:othercontainer"which might need them to be in the same compose file (the docs aren't clear).
network_mode: “container:gluetun”
Is how you can do it with separate compose files. And yes you’d need to map the ports in the gluetun compose file for any container you route through gluetun.
Ohhh this might be my issue. I'll have to try it tonight
Ah cool, the docs made it sound like container: uses the container ID hash instead of the name so I wasn't sure how that works. I just put stuff like this in the same compose file since they're all closely related.
ZimaOS was a love/hate relationship for me. I setup a i7-7700K, 32GB DDR4, dualc10Gb SFP+, 24-bay SAS with x2 LSI 9300-16i raid cards.. Technically that's only 12 PCIe lanes (8 for x2 cards and 4 for NVMe's) but ZimaOS, even after paying for the premium upgrade (< 4 drives supported), couldn't handle large quantity disks with large capacity.. I had 10x 8TB drives and 8x 16TB drives, each in raid5 with a hot spare, and Zima would constantly become unresponsive with <50TB of data.
Idk if it was a power issue (850w PSU), raid card, or the OS, but I found myself struggling to keep it usable. I had attempted the arrs stacks but ran into issues. Idk if it was corrupted eventually, but I went back to my old server shell until I can resolve it and make it stable. Lemme tell you, moving 50TB+ across 2x 1GbE is excruciatingly slow... I was so thrilled to be on 10Gb for the short time 😢