ANSWERED Connection refused (111)

[fawken_kelpo 0]

Hi everyone, I got AirVPN to connect it to qBittorrent that I have installed on my Truenas Scale server, after setting everything up it works for a minute, and then I get Connection refused (111), then I have to reinstall the app, it works for a minute, and stops working again.

I have set up port forwarding on my verizon router, but that didn't fix it. I have the proper port set up in qBittorrent, I followed this guide to set everything up

My docker compose yaml:

services:
  gluetun:
    cap_add:
      - NET_ADMIN
    container_name: gluetun
    devices:
      - /dev/net/tun:/dev/net/tun
    environment:
      - TZ=America/New_York
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=wireguard
      - WIREGUARD_ENDPOINT_IP=REDACTED
      - WIREGUARD_ENDPOINT_PORT=REDACTED
      - WIREGUARD_PUBLIC_KEY=REDACTED
      - WIREGUARD_PRIVATE_KEY=REDACTED
      - WIREGUARD_PRESHARED_KEY=REDACTED
      - WIREGUARD_ADDRESSES=REDACTED
      - FIREWALL_VPN_INPUT_PORTS=REDACTED
      - SERVER_COUNTRIES=
      - DNS_ADDRESS= REDACTED
    image: qmcgaw/gluetun:latest
    ports:
      - 8080:8080
      - 6881:6881/udp
      - 6881:6881/tcp
    restart: unless-stopped
  qbittorrent:
    container_name: qbittorrent
    depends_on:
      - gluetun
    environment:
      - PUID=568
      - PGID=568
      - TZ=America/New_York
      - WEBUI_PORT=8080
    image: linuxserver/qbittorrent:latest
    network_mode: service:gluetun
    restart: unless-stopped
    volumes:
      - ./configs/:/config
      - /mnt/NAS 16TB 2 Vdevs Mirrored /arr-apps/Downloads:/DownloadsT

My truenas version: ElectricEel-24.10.1

If anyone has any suggestions on what I can try, I'd really appreciate it, thanks!

Update: I was able to resolve this issue by having 2 forwarded ports, when 1 stopped working, I switched to the other one within qBittorrent, and now it's been working well so far, not sure why this happens though.

[Staff 10081]

7 hours ago, fawken_kelpo said:

Update: I was able to resolve this issue by having 2 forwarded ports, when 1 stopped working, I switched to the other one within qBittorrent, and now it's been working well so far, not sure why this happens though.

Hello!

Problem solved. The reason of the problem and why your method works perfectly can be inferred from GlueTun behavior described here: https://airvpn.org/forums/topic/63708-gluetun-port-forwarding-works-for-an-hour/?do=findComment&comment=239350

By changing port you force a new socket on the rebuilt tunnel. Re-starting qBittorrent from scratch or the whole container should fix the issue as well. Please note that you have an additional option for mitigation described in the linked thread that does not require the workaround you implemented, worth a try.

Side note, please insert the proper port for qBittorrent on your compose file ports: section and if necessary set properly the FIREWALL_VPN_INPUT_PORTS variable. Ref. https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/firewall.md

Kind regards
 

[fawken_kelpo 0]

20 hours ago, Staff said:

Hello!

Problem solved. The reason of the problem and why your method works perfectly can be inferred from GlueTun behavior described here: https://airvpn.org/forums/topic/63708-gluetun-port-forwarding-works-for-an-hour/?do=findComment&comment=239350

By changing port you force a new socket on the rebuilt tunnel. Re-starting qBittorrent from scratch or the whole container should fix the issue as well. Please note that you have an additional option for mitigation described in the linked thread that does not require the workaround you implemented, worth a try.

Side note, please insert the proper port for qBittorrent on your compose file ports: section and if necessary set properly the FIREWALL_VPN_INPUT_PORTS variable. Ref. https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/firewall.md

Kind regards
 

Thank you so much!