gluetun VS docker-qbittorrentvpn

I've been using the LSIO Webtop images for a few years. They're awesome for composable desktops that I run behind a VPN for a quick and easy dirty connection at home.

Combine the Webtop images by forcing it's traffic through the Gluetun [0] container and you're up and running. These Webtop containers are nice and snappy as well thanks to Kasm. Awesome OSS.

[0] https://github.com/qdm12/gluetun

There is gluetun, https://github.com/qdm12/gluetun, which servers a similar purpose and supports ovpn and wireguard. It's mainly used with Docker to have namespace-based proxying of traffic for a container.

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.

https://github.com/DyonR/docker-qbittorrentvpn is the container I use so I don’t see an easy way to use port forwarding with this method.

I am running this docker image on my raspberry pi (https://github.com/DyonR/docker-qbittorrentvpn) , which runs a qbittorrent over wireguard(client). I have setup a wireguard server on a vps.

Unless he stopped using GitHub idk https://github.com/DyonR/docker-qbittorrentvpn

After changing CIDR I decided to try one more thing. qBittorrentVPN , which previous also didn't work now works like a charm. It doesn't have kill switch hardcoded, so I had manually set them to my new CIDR and my local network. I only worry that other apps from TrueCharts might have hardcoded other CIDR bits witch may be a problem in the future But for now it's victory!

Ummm this sounds naive if you ask me but if you use Hetzner with a torrent client combined with vpn (e.g. https://github.com/DyonR/docker-qbittorrentvpn) you should be good to go. Hetzner isn't bad.

I run this one: https://github.com/DyonR/docker-qbittorrentvpn in my kubernetes cluster. It supports IVPN just fine (at least Wireguard, since I don't use OpenVPN). Once the WG tunnel is active, you should have an interface named "wg0" in the interface list: Tools->Options->Advanced->Network Interface. Select that and QBit will use that interface only (which means it won't communicate if the WG tunnel is down; which is what I want.

Your cheaper option but with some learning involved is to rent a hetzner for example, use swizzin in conjuction with something like a vpn for qbittorrent, some details: How to use a vpn with qbittorent? : qBittorrent (reddit.com) Also I believe there is a docker image, here is one: GitHub - DyonR/docker-qbittorrentvpn: Docker container which runs a qBittorent-nox client with an optional WireGuard or OpenVPN connection Hetzner is in no way public torrent friendly, which is why public trackers must be used only behind a reliable kill-switch vpn option.

The qBit + VPN is a Docker container that uses Wireguard or OpenVPN to route only the qBittorrent traffic through the VPN. It also has a kill switch built in. The project readme can probably explain how it works better than I can

You can request further assistance here: https://github.com/DyonR/docker-qbittorrentvpn/issues