Blairwin Posted January 21, 2022 Share Posted January 21, 2022 I have two docker containers of binhex/arch-qbittorrentvpn and one does not open on the correct custom webui port I specified. I have changed the WebUI element to 8085 as such: When I click on the container and select WebUI it takes me to the default port 8080; however, I can navigate to the UI by manually entering my IP:Port in my browser. It appears that only this one container is affected, all of my other containers appear to be working. I have cleared browser cache, tried a different browser, restarted unraid, and rebuilt my docker image. So far nothing has worked to fix the issue. Quote Link to comment
Squid Posted January 22, 2022 Share Posted January 22, 2022 The webUi always refers to the container port and really shouldn’t ever need to be touched. All you have to do is change the appropriate host port on the template and it figures it all out. Also, if you running the container in either host network or assigned it a specific up address then all port mappings are ignored by design of docker itself Quote Link to comment
Blairwin Posted January 22, 2022 Author Share Posted January 22, 2022 2 hours ago, Squid said: The webUi always refers to the container port and really shouldn’t ever need to be touched. All you have to do is change the appropriate host port on the template and it figures it all out. Also, if you running the container in either host network or assigned it a specific up address then all port mappings are ignored by design of docker itself I would assume the same, changing the variable in the template and it gets updated, but its not working. I've also tried changing it in the docker template and it doesn't work. I'm running it in Bridge with no static address. Quote Link to comment
Blairwin Posted January 27, 2022 Author Share Posted January 27, 2022 I attached copies of my xml files. They are setup correctly but the webui function doesn't work as described above. my-binhex-qbittorrentvpn-Sonarr.xmlmy-binhex-qbittorrentvpn-Radarr.xml Quote Link to comment
bonienl Posted January 27, 2022 Share Posted January 27, 2022 There is nothing wrong with the webGUI. When using bridge mode you need to create a port mapping for each port that is needed, including the port to access the webUI. Quote Link to comment
paulio23 Posted July 22, 2022 Share Posted July 22, 2022 Have you figured this out? im having the same problem. ive got two of the same docker running. changed the mapped port and the WebUI port on of the dockers (8879 on one and 8868 on the other), but when i click on "WebUI" from the dashboard on either docker, it opens 8868. Quote Link to comment
trurl Posted July 22, 2022 Share Posted July 22, 2022 6 minutes ago, paulio23 said: same problem Did you read the replies on this thread? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.