Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Stuck on 2.4.2-release-p1 (amd64) since Dec 2017

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    6 Posts 2 Posters 936 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      koferong
      last edited by

      Hi Forum- I've not been able to get my Netgate-SG-2440 to update from 2.4.2-p1 for almost a year. The auto-update check on dashboard always returns "The system is on a later version than official release." I've posted on pfsense forum to enquire about this problem but nobody seems to have any clue.

      Is the only solution to reinstall the latest image file? I'm hesitant to do this for fear it might break something else.

      Could the auto-date failure be related to the PHP error that I also get persistently on the dashboard: "PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/ssh2.so' - Shared object "libssh2.so.1" not found, required by "ssh2.so" in Unknown on line 0"?

      Thanks in advance for your help!

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by stephenw10

        You probably have the wrong pkg repo selected or did at one time.

        Make sure you have the 'Latest stable 2.4.X' branch selected in System > Update then go to Diagnostics > Command prompt and execute:
        pkg-static clean -ya; pkg-static install -yf pkg pfSense-repo pfSense-upgrade

        However I too would recommend backing up the config and installing 2.4.3p1 clean. That is the safest way.

        Steve

        1 Reply Last reply Reply Quote 0
        • K
          koferong
          last edited by

          Hi Steve

          I ran the script you suggested, but it didn't make any difference. I'll try reinstalling when I get a chance.

          Just curious if this meant anything...on the System Update page, I get this every time, even if I'm on the latest stable version:

          Current Base System 2.4.2_1
          Latest Base System Warning:
          Status Running a newer version.

          Thanks!

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            It seems like it's seeing something older that 2.4.2_1 when it checks. Which I can only imagine is 2.3.5_2 at this point though that doesn't make much sense if it is on the 2.4.X branch.
            I would still recommend re-installing and restoring the config. If you use the PFI or ECL methods that can be very quick and easy: https://www.netgate.com/docs/pfsense/backup/automatically-restore-during-install.html

            Steve

            1 Reply Last reply Reply Quote 0
            • K
              koferong
              last edited by

              At last...it only took me a few hours to get back to normal☹ ...the latest 2.4.3p1 update is now running.

              Had to go through a full install via console, but the PFI or ECL method didn't work since the USB device couldn't be mounted after the image file was written to it, and hence no way to add the config.xml file. The following link also helped me out tremendously...at least up until the boot and install pfsense part (the remaining part didn't seem to apply to me):
              link text

              One more thing...packages need to be reinstalled after pfsense is restored.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                For refernce you need to use a FAT32 formatted USB stick for PFI or ECL. Since the installer image is UFS that generally means using a separate USB stick to hold the config.

                Packages should be re-installed automatically when you restore the config. If you didn't have a valid WAN interface at that point that process would fail. The package config is retained though.

                Steve

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.