suddenly, all my Docker web interfaces are not working. This issue is with Docker using the bridge interface. The Docker local IP is showing as 172.17.x.x, while the routing table entry for the Docker bridge interface is displaying as 172.18.x.x.

 

Do you have any suggestions on how to fix this?

172.x.x.x IP addresses for containers in bridge is it's internal IP, and is always subject to change.  With any bridge container, you access it's IP via the Host (server) IP and Port, not it's internal

 

The WebUI entry on all the templates is almost always something akin to this:

http://[IP]:[PORT80]

Which takes you to the server's IP address, and whatever the container's port 80 is mapped to.  

 

Same thing with having one container communicate with another (EG: Radarr and SabNZBd).  Within Radar you tell it that SAB is at whatever host IP address and the applicable port, not the 172.x address

On 3/18/2025 at 4:37 AM, Squid said:

172.x.x.x IP addresses for containers in bridge is it's internal IP, and is always subject to change.  With any bridge container, you access it's IP via the Host (server) IP and Port, not it's internal

 

The WebUI entry on all the templates is almost always something akin to this:

http://[IP]:[PORT80]

Which takes you to the server's IP address, and whatever the container's port 80 is mapped to.  

 

Same thing with having one container communicate with another (EG: Radarr and SabNZBd).  Within Radar you tell it that SAB is at whatever host IP address and the applicable port, not the 172.x address

Thank you for explaining this to me.

 

I changed one of the containers' Network Types from bridge to custom:br0. The WebUI is working now. I am not sure what stopped all the containers from working, as I did not change anything; I just replaced the CPU. Should I change all the container network types from bridge to custom: br0?