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

    pfSense 2.4.3 / pfBlockerNG 2.1.2_2 -> _5 update kills pfSense

    Scheduled Pinned Locked Moved pfBlockerNG
    9 Posts 5 Posters 2.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.
    • J
      jacotec
      last edited by jacotec

      Hi,

      I'm running pfBlockerNG 2.1.2_2 (PHP 5.6 version) for a couple of weeks now on pfSense 2.4.3. Yesterday I've switched over to the Develop branch to see if there are any updates, saw the 2.1.2_5 update and hit the update button. Big mistake as it seems :-(

      That update tried to delete all PHP 5.6 resources on pfSense 2.4.3 which are essential ... so as a result I was offline for half an hour while restoring my complete firewall VM from the last night's backup.

      I'm absolutely not sure if it's intentional in some way to perform this catastrophic action on a 2.4.3 install and I warn anyone who is still on the 2.4.3 stable branch but running pfBlockerNG 2.1.2_2 (PHP 5.6 version) package to perform the update! It appears it wants to change the main PHP version of the whole pfSense installation without any kind of warning or confirmation, leading to a serious crash!

      Not sure why it did not recognize that it was the PHP5.6 version which I did install with 2.1.2_2 :-(

      1 Reply Last reply Reply Quote 0
      • M
        mhab12
        last edited by

        I am experiencing a similar issue after update to 2.1.4_8.

        The box seems to be working, passing outbound traffic etc, but the inbound rules I have configured based on GeoIP must not be loading properly. I can access the WebGUI from the LAN and everything else appears to be working. I've tried running an 'update' task from the pfBlockerNG/update page but this did not fix things. Any other 'best practices' after a package update short of rebooting the whole box?

        J 1 Reply Last reply Reply Quote 0
        • J
          jdeloach @mhab12
          last edited by

          @mhab12 said in pfSense 2.4.3 / pfBlockerNG 2.1.2_2 -> _5 update kills pfSense:

          I am experiencing a similar issue after update to 2.1.4_8.

          The box seems to be working, passing outbound traffic etc, but the inbound rules I have configured based on GeoIP must not be loading properly. I can access the WebGUI from the LAN and everything else appears to be working. I've tried running an 'update' task from the pfBlockerNG/update page but this did not fix things. Any other 'best practices' after a package update short of rebooting the whole box?

          I updated to pfB 2.1.4_8 yesterday but have not noticed any issues. Not sure what the new update was suppose to fix. Tried to search for what it is was suppose to fix but couldn't find it.

          I think there are some known issues with the new development version of pfB and pfSense 2.4.3 that have to do with PHP. If you search the messages there are some patches that you can apply that are suppose to allow you to run the development version on pfSense 2.4.3. I think pfSense 2.4.4 uses PHP 7.X and I think the new development version of pfB has trouble determining which version of pfSense you are running. It's just one of the issues one runs into with using the beta versions of software.

          1 Reply Last reply Reply Quote 0
          • M
            mhab12
            last edited by

            @jdeloach said in pfSense 2.4.3 / pfBlockerNG 2.1.2_2 -> _5 update kills pfSense:

            wn issues with the new development version of pfB and pfSense 2.4.3 that have to do with PHP. If you search the messages there are some patches that you can apply that are suppose to allow you to run the development version on pfSense 2.4.3. I think pfSense 2.4.4 uses PHP 7.X and I think the new development version of pfB has trouble determin

            Is there an easy way to roll back the pfBlockerNG package to the prior version? Would restoring a prior backup install the package version that was installed when that backup was taken?

            J 1 Reply Last reply Reply Quote 0
            • J
              jacotec @mhab12
              last edited by

              @mhab12 I think once the PHP5.6 stuff is uninstalled the pfSense installation itself is not quite OK. Had several issues and found it most safe to roll back my last backup.

              1 Reply Last reply Reply Quote 0
              • M
                mhab12
                last edited by

                A reboot seemed to fix any issues I was having and inbound rules are working as desired again.

                1 Reply Last reply Reply Quote 0
                • A
                  anttechs
                  last edited by

                  OMG my Pfsense has crashed to now and it was after I installed Pfblocker again, not blaming Pfblocker.
                  It said something about missing files and I tried everything but I shall just have to reinstall Pfsense.
                  Nevermind I think it was something to do with the pfblocker_devel version I install.

                  Intel(R) Celeron(R) CPU J1900 @ 1.99GHz
                  Current: 1992 MHz, Max: 1993 MHz
                  4 CPUs: 1 package(s) x 4 core(s)
                  AES-NI CPU Crypto: No
                  8 Gig RAM
                  250GB SSD

                  https://ant-techs.is/ip-blocklists

                  1 Reply Last reply Reply Quote 0
                  • rbgargaR
                    rbgarga Developer Netgate Administrator
                    last edited by

                    The problem here is you chose development branch, which points to 2.4.4 pkg repository, but you didn't upgrade the whole system to 2.4.4.

                    So you ended up with a 2.4.3 system configured to consume 2.4.4 packages. 2.4.4 moved to PHP 7.2 and all packages on its repo uses it. When you chose to upgrade pfBlockerNG it messed up the system.

                    Renato Botelho

                    1 Reply Last reply Reply Quote 2
                    • A
                      anttechs
                      last edited by

                      I am so looking forward to the new version.
                      the dev version is excellent :)

                      Intel(R) Celeron(R) CPU J1900 @ 1.99GHz
                      Current: 1992 MHz, Max: 1993 MHz
                      4 CPUs: 1 package(s) x 4 core(s)
                      AES-NI CPU Crypto: No
                      8 Gig RAM
                      250GB SSD

                      https://ant-techs.is/ip-blocklists

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