@joeker I don't work here anymore.

@human705 yes

@Atom2 thanks that fixed it for me for my 2100 I was having that error also.

I would expect that to be difficult. I've never tried to do it.

Hmm, I no explanation as to why it would fail then succeed. I would expect it to either fail or succeed the same way every time. 23.01 is a special case. It was the first version to introduce dynamic package repos. As such everything on an earlier version has to update to 23.01 first and then to the current version. Steve

@stephenw10 You are a gentleman and a scholar. I was mentally preparing to reinstall pfsense today but this worked. Thank you

Yup, that's the same EFI console issue. I believe there is a thread for that over in the Virtualisation sub. I personally don't have anything with hyper-V to test in.

@KOM said in How to migrate from pfsense+ to CE: How to Convert From pfsense plus 23.05 to pfsense CE 2.7 Thanks.

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