Hey yall,

I am having trouble with docker containers, before 7.2.5 update, all my docker services were accessible using their 172.19.0.X IPs (custom network called dockernet), as I had a static route on my router. But after the 7.2.5, 7.2.6 and now 7.3.0, update, the issue still persists. I've tried to toggle Host access to custom networks on and off, and Docker custom network type from ipvlan to macvlan and back to ipvlan. But regardless, I can't access the docker containers from their container IPs.

What I've found:

Using the unRAID terminal, I can ping the container IP - so the server and the container network (dockernet) is fine

If I ping from my router terminal to container network that times out.

I haven't changed anything in my router or in my docker settings. After the update, it just stopped working .

I can upload my diagnostic logs, but I can someone just confirm that the annoymous logs won't contain docker enviromental keys, because some of the enviromental keys contain API and/or passwords.

Thank you

Edited May 18May 18 by OmgItsHeaven
Typo fix.

Hey,

For anyone that comes across this page. I've somewhat managed fixed problem.

I still don't know what changed in unRAID or the docker engine in the 7.25 to 7.30 updates, but my semi-temporary solution was to create a custom br0 ipvlan on the same subnet as my LAN network and attach my reverse proxy container directly to it. Then connect my reverse proxy container to the custom docker network and access my services through that.

What I've tried before creating the br0 ipvlan: creating a new custom network, manually adding a static route in the network setting on unRAID and manually adding an entry in the iptables to see if it could fix the problem. That did not fix my problem.

@OmgItsHeaven How does it look in real-life?

Can you post config/screenshot?
I have the same issue, My GW (Router) and local LAN cannot access the custom docker network.

On 6/2/2026 at 12:26 AM, Seq said:

@OmgItsHeaven How does it look in real-life?

Can you post config/screenshot?
I have the same issue, My GW (Router) and local LAN cannot access the custom docker network.

Heya,

Its a bit late, but in case you were still having the problem or if someone else has a similar problem. Here is what I did.

Essentially in the docker setting, I clicked on that tick box next to IPV4 custom network on interface br0 (not in this picture, but it will show up if you stop docker), and defined the subnet and gateway. (That is for my local network).

Because I access my container through a local reverse proxy, I only edited my local NPM container. The primary network was the br0 network, and I defined a static IP, and under advanced, I added --network=dockernet under extra parameters.

Basically after that, I was able to access my containers through the reverse, but I stil am not able to access my container by putting the direct IP. But this gets the job done