Placing docker containers on custom docker network makes them inaccessible

[thatnovaguy]

I'm wanting to put my docker containers on a custom network so I can use the container name in place of the ip address when setting up the various arrs and other things. Once a container is moved to the new custom network it's webui becomes inaccessible. I'm not sure what I'm doing wrong or if it's something messed up within my setup.

 

[bonienl]

webUI access to containers won't work with user defined custom networks.

 

You can use bridge (e.g. br0) custom networks to put a container on a dedicated IP address.

I run my own DNS server on my LAN network, which allows me to create names with associated IP addresses.

 

[thatnovaguy]

13 minutes ago, bonienl said:

webUI access to containers won't work with user defined custom networks.

 

You can use bridge (e.g. br0) custom networks to put a container on a dedicated IP address.

I run my own DNS server on my LAN network, which allows me to create names with associated IP addresses.

 

NVM I sorted it. Somehow the container port got changed to match the host port so it was internally pointing to the wrong port.