Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
AbstractWebApplication::validateHostHeader prevents webUI from being accessible when running in a docker container #7641
qBittorrent version and Operating System:
If on linux, libtorrent and Qt version:
What is the problem:
Tying to access the webUI from within the local lan with qbittorrent-nox running in docker container on another host on the lan causes the following warning message in the logs:
The webUI is not displayed, no page is displayed at all.
What is the expected behavior:
The webUI would be displayed
Steps to reproduce:
Run qbittorrent in a docker container and try to access the webui from another host.
Extra info(if any):
The full message is:
I'm just using the standard docker container set-up: The interface inside the docker container is eth0 and the ip address is 172.17.0.3. The qBittorrent webUI is listening at port 8080 inside the container. Docker is mapping the external port 21011 to the port 8080 inside the container. The host is a raspberry pi at IP 192.168.1.100 and I'm trying to connect from another PC on the lan who's IP is 192.168.1.118. I have some other self hosted services running on the Pi that work fine, and qBittorrent 3.3.13 was not having this problem.
As a workaround, obviously you can set both ports to the same number and it should work.