pfSense thinks that 2.6 is the newest version after a reboot of system running 23.01

gonace

Hi
I'm in a bit of a strange situation where my pfsense installation, running 23.01, after a reboot thinks that the newest version is 2.6.0.

The dropdown under "Update Settings" says "Current Stable Release (2.6.0 Release)" and "Latest Beta Snapshos (2.7.0 Beta)"

And "Your device has not been registered for pfSense+. Please purchase a pfSense+ subscription to receive future updates." but before the reboot it was registered.

I've previously had "pfSense+ Software Subscription × 1
Home (Non-commercial use)"

When goin into System -> Register the following message is displayed
"Thank you for choosing Netgate pfSense Plus

Your device does not require registration, we recognize it already. You may have already registered, or it may be a pre-registered Netgate appliance.
Register Netgate pfSense Plus"

Any ideas on how this can be resolved?

Regards
Erik

gonace

This post is deleted!

gonace

Hi
It seems like the license has "disapeared" and re-entering it seems to get pfSense to understand what version is installed and what branch it should use.

The web-gui did not however work and said that it was unable to find any updates, even after the router was restarted, running a pfsense upgrade from the CLI worked fine.

And after the upgrade and reboot it seems like everything is back and working.

It seems like the activation state is not saved however, when registering it just says "Thank you for choosing Netgate pfSense Plus" but when going to the registration page again it seems like you can enter the same license over and over without it persiting.

The system is spewing out the following error in system.log

Sep 23 12:13:51 pfsense php-fpm[2715]: /pkg_mgr.php: The command '/usr/local/sbin/pfSense-repo-setup' returned exit code '1', the output was 'pfSense-repoc-static: invalid signature failed to read the repo data. failed to update the repository settings!!!'

Regards
Erik

stephenw10

Send me your NDI in chat and I'll check it.

The error from repoc and the fact it fell back to the default repos indicates it may have changed since it was registered. Did you add or remove hardware from the firewall?

Steve

gonace

@stephenw10 hi, no I've been using the same (HPE MicroServer Gen 10 Plus) since 2020, I could not find my old activation token so I ordered a new one from your store today. I've sent my NDI to you via a a chat :)