25.07.1-RELEASE Package Manager Updates Failing
-
I see a bunch of up dates e.g. System Patches 2.2.23 -> 2.2.24
They keep disappearing and coming back. When I click on them, i get
WARNING: Current pkg repository has a new PHP major version. pfSense should be upgraded before installing any new package.i am occassionally getting below as well
check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-11-07 13:15:21 -
THis is waht I see - and you see the same thing now.
.... 0) Logout / Disconnect SSH 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart GUI 3) Reset admin account and password 12) PHP shell + Netgate pfSense Plus tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option: 13 Messages: Your Netgate device has pfSense+ as part of your device purchase. >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching data.pkg: . done Processing entries: . done pfSense-core repository update completed. 5 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching data.pkg: ...... done Processing entries: .......... done pfSense repository update completed. 734 packages processed. All repositories are up to date. Your packages are up to date Netgate 4100 - Serial: 2014321418 - Netgate Device ID: e57dfdcabcdef5a2527a *** Welcome to Netgate pfSense Plus 25.07.1-RELEASE (amd64) on pfSense *** ....System Patches 2.24 ??
Do you have details ? -
@Gertjan if I try to update any of them, i get the error above.
I saw when i clicked on the link that the version is 2.24 but then it fails and rolls back.
will try the console way.
-
@Gertjan p.s. it said successfully updated from the console, but in the UI still shows the same error when trying to update the packages
-
You are on the Current Stable Version 25.07.1, right ?
I can't see where your 2.24 comes from ....
-
@Gertjan that is what is says in the title. 25.07.01.
the patches was a typo. current patches are 2.2.23
if you click on the upgrade, you can see it shows the next version will be 2.2.24
but then rolls back because of the PHP error, but if you look at the packages in the screenshot
php should already be 8.4.13 -
@4o4rh I have the same problem.
-
Also here, this error appeared for the second time today (this is with CE image)
Standard input code: New alert found: check_upgrade: "Updating repositories metadata" returned error code 1 -
To @all
This is what I should see :
But ... when I visited this page initially, the "Latest Base System " proposed some beta named as a possible update, and the green Update button was there.
Or, I'm at the stable branche, not the 'dev' branch.So : my 'conclusion' : something is happening.
So, for this weekend : leave things as they are
-
Feels like beta-repos got mixed into the stable release in the backend system...
-
Something like that.
Not uncommon btw. Could mean nothing at all, as it could mean we wake up tomorrow morning with a new pfSense version, probably a RC1 candidate. -
chime in - seeing the same thing - set for stable, but its like it wants to update to the 25.11 beta..
Something is goofy - tried toggling and saving.. Just seems stuck on wanting to update to a beta.
-
Are you still seeing it?
-
Had to switch branch to beta and back to stable, seems back to normal for now
-
Backstory on this actor.. Stephen Stucker he was added to the cast of Airplane and allowed to just do whatever he wanted. Movie was much better with his whit!
-
@stephenw10 yeah did a bit of resaving that I was on stable - and seems to be back to normal now.
-
@stephenw10 spoke too soon I guess - its back
Had to go in and hit save again on update settings. To get it back showing stable 25.07.1
edit: Then check a little bit latter and its back to the beta again.. Yeah something is borked.
-
Yup, seeing the same.
Though on my system dashboard said that beta update available, but the update page said no updates and Latest Base System was stable version. After a while with hopping between dashboard and update page, it started to show the beta as Latest Base System again. -
Yup, a change was still in place. It's now been reverted until we confirm the root cause.
You should no longer see that.
