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.
Selfhosted
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!
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
Btw, I don't remember where, but the compose file do exist somewhere on the system.
Even though I made a mistake. Happy to help!
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.
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 😢