Indeed the memory can be an issue especially with larger upgrades. The memory usage during ZFS upgrades has been improved in 25.07 (to be released soon) to address the issue. You can check the system log for signs of processes being killed abruptly. If however you're still using UFS it's more likely to have been some other issue.

I decided to check out the repo to see what build looks like for CE. I noticed that 2.8.0-RELEASE is still not an available branch in the repo. The master branch version is currently 2.9.0-DEVELOPMENT. Is netgate going to post the 2.8.0-RELEASE branch for the main package and FreeBSD-src?

Upgrading from the local console is always the safest way. That is using the root user. More importantly you will see all the output from upgrade including after the reboot. So if there's some issue with hardware in the new OS version you will see it and be able debug.

@chpalmer said in Strange behavior with gateway: ??? When the default gateway is set to a failover group the 'Default' column in the gateways list should show the tiers. But in this screenshot it doesn't: https://forum.netgate.com/post/1221365 That's unexpected.

@stephenw10 Unfortunately I am going to have to wait till I can bring down the network to test. If I take it down now and it doesn't come back up I will be having some hell to pay from the family...lol.

@Wolfgangthegreat For example (this is checked by default): [image: 1753113612568-8544523b-d69b-4088-b221-d2532912455c-image.png]

There was a backend issue that's now fixed.

Yup, there was a backend issue. Should be good now.

The repo seems to be back online today Jul 19th, I was able to complete the fresh install.

Hmm, but they are policy based tunnels? And 300 Phase 1 configs not a total of 300 Phase 2 configs for example? I'm not aware of any issue in 2.8 that might present like that for IPSec.

and then it worked...

@PiAxel said in update from 25.07 beta to 25.07 RC: The last version doesn't work for me! ?? How do you know that the latest version doesn't work for you, before installing that latest version ? ( )

@jc1976 can you check if you hit the same issue as: Squid: "Undefined symbol "_ZTVNSt3__117bad_function_callE" after upgrade to 2.8?

@NetworkNerd Just in case you haven't tried this yet. The new Netgate online installer does provide you the option to set up the WAN interface connection details such as PPPoE etc as part of the process. I'm not a fan of the choice to remove offline installers by any means but at least they do provide this functionality.

@stephenw10 I a not using squid guard so I have to enable and check, I enabled the squid proxy server and squid guard proxy filter they both are running fine without any errors. Thanks for the help and quick response

For future reference you should always be able to upgrade to the newest offered version in one step. We test upgrades from the previous two versions.

@stephenw10 said in Kernel Panic when Upgrading to 2.8.0 beta: Hmm, interesting if it's really disabled in the BIOS pfSense shouldn't see it at all. Something not working right there. Reply Correct. Under the list of devices in the BIOS on the NUC, WiFi is not checked.

...well, after some false starts (like loading 2.7.2 and running into different interface names on the new hardware (i,e. igc0 vs igb0, etc..) which did not allow th eloading of my VLANS etc... I ended up editing the backup config file, replacing "igb" for "igc", and loading 2.8.0... all is working great now on the new hardware.... I will wait until I can upgrade from 2.8.0 to Plus... reason to go to Plus is to contribute $ to the project, as I have been using pfSense for free for years now... am recently retired and delving into IT and learning as I go... Thanks for all the replies and suggestions !

@lansmurf said in Upgrade from 2.7.2 to 2.80 failed, unable to boot: You are right it is an image file of the installer... Ah, OK, thanks!

We were able to finally figure out all of the URLs that the pfSense box was sending requests too and we now have a working squid proxy. Thank you.