September 28, 2025Sep 28 So I have been struggling for a while now with being able to put a container behind another container vpn. Everything I see online seems simple as hell but when I try in my setup it just doesn't work.So I have container A that is a vpn container. Its connected and working properly. I can access its WEBUI and I can pull an ip in console to confirm that is not using my IP.I then installed container B and I tried two things: First was adding an extra parameter of --net=container:container A, then going into container A and adding the port under a line there that said VPN_INPUT_PORTS. I mean the container seems to be up and running but I can't access it. I can pull console and see that is going through the vpn IP but I can't access the container via the ip and port in any shape or form. The other way was to not add the extra parameter and instead just do the drop down menu network, pick the container as the network device and then add the port in there like the previous step. Doesn't work either.I have tried this with several containers I want to have behind a vpn and none of them have worked so far. Been beating my head against a well for days now. Going all over reddit, here and even using ai to see if they were better at googling than me.Is this a thing that is just broken right now in Unraid 7.1.4 or am I doing something stupid or missing something simple?
September 29, 2025Sep 29 You must not publish any ports in B. All ports must be exposed in A. And most importantly: you must configure the service in B to listen on 0.0.0.0, otherwise it is only accessible locally (and not from the Unraid host).Mini Militia App Lock Edited November 2, 2025Nov 2 by avensis
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.