qBittorrent behind firewall

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 I guess it is just randomly breaks for now since it appears to be back.

Current Config file (minus the keys and stuff)

 undefined

    
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

You're viewing a single thread.

10 comments

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.
If the VPN provider does not support port forwarding then it is normal and expected to always be firewalled. Toggling random ports doesn't change that fact.
Not sure why you would sometimes see your status as fully connectable, guessing either it's a Windscribe misconfiguration when you initially connect (?) or qBittorrent gets confused during the intitial connect. Or there's some other misconfiguration.
You might want to see if other people using that VPN provider have more insight, maybe they are doing something strange with the ports when you initially connect & eventually close them on you.
- So your saying it should have never worked even if I was not using docker? Like when I just used the VPN client and normal qBit client? Sorry if dumb question.
  Also it's now working.... I have no idea
  
  So your saying it should have never worked even if I was not using docker?
  Correct.
  Also it’s now working… I have no idea
  Yeah that's weird, I don't know if you accidentally found a way to hack Windscribe into temporarily giving you a port forward on their free plan. But otherwise you do need to be a paid member on their Pro account for that feature.
  Or it's just going to randomly stop working again.
  Is there a way to actually test your port forward within Docker? I'm not familiar enough with that configuration to suggest anything but maybe someone else knows about that. Usually without Docker I'd just start up the torrent client & then use a web browser with any port test website (https://www.canyouseeme.org, https://www.yougetsignal.com/tools/open-ports, etc.). But for Docker not too sure how to go about that.
  
  Cheers thanks for the information I kinda just assumed it just worked... Lol
- Not sure why you would sometimes see your status as fully connectable
  One side of the connection needs a public address, not both. When both parties don't have a publicly addressable IP, the status is firewalled. I guess.
  
  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.
  
  You might be confusing public IP addresses with ports?
  I mean publicly addressable address like in: not in a private network where SNAT/ masquerading is in place between the torrent-client's host and the Internet.
  It was mentioned, that no port forwarding is in place.

10 comments