Upgrade 2.3.2 to 2.3.2p1 still showing 'New version available?'

  • Yesterday I upgraded from 2.3.2 to 2.3.2p1 by clicking on the 'New version available' in the portal.
    It started downloading and installing but after a while (90 seconds?) it returned to the homepage, again showing that a new version is available.

    At first I thought the upgrade went wrong but then I looked at the console (I run pfSense in a VM) and noticed that the real upgrade was still in progress. I waited patiently and after 5-10 minuted the system had upgraded just fine.
    Somehow when the upgrade takes a long time the website returns to the home page too soon and tells that an upgrade is required while in reality an upgrade is in progress.

    Although simply waiting results in a proper upgrade this will cause many support questions and frustration and maybe even problems because people will restart their pfSense while the upgrade is in progress, just because they think the upgrade failed.

  • 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.


    Edit: Sorry, I just noticed this forum post after I had posted the above.      ----->  https://forum.pfsense.org/index.php?topic=119290.0

Log in to reply