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

    pfblockerNG generating PHP errors

    Scheduled Pinned Locked Moved pfBlockerNG
    17 Posts 8 Posters 2.8k 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.
    • lohphatL
      lohphat @RonpfS
      last edited by

      @ronpfs ETA on fix? Will go back to release if it's going to be weeks/months.

      SG-3100 24.11-RELEASE (arm) | Avahi (2.2_6) | ntopng (5.6.0_1) | openvpn-client-export (1.9.5) | pfBlockerNG-devel (3.2.1_20) | System_Patches (2.2.20_5)

      RonpfSR 1 Reply Last reply Reply Quote 0
      • RonpfSR
        RonpfS @lohphat
        last edited by

        @lohphat said in pfblockerNG generating PHP errors:

        it's going to be weeks/months

        That's probably the case.

        2.4.5-RELEASE-p1 (amd64)
        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

        1 Reply Last reply Reply Quote 0
        • S
          strangegopher
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • R
            RandomVMTeam
            last edited by RandomVMTeam

            So it seems like I should not be using pfblockerng or prfblockerng-devel on the pfSense devel relases 2.4.4 and above.. I currently am on the latest snapshot to date and have been experiencing some issues with pfblockerNG-devel w/ pfsense-devel.

            BBcan177B 1 Reply Last reply Reply Quote 0
            • GrimsonG
              Grimson Banned
              last edited by

              2.4.4 is a development version and not a release candidate, it's not even beta yet. You should expect it to be broken, or break any minute. If your not using it to help the developers and hunt bugs you should stay on 2.4.3 for now.

              1 Reply Last reply Reply Quote 0
              • BBcan177B
                BBcan177 Moderator @RandomVMTeam
                last edited by

                @randomvmteam said in pfblockerNG generating PHP errors:

                So it seems like I should not be using pfblockerng or prfblockerng-devel on the pfSense devel relases 2.4.4 and above.. I currently am on the latest snapshot to date and have been experiencing some issues with pfblockerNG-devel w/ pfsense-devel.

                What errors are you receiving? Please also update to the latest 2.2.5_11 as there are some fixes in this version.

                "Experience is something you don't get until just after you need it."

                Website: http://pfBlockerNG.com
                Twitter: @BBcan177  #pfBlockerNG
                Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                R 1 Reply Last reply Reply Quote 1
                • S
                  strangegopher
                  last edited by

                  no errors for me at all in latest version.

                  1 Reply Last reply Reply Quote 0
                  • R
                    RandomVMTeam @BBcan177
                    last edited by RandomVMTeam

                    @bbcan177 The error im experiencing seem to be related to enabling GeoIP blocking.. I currently cannot.. Im on pfblockerNG-devel 2.2.5_11 and the latest pfsense devel snapshot. Besides enabling GeoIP categories everything is working great in pfsense and pfblockerNG.. Just seeing these crashlogs on the dashboard for quite a while.

                    Crash report details:

PHP Errors:
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'action' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'aliaslog' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'action' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'aliaslog' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'action' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'aliaslog' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'action' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'aliaslog' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'action' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'aliaslog' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'action' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'aliaslog' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'action' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'aliaslog' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'action' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'aliaslog' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'action' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
[30-Aug-2018 09:48:20 America/New_York] PHP Warning:  Illegal string offset 'aliaslog' in /usr/local/www/pfblockerng/pfblockerng_category.php on line 161
                    BBcan177B 1 Reply Last reply Reply Quote 0
                    • BBcan177B
                      BBcan177 Moderator @RandomVMTeam
                      last edited by

                      @randomvmteam said in pfblockerNG generating PHP errors:

                      The error im experiencing seem to be related to enabling GeoIP blocking.. I currently cannot.. Im on pfblockerNG-devel 2.2.5_11 and the latest pfsense devel snapshot. Besides enabling GeoIP categories everything is working great in pfsense and pfblockerNG.. Just seeing these crashlogs on the dashboard for quite a while.

                      Thanks for posting... I fixed the issue in this PR:
                      https://github.com/pfsense/FreeBSD-ports/pull/562/files

                      Once its merged, the package will be on version 2.2.5_12

                      Typically, you would configure the GeoIP pages from the Continent pages, and then use the overview page after that... I never considered that users would/could enable a Continent without first configuring it beforehand... :)

                      Without users help, its difficult to track down these kinds of errors, since it needs a specific set of events to trigger an error... So the more people who test devel the quicker it gets any bugs fixed.

                      Thanks!

                      "Experience is something you don't get until just after you need it."

                      Website: http://pfBlockerNG.com
                      Twitter: @BBcan177  #pfBlockerNG
                      Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                      R 1 Reply Last reply Reply Quote 1
                      • R
                        RandomVMTeam @BBcan177
                        last edited by

                        @bbcan177 would it be easier to submit issues I find directly to the github page? (assuming pfsense/pfsense-packages)

                        BBcan177B 1 Reply Last reply Reply Quote 0
                        • BBcan177B
                          BBcan177 Moderator @RandomVMTeam
                          last edited by

                          @randomvmteam said in pfblockerNG generating PHP errors:

                          would it be easier to submit issues I find directly to the github page? (assuming pfsense/pfsense-packages)

                          Forum would be better.

                          "Experience is something you don't get until just after you need it."

                          Website: http://pfBlockerNG.com
                          Twitter: @BBcan177  #pfBlockerNG
                          Reddit: https://www.reddit.com/r/pfBlockerNG/new/

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