crafty35a
-
Posts
22 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by crafty35a
-
-
1 hour ago, Squid said:
While you don't specify which qbittorent you are using, a common issue with how maintainers specified the WebUI entry was something like
http://[IP]:[PORT8080]
where 8080 is the host port. The port number in the WebUI entry always refers to the container port and the system remaps and adjusts the value accordingly
I am using Hotio's container, but it's not anything like that. I manually specified the entire URL and port, no variables - but the second container still links to the first container's specified URL.
As a test, I just changed the second one's WebUI setting to http://www.google.com - but the UnRAID UI still links to the custom URL I have set for container 1.
Multiple issues setting Docker container custom WebUI URL
in Stable Releases
Posted
Similarly, I just tried editing the WebUI for my second linuxserver/sonarr instance, and no matter what I set it to, it is sending me to the WebUI setting that was first defined when I set up the container.