Linked above is another user with the same or similar problem to myself. The short of it is our IP address and port that we assigned on a custom network doesn't show up in the GUI. I can navigate manually to the ipaddress:port and access the webui. When I click the webui button on the container, nothing happens. The container won't communicate with other containers also. I have 3 broken containers; a vpn proxy, an indexer, and a download client. I feel the problem isn't just affecting the broken ones but the working ones as well. I have a 2nd indexer and download client and they too can't communicate with each other despite their appearance in the docker list being correct. Their webui work fine. I have cloud storage using a mariadb container and collab for documents, it's communication with those 2 containers seem to be unhindered.

 

I have a reverse proxy running as well, as far as I can tell it is working perfectly fine and forwarding me to the correct services.

 

For the other user, @joelones, it broke after an OS update. Rolling back didn't fix. For me it broke when I added a new drive to the array. I did an unbalance of the shares to move files to the new drive. I also ran docker safe new permissions as unbalance instructed me.

 

Recent testing shows that newly installed containers will assign their default port and work standalone. But when I set them to a different port that change never reflects on the docker list nor when navigating to the webui. If I install a new container and utilize the Bridge network. It assignes the 172.17.0.x IP and the container port is as it states and the 192.168.1.x port is also correct showing the changed port from default. I did testing with my broken containers switching to Bridge network and they won't communicate with each other. Not with 172 or 192 IP address in their settings.

 

You can check the other post for info I might have missed. But I think the meat of it is above.

Attached is my diag.

 

All my dockers run on the custom network. There are some on host or bridge. They were either required to be there to work or they didn't have functioning purpose to be on the custom network.

 

I have full backups dating back to May of both docker and Unraid. Have held off on restoring a backup of Unraid until I can understand the problem better, and that it didn't fix the problem on the other post.

 

Normally I have interest to troubleshoot and find the problem so it can be documented. At this point, I just want my services working again. If a nuke is what it takes, I've got backups.

waffle-diagnostics-20240731-1235.zip

I finally tried rolling back the docker image to a previous image. It's finally working now. Not sure what the issue was. Very strange to me to see it happen to multiple containers.