@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
...and to @comet424

I wasn't able to perform the 2.8.0 update this weekend, but when I got to the school this morning, it worked perfectly!

I appreciate the support from both of you, and from Netgate.

The backup/standby pfSense instance is back in place and ready in case I have a hardware failure, or a failure of the gray matter between my ears!

My best to all of you.

@Wolfgangthegreat For example (this is checked by default):
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...

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.

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