Open Jorman opened 4 months ago
Isn't it a duplicate of #20006?
It would seem so, but that one was closed as if it was resolved, actually the current version of qBittorrent has libtorrent 2.0.10 inside it? and so is it just a "delay" in the linuxserver build or actually libtorrent for the current version of qBittorrent has not yet been updated to 2.0.10? Anyway yes it is the same problem, I didn't find it because I didn't search it among the closed ones
actually the current version of qBittorrent has libtorrent 2.0.10 inside it?
If you use official docker image, then no, it wasn't updated yet.
I guess docker image waits for the next qBittorrent release to bundle a new libtorrent version. Unlike distro packages where the app and library are updated independently.
Thanks for the info, I'll wait the official update, in the meantime I switched off the UPNP for the webui, as in the suggestion provided in the other topic
Thank you
qBittorrent & operating system versions
qBittorrent: v4.6.3 Web UI (64-bit) Operating system: Debian 11 x64 Docker version: 20.10.21, build baeda1f
What is the problem?
I noticed a problem with port forward functionality. I don't know exactly how long this problem has been present, but for a while already, I don't know though if it is a qBittorrent problem or a Linuxserver version problem
It happens that during startup, the mapped port is "confused" with the webui port, I don't know for what reason, how can I do to get a more detailed log?
Steps to reproduce
In the docker qBittorrent is set up as the host, I use it in this manner, so I take advantage of UNPN, but lately it's been doing this thing Ecco il docker-compose
Additional context
No response
Log(s) & preferences file(s)
Do you have any idea what is going on? Is it a qBittorrent problem or is it a Linuxserver problem?
Thanks J