As described in the title, I can't access the webui for docker containers, even locally, when the containers are configured to use a wireguard interface that's configured via unraid. I know the wireguard connection works fine as I can ping external sites over the interface from unraid itself (over the wireguard interface) and from inside the container, so it doesn't seem to be a connection issue. More likely some routing issue? The webui works fine when configured in bridge mode. I get "connection time outs" when the interface is up. I was trying to follow the guide here

 

Most people have had issues trying to do this remotely, but my issue specifically is local, so I'm not sure where to go with this to fix it.

Try Tailscale:

 

 

It's been some time since I posted this, so I wanted to post the "solution".

 

The iptables created by Unraid's built in wire guard interfere with accessing the webui from another vlan. In my case, I was trying to access the webui from a different vlan. I had no issues when the tunnel was down, but if the tunnel was up (even if no containers were using the interface) it wouldn't work.

 

So the guide should really note that this limitation; you can't access webui from a different vlan if the wire guard tunnel is up, regardless of how you have your vlan configured.

Edited October 8, 20241 yr by Relic664

Hmmm, thank you for this info. Ive been struggling with this myself for two weeks. I will check if moving my computer to the same vlan as the server will help for me aswell.

Edited October 8, 20241 yr by _omk_

Yes, can confirm. Moving over to the other vlan now makes the webui work. Thank you so much for that info! I was going crazy!!!

This was also driving me crazy, and I now know what the issue is thanks to this post. Is there any way solve this with IP routing tables or something? I really want to use the feature, but am accessing using a laptop on a different VLAN/subnet. Given that this isn't a problem outside of using the built in VPN Manager for Docker routing, there must  be a way?

On 1/21/2025 at 4:45 AM, Charlie_Croker said:

This was also driving me crazy, and I now know what the issue is thanks to this post. Is there any way solve this with IP routing tables or something? I really want to use the feature, but am accessing using a laptop on a different VLAN/subnet. Given that this isn't a problem outside of using the built in VPN Manager for Docker routing, there must  be a way?

I managed to access from a different VLAN by creating a NAT policy on my pfsense router.
I created a virtual ip 10.25.30.250 in the subnet of the server.
All traffic from my computer (10.25.0.4) going to my my server IP+port is translated to look like it is coming from 10.25.30.250.

On 1/7/2026 at 10:51 AM, Sak said:

I managed to access from a different VLAN by creating a NAT policy on my pfsense router.
I created a virtual ip 10.25.30.250 in the subnet of the server.
All traffic from my computer (10.25.0.4) going to my my server IP+port is translated to look like it is coming from 10.25.30.250.

Thanks very much - I'll have a look at my Unifi console to see how I can achieve the same.

On 3/16/2026 at 10:43 AM, Charlie_Croker said:

Thanks very much - I'll have a look at my Unifi console to see how I can achieve the same.

Did you ever figure out how to achieve this with the Unifi? I am facing the same issue with the UDM Pro.

6 hours ago, Rudedawg17 said:

Did you ever figure out how to achieve this with the Unifi? I am facing the same issue with the UDM Pro.

Just use wireguard on your Unifi router.

For others that don't have the luxury of a wireguard enabled router, this is the setting you need to look at in Unraid VPN manager (toggle basic to advanced mode).
These are the list of networks you are allowing to be accessible from your wireguard tunnel.
In my example I have 2x networks I wish to access, the last is the wireguard network itself which should be there already (may be a slightly different subnet).