I’ve spent all today and yesterday trying to get this working with PureVPN and QBitTorrent and it hasn’t been working much at all 😭. It’s been painfully slow when it works at all, which has been rare. Although it has been doing the job of hiding the Docker container IP so that’s good, and it makes me think it’s something minor, like port forwarding not working because of PureVPN or something off with my settings, or it’s a qBittorrent issue, or Docker and Linux inexperience.
Admittedly troubleshooting has been slow because I’m super new to Linux and Docker and keep running into permission and file system issues. Running the VPN and torrent straight in my computer was way easier, but I’d really love to be able to run Plex and a torrent client on the same computer on at the same time with Plex not going through the VPN and the torrent client going through it, which is what this seems great for.
I’ve set it up with PrivadoVPN without issues, using Docker. Gluetun in its own docker container and Qbittorrent in its own, with network mode set to use the Gluetun contaoner. Haven’t tested downloading a lot though. Gluetun has some good docs how to set it up in Docker.
Maybe it’s my VPN provider then. I’ll have to try it with another one. I’ve followed so many of those documents. Do you use Port Forwarding with PrivadoVPN?
There's already a pretty recent post about this on the threadiverse. I recommend checking the discussion there as lots of us are not likely to repeat our comments.
Thanks for adding this. (I think I used the crosspost button on the desktop PC… yet, indeed, in my Lemmy client on mobile I’m not seeing the reference).
The container connects to the VPN and only the VPN, now you can route whatever docker containers you want through that container as a network. Now that one VPN connection can serve any container you want.
I use gluetun to route traffic from some of my containers that need a VPN. qBittorrent, Jackett etc. Some containers dont have the option to configure a proxy so you’d have to setup a VPN client within a container which isn’t ideal. With gluetun its easy to attach a container to it and it just works
Why isn’t it ideal? I’m currently using this setup with containers routed through a gluetun container connected to a vpn via wireguard, and it seems to be working fine. I’ve verified using curl inside the relevant containers to query an IP checker and I’ve also used a torrent IP checker to confirm my torrent client isn’t leaking my IP.
Also the biggest benefit; You only need 1 VPN connection and 1 key pair for gluetun to connect everything. Most VPN providers limit the amount of active simultaneous connections. If you have lots of containers that need it then it’s not possible
Dodaj komentarz