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
this post was submitted on 14 Nov 2023
53 points (92.1% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54565 readers
454 users here now
⚓ 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
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
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).
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
Idk man I just turn the vpn on and bind the net interface to proton
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.
Do you use a proxy server through the settings, or just turn on your VPN and run it while torrenting?
I use Nord, and with the former method I was having issues. I reported it in an issue on the GitHub, and even contacted Nord for support. Now, there does seem to be a lot of down time with the regular method, but with the proxy ("better" method normally) there was times where it was exactly as you described- tons of seeds or leeches, but no connections, uploads, or downloads across the board.
In the execution log, there was an error that'd pop up repeatedly. I can't remember or see at the moment what that error is, something about SOCKS5, the proxy connection. But after popping 5-10 times, that's when everything would hit zeroes. I would have to close and reopen qBittorrent to get it to start again. When I used uTorrent before, I never had these issues, so I was thinking about moving on to some other torrent application. Wanting to stay with Open Source programs kept me for now.
I just fire up the VPN and run it with default settings, minus the port forward within the VPN client itself. So far after a few days of having split tunnel off, it's still working. Proton did recently release an update, I may try turning it back on, as having VPN active without split tunnel breaks my remote connection outside my home network.