FreeBSD - Unable to bind Web UI to port

[Tachikoma]

Hello,

I'm using qBittorrent on Windows for years with no problem. Yesterday I tried it on FreeBSD too.
I have a NAS with Nas4Free 10.3.0.3 (3379), and I wanted to replace it's built in Transmission client with qBittorrent running in a jail (mainly for the lack of proxy support in Transmission).
I installed qbittorrent-nox11 with pkg and when I launch it stops after the webUI default admin password warning, never get to the message about the webUI listening on the given port.
Checking the logs I see the following:

(N) 2017-01-14T10:49:39 - qBittorrent v3.3.10 started
(I) 2017-01-14T10:49:39 - qBittorrent is trying to listen on interface 192.168.2.4 port: 8999
(N) 2017-01-14T10:49:39 - Peer ID: -qB33A0-
(N) 2017-01-14T10:49:39 - HTTP User-Agent is 'qBittorrent v3.3.10'
(I) 2017-01-14T10:49:39 - DHT support [ON]
(I) 2017-01-14T10:49:39 - Local Peer Discovery support [ON]
(I) 2017-01-14T10:49:39 - PeX support [ON]
(I) 2017-01-14T10:49:39 - Anonymous mode [OFF]
(I) 2017-01-14T10:49:39 - Encryption support [ON]
(I) 2017-01-14T10:49:39 - Embedded Tracker [OFF]
(I) 2017-01-14T10:49:39 - UPnP / NAT-PMP support [ON]
(I) 2017-01-14T10:49:39 - GeoIP database loaded. Type: GeoLite2-Country. Build time: Wed Jan 4 02:59:05 2017.
(C) 2017-01-14T10:49:39 - Web UI Error - Unable to bind Web UI to port 8181
(I) 2017-01-14T10:49:39 - qBittorrent is successfully listening on interface 192.168.2.4 port: TCP/8999
(I) 2017-01-14T10:49:39 - qBittorrent is successfully listening on interface 192.168.2.4 port: UDP/8999
(I) 2017-01-14T10:49:39 - External IP: xx.xx.xx.xx

Earlier I had another critical log entry:

(C) 2017-01-14T10:26:06 - qBittorrent failed listening on interface 0.0.0.0 port: TCP/8999. Reason: Protocol not supported.

But that was eliminated by setting the connection interface (Connection\Interface=re0)

I have the following ifconfig in the jail:

re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether b0:48:7a:80:31:4a
        inet 192.168.2.4 netmask 0xffffff00 broadcast 192.168.2.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
bge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO,LINKSTATE>
        ether 3c:d9:2b:02:0d:31
        media: Ethernet autoselect
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>

I also tried running it from outside of the jail and that is working, binding to the listening port is successful.
Can someone help on this, what is missing?. Many thanks...

[Peter]

Well it sure sounds like the jail is misconfigured.
I only used FreeBSD, and FreeNAS, but never Nas4Free.

Do you have full access to the system on Nas4Free?
Do you set up the jails by yourself?

I would look into the usual stuff.
1) Google Jail port bind
2) Google jail management (it threw me up this: https://www.freebsd.org/doc/en_US.ISO88 ... zjail.html)
3) Try #FreeBSD

By the way, why the 10.3.0.3 version?
I went to the website to grab the ISO so I could help, but there is also a 11.0.0.4 version...

[Tachikoma]

Hello,

Thanks for the reply.
I use TheBrig as a jail manager, because it integrates nicely to the Nas4Free menu system. I'm really in novice level in FreeBSD, I chose Nas4Free because it provided a fully automatic NAS framework with easy to use gui. It's just happened to be based on FreeBSD.

I didn't update to the latest version of it yet, I can try, but it would be good to understand what is happening. Usually the reason of port binding failure as I understand is that the port is used by another process, and I believe it is in connection with trying it in a jail environment somehow. Unfortunately this is the only option for me, as Nas4Free works from RAM disk with a very limited size.

Worth to note here that I successfully installed a Transmission client to this very same jail, and it was working OK, I'm able to access it through its web-ui. So something could be not OK around qbittorrent-nox.

Thanks once again, regards...