23.01 -> 23.05 Upgrade GUI not updated - upgrade corrupted
-
@steveits but 2.7 is development. can we then switch to 23.05?
-
@gwaitsi I don't think so right away but eventually, yes. One can't upgrade directly from 2.6 to 23.01 because the OS and PHP both changed major versions. So their upgrade path was to the closest Plus version to 2.6, then upgrade Plus versions to current.
You had asked to "revert back to community 2.6 version or at least 2.7 dev version."
-
@gwaitsi This is not an issue with pfsense. Yes, the GUI update does not seem to be working. However, updating from console worked fine for me. Your situation seems to be user error and is not a reason to abandon great software. The pkg upgrade command was the big mistake. You upgraded your packages before updating pfsense. That's a no no and pfsense docs will tell you that as well. Unforuntately, you will have to reinstall and recover from a backup.
Next time you're in this situation, refer to the pfsense docs. That's where I found the correct command to perform the update to 23.05. The command "pfsense-upgrade" would have got you updated to 23.05 no problem. -
@raffi_ i have re-installed both CE 6 and 7 to no avail. they will only shows packages within their own branch. trying to go to any other branch i.e. CE 6 to plus or 7 brings unable to check for updates
pkg-static upgrade gives me "could not load client certificate /etc/ssl/pfsense-repo-custom.cert
-
@gwaitsi so i can switch between 6.0 and 7.0 dev but, it seems because I don't need to register as my device from plus is recognized, something is missing.
i already copied over the files from another 23.01 box
pfSense-repo-custom.cert
pfSense-repo-custom.keybut I get the errors
repository pfsense-core has a wrong packagesite need to recreate database
pkg-static meta.txz bad request
pkg-static packagesite.pkg bad request
pkg-static packagesite.txz bad request
unable to update repository pfsense-core
unabe to compare version of pfsense-reposo much for 1hr restoring
now i also discover, even if i wanted to restore the auto backup, 2.6 is saying it can't decrypt it. i hope that is because it was created with 23.01.
-
It is clear that my proposal is somewhat late, but why not just use boot environments next time? Especially when the system boots up, there shouldn't be any problem rolling back to any previous version, well almost.
-
@raffi_ said in 23.01 -> 23.05 Upgrade GUI not updated - upgrade corrupted:
the GUI update does not seem to be working.
Not true, just did two earlier; however, one had a hiccup but sort itself out.
-
@gwaitsi I had the same as your first screen shot, then, I re-registered, still got the same, rebooted, tried again and all was good, upgraded easy-peasy.
-
@nollipfsense what do you mean re-registered. It doesn't allow me to enter anything in the box, when the bar at the top says my device is already recognized
-
@stephenw10 this could be my token right? I copied the files from my other 23.01 system
pfSense-repo-custom.cert
pfSense-repo-custom.keybut not able to access the upgrades.
How do i fix this please?
-
@gwaitsi Re-registered means going to Netgate and register again (free), check email for new key, copy key and paste in registration box on pfSense. Then, I tried upgrading, got upgrade failure, rebooted, tried again and all was good.
-
@gwaitsi said in 23.01 -> 23.05 Upgrade GUI not updated - upgrade corrupted:
I copied the files from my other 23.01 system
That won't work...just re-register...it's free.
