VPN and qBittorrent not playing nicely (lemmy.dbzer0.com)

submitted 1 year ago by NeroC_Bass@lemmy.dbzer0.com to c/piracy@lemmy.dbzer0.com

15 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[-] NeroC_Bass@lemmy.dbzer0.com 5 points 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 8 points 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.

[-] NeroC_Bass@lemmy.dbzer0.com 1 points 1 year ago

This may be what I need to look into. Either this or virtualization. Thank you for the tip!

[-] LunchEnjoyer@lemmy.world 2 points 1 year ago

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

[-] plague_sapiens@lemmy.world 2 points 1 year ago

Just containerize/virtualize the shit and no split tunnel needed. Custom routes and fw rules can help too...

[-] lemmy_nightmare@sh.itjust.works 1 points 1 year ago

Are you on Arch? Because I am facing the exact same split tunneling issues using PIA VPN

[-] MomoTimeToDie@sh.itjust.works 8 points 1 year ago

Of course not, he would have announced it already if he was

[-] lemmy_nightmare@sh.itjust.works 2 points 1 year ago

🤣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