Well, it finally happened; now you need to restore a Virtual Machine, Container, or worse yet, the hypervisor host.
It goes without saying, but the easiest way to recover is from a snapshot which you made before you made a change that broke your Virtual Machine or Container — you did take a snapshot, right? The easiest way is to increment or rollback snapshots via the GUI under the Snapshots option for each of them, but if you need to do it by the command line, then you can.
First, obtain a list of your Virtual Machines or Containers in order to obtain their ID:
To make a snapshot:
Virtual Machines allow you to save the state of RAM with a snapshot (
vmstate) on top of their storage and configuration, while as Containers can only snapshot their storage and configuration.
To list the snapshots:
To restore a snapshot:
Suppose that something went awry while I was on Christmas vacation, and I wanted to pave over the changes with the last working state and boot the Virtual Machine or Container after a successful snapshot rollback (
WARNING: when these steps are completed, this will expose your Proxmox host’s GUI and SSH to the Internet.
Please ensure that you’re using a difficult password for your Proxmox root account, which you can reset after launching it via the QEMU emulator.
Remember the initial installation process above? Reboot the server into Rescue mode so that you can load Proxmox via QEMU and login with
root and your password:
List the Virtual Machines and/or Containers to get their IDs and turn off auto-booting for each.
Using the ID of
100 as an example for a Virtual Machine or Container, and to disable it from booting, use:
Turn off the Proxmox firewall for the entire cluster if you enabled it:
sed -i \ 's/^enable: .*/enable: 0/' \ /etc/pve/firewall/cluster.fw \ ;
/etc/network/interfaces with the recovery configuration:
cp -va \ /etc/network/config-recovery \ /etc/network/interfaces \ ;
Now you can shut down Proxmox from within QEMU:
shutdown -h now
In the rescue shell, reboot the physical server, which should load into Proxmox:
10 replies on “Deploying Proxmox 7 behind a firewall VM”
Great post. Thank you so much – exactly what I was looking for!
But I’m missing a step-by-step guide to include Traefik 2 to your setup.
Or can’t I simply find it?
I try to split complex topics into their own articles. You can find my Traefik 2 guide at https://LTG.FYI/Traefik-2. Please let me know if you have further questions, and I’ll try to answer them here or perhaps write additional articles.
Great post. Thanks!
I’m just in the process to replicate your setup.
Nearly everything is working but I can’t get any DNS servers working on OPT2. The traffic is routed over the WireGuard-VPN, all fine.
But it seems that any UDP traffic is blocked and I can’t figure out where to unblock it. Any hints much appreciated! Thank you.
Off the top of my head, maybe I forgot to document the DNS Resolver section, but will have to go re-read my article and look for anything that I might have missed, but am in the middle of bee season (video of some of it: https://LTG.FYI/YouTube) and helping restore multiple ranches, so it may take me a moment.
I’ll e-mail you and try to figure it out with you. Once you and I figure this out, I’ll make appropriate edits to the article or one of us can write here in the comments about what needed to be changed.
EDIT: I e-mailed you and the e-mail bounced back as an invalid address. Please feel free to reach out again with a way for me to contact you, so that we can try and figure out what the problem is.
Thank you so much for your tutorial!!!
I can’t access the Ingress server from the VMS_Hetzner network, from external it’s working.
Like in your example: “Now I can access the simple server remotely by visiting http://126.96.36.199:8000”
I can access the website from my browser, but not from a browser running with any VM on the VMS_Hetzner network.
Any idea which Firewall rule is blocking the access from VMS_Hetzner to WAN_Hetzner?
Hi Loomer, you are most welcome! 🙂
I used the interface’s address for the VMs to access the firewall interface. Please see https://thad.getterman.org/articles/proxmox-7-behind-firewall-vm/5/#live_desktop for an example of a Virtual Machine accessing the firewall’s GUI via the VM interface address to configure it instead of the WAN address.
EDIT: I e-mailed you and the e-mail bounced back as an invalid address. Please feel free to reach out again with a way for me to contact you.
I am new to proxmox and your article just blew me away.
I just got the hetzner with 15hdd (no nvme) and I asked for KVM to install proxmox directly on the baremetal
But you do some sort of magic.
you boot into recovery and install proxmox in qemu?
I cannot say I follow
I am not sure I follow (and obviously I already broke my setup trying to change the network settings)
I’ll e-mail you so that we can schedule a time for me to have office hours with you; you screen share with me in observation mode so that I can tell you what to click on and help you get up and running.
I’ll make a YouTube video out of it and then add one or more relevant videos to this article.
Louis T. Getterman IV