Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web interface not available on latest #22

Open
RacerBas opened this issue Jun 3, 2020 · 6 comments
Open

Web interface not available on latest #22

RacerBas opened this issue Jun 3, 2020 · 6 comments

Comments

@RacerBas
Copy link

RacerBas commented Jun 3, 2020

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

@wernight
Copy link
Owner

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

@major-mayer
Copy link

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?

@jetexe
Copy link

jetexe commented Mar 15, 2021

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

@Z0lid
Copy link

Z0lid commented Oct 9, 2021

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?

@jetexe
Copy link

jetexe commented Oct 11, 2021

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

@wernight
Copy link
Owner

wernight commented Jan 7, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants