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?

  • NeroC_Bass@lemmy.dbzer0.comOP
    link
    fedilink
    English
    arrow-up
    5
    ·
    8 months 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
      link
      fedilink
      English
      arrow-up
      8
      ·
      8 months 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.

        • Lunch@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          8 months 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
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      8 months ago

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