Recently done four of them. Two upgrades from 2.7.2 and two net installed. All went ok & reinstalled packages after.

I agree an iso would be useful but I’ve managed without.

Next one will be an ESXI vm, so will try both methods on that.

Hmm 300 IPSec VPNs is a lot. What sort of IPSec config are are you using?

What is shown as using the CPU cycles when that is loading up one core?

What size is the config file? Do you have ACB enabled?

@stephenw10 i have same issue

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

( 😊 )

Try installing it at the CLI with debug to get more error output:
pkg -d install pfSense-pkg-squid

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

may be I go the issue we just nee dot reboot the firewall and select the old kernel and boot the firewall after boot it will reboot again and you can access the latest version of firewall which 2.8.0 I tried and it work for me.

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

@fireodo said in php error with suricata after updating to 2.8:

@bmeeks said in php error with suricata after updating to 2.8:

Part of the install/update process for the package rebuilds the enabled rules.

Maybe to much rules too?

A possibility for sure, but the rules rebuild was apparently working under the previous pfSense version if I am understanding the OP correctly.

He also has pfBlockerNG installed and it will use a lot of PHP memory for some tasks.