Does anyone know how to run qbittorrent and protonvpn in a VM? When I try to run the qbittorrent setup app I get this message (image below) and I don't see anything mentioning a VM in the qbittorrent [dot] org forum.

I am new to torrenting, so I don't really know what to do. I figured/assumed that torrenting/seeding in a VM might be safer as it is another layer deep, and that it may help keep traffic separate (inside the VM: I'd be using a vpn and torrenting, and outside the VM: I'd not be using a vpn and just regular internet surfing). Is this possible?

Thank you.

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 1 year ago (13 children)

Regardless of where you decide to run your VPN (normal system, VM, or container), just don't forget to turn killswitch on in the VPN settings. ProtonVPN is very good at this. They have killswitch built-in in all their client apps. And it's quite a tricky thing to configure manually.

  • source
  • hideshow 13 child comments
  • [–] 10 points 1 year ago (4 children)

    I just tie qbittorrent to the VPN virtual adapter, so even if Proton disconnects the traffic stops rather than moving over to my WAN IP.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 1 year ago (3 children)

    Got an explanation for how to do this?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 11 points 1 year ago (2 children)

    Preferences -> Advanced -> Network Interface

    Then select the VPN connection. That's what I do for qbittorrent. Not sure about other programs.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago (1 child)

    My VPN connection appears to change whenever I connect, because it's connecting to the quickest server, so I am not able to use the same settings in qbittorrent. How do you manage server shifts like that?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago (5 children)

    Kill switches aren't as reliable, binding your VPN to your torrent client is the only sure fire way to ensure you don't leak traffic through your home IP.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 1 year ago (4 children)

    Why? Killswitch is by definition a mechanism to not leak traffic outside VPN. This is exactly the purpose it's designed for. It is binding all traffic to VPN connection on system level. That is what it does under the hood, at least in ProtonVPN. It's using iptables or firewalld or whatever else is present in the system. Even when your VPN client app isn't running, killswitch is still there (and you can't access internet until you connect to the VPN).

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 1 year ago (3 children)

    I'm not the only person who thinks Kill switches don't live up to their name

    Bind always. Kill switches don't work reliably. https://www.reddit.com/r/torrents/comments/1hq8uh4/comment/m4o8n35/

    Kill switches can fail. Always bind your client to your vpn adapter. https://www.reddit.com/r/torrents/comments/1hq8uh4/comment/m4u9xod/

    While using a kill-switch is a good step, it may not provide complete protection. Combine it with binding your VPN network interface to qBittorrent for added privacy and security https://www.reddit.com/r/surfshark/comments/1jbf8sj/comment/mi1h8bc/

    Killswitches aren't perfect. Binding is. https://www.reddit.com/r/surfshark/comments/1jbf8sj/comment/mhtpc5t/

    Yep binding is so much better than killswitch. https://www.reddit.com/r/surfshark/comments/1jbf8sj/comment/mhu9gip/

    torrenting with kill switch turned on, leaks? https://www.reddit.com/r/ProtonVPN/comments/1261e5h/torrenting_with_kill_switch_turned_on_leaks/

    That's not a killswitch, that's binding your connection. It literally says that right in the screenshot. smh, kids these days. Killswitch is managed by your VPN, totally separate thing, and can still leak your IP at times. https://www.reddit.com/r/Piracy/comments/v2d3gp/comment/iatgezx/

    I've had an occurrence even in windows with kill-switch on where the app closed and downloads continued. https://www.reddit.com/r/unRAID/comments/1hmihfe/comment/m3ubxj8/

    Instead of kill switch (which fails a lot on many VPNs) you should bind your VPN to your torrent client. https://www.reddit.com/r/ProtonVPN/comments/1b7b6j3/comment/ktm29z8/

    Bind interface. Kill switch is the wrong way to go. https://www.reddit.com/r/Piracy/comments/1937alg/comment/khaey90/

    Kill switch is not reliable and can expose your IP. Please search for "how to bind vpn qBitTorrent" and follow the directions to bind the internet adapter to your vpn. That is the only safe way. https://www.reddit.com/r/Piracy/comments/1j4023b/comment/mg4iy2q/

    Bind qBit to your VPN. This stops all torrent traffic if your VPN drops it's connection or you forgot to connect. It's more reliable than a Kill Switch. https://www.reddit.com/r/qBittorrent/comments/ud2k5m/comment/i6ejaeg/

    Kill switches are unreliable, use binding instead https://www.reddit.com/r/torrents/comments/174pwzi/comment/k4aocdo/

    Bruh needs to learn how to bind his VPN & Torrent Client... Y'all, kill switches are NOT good enough. https://www.reddit.com/r/Piracy/comments/1b5mpgp/comment/kt6a10y/

    Bind your connection. Kill switches are functionally useless. https://www.reddit.com/r/torrents/comments/1c5yt4n/comment/kzxnzce/

    These are what I could find in the last 15 minutes, hopefully this is enough.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 1 year ago (1 child)

    Any idea if gluetun does this by default? A popular setup is setting the network mode on the application docker to the gluetun service and then gluetun itself says it has a killswitch built in. I assume they did that well since its very popular and this is pretty much the main purpose of the container.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago*

    Okay, I see. So killswitch implementation might be non-perfect, depending on VPN. And there are reports of Surfshark leaking IP when torrenting under killswitch. I guess they might not have "permanent killswitch" option like ProtonVPN and this is why it happened. So basically if torrent app launches before VPN or VPN closes before torrent app killswitch might get turned off together with VPN app and some traffic might leak. This is impossible under "permanent killswitch". So to rely on killswitch I guess the first thing to check is if internet is accessible after closing VPN client app. If not, then it's a good killswitch. But with qBittorrent it's always a good idea to use that setting for extra safety. It might not be present in most other torrent apps though, and to do the same manually using iptables or whatever might be tricky and error-prone.

  • source
  • parent
  • [–] [S] 1 point 1 year ago (1 child)

    Thank you. Do you mean even with ProtonVPN it is hard to configure?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    ProtonVPN makes it super easy - just a checkbox in options. But if you were to set up VPN yourself manually using OpenVPN configs for example, it's very hard and error-prone. For me this is probably the most valuable thing in ProtonVPN client apps.

  • source
  • parent