@stephenw10 The upgrade failed with the following error: 'failed insufficient space remaining for /boot/loader.efi', which is exactly why I was looking at jimp's fix. Only problem was, the install did a umount on /boot/efi just before I got that error. When it did that, it did not revert the umount so I have been trying to figure out exactly where mine should be mounted. Most posts refer to /boot/efi being mounted to /dev/msdosfs/EFISYS, which I don't have. Based on everything I have found, it looks like it should be mounted to /dev/ada0p1. Unfortunately when I do that I also notice that BOOTx64.efi is missing from that directory. I did find where I can replace that file with loader.efi and rename it.

Before I proceed, I just want to make sure I have mounted the correct location to /boot/efi. When this problem first happened, I did run the df -hi /boot/efi and got the following reults:

Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/gptid/ac11fbb1-5651-11e8-b5a2-00907fd0950c 222G 18G 186G 9% 69k 30M 0% /

I have since temporarily performed a mount_msdosfs /dev/ada0p1 /boot/efi and when I run the same command I get

Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/ada0p1 766K 1.5K 765K 0% 2 510 0% /boot/efi

Which according to information I have been able to find online in other forum posts would be correct for some installation, even potentially mine.

@Wolfgangthegreat
Thank you for the info. I won't be able to attempt the upgrade to 2.8.0 until tomorrow.
I'll let you know status then.

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

Update: It appears to be functional as of last attempt at 15:35 CDT.

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