Messages

Some things come to mind:

1. Why are the interface names different? By using vtnet interfaces, you could have the same names as before, regardless of which hardware PVE uses.
2. IDK how things are set up when you start the setup wizard with a WAN interface with a fixed IP - maybe, there is no outbound NAT, which would prevent the LAN side from working correctly.
3. Do you know this article?

Thanks so much. I got it working. I'm not exactly sure what I messed up previously. I might have had the gateway setup wrong. That is a mystery though, since DNS was working on the firewall.

I'm humbled by you doc. So many things I didn't (don't) know. That was very helpful.

This is for a homelab setup. Previously I had OPNsense on dedicated hardware, which is why interface names are different. We're moving house, so I'm redoing all our networking. Now I can start adding vlans etc. Thanks again.

I'm trying to get a new install as a VM under proxmox working. Previous installs have worked for years. After 2 days, this one is driving me crazy.

The WAN interface has static IPs, and is configured as such. On the firewall, DNS is working. I can ping google.com.

From my laptop DNS is not working. If I ping google's IP directly, that does not work either. I can see the ICMP packets coming in the LAN and WAN interfaces with tcpdump.

I don't see any problems when I watch the live firewall logs.

I've done a fresh install several times now, setting up the interfaces in different orders. I used the Wizard for setup. Other times I tried a manual setup.

Any ideas how to get this to work?

My setup is about as simple as possible. Defaults out of the box.

I have not tried restoring my running system to the new one, as the hardware is different with different interface names. My working system is 25.7.

Thanks

After upgrading to 25.7.10, acme-client no longer works. I get an error in /var/log/system/latest.log saying:


AcmeClient: No SFTP upload automation found with uuid = '24d2a47a-65ae-4e1a-863a-dc15f7bb0e94'

I tried reinstalling os-acme-client. No change.

The uuid is is coming from the /config/config.xml:

<certificates>
  <certificate uuid="2ee381f0-082c-4034-b2e7-9e110d8e990c">
    <restartActions>24d2a47a-65ae-4e1a-863a-dc15f7bb0e94</restartActions>

I tried deleting that line in hopes it would re-create it, but it didn't.

Acme is updating the certificate, its just not running the automation.

Any idea how to resolve this?

Thanks, Andy