Deploying Proxmox 7 behind a firewall VM

In order to make egress traffic, you’ll want to copy the default “Allow all” rule from the PROXMOX rules to the VMS_HETZNER rules. You can do so by clicking on the Copy icon which is in between the Edit and Disable icons. When you have the option to edit your duplicated rule, change the Interface option from PROXMOX to VMS_HETZNER and the Source from PROXMOX net to VMS_HETZNER net, and then click on the Save button.

To discover your Virtual Machine’s IP address with CIDR, run the following command in a terminal:

ip -f inet addr show | awk '/inet / {print $2}' | tail -n1

In my case, my Virtual Machine’s DHCP-assigned IP address is 172.16.0.200.

On this same Virtual Machine, you can use Python 3’s simple HTTP Server module to serve the contents of the desktop on port 8000 by opening a terminal and running the following command:

python3 -m http.server --directory ~/Desktop/ 8000

You can confirm that it’s working by opening a web browser inside of the Virtual Machine and going to http://localhost:8000 and should see a screen similar to this screenshot.

Remember earlier where we created NAT rules to access Proxmox from the Internet? The same principle applies here. Now that we have a web server running in a Virtual Machine on port 8000, we need to expose the port to the Internet. We’ll set the target IP to the one that we discovered above, 172.16.0.200.

Aside from a simple demonstration and for a real-world deployment, you would assign a Static DHCP IP Address to the Virtual Machine in the firewall DHCP Server page for the interface or set the Virtual Machine’s IP address manually.

Now I can access the simple server remotely by visiting http://65.109.71.115:8000