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?
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
If you are using Linux I wrote a script just for that!
https://github.com/giu176/ProtonVPN-auto-NATPMP
I’m using it on my headless server and it worked fine for the last two months. Tell me if you need help in the setup (the Readme should be exhaustive).
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!
In case you need a pointer, I had to do this recently too. I’m no docker expert, but this works for me 👌
--- version: '3' services: gluetun: image: qmcgaw/gluetun:latest hostname: gluetun container_name: gluetun restart: always cap_add: - NET_ADMIN environment: - VPN_SERVICE_PROVIDER=custom - VPN_TYPE=wireguard - VPN_ENDPOINT_IP= - VPN_ENDPOINT_PORT=51820 - VPN_PORT_FORWARDING=on - VPN_PORT_FORWARDING_PROVIDER=protonvpn - WIREGUARD_ADDRESSES= - WIREGUARD_PUBLIC_KEY= - WIREGUARD_PRIVATE_KEY= devices: - /dev/net/tun:/dev/net/tun ports: #Proton - 34803:34803/udp - 80:80 #Gluetun - 8888:8888/tcp # HTTP proxy - 8388:8388/tcp # Shadowsocks - 8388:8388/udp # Shadowsocks - 8000:8000/tcp # HTTP Control Server - 8090:8090 # qBittorrent volumes: - /docker/appdata/gluetun:/gluetun #QBITORRENT qbittorrent: image: linuxserver/qbittorrent:latest container_name: qbittorrent network_mode: service:gluetun depends_on: gluetun: condition: service_healthy environment: - PUID=1000 - PGID=1000 - WEBUI_PORT=8090 volumes: - /docker/appdata/qbitorrent:/config - /data/torrents:/data/torrents restart: always
Just containerize/virtualize the shit and no split tunnel needed. Custom routes and fw rules can help too…
Are you on Arch? Because I am facing the exact same split tunneling issues using PIA VPN
Of course not, he would have announced it already if he was
🤣but seriously. PIA VPN announced that their split tunneling broke with some changes in the newest kernels/distro packages and said they will look into it
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.
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.
