I'd swap the storage card out for a fresh one.

I have encountered a similar issue. I recently upgraded two pfSense appliances, both from v2.2.3 to v2.3.2_1. Both upgrades proceeded as usual and expected, without issue and completed. Now in the Dashboard, one system is showing "The system is on the latest version." and the other system is showing "Version 2.3.2_1 is available." On the system that is suggesting the 2.3.2_1 upgrade is available, if I go to "System" –> "Update", the system reports the following "Current Base System      2.3.2_1   Latest Base System      2.3.2_1 Status      Up to date." The upgrade was done last week, however I have just noticed this today, which does not imply anything other than I have just noticed it today. The system with the pfSense version anomoly in the Dashboard, is running the 32bit version of pfSense on an old HP DL360 G3 server. The system which presents the version correctly in the Dashboard, is running the 64bit version of pfSense on a Dell Optiplex 990 SFF. Cheers Edit: Sorry, I just noticed this forum post after I had posted the above.      ----->  https://forum.pfsense.org/index.php?topic=119290.0

Good news OlliC! I have not tried again to update. I have historically upchucked my PFSense build, started from scratch and recovered via a backup. This time though built a duplicate machine on standby.

Thanks for the update. The increase is not causing any issues for the system.

There's always going to be a few edge cases that fail an update, there is with every release. The reason it looks like a lot is they come here looking for help in fixing it. Also you don't hear anything out of the people who have successful updates. Squeaky wheel gets the grease kinda thing. I am one who updated without issue. If you're worried about it backup your config to a safe location and if it all goes bad reinstall and restore your config. Easy peasy.

Thanks for the pointer.  While I needed that option set, I also had to enable the checkbox for WebGUI redirect (System–>Advanced). BTW - A huge shout-out to the pfSense technical support team.  After struggling with this for a few hours, I opened a ticket and immediately had a couple of great engineers on the phone (maybe 2min wait at most).  Brandon and Chris helped figure out the problem in short order as well as clear up some questions about CARP, NAT, and NAT Reflection.  Thanks guys!

Well, one of my test systems now shows: Netgate APU Serial: 655dc6... While the APU part is correct, this device has never seen Netgate. Technically correct would be: PC Engines, APU

@securityconscious: Catch my fix here: https://forum.pfsense.org/index.php?topic=119290.0 This worked for me as well.  I had the same problem.

If I go to DIAGNOSTICS / ntopng Settings / Access ntopng, I can accept the certificate and enter ntopng. From DIAGNOSTICS / ntopng, I get a reset. the https: is missing in the DIANGOSTICS / ntopng item link. I am using port 3000.

Perhaps try this related solution which fixes a few things: https://forum.pfsense.org/index.php?topic=119290.0 Let me know if it solves your issue.

Updated 2.3.2 to 2.3.2_1 and got the same error. Solution is the same. But… what is wrong?

Update finished successfully: >>> Setting secondary partition as active... done. Upgrade is complete.  Rebooting in 10 seconds. >>> Locking package pfSense-kernel-pfSense_wrap... done. Success Thanks!

I'd try wiping the secondary and setting it up from scratch. You just have to get the basic settings done and sync it.

Seems like the pfsense package repositories are struggling with the load.  Have you considered putting Cloudflare in front of it?  It could cache all the packages for you and serve them from the global CDN.