Router NOT seeing any of the LXC container IP addresses for port forwarding

cmrho

New Member
Nov 4, 2024
24
5
3
Hi all. I'm sure this is a simple fix and silly mistake I'm making. I'm trying to forward some ports to an LXC container in PVE (sftp server). I have no issues doing this with docker jails nested inside my truenas server, but my router (google nest) is not seeing any of my LXC container IPs. Now that most of you have unrolled your eyes at reading that the router is a google router (I know, I know...), I don't think that is the problem. In truenas, I don't have a bridge set up. I assign the NIC to the jail, assign a static IP to the jail, and the router can forward ports with no issues to that jail. I think the issue with the pve setup is that it uses a bridge by default.

My firewalls are turned off for all the LXC containers.

Does anyone have any tips on how I could resolve this? Perhaps I could set up a reverse proxy with my nginx, but not sure that would work with port 80 going to 2022.