cardboard_boks

Understood and thank you for your reply. Turns out an underlying network conflict, which was the root cause of a much larger issue I just faced, also stopped me from being able to refer to the server's IP. Just happens targeting the docker IP and going through the VPN masked that issue for these dockers. Looks like a jumped the gun on what this problem really was and somehow found a workaround that I now know is not the correct way. Everything is now pointed back at server IP's and working happy happy again. This has been a week of many learnings, thanks again

I have just moved over to using Gluetun for my VPN needs, all set up and working fine. The issue I can't seem to find a solution for (limited linux knowledge on my end) how to have it have a predictable Container IP on reboot. Dockers running through Gluetun need to communicate using Gluetuns Container IP, hence why having it always the same is required. Currently I have it as the first docker to start, so far it has always got the same IP, so it isn't not working, but this is a very flaky solution. I think setting Gluetuns Network type to custom and setting a fixed IP is the correct path, but just doing this causes all the Container Port(s) to not populate, and then no comms to any docker running through Gluetun, and I assume no network for them either. So I am missing something.... In router terms, I would reserve the IP address and it would always be giving it, but I lack the knowledge to translate that concept into Unraid/Docker technology.