[Resolved] Docker Qbittorrent WebUI port appears "filtered" and is not accessible

Hi,

[context}

I am trying to install a docker Qbittorrent+openvpn (Headless qBittorrent client with WebUI and optional OpenVPN connection) on my new NAS running OMV latest version.

I have the same stack running on my previous OMV NAS without issue, but this Qb stack is just a more recent version (moving my old x32 NAS to a new x64 NAS).

[issue]

The QB container looks like running (Started qBittorrent daemon successfully), but I cannot access the WebUI interface (no http answer). Port defined is 9090.
NOTE the container is launched via Dockge and is not managed inside OMV itself, but I can see the container running in "Service-Compose-Containers" menu.

[troubleshooting]

When I look from my desktop to the ports on the NAS, I see this for port 9090 :

$ nmap -sT 192.168.1.32

..
9090/tcp filtered zeus-admin

..

I tried first using 8080, but it is the same, port appears as "filtered". What does that mean ?
Is that a firewall related issue ?

Thank you for your help.

Still investigating my issue, and found the root cause.

It seems to be docker image problem, and about the network route defined. Fortunately, I still have my x32 (armv7) stack running, so I can compare. And this is what I can see :

Previous and working machine (odroidhc2 is the localhost where OMV is installed) :

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.8.0.1        128.0.0.0       UG    0      0        0 tun0
0.0.0.0         172.27.0.1      0.0.0.0         UG    0      0        0 eth0
10.8.0.0        0.0.0.0         255.255.0.0     U     0      0        0 tun0
128.0.0.0       10.8.0.1        128.0.0.0       UG    0      0        0 tun0
172.27.0.0      0.0.0.0         255.255.0.0     U     0      0        0 eth0
192.168.1.0     172.27.0.1      255.255.255.0   UG    0      0        0 eth0
193.32.126.81   172.27.0.1      255.255.255.255 UGH   0      0        0 eth0

New and not working machine (NAS-N150 is the localhost where OMV is installed) :

# route -n                                          
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.8.0.1        128.0.0.0       UG    0      0        0 tun0
0.0.0.0         172.20.0.1      0.0.0.0         UG    0      0        0 eth0
10.8.0.0        0.0.0.0         255.255.0.0     U     0      0        0 tun0
128.0.0.0       10.8.0.1        128.0.0.0       UG    0      0        0 tun0
172.20.0.0      0.0.0.0         255.255.0.0     U     0      0        0 eth0
193.32.126.82   172.20.0.1      255.255.255.255 UGH   0      0        0 eth0

You can see there is no route for 192.168.1.0/24 for eth0, making my local network inaccessible from the docker container.

So I added the missing route :

# ip route add 192.168.1.0/24 via 172.27.0.1 dev eth0

And now QB WebUI is accessible !

I hope this change is permanent and that I will not have to enter that command after each startup... Not tested yet !

gderf ,

The compose file is almost the same than the old one, so I guess issue is elsewhere... may be related to the new machine arch ?

- old machine is odroid-hc2, an armv7l SBC

- new machine is the Beelink Me mini, N150 Intel x86-64. Btw, this machine has 2 network adapters, but I use only one, and there is only one visible from OMV, so I guess this is not the issue.

The compose file is like below (using 8080 port now) :

services:
qbittorrent-openvpn:
image: chrisjohnson00/qbittorrent-openvpn:latest
container_name: qb-openvpn
privileged: true
sysctls:
- net.ipv6.conf.all.disable_ipv6=0
volumes:
- /srv/dev-disk-by-uuid-f39c071a-91e2-4184-971f-a722a7697ca5/Download:/downloads
- /srv/dev-disk-by-uuid-f39c071a-91e2-4184-971f-a722a7697ca5/AppData/Qbittorrent:/config
environment:
- VPN_ENABLED=yes
- LAN_NETWORK=192.168.1.0/24
- NAME_SERVERS=8.8.8.8,8.8.4.4
- VPN_USERNAME=xxxxx
- VPN_PASSWORD=yyyyy
- PUID=996
- PGID=100
- WEBUI_PORT_ENV=8080
- INCOMING_PORT_ENV=8999
ports:
- 8080:8080
- 8999:8999
- 8999:8999/udp
restart: unless-stopped

Good news: it seems the new route is still present after restarting container.

Yes, through WebUI, I can select network interface to work with (tun0). And the qb process will stop if vpn connection goes down if I remember well.

Thank you for the link, I know I should use a more active image, I will definitely consider this.

Hum, I have to answer no. How should I test this specifically ?

Very clever tool ! Despite I have no UI on the NAS, I managed to open magnet using a firefox extension (Add link to qbittorrent WebUI) and that worked easily ! And I can see the IP address is from the VPN provider and not my own address.
Very good test indeed, thank you !

My version is 4.6.7, so I will definitely upgrade with the image you suggested above.

Thank you so much for all your advises, very useful !

New container from https://github.com/Trigus42/alpine-qbittorrentvpn installed and running, no issue setting it up !