Version: 6.11.3

 

I use Wireguard with remote tunneled acces. I can connect to my unraid Server but the Docker Apps wont load the Web UI. This affects all Docker Containers set to bridge mode or br0. In LAN I am able to open the GUI with all of them.

 

I put a static route in my router, but I am not sure if that was done right. I guess not. Maybe anyone here could help me out? 1ß.168.178.25 is the IP of the unRAID Server

 

 

 

If you need more informations about network config please let me know and I can provide them for you.

The setup seems fine, are you able to access the server's webgui? If so, at what url(s)?

 

If you can access the webgui then you should be able to access docker containers on bridge without doing anything special. What url(s) are you using?

 

If you are trying something like http://tower.local:1234 , that won't work because tower.local does not resolve over VPN. You'll want to use an IP address.

If that doesn't help, be sure to go through the first two posts here: https://forums.unraid.net/topic/84226-wireguard-quickstart/

 

And finally, 6.11.3 is pretty old. I'd recommend upgrading to 6.12.4

I always used the IP Adress to access the Web Ui of the the server itself. That is the 10.168.178.25. From there I can access the containers as usual. I can also open the Web Ui of Containers with network interface "Host" and"bridge" Sorry for the confusion just tested it again. I can not access Web UI of dockers with interface none which are routet through a docker running a VPN itself and dockers running on onterface br0.  The docker running the VPN Sevice has got a bridge interface, too.

I try to access them via 10.168.178.25:Port_of_Service or http://10.168.178.25:Port_of_Service. Opening them within LAN does not make any problems.

 

Edited September 22, 20232 yr by pille

I can't think of any reason why http://10.168.178.25 would work for the webgui but http://10.168.178.25:Port_of_Service would not work for a container.

 

My best suggestions are in my previous comment.

Hmm ok. Strange then.

I just saw that the connection to 10.168.178.25 is via https but this should not matter.

Will try to upgrade and see again.

why do you use static routing with nat enabled?

1 hour ago, pille said:

 I can not access Web UI of dockers with interface none which are routet through a docker running a VPN itself and dockers running on onterface br0. 

 

Of course you cant.

For br0 access, you would need to enable host access, then you would need to modify your wireguard config.

Secondly. You cant access your vpn routed container, because and i assume here something like binhexvpn or so, youre from a wrong subnet and need grant access to that subnet within iptables of that container.

Plus, i think you need to modify the wireguard config for that aswell, especially with nat. although, dont nail me onto it. i havent tried to access vpn routed container interfaces from within the vpn tunnel yet.

Edited September 22, 20232 yr by Mainfrezzer

25 minutes ago, Mainfrezzer said:

Secondly. You cant access your vpn routed container, because and i assume here something like binhexvpn or so, youre from a wrong subnet and need grant access to that subnet within iptables of that container.

Plus, i think you need to modify the wireguard config for that aswell, especially with nat. although, dont nail me onto it. i havent tried to access vpn routed container interfaces from within the vpn tunnel yet.

 That is kind of what I thought. Strange that it worked flawlessly till yesterday when we played around with the DuckDNS thing and deleting /adding Ports and static routes.

 

here the iptables from the nordvpn docker

 

Edited September 22, 20232 yr by pille

working again. Had to change the 10.168.178.0/23 to 10.0.0.0/8

 

Still not able to access br0 , but shoul dbe possible, right?

Edited September 22, 20232 yr by pille