I have a couple containers now that are not apparently reading the WebUI data correctly from their XML files.

I've verified the data is correct in the XML files, but it's not getting picked up on a container restart.

 

 

 

Any ideas why this would happen?  I've tried changing the WebUI data and restarting the container, to no effect.  It stores the changes, but doesn't update the menu correctly. I can manually put in the correct port for the web address and access the appropriate container WebUI, so I know everything is running as it should.

I have tried restarting the Docker service, with no effect.

I will also note, I have 2 containers exhibiting this problem, and both are minecraft containers, of which there are 3 java and 2 bedrock (my kid is beginning to annoy me. ) 1 each of java and bedrock are not updating their WebUI.

 

Edited January 10, 20215 yr by sota

The entry on the WebUI should read

http://[IP]:[PORT:8222]/

The WebUI entry refers to the container port, not the host port, and should never really need to be changed

It still isn't changing the address:port listed in the drop down menu though, even when I put it back to 8222.

What version of unraid are you running?  My 6.8.3 and 6.9 do not show the name of the container at the top of the drop down

6.7.2

28 minutes ago, sota said:

6.7.2

You really should stay more current. Unraid's upgrades are free, and each one adds fixes for issues found along the way. Staying so far behind makes you vulnerable.

I'm not exposed, as the machine doesn't have carte blanche connectivity to the internet.

and I don't like to "fix" things that aren't broken.

You do realize the irony of posting about an issue and then saying you don't like to "fix" things that aren't broken?

if you are implying that upgrading to beyond 6.7.2 will fix it, as in it is a known bug that was resolved, then that's a possible avenue.

I'm more interested in finding out why editing things that should result in changes, do not.