Opened a bug to track it: https://redmine.pfsense.org/issues/14921

@stephenw10 Thanks for your comment , your are correct regarding the image i used the serial image , i was think about last night and down loaded the VGA image , this worked a treat this morning. I was going to mark this as solved . Thanks, Mike

That would solve the problem, yes. It's probably easier than the multiple upgrade steps that would be required to upgrade from 2.3.3 anyway. However one thing to be aware of here is that 2.3.3 supported 32bit hardware and 2.7 does not. So check that whatever you're running on is 64bit capable. Steve

'Bad Request' like that means it's sending an invalid client cert. If you have not recently opened the gui run pfSense-repoc before running those pkg commands. Steve

Sent in chat

@stephenw10 Thank you!

Yes, just download the config from Diag > Backup/Restore then restore it into 2.7.

Solved: I had a static DNS entry for ews.netgate.com to 127.0.0.1 added in the past to speedup dashboard loading time in case of internet down Removed it, now I've started the upgrade

Try running at the command line: pkg -d update Check any errors. If there are errors try: pkg -d4 update If completes quickly without errors it implies you have an IPv6 connectivity issue. You can set pfSense to prefer v4 In Sys > Adv > Networking if necessary. Steve

@stephenw10 Many thanks, this resolved my issue and now the installer can see the nvd0 drive. I had a feeling it was something to do with the partitions but I wasnt sure. The limited BIOS really threw me for a loop.

Hmm, interesting. That shouldn't be required and I'd be hesitant to recommend it until I fully understood exactly what that did or why it was needed.

Probably this: https://redmine.pfsense.org/issues/14569 Or rather this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269133

@SpitefulMonkey More info is needed. If I would set this : [image: 1696410938075-55399d61-8fec-49f8-a73f-1a47afb78493-image.png] then my 23.05.1 would be more recent that what is set "23.01" and I would see probably that (your) message. So, in that case : easy solution. Check also the other "Update settings" menu.

@DaddyGo sorry - I ended up doing the config backup, clean install, config restore. 5 mins thing a few days ago when I could finally get to the site. Would have preferred a remote fix, but sometimes you need physical fingers and thumbs :)

@stephenw10 Thanks! That did the trick! John

Just happened on this thread, because I too am a total newbie to PfSense and am currently going through the learning process while setting it up with the help of the docs, and nguvu's very helpful "pfSense baseline guide with VPN, Guest and VLAN support"... I have to say that everyone here is so extraordinarily helpful. Have a nice day everyone! A chappie

@stephenw10 Yes, You are right. Only few items were left in the partition. root@:~ # mount /dev/ada0p2 /mnt root@:~ # ls .k5login .profile .shrc recover_configxml.sh root@:~ # cd /mnt root@:/mnt # ls .cshrc .profile .rnd .snap .sujournal dev lib libexec sbin usr var root@:/mnt #

I would recommend at least uninstalling Squid before the upgrade. There have been issues with the install/uninstallscript in that package across a php version.

i managed to get updated to 2.7 in the end. I reverted to a 2.4.4 snapshot and then changed the update branch.

@Tom8 said in Unable to check for updates: is possibly a misconfiguration from my ISP I agree @Tom8