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
[BUG] Cannot access WebUI with completely new docker image and default settings #305
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Mine did also stopp working.. well it's up and running but WebUI can not be accessed. Docker version 26.1.2, build 211e74b
|
OP did not do the port mapping correctly. The limitation is explained in the readme. Second poster's issue is likely gluetun related, which we don't provide support for. |
You are assuming and you are wrong, cause it has been working without any issues, both services, as I said IT just from everything working fine went to not working. ..so I went ahead and got a older image of qBittorrent and guess what, everything is working. Assuming shouldn’t be part of troubleshooting. |
No assumptions are made? Aptalca is just setting expectations that we will not support gluetun. There are two symptoms here, OPs There is not provided enough information to troubleshoot, as the image works fine in our tests, which are not using gluetun.
Does not help, what version? some ancient one from years ago? or just 2-3 builds ago? |
I got triggered by that exact fact, there is no need to point out that this team dose not support some other tools, no one is actively or indirectly seeking any support for such situation or issue either.. OP did (and so did) try to run qBittorrent without the dependency of Gluetun. I actually even removed Qluetune and qBittorrent (including Networks) images entirely and restarted the Docker Daemon even. Pulled the latest image of qBittorrent with all new auto generated config files and the problem was exactly the same. I for one fail to see logical reasons for this issue being related to any other service I'm running so I have not mentioned any of those. There is no hostility from my part but sure if that is your take of things then that is on you. We are here reporting the issue encountered, if the logs and so on are not enough then please do point out what else is required. |
Would probably need a bit more than the issue template asks for. This should cover enough to troubleshoot further. |
Is there an existing issue for this?
Current Behavior
Attempt to access via IP:Port. Get unauthorized
Expected Behavior
WebUI should load
Steps To Reproduce
docker compose up -d
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: