By default, Unraid has a way to configure the Wiregurad tunnel as a custom network from the VPN Manager.
My question is, if I allow the qbittorrent docker container to communicate through this Wireguard tunnel, can I torrent safely?
I have been using the binhex-qbittorrentVPN docker container, but I would like to switch to this method if I don’t have to worry about the ip leaking in the way I just described.
Thank you in advance!
I would not recommend this route. binhex-qbittorrentVPN was built so that it is not possible for the IP to leak, so you’re better off continuing to use that docker container. Read Q1/A1 here for more info (this applies to all binhex VPN containers).
Where is the other end of your wireguard tunnel?
What I do is configure my VPN within the binhex-qbittorrent container itself and then bind it to the VPN itself within qbittorrent. I use Wireguard so the tunnel in Qbittorrent is WG0. You can test it to make sure it’s connected to it by using ipleak.net and chuck their torrent into qbittorrent and it will show you the IP it sees. If it’s your VPN IP then you’re good to go.
If you have to ask, then you should just stick to binhex so you dont fuck yourself on accident.
No, get a seedbox in a far away land if you are torrenting from home.
fly ten middle weary forgetful merciful shocking full reach puzzled
This post was mass deleted and anonymized with Redact
I use it and it’s fine. Just to a test torrent using lPLeak website to ensure it’s using the tunnel.
if I allow the qbittorrent docker container to communicate through this Wireguard tunnel
Who’s VPN are you connecting to?
If switching to wireguard is what you’re after, check out hotio’s qbittorrent + wireguard container. Similar to binhex, but wireguard instead of openvpn. And not Arch based, so a ton smaller.
Consider switching to a VPN provider that supports port forward like TorGuard (be sure to get a discount!), AirVPN or any other you can Google for “ port forward” and “ wireguard”.
I don’t rely on my vm that’s running qbittorent or any of my dockers. I control it on the router level with traffic rules. Run a ubiquiti dream machine. If the VPN I’m having traffic from those specific IP addresses goes down everything is funneled to null basically. I had to set it up this way as I already was using a VM to download torrents and it was the easy button.
Isn’t that the same with using a wireguard connection as the network for your container?
I would say the wireguard network is even better: the container never needs or has direct access to the internet, unraid sets up the connection instead of the container, and if the connection goes down, the container can’t go anywhere. Else the container still needs direct internet access at some point, and a mistake in the script can leak your ip (and binhex did have a leak in the past, not sure on the specifics).
So unless unraid would still allow internet access on the vpn network when the connection is down, it should be at least as secure?
This is nice documentation, thanks!
Ahhhhh. It’s been years since I set any of this up. I’m glad to see the ol’ binhex docker loopdeedoo is still the preferred method
It connects to Mullvad VPN
Can also open the Qbit console and run:
Curl ipinfo.io
It’ll show what that connection looks like and if it’s not what you normally connect to (I purposely pick a VPN server in a different state so I don’t have to think hard at a quick glance if it’s “right” ), you’re secure.
+1 for binhex
And don’t use cheap, super commercial VPNs like PIA. Go with a more expensive, principled service like Proton.
You’re right, there’s a point.
That is very very useful info, thanks!
I’ll just stick to binhex ver.
binhex’s already does wireguard.