docker-qbittorrent icon indicating copy to clipboard operation
docker-qbittorrent copied to clipboard

Web interface not available on latest

Open RacerBas opened this issue 5 years ago • 6 comments

On stable release I get the webpage but on latest or 4.0 I only get 401 Error Has anyone else experienced this?

RacerBas avatar Jun 03 '20 16:06 RacerBas

Try deleting the container and restarting or even clearing the volume.

wernight avatar Jul 29 '20 14:07 wernight

For me both the stable and the latest release does not work. If i try to access the web UI it always instantly returns a 401 status code, not asking me to enter a password.

I've restarted and recreated the container many times, tried to switch volumes and also tried bind mounts instead of volumes, but it did not change. Do you have other suggestions what to try? The logs are completely empty...

I bind the port 8080 to 8083 but i can't imagine that this will make a difference right?

major-mayer avatar Jan 12 '21 09:01 major-mayer

qBittorrent check origin header. You must to bind same port as you expose in docker

$ docker run --rm -p 8083:8083  wernight/qbittorrent:4.2.5 qbittorrent-nox --webui-port=8083

Or you can disable CSRF protection by settings file

jetexe avatar Mar 15 '21 10:03 jetexe

I'm having the same issue, qbiittorent is running behind nginx in another container, and its giving me 401's

Or you can disable CSRF protection by settings file

How can i do that?

Z0lid avatar Oct 09 '21 20:10 Z0lid

I strongly advise against it! You can only do it for tests. Not in production!

  1. Copy default config file from here
  2. Add WebUI\CSRFProtection=false into Preferences section
  3. Mount result config into /config/qBittorrent.conf path of container via config or volume docker options

jetexe avatar Oct 11 '21 06:10 jetexe

Reverse proxy shouldn't directly affect this. What could be an issue is the reported user's IP. qBittorrent has some brute force protection by default if I recall, and if it thinks that all requests are coming from your reverse proxy IP as opposed to the machine sending the request, than it'll quickly lock out any further request.

Caddy is IMO a simpler better solution as a reverse proxy compared to Nginx.

wernight avatar Jan 07 '22 13:01 wernight