-
Notifications
You must be signed in to change notification settings - Fork 35
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
Comments
Try deleting the container and restarting or even clearing the volume. |
For me both the stable and the latest release does not work. 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. I bind the port 8080 to 8083 but i can't imagine that this will make a difference right? |
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 |
I'm having the same issue, qbiittorent is running behind nginx in another container, and its giving me 401's
How can i do that? |
I strongly advise against it! You can only do it for tests. Not in production!
|
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. |
On stable release I get the webpage but on latest or 4.0 I only get 401 Error
Has anyone else experienced this?
The text was updated successfully, but these errors were encountered: