I have been using this config for qBittorrent for awhile and been working for the most part. Sometimes it gets “connection status: Firewalled” I would fix this by going to settings -> connection and click the “Random” button a couple times and save and then it would work again. This seems to not work anymore. Is there a better fix for this? Back before I used docker I don’t remember ever having to do this. I have never done any kind of manual port forwarding my current VPN provider does not do that at the price I have it for right now. Let me know if you need more information about my setup or something

Thanks

Current Config file (minus the keys and stuff)

services:
  gluetun:
    image: qmcgaw/gluetun:latest
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_SERVICE_PROVIDER=windscribe
      - VPN_TYPE=wireguard
      - WIREGUARD_PRIVATE_KEY=
      - WIREGUARD_ADDRESSES=
      - VPN_ENDPOINT_PORT=
      - WIREGUARD_PRESHARED_KEY= 
      - SERVER_REGIONS= 
    ports:
      - 8080:8080
      - 6881:6881
      - 6881:6881/udp
    restart: always
    
    
  qbittorrent:
    container_name: qbittorrent
    image: lscr.io/linuxserver/qbittorrent:latest
    network_mode: "service:gluetun"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - WEBUI_PORT=8080
    volumes:
      - /home/blxter/server/qbittorrent/config:/config
      - /home/blxter/raid/media/torrents:/torrents
    restart: unless-stopped
    depends_on:
      gluetun:
        condition: service_healthy
  • Brickfrog@lemmy.dbzer0.comEnglish
    0·
    6 months ago

    You might be confusing public IP addresses with ports? If your torrent client doesn’t have a public IP address that just means it’s offline / no internet. Maybe your internet is down or the VPN is disconnected. You’re won’t torrent anything at all in that state.

    One side of the connection needs a public address open port, not both. When both parties don’t have a publicly addressable IP open port, the status is firewalled. I guess they can “see” each other but are unable to exchange any torrent data.

    For what it’s worth in the situation where both peers don’t have open ports (meaning they are both firewalled) they end up having to wait for another peer to join that torrent swarm that happens to have a open port, that’s the only way any data will exchange in that swarm. Until that happens those two peers will sit there waiting and not exchanging data.