@yuryk

If you don't specify 'something', this :

ce374e1e-7370-4192-8b06-32173c657b86-image.png

will ask for an A record.

This :
d6e1a4fd-66eb-4922-a669-9ae4fb866379-image.png

doesn't use 'A' (or AAAA) records 😊

Check the "pfSense Packages" forum : the top most post : DNS Broken for pkg.pfsense.org

@mohkhalifa said in Packages are not available:

I don't have the option of "Automatically create a boot enviroment prior to performing system update"

That option would be present if you have installed pfSense 'from scratch - from firmware file - from USB' and you have chosen 'ZFS' as a file system.
That is, if that option exists for your hardware.

ZFS is nice to have, as you can create a 'snap' from your current pfSense, and try out a new upgrade/update, and go back if needed.

@jimp Thanks, that seemed to get rid the error. However since I am moved on from OpenVPN to WG, this was bit of a forcing function for me.

It varies based on hardware, config complexity, and numerous other factors. There is no way to know beforehand how long it will take, so it just retries periodically. There is already a feature request in to get rid of the confusing countdown timer:
https://redmine.pfsense.org/issues/14008

Thanks both!

Close to midnight here, but thanks for the super-rapid responses ...tomorrow morning I'll give it a go!

Chris

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

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