Container Webui context menu IP/Port not updating when changes are made

Tested this on 6.9 Beta 30 (ish) and it works perfectly.   Looks like you've done two things here

 

The template shows 

 

  <WebUI>redacted.duckdns.org/</WebUI>

and the applicable config line shows 

 

  <Config Name="WebUI" Target="8080" Default="8080" Mode="tcp" Description="WebUI - Default 8888" Type="Port" Display="al>

Now, the complete line isn't there (you've cut off the end of it), but what you did is that at some point, you edited the app, switched to advanced view, and then edited that URL to be what you've got above.

 

You can change the port all day long when you edit the Port, but because the actual URL you've changed previously to the duckdns address doesn't include a reference to either the IP or the Port, nothing is ever going to happen.

 

The appropriate line for WebUI is

 

http://[IP]:[PORT:8080]

Set up like that, the system will properly adjust the webUI in the drop down to reflect the IP address and the Port number you've selected.

 

or, if you want it to go to a particular reverse proxy, then

http://redacted.duckdns.com:[PORT:8080]

Note that the 8080 IS correct in the above lines, regardless of whatever you change the port to be.  It refers to the CONTAINER port, and when changing the port mapping you're adjust the host port.

Changed Status to Retest

Hey Squid! First off, thanks for you reply and for keeping my information private. I actually ran across this problem because I nixed the domain name you redacted and was moving my containers to another.

 

Reading your post, it seems like the idea here is that my values aren't configured properly for WebUI?

 

I have two trilium instances, one that doesn't do this and one that does, so it was pretty trivial to to test.

"trilium" works, "trilium-joran" doesn't.

On trilium, I changed the WebUI values to:

 

https://[IP]:[PORT:8080] , this became 192.168.2.68:8888 in webUI 

 

http://redacted.duckdns.com:[PORT:8080] , became http://redacted.duckdns.com as expected (wanted to try one that shouldn't work at all) 

 

and finally https://trilium.myCURRENTdomainname.duckdns.org > mapped to https://trilium.myCURRENTdomainname.duckdns.org just like I wanted. My other working containers function like this too.

 

On trilium-joran I changed it to:

http://[IP]:[PORT:8080] is still showing https://trilium.domain.you.redacted.duckdns.org

 

http://redacted.duckdns.com:[PORT:8080] is above.

 

https://trilium.myCURRENTdomainname.duckdns.org is above.

 

Something weird happened when I tried remove the port mapping, too. Since I didn't need it on Trilium to access through a reverse proxy, I removed the port mapping which unexpectedly removed the WebUI option from the Docker page altogether. So when I tried to access Trilium from there it only showed Console and the rest of the usual options. Opening it via the domain name I'm using was a-okay.

 

I got confused and the XML looked good so I re-added the port mapping. Not only did the WebUI option come back for Trilium, it also set Trilium-Joran to the exact same Web UI address as Trilium.

 

So now, I've got

 

Trilium: XML is https://myCURRENTdomainname.duckdns.org > WebUI shows https://myCURRENTdomainname.duckdns.org

 

Trilium-Joran: XML is https://[IP]:[PORT:8080] > WebUI shows https://myCURRENTdomainname.duckdns.org

 

Neither container has changed behavior otherwise, Trilium will make the web address whatever I please, but trilium-joran's can only be updated by removing all port mappings for one, which removes the web ui option completely for that specific container, and then adding one back in, which forces the address for both containers to the one that had its port mapping removed and re-added. 

 

Funky.

 

I also have at least one other fully functional behind my reverse proxy set up with a similar subdomain scheme at https://git.myCURRENTdomainname.duckdns.org which I can change to whatever. 

Edited October 27, 2020 by Magicaldave

I don't run custom networks, but on your Adguard (br0), there is no port mapping at all, so the [IP]:[PORT:8080] will always resolve as [IP]:8080 regardless if you change the port mapping (since port mappings are ignored).

 

I've tested simply changing the WebUI entry, and it does pick up changes no problems on br0 (6.9.0-beta31)

The host port mappings aren’t being used at all for most of my dockers at the moment, that’s part of how I arrived at the issue in the first place. It’s just that the GUI link to my docker isn’t changing to what it’s set to in the XML. 

 

I found a weird sort of workaround in the process of removing the port mapping, but that itself was problematic since no ports mapped to host means no webGUI option anyway. So I guess my real solution is gonna be to add the webpages to unRAID using a plug-in. 
 

not that it’s a big deal anyway, but annoying to have to delete the template for some containers in order to get the address to match what it already is in XML. Seems like a defect somewhere. 
 

I’ll check perms on the template files when I regenerate them and see if it makes a difference.