@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.

@stephenw10 said in packagesite.txz: Authentication error: It's in the system infomation widget on the dashboard or above the menu at the console. Or shown by running gnid at the CLI. ok. i have sent it to you with forum chat.

Ok so here is what happened. After I removed the https protocol the repository updated. However, when I tried to install the package, pfsense automatically updated the pfsense.config file. So this issue is still there.

jimp, I used the USB Image Writer that came stock with my Linux distro. I created another boot usb drive on an old 2.0 usb drive and the pfSense install had not trouble completing. On to configuring!!! Thanks for your help!

This is what fixed it for me. https://redmine.pfsense.org/issues/14137

@chrisnz like @SteveITS indicated a clean install of the Feb 15th snapshot then upgrading to 23.01 will fix the PHP issue. Original comment here: PHP Issue Also read here: Here

@rcoleman-netgate Thank you. The certificate seemed very strange but the problem is now solved.

@mikedpitt Would be nice if you left the thread with more information like which version actually worked for you.

@steveits said in Netgate SG-3100 failed firmware upgrade.: They usually send the firmware link pretty quickly. I can personally confirm this. I haven't used Netgate customer support very much, but at least for me, they've set the "CS" bar pretty high.