@bob-dig said in Proposed to upgrade to beta 23.05.b.xxxx, but not following the beta branch:

Maybe some sort of check for free space can be implemented in the future.

There is a an open bug for that internally but that's likely to be solved be adding features such as: https://redmine.pfsense.org/issues/13740

You should see the release as current stable now.

@gwaitsi There is not a public download for Plus. See thread https://forum.netgate.com/topic/180273/clean-install-of-pfsense-23-05-plus-non-netgate-hardware

@adam-lantos said in 23.05-RELEASE:

Was the 23.05 release published and then pulled back?

Don`t be afraid it is the same image according to the explaining from @stephenw10 and so there is nothing
different.

All of this (and more) is covered in recent docs updates:

https://docs.netgate.com/pfsense/en/latest/hardware/memory.html

@jimp I have added the change again there is still an issue with adding the key into the gui I have added @LamaZ code into the Fork and submitted a pull request so there is some visibility on the missing key issue for NTP Auth

@bcdouglas said in 23.05.r.20230511.0600 Another instance of pfSense-upgrade is running:

I'm on 23.05.r.20230519.0600. Attempted upgrade to 23.05.r.20230521.0305 (still) gives me the "another instance..." error.

If you wait a day or in real 24 hours the lease of the cert is renewed and you can try it out again.

@johnpoz I already had that option ticked (don't know why though) but I had not added the firewall reject rule as per the documentation.

However, after adding the reject rule none of the gateways come up. The reason is most likely because I have gateway monitoring enabled, and dpinger does not get a response to the pings as the gateway is not up (get caught by the reject rule), so we end up locked... catch-22.

I was hoping to use gateway monitoring to detect failure on one gateway in the gateway group to trigger a switch to a tier 2 gateway. But perhaps that is never going to work?

@jimp I did a reboot and I can't reproduce it now. I was changing the default gateway from a gateway group to a VPN interface.

@jimp Thanks for the reply.

This is on a 2100, so no BIOS that I'm aware of. I'll delete the file as you suggest before the next RC or final release.

@stephenw10 but as it is only happens after a reboot, and hopefully not caused by data corruption, it is a minor issue,because we never need to reboot pfSense!

Mmm, not seeing any issues here. Can you post what you've configured?

That change was only in the master branch for 23.09, but I've picked it back for 23.05 now since we have to do another round of builds.

@joedan said in RSS feed is broken:

must be of type ?int

If "20230513" (buid from last saterday ?) wasn't working, it would/should work with the 3 edited lines shown above by Jimp.

@bcdouglas I was finally able to get beyond 23.01. I started from the 2.7 Dev current build. Made a backup of my config.xml. Reinstalled the Feb 15th build but did not install any packages.

Opened a ticket to get my certificate bumped so that I could get a new build. However, I was stuck in the same position as you. I could not update anything, nor could I install any packages from the GUI even though I wasn’t planning to anyway.

To get moving ahead, I was able to install the System_Patches package from the CLI. Then I was able to apply all recommended patches from the Systems_Patches GUI. I rebooted and then was able to see and update to 23.05. Once up on 23.05 I restored my original 2.7 config.xml, rebooted again. My old packages were all reinstalled without a hitch.

I have a Cyberpower UPS and I did need to replace the usbhid module with the one I was using for 2.7. (Search the NUT package discussion in the forum if you need this)