Docker WebUI links wrong after network changes

[veri745]

I recently got a new router and changed my network config.

 

My old network had a subnet of 192.168.1.0/24, and my new network has a subnet of 192.168.2.0/24

 

My unraid server used to have a fixed IP of 192.168.1.200, and now it is located at 192.168.2.100

 

I updated the network.cfg with the new network info: IPADDR/GATEWAY/DNS etc, updated my port mappings for my docker containers, rebooted the server, disabled/re-enabled docker.

 

But still, the WebUI links for each of my docker containers links to 192.168.2.200.  This is the new subnet, but the old fixed IP octet.

 

What do I need to do here?

 

*edit*

Unraid version is 6.12.3

Edited September 7, 2023 by veri745
unraid version info

[veri745]

BTW, the docker containers are all up and working, and talking to eachother.

[veri745]

Also note, it's not all docker containers.  One new container I added gets the proper WebUI link, as well as a couple of the old ones, notably the containers that connect via VPN, which needed config changes before they would connect afterward.

 

But restarting/shutting down individual containers, nor disabling/re-enabling docker seems to fix the others.

Edited September 7, 2023 by veri745

[Squid]

When editing the container, switch to Advanced view.  What does the WebUI line say?

[veri745]

1 hour ago, Squid said:

When editing the container, switch to Advanced view.  What does the WebUI line say?

Example:

http://[IP]:[PORT:8181]/

 

[veri745]

OK, another subsequent reboot seems to have resolved the issue. I'm still confused as to where that incorrect IP was coming from. 

[JonathanM]

8 hours ago, veri745 said:

I recently got a new router and changed my network config.

 

My old network had a subnet of 192.168.1.0/24, and my new network has a subnet of 192.168.2.0/24

Hindsight 20/20, it probably would have been much easier to reconfigure the new router to match the old settings instead of reconfiguring the rest of your network.

[veri745]

30 minutes ago, JonathanM said:

Hindsight 20/20, it probably would have been much easier to reconfigure the new router to match the old settings instead of reconfiguring the rest of your network.

Yes, except I wanted a different subnet because it created issues with connecting to my wireguard VPN from remote networks using the same subnet.

Maybe there's another way to fix that, but I figured new router/firewall install was a good opportunity to do so.