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

    Version 2.3.3_1 is available

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    55 Posts 30 Posters 29.0k 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 Offline
      Kamen
      last edited by

      Initiated the update (from 2.3.3) via WebGUI and it gave me the failure message BUT it also stopped working (Internet, etc.) I reset the box and no service after that, either. I could not wait hours, so I reverted to my backup router. There is no monitor/keyboard on the pfSense computer, so I'll see when I can get to it.
      Just FYI, but very disappointing.
      Kamen

      1 Reply Last reply Reply Quote 0
      • Z Offline
        zizwiz
        last edited by

        My GUI upgrade hung.  System still running 2.3.2, GUI showing "unable to check for updates.

        ssh update doesn't work:

        pkg -v
        1.9.4

        pfSense-upgrade -d
        pkg: No package(s) matching pfSense-kernel-*

        Updating repositories metadata…
        Updating pfSense-core repository catalogue...
        pfSense-core repository is up-to-date.
        Updating pfSense repository catalogue...
        pfSense repository is up-to-date.
        All repositories are up-to-date.
        ERROR: Unable to compare version of pfSense-repo

        1 Reply Last reply Reply Quote 0
        • jimpJ Offline
          jimp Rebel Alliance Developer Netgate
          last edited by

          @zizwiz:

          My GUI upgrade hung.  System still running 2.3.2, GUI showing "unable to check for updates.

          ssh update doesn't work:

          pkg -v
          1.9.4

          pfSense-upgrade -d
          pkg: No package(s) matching pfSense-kernel-*

          Updating repositories metadata…
          Updating pfSense-core repository catalogue...
          pfSense-core repository is up-to-date.
          Updating pfSense repository catalogue...
          pfSense repository is up-to-date.
          All repositories are up-to-date.
          ERROR: Unable to compare version of pfSense-repo

          That looks like you have some major problem with your local pkg data. Please start a new thread, it is not related to this update.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 0
          • S Offline
            Supay
            last edited by

            @jimp:

            @zizwiz:

            My GUI upgrade hung.  System still running 2.3.2, GUI showing "unable to check for updates.

            ssh update doesn't work:

            pkg -v
            1.9.4

            pfSense-upgrade -d
            pkg: No package(s) matching pfSense-kernel-*

            Updating repositories metadata…
            Updating pfSense-core repository catalogue...
            pfSense-core repository is up-to-date.
            Updating pfSense repository catalogue...
            pfSense repository is up-to-date.
            All repositories are up-to-date.
            ERROR: Unable to compare version of pfSense-repo

            That looks like you have some major problem with your local pkg data. Please start a new thread, it is not related to this update.

            I'm not so sure.

            I upgraded to 2.3.3 1 and saw masses of stuff break across my install.  My package manager was the main problem, it could no longer connect to check for any updates and it claimed I had no installed packages and was unable to reinstall anything.  I tried both from the GUI and command line, both continued to fail.  I havecompletely  scrubbed and reinstalled my box three times now and I keep getting the same issue.  2.3.3 works fine.  Upgrading to 2.3.3 1 leaves it in a horribly broken state where it still routes and all the basic functions are fine, but the package manager appears to broken and unable to do anything.  I'm going to have to scrub this again and refuse to upgrade to 2.3.3 1 as if it can't even manage to cleanly upgrade from a fresh install then there is something wrong in there.

            1 Reply Last reply Reply Quote 0
            • S Offline
              Supay
              last edited by

              @Kamen:

              Initiated the update (from 2.3.3) via WebGUI and it gave me the failure message BUT it also stopped working (Internet, etc.) I reset the box and no service after that, either. I could not wait hours, so I reverted to my backup router. There is no monitor/keyboard on the pfSense computer, so I'll see when I can get to it.
              Just FYI, but very disappointing.
              Kamen

              I had the same issue with my first upgrade.  I lost both the package manager and saw breakage all over the place with loss of internet access which seemed DNS related as I could still directly ping IPs, but I couldn't find any reason for this in the logs.  I tried a factory default reset but that actually made it worse a I lost even being able to reach the external internet even though again I could see no rules causing this and nothing in the logs.  Three complete scrubs of the box and a fresh install leaves with me all routing functions working, but upgrading to 2.3.3 1 breaks the package manager everytime.

              1 Reply Last reply Reply Quote 0
              • U Offline
                Uxorious
                last edited by

                Same partial upgrade problem here.
                Fixed by: pfSense-upgrade -d

                (And as others have mentioned, the new update system is pretty flaky. This is the 2nd time I've had to manually fix it after updating)

                1 Reply Last reply Reply Quote 0
                • S Offline
                  Supay
                  last edited by

                  @Uxorious:

                  Same partial upgrade problem here.
                  Fixed by: pfSense-upgrade -d

                  (And as others have mentioned, the new update system is pretty flaky. This is the 2nd time I've had to manually fix it after updating)

                  The new update system really is flaky.  Since 2.3 I have never had so many issues with pfsense.  Nearly every update completely breaks my system.  I've already tried manually updating using pfSense-upgrade -d over ssh but it just hangs on updating the repositories and eventually states that it is unable to update them.  This issue only affects 2.3.3 p1, so I'm going to have to revert back to 2.3.3 and refuse all upgrades until this is fixed.  Or consider trying something other than pfsense as this level of breakage is concerning.

                  1 Reply Last reply Reply Quote 0
                  • J Offline
                    JorgeOliveira
                    last edited by

                    Two things that pfSense needs to provide is:

                    1. An offline update system or way to mirror the updated packages to own network before the actual upgrade procedure.
                    2. Rebuild ISOs with the patch-level fixes.

                    Yet… I have no reasons for complaint as I have never faced any problems during upgrade. I usually don't update on the first day after updates got available, I normally wait a few days.

                    Also I have systems where I run 2.3.x development branch and breakage has only occurred in extreme situations. Running the pfSense virtualized and having snapshots to revert back to is a blessing.

                    My views have absolutely no warranty express or implied. Always do your own research.

                    1 Reply Last reply Reply Quote 0
                    • H Offline
                      happyqban
                      last edited by

                      Updated from the GUI ok, the only issue being that after the first automatic reboot the VPN was still down, I had to manually restart the server pfSense to get it back up and running

                      I've got the brain of a four year old. I'll bet he was glad to be rid of it. - Groucho Marx

                      1 Reply Last reply Reply Quote 0
                      • B Offline
                        bheinsius
                        last edited by

                        Coming back to DNS forwarder not resolving local (fully-qualified) hostnames after upgrade from 2.3.2_1 to 2.3.3_1, it turns out this was caused by:

                        I had the same issue, not even long domain names worked in the DNS forwarder.
                        Turns out it is due to a setting in the General Setup "DNS Server override"

                        "If this option is set, pfSense will use DNS servers assigned by a DHCP/PPP server on WAN for its own purposes (including the DNS Forwarder/DNS Resolver). However, they will not be assigned to DHCP clients."

                        That was checked on my setup and as such none of my local - full domain forward overrides - worked anymore.
                        This was never a problem before pfSense 2.3.3_1.

                        Perhaps it makes sense, but at least unchecking that and manually setting the DNS server setting above that instead of getting it from DHCP immediately fixed the issue I was having.
                        After that I could query for any of the internal DNS entries again.

                        Thanks to @wila (https://forum.pfsense.org/index.php?action=profile;u=320599)

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