this post was submitted on 14 Nov 2023
53 points (92.1% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54424 readers
366 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
Ko-fi Liberapay

founded 1 year ago
MODERATORS
db0@lemmy.dbzer0.com
sunbrothersco@lemmy.dbzer0.com
dataprolet@lemmy.dbzer0.com
Flatworm7591@lemmy.dbzer0.com
RandomLegend@lemmy.dbzer0.com
53
VPN and qBittorrent not playing nicely (lemmy.dbzer0.com)
submitted 11 months 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
[–] CalicoJack@lemmy.dbzer0.com 8 points 11 months ago (1 children)

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 11 months ago (1 children)

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

[–] LunchEnjoyer@lemmy.world 2 points 11 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