I've been on and off been having issues connecting to seeds and peers for anything I download with qbit lately. I have ProtonVPN and I am connected to p2p servers, some torrents are stuck at 0(0) whereas some will be stuck at 0(2817).

I have made sure the port in qbit is set correctly and the interface device, along with opening the port on my router. Ultimately what seems to work is I have to change the port several times, change the interface to ethernet, then back to Proton, then a single download works. Any tips for a fellow pirate?

  • VHS [he/him]
    ·
    1 year ago

    AFAIK, the port on your router is irrelevant as the VPN bypasses it. I'm not familiar with ProtonVPN, but with PIA you can get a forwarded port in the VPN app and specify that port in your P2P application. I use that method for Soulseek, but my qBittorrent works correctly in both directions without doing anything special.

  • DAMunzy@lemmy.dbzer0.com
    ·
    1 year ago

    I'm in windows with SurfShark and qBittorrent. I sometimes have to close out qBittorrent and disconnect from the VPN. Sometimes that doesn't work and I have to reboot the laptop. That normally fixes the problem for me. I tried looking at the ports and forwarding and interfacing but those seemed to do nothing to fix my issue. I have a feeling that it is the network drivers and/or the hardware itself.

  • NeroC_Bass@lemmy.dbzer0.com
    ·
    1 year ago

    Not having to update the router port sure makes things easier, especially since Proton changes the port at times.

    I believe I have found the issue, it appears split tunneling is broken right now. As soon as I disabled it, suddenly got seeds and was able to seed again. Shame split tunneling is not working again, as I need it off for local hosting certain games.

    • CalicoJack@lemmy.dbzer0.com
      ·
      1 year ago

      Docker is a cleaner solution for split tunneling. Container for the VPN (gluetun), and container for qbit bound to the VPN container for network access. You still need to manage the listening port when Proton changes it, but that's easy enough.

      If you set it up right, it also doubles as a bulletproof killswitch since qbit can't see any other network.