I’m trying to link a docker container qFlood to my VPN (proton) on the host to prevent IP leaks.
When everything is on the host, I can just choose “proton0” in the network interface to use, but I don’t know how to do that inside the container because this interface is not exposed to the container.
Is there a way to do that?
Or even to implement the VPN inside a container?
What the alternative to prevent IP leaks with qBit on docker?
edit:
I used gluetun + qFlood as advised and it worked like a charmed except that I could’t seed or leach at all
Turns out the solution was to change the network interface in qBittorrent options from eth0 to tun0… Simple as that
Thank you all for the help!
I’m not sure about containers, but in Qbittorrent, Settings, Advanced, there is a “Network Interface” setting you can use to force qbit to only use a particular network interface. My VPN has it’s own network interface, so if it drops out, qbittorrent just stops downloading until the VPN comes back up. So, no IP leaks. Hopefully this helps you out a bit!
My VPN client runs on another container, and I just tell my qbittorrent container go use network of my VPN container via a docker command during qbittorrent container creation
Do you use docker compose?
https://www.youtube.com/watch?v=xbSfaKwyfXE&t=33s
version: '3.7' services: gluetun: image: qmcgaw/gluetun:latest container_name: vpn cap_add: - NET_ADMIN ports: - '8080:8080' environment: - VPNSP=protonvpn - VPN_TYPE=openvpn - OPENVPN_USER=xxxxxx - OPENVPN_PASSWORD=xxxxxx - REGION=United States restart: unless-stopped qbittorrent: container_name: qbittorrent image: cr.hotio.dev/hotio/qbittorrent:latest network_mode: 'container:vpn' environment: - PUID=1000 - PGID=1000 - UMASK=002 - TZ=America/New_York volumes: - '/home/xxxx/qbt:/config' - '/home/xxxx/INCOMING:/downloads' restart: unless-stopped
That should get your started
So I was wondering if you solved this?
If not, maybe try the qBittorrent image from LinuxServer instead?
I had your same problem that everything was stalled but switching to LinuxServer image fixed it :)
Also, I just had this issue as well, make sure you use port forwarding on whatever VPN you have!
I believe Gluetun has native support for Proton, so all you should need is to add “VPN_PORT_FORWARDING=on” to your environment on Gluetun container, and it will give you a port number. Put that port number in qBittorrent in the “Listening” port and you should be able to seed too! :)
Lemme know if you have any other questions, and I’ll do my best to help :)
Hey ! Sorry I didn’t saw your message. I came here to explain how I solved it (just now)!
I discovered a lot of nice option in gluetun (like port forwarding)
But turns out the solution was to change the network interface in qBittorrent options from eth0 to tun0… Simple as that
Thanks for your help!
I do
Thank you it’s really helpful
I’ll try it
awesome let me know if you run into any issues!
So it’s seems to be working but all torrents are stalled for some reason
IP leaks can see their file and I can curl an IP from qflood container but somehow the torrent won’t download
strange. maybe try a different torrent client?
So I was wondering if you solved this?
If not, maybe try the qBittorrent image from LinuxServer instead?
I had your same problem that everything was stalled but switching to LinuxServer image fixed it :)
Also, I just had this issue as well, make sure you use port forwarding on whatever VPN you have!
I believe Gluetun has native support for Proton, so all you should need is to add “VPN_PORT_FORWARDING=on” to your environment on Gluetun container, and it will give you a port number. Put that port number in qBittorrent in the “Listening” port and you should be able to seed too! :)
Lemme know if you have any other questions, and I’ll do my best to help :)