The console was not locked before upgrading? You are seeing errors when booting? If it was running ZFS you can roll back the ZFE BE snapshot. If it's UFS you could try a manual filesystem check: https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html#manual-filesystem-check Otherwise a clean re-install to 24.03 is probably the quickest way back: https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html Steve

The debug shows the connection is just timing out. Can you: ping ews.netgate.com ?

@stephenw10 thanks, I’ll try!

No worries. Good result!

@tordini thanks, I switched over to the non-devel package also and it's working fine. The only minor issue I have now is the percentage of domains blocked counter on the dashboard is pegged at 100% which is wrong. I had this issue a long time ago, I ignored it back then and I'll do the same now.

You can't run that dd command from the loader prompt. You would need to boot the installer and choose the shell from the initial menu there. Then clean the eMMC and exit back to the installer to continue. Steve

@chicknbread Same problem. Solved by Steven's suggestion. Thank you.

Yup use that if you need to do it off-line. But is that the case? You can't define a WAN to use with the on-line installer?

I just wanted to add my thanks too – I was trying to install the same latest Realtek drivers to support a generic dual port 2.5G NIC (uses 8125 chipset) but got stuck with the version mismatch error preventing the driver to load. I should have just come to this Forum first! Phil

Ah, yup hopefully that will help.

Hmm, nope that should work fine. If it fails like that it will drop to the command line with the network still configured. Try to ping the servers: ping ews.netgate.com Or connect dircetly: curl https://ews.netgate.com If those don't show the issue try using the legacy installers: https://atxfiles.netgate.com/mirror/downloads/

Nice

@johnpoz Hello and thanks for your message, Thank you very much for your message and the time you took to answer. Finally, I decided to remove the ClearOS box and connected PFSense directly to the modem/routeur and it worked. Thanks again for your time :) Best Regards

@stephenw10 said in Dashboard unable to report current version.: In 2.7.0 run: certctl rehash Then recheck. Thanks! That fixed the issue.

It's already fixed though, just waiting for the next release.

@stephenw10 I know that recommendation. I did the upgrade from the serial console and it also failed.

The beta7 installer? There is a newer installer available if so. But you can also just try the legacy installer images.

Good day, @stephenw10 Thought I would put the period on this post. I used the "pfSense-CE-memstick-2.7.2-RELEASE-amd64.img.gz". I was able to connect via the serial cable during POST, catch the BIOS and enable USB booting. From there, everything has gone very smoothly. I'm very happy with the hardware and software. I have several Noctua fans, 16 GB of DDR4 ECC RAM and a i7-7700T CPU heading my way after reading this epic forum ballad. This seems like a really great forum and I am grateful that such a altruistic resource is available, and well moderated, for professionals and home-labbers alike. Thank you all!

@jc1976 You saw all the other recent (last 24 hours) 'pfBlockerng' and 'pfblockerng-devel' forum posts ?

@stephenw10 Many thanks for the post. Reinstall and restore worked a treat. Life saver