Submitted 5 months ago by paequ2@lemmy.today to selfhosted@lemmy.world
Occasionally I see people mention gluetun.
I use gluetun to connect specific docker containers to a VPN without interfering with other networking, since it’s all self contained. It also has lots of providers built in which is convenient so you can just set the provider, your password, and your preferred region instead of needing to manually enter connection details manage lists of servers.
Another nice feature is that it supports scripts for port forwarding, which works out of the box for some providers. So it can automatically get the forwarded port and then execute a custom script to set that port in your torrent client, soulseek, or whatever.
I could just use a wireguard or openvpn container, but this also makes it easy to hop between vpn providers just by swapping the connection details regardless of whether the providers only support wg or openvpn. Just makes it a little more universal.
It works with containers so I can create a setup where requests sent from the container goes through the VPN. I use it for my Redlib setup to bypass rate limiting. Unless you have your host to route all traffic through a certain node, it should work independently from Tailscale.
How do you use it in you setup?
Others explained what it is. To implement it, I basically followed this guide: drfrankenstein.co.uk/qbittorrent-with-gluetun-vpn…
It’s like a vpn app but for containers instead. I personally use it for invidious-companion which I route to Albania so google doesn’t block it.
I also use Albania for my VPN, only because it’s the first country in the server list
Gluetun can connect to multitude of VPNs, but most importantly it can be used to force other containers to use only the gluetun network, meaning if you disconnect from VPN for whatever reason, the other containers don’t suddenly send data over non-VPN network.
So if you’re torrenting and use gluetun to provide internet to the qBittorrent container, you won’t accidentally reveal your real IP if your provider’s server goes down for a few seconds.
meaning if you disconnect from VPN for whatever reason, the other containers don’t suddenly send data over non-VPN network.
Is that 100% certain? I think I can recall stories from 15 years ago, where torrent clients had kill switches and they still leaked data.
That really depends on the implementation. In the case of gluetun, yes, no data can leak.
In Linux, by interface binding, no data can leak as well. No idea how Windows network stack is implemented.
I’d seen gluetun mentioned but didn’t know what it was for until a moment ago.
I’ve heard of tailscale and at least know what that does but never used it.
I personally have a mullvad subscription. I have a container connected to that with wireguard, and then for services I want to use that VPN I just configure them to use the network stack from that container.
I’m not suggesting that my way is the best but it’s worked well for several years now.
I just configure them to use the network stack from that container.
Can you explain how you do this (or link to a guide that you found useful)? Thanks
services: qbittorrent: image: lscr.io/linuxserver/qbittorrent container_name: qbittorrent environment: - PUID=888 - PGID=888 - TZ=Australia/Perth - WEBUI_PORT=8080 volumes: - ./config:/config - /srv/downloads:/downloads restart: unless-stopped network_mode: "container:wg_out"
this is my compose.yml for a qbittorrent instance.
the part you’re interested in is the final line. There’s another container with the wireguard instance called “wg_out”. This network mode attaches this qbittorrent container to that wireguard container’s network stack.
That is essentially what gluetun does. It is a little simpler to set up given that it is all preinstalled and you just select your provider and details and it is done. And again, you just specify the network for other containers to use the gluetun service and it is done. Very simple, easy for using many services through one VPN connection, and available on things like CasaOS with simple setup.
It’s not a “normal” vpn client. It allows you to create a network in your server using a variety of vpn providers so other containers can use it to connect to the internet. You use tailscale to connect to your server from outside home, but you use gluetun for your containers to connect to the outside world without exposing your real IP.
You can even install Tailscale in your Gluetun container and use it as an exit node so you have a VPN while using Tailscale. This is most useful for mobile devices where you can only have one active VPN.
Hell, I route a TS exit node through gluetun so I can access my LAN while also covering my outbound traffic.
superglue@lemmy.dbzer0.com 5 months ago
I have a torrent client in a docker container thats hooked up to it. Makes it so its not possible for your real IP to leak. If the VPN disconnects the torrent container loses internet.
modus@lemmy.world 5 months ago
Isn’t that possible from within the torrent client? I use interface binding in qBittorrent and it cuts off whenever my VPN drops. Or does this not work from within the container? (My torrent client is not in a container as I’m still learning.)
watson387@sopuli.xyz 5 months ago
I have Deluge and Gluetun in containers. Deluge relies on Gluetun and won’t do anything unless it’s running and connected.