@scurrier it went pretty well. Only things that threw me off were: The serial console was somehow cutting off some of the text at the login screen before rebooting, even though I had already configured my terminal correctly in the last, leading me to think my settings were wrong. They weren't, it was some pfsense console problem fixed by rebooting. The password prompt for the encrypted config has a timeout but doesn't say so, so when I went to my password manager to get the password, it timed out and I had to reboot and try again.

I'm getting the same error. I'm running on VMware ESXI 8.0U1. I have tried 3 times to upgrade to pfSense Plus from CE 2.6.0 brand new install and it fails each time. Why is it that we don't have a direct upgrade to pfSense Plus? Clearly the upgrade path doesn't work from CE 2.6.0. On another note, I tried upgrading from CE 2.7.0 and the same result as well. And lastly, I have noticed I get a SCSI error if there is a VMware snapshot on the machine during a boot of CE 2.6.0. If I remove the VMware snapshot and then reboot, no error. (This is separate from the certs.inc fatal error though and doesn't seem to affect it.) Can anyone figure out what's causing this problem? Even NetGate's own hardware is failing with this error. [image: 1684004610272-img_9122-resized.jpg]

Yes, it will be once 23.05 is released.

https://docs.netgate.com/pfsense/en/latest/recipes/virtualize-esxi.html

@catspecial202 said in GUI unresponsive and NG2100 stuck updating square slowly flashing orange 2+ hrs: None of the edits to my original post can be seen to the community? Correct.

@rcoleman-netgate Submitted it again and got an email acknowledgement with an issue number. Thank you!

I just wanted to pop in and say that I was also running into a "Bad Request" issue just now on 23.01 when trying to run pkg update and I was able to resolve this by plopping in my Register key via the UI. I was going through some troubleshooting last week with pfSense support and during the re-issuing of Plus certs it must have wiped the Registration key somewhere along the way. I was upgrading from 2.7.x CE to 23.01 Plus.

@matrix-31 The correct snapshot is Feb 15th. Anything after/more recent than Feb 15th caused issues. You should be good.

@vmhomelab said in Unable to check for updates | Restored backup: but it is still the ce edition installed What release specifically?

@the_nino As another update of things tried. Looking thru old google posts, I've brought the system down to 1 8gb dimm. No change. I also saw older posts that referenced it was an issue with something to do with efi video settings. Some people reported installing a video card solved the issue. I put in a known good 1030 I have, but unfortunately, same issue. I also found a BIOS option that had the video memory at 64mb. I increased it to 512MB, no change. Not sure on that option, the sizes implies to me that only applies to onboard, but its changed anyway. No help, same issue. I also took the USB 2.0 drive I am trying to boot PfSense with, and used it on my other desktop. My desktop was able to boot right to it, and the installer for PfSense loaded right up. I took one of my USB 3.0 drives, and imaged it with FreeBSD. I then put that into the HP machine I am having issues with, and it was able to boot right into FreeBSD and I was able to get to shell, or the installer. The only thing I noticed was the option 5 was showing video, whereas in my screen shot on this post, PfSense never seems to default to video. But even changing to video has the same issue, so perhaps thats nothing.

@jimbob-indiana said in save the branch?: My question is about the lingo You are saving an update setting. Which tells your pfsense install what branch of the code you want to be on, so what updates it should monitor and offer to you.

Hi Jimp, Thank you for your suggestion Im going to try the upgrade to 20.x and then to 23.0 from there. I received the installer from TAC as well as my plan B. Again, thank you!

No ZFS for the ARMv7, sorry you have to stay on UFS.

@gpz1100 said in Pfsense+, tokens vs nic changes, broken registration: Is the NDI tied to the physical nic mac or virtual (spoofed)? To get the wan operational its mac has to be spoofed. The MAC as it is presented to the core OS. Internal spoofing in pfSense is not taken into account.

@rcoleman-netgate said in CE to Plus - Unable to check for updates: @bingo600 said in CE to Plus - Unable to check for updates: @stephenw10 Since my first install crashed w. a bad hdd , could i have exhausted the Netgate Cert Server ?? - I just failed once Open a ticket with your NDI and we'll bounce that cert for you (if that is the issue). I have just been able to upgrade now. So my money is on exhausting the SSL Cert server. Why is there such a low limit on the cert server ?? Worth noting the problems you have with your QOTOM matches my own experiences in 2016 with them. I scrapped them all as soon as I could manage it. Well to be fair i think the Qotom is "innocent" , it has been running flawlessly since 2017. But I have had ntopng permanently active, and my guess is that it has worn out the SSD disk. I should not have used a "consumer" ssd with that amount of logging. I have stopped running ntopng permanently active. And have changed to a server grade SSD. Thank you for the answer Ryan, and offer to contact TAC. But this experience worries me a bit, wrt. switching my work boxes to Plus. At least until i can buy a "whitebox" subscription, and get access to the Plus image via TAC. My next prod boxes will likely be Netgate, but bean counters ...... /Bingo

I was reinstalling 2.6 (ZFS) on the APU6B4 and then I was upgrading to 23.01 and all went fine for me, after installing all needed patches and packets I am now better sorted then ever before! But the APU4D4 I was deciding to give TNSR 23.02 a chance. With pfSense 2.7 DEVEL installed on it, I was never getting hot in touch, problems over problems only after the first upgrade of the entire system!

I updated without any problem to 23.01 it took around 8 minutes and everything worked well.