@andy58 I agree! there should be a disk space check command issued before update starts.

Yes, probably. Check the RAM usage. Check available disk space.

@dgall There is a new (beta) Installer: https://docs.netgate.com/pfsense/en/latest/solutions/xg-7100/reinstall-pfsense.html

@pixel24 said in No Update 2.8.0 available: @Gertjan I've never worked with the Pathes package before. I've always installed updates exclusively through the web UI. That is for program updates. Netgate releases fixes in between version updates. They are normally included in the next version. They often backport security fixes.

@stephenw10 Hello, The device has only two nics but when I installed pfsense plus they were detected right away properly as active and was able to choose WAN and LAN and it was good a detecting internet on the WAN interface. In any case it is working now. Thanks

@SteveITS @jimp Ok thanks, I applied all the patches and performed the normal system reboot. Everything seems to be working fine.

Sophos XGS 87 is not supporting pfSense. Bless

@stephenw10 The inclusion of the pfSense-repoc package in the command below + the temporary removal of Snort and pfblockerNG did the trick. pkg-static clean -ay ; pkg-static install -fy pkg pfSense-repo pfSense-repoc pfSense-upgrade Happily running on version 24.03 now. Cheers!

@SamJWard Hmm... they don't have monitoring system in place to notify their server admins that the systems are down? Would be nice if they have a network status page on the netgate support site in cases like this so we don't waste time trying to figure out if there is something wrong with our pfsense / netgate appliances like I dealt with today. This would also prevent un-necessary tickets. Yes I am a bit frustrated to spend couple of hours troubleshooting only to find out it wasn't my instance. Although I am used to it in the IT world. Least now I know after finding a couple of posts about this that I can stop troubleshooting and wait till in the morning to try again.

Hmm, yes that should not need to be registered and should always return as eligible. Send me the NDI and serial in chat and I can check it. Or open a TAC ticket: https://www.netgate.com/tac-support-request

More info needed. If you're running ZFS you can roll back the BE, yes. But that also means it upgraded and verified the boot or it would have rolled back automatically. So if the upgrade was successful that implies some other failure in the new version. It failed to pull an IP address?

OK so it's trying to use something in pkg that doesn't exist in 2.4.5. So, again, what update branches do you see offered in the GUI? 2.4.5 to 23.01 is too large a jump. You will probably need to upgrade first to something closer to 2.4.5.

Send me your NDI and/or Order number in chat and I'll check it. Steve

@stephenw10 I will try to uninstall and then install it via "pkg upgrade" again.

This: https://redmine.pfsense.org/issues/15396

@SteveITS I don't think I uninstalled plus. I believe at some point I must have reinstalled the image in order to get ZFS and then I restored from whatever config backup I had. ...maybe I explicitly uninstalled Wireguard at some point. This is a home setup, so I don't keep notes on it like one might for a business install :) Rich

@SteveITS said in 24.03 pulled?: @hspindel not as of last night. Which branch do you have selected? I'm on the RELEASE branch. Mysteriously, 24.03 just now reappeared as an upgrade.

@stephenw10 Well, to fix the issue, I was lucky I made a backup before attempting to update. I ended up downloading the new 2.7.2 CE ISO with my MacBook Pro through my iPhone hotspot, checked the checksum, and burned the ISO to disk. I wiped the SSD on my computer that pfSense was installed on. I then installed a fresh/clean pfSense 2.7.2 CE. I restored the backup. I updated pfSense to 24.03. All is good now. Wheeeew!

@stephenw10 Thank you Steve. That worked.

That's what you see on the video console when the serial console is set as primary. Everything after mounting root until the console menu comes up is shown on the primary console only. Except for a few things like new device detection and link state changes, hence you see the aesni0 device. It was probably waiting for some input on the serial console but would have eventually rolled back the BE snap after not verifying the boot. Steve