When using a VPN, your own router should not be involved in port forwarding. Proton must support port forwarding with p2p traffic, the specific VPN software you use must be setup to use Proton’s port forwarding, and your qbittorrent must be properly configured to use the correct port
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
💰 Please help cover server costs.
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.
Idk man I just turn the vpn on and bind the net interface to proton
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.
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.
This may be what I need to look into. Either this or virtualization. Thank you for the tip!