Post B8NhASa1k7lyaHwKpM by mrjunge@raru.re
 (DIR) More posts by mrjunge@raru.re
 (DIR) Post #B8NhASa1k7lyaHwKpM by mrjunge@raru.re
       0 likes, 0 repeats
       
       Spending a whole day trying to get my containerized VPN client connection to the VPN server working such that I can access client container reverse proxy via the VPN server interface address, only to find out all I had to do was set `AllowedIPs` to `0.0.0.0/0` in the client configuration.
       
 (DIR) Post #B8NhjjrLUU6SJJrXxA by mrjunge@raru.re
       0 likes, 0 repeats
       
       Tomorrow I will find out if setting iptables rules *inside* the client container for ports not published to host is any different from either setting those rules on the host or setting those rules on the VPN server host, or what combination of those will be necessary. (I'm n00b).
       
 (DIR) Post #B8Niqi9yJ9j71LSndw by mrjunge@raru.re
       0 likes, 0 repeats
       
       Honestly this whole set up will make it so that if I ever can't afford cloud hosting, I can simply redeploy a different container Compose file on the homeserver that doesn't presuppose a remote VPN server. So I would still have some, albeit more limited, access to my servers while having more control over my data. Also makes VPS migration easier if most of the essentials are actually on the local network to begin with.