@WB3FFV I would like to know that too

@SteveITS I went back and retraced my steps, ONLY to realized that I had actually been attempting to restore an OPNsense config and NOT a pfSense config into pfSense 2.8.0... Today I had been running the same exercise (prep for switching from Cable to Fiber) in both... Hence False Alarm: pfSense 2.8.0 was "Correct", in fact it was NOT a pfSense config!!! Restoring Today's Initial Chrome config into pfSense 2.8.0 works as expected... Lawrence Houston

@w0w said in Upgrading from 25.07 to 25.07.1 causes a fatal trap 12 on boot.: I just forgot that I have Filer package Ha, I've done that.

@m80s said in Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare: @stephenw10 in my case I tried with 25.07.1: DuckDNS DeSec both with IPv4 and both failing. Yeah that's unexpected. Unless they are using a WAN with a gateway that shows as down. In which case you would be hitting the new behaviour requiring gateway monitoring be corrected.

Your root filesystem is down to 1.5G with only 345MB available. It is a space issue. Go to System> Boot Environments and remove any older snapshots you're no longer using. I usually recommend removing all but the currently running BE and one previous one. Then retry upgrading.

@dennypage Last night I upgraded the 2100 via the console with pfBlockerNG and Avahi packages left in place, and after 20 minutes or so it came back up and avahi appears to be working properly.

@stephenw10 Hi Stephen. That's why I posted -- the 25.07.1 update has been out for well over 24 hours and yet there was no upgrade available LED flashing. I upgraded last night so we'll see if it picks up when the next upgrade is available.

Ah, good and bad news then I guess. Thanks for following up. Yes, some SSDs will fail to a read-only state such that they appear to take changes but lose it at reboot. And that can be confusing!

Yup use Python mode if you have kea2unbound and DNS-BL.

@hspindel said in Upgrading 24.11 to 25.07 fails: @keyser Thank you. So do you concur that removing packages is a good idea? And I have to reinstall manually? Yes and yes

@luckman212 said in Auto update check, checks for updates to base system + packages and sends email alerts: That's why e.g. the current script isn't detecting 25.07.1 etc. Check that you've selected : [image: 1755701317878-103cf890-ded4-4473-8a21-21333f615049-image.png]

If it's the first time it's changed I can probably migrate it to the new NDI. Send it to me in chat and I'll check it.

That ^, It's actually taking up far more space. That error: pkg: "out of space" returned error code 3 confirms it out of disk space. I would remove all but the current and one previous BE and run the upgrade again.