pfblockerNG generating PHP errors



  • Hi,
    pfblockerNG is generating errors. As far as I can tell blocking is working fine, but every time I open the webgui I get this error:

    Crash report begins. Anonymous machine information:

    amd64
    11.2-RELEASE
    FreeBSD 11.2-RELEASE #36 79c8a561b61(RELENG_2_4_4): Tue Jul 10 06:14:32 EDT 2018 root@buildbot3:/builder/ce-master/tmp/obj/builder/ce-master/tmp/FreeBSD-src/sys/pfSense

    Crash report details:

    PHP Errors:
    [10-Jul-2018 17:00:01 Europe/Amsterdam] PHP Warning: Illegal string offset 'vip' in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 910
    [10-Jul-2018 17:00:36 Europe/Amsterdam] PHP Warning: Illegal string offset 'vip' in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 910
    [10-Jul-2018 17:00:40 Europe/Amsterdam] PHP Warning: Illegal string offset 'vip' in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 910
    [10-Jul-2018 17:03:03 Europe/Amsterdam] PHP Warning: Illegal string offset 'vip' in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 910

    No FreeBSD crash data found.

    I am using pfsense version: the Latest Base System 2.4.3_1
    I am using pfblockerNG version 2.1.2_4

    Any help is appreciated! Thanks!


  • Moderator

    What did you configure for the DNSBL VIP address? It should be a literal IP address. Are there any odd characters in that field?

    The new pfBlockerNG-devel has some validation on field inputs.


  • Moderator

    In pfSense 2.4.4, it moves to PHP v7 which changed how arrays are defined. Unfortunately, you will need to drop down a lower pfSense version until the package is reworked to address the new changes in PHP7.



  • Hi BBcan177. Thanks for your quick reply! Yes I figured out it has something to do with the php version. Last night I went back to the latest stable pfsense with the latest stable pfblockerNG. I restored my backup and everything is well :). I guess I'll wait for the final versions before I upgrade again.

    Thanks!



  • I'm a little confused. Has the PHP errors been resolved?



  • @dayve Not at the moment, you have to go back to 2.4.3 to get a working solution.



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



  • @lohphat said in pfblockerNG generating PHP errors:

    it's going to be weeks/months

    That's probably the case.



  • This post is deleted!


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



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


  • Moderator

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



  • no errors for me at all in latest version.



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

  • Moderator

    @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!



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


  • Moderator

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