Crash report on 24.03
-
Crash report begins. Anonymous machine information:
amd64
15.0-CURRENT
FreeBSD 15.0-CURRENT #0 plus-RELENG_24_03-n256311-e71f834dd81: Tue Apr 16 00:38:18 UTC 2024 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-24_03-main/obj/amd64/dyNDzqbt/var/jenkins/workspace/pfSense-Plus-snapshots-24_03-main/sources/FreeBSCrash report details:
PHP Errors:
[22-Apr-2024 03:52:44 PHP Fatal error: Uncaught ValueError: range(): Argument #3 ($step) must be greater than 0 for increasing ranges in /usr/local/www/pfblockerng/pfblockerng_category_edit.php:391
Stack trace:
#0 /usr/local/www/pfblockerng/pfblockerng_category_edit.php(391): range(1, 17, -1)
#1 {main}
thrown in /usr/local/www/pfblockerng/pfblockerng_category_edit.php on line 391 -
@Antibiotic And what to do now? Its happened, when trying to add feeds
-
@Antibiotic said in Crash report on 24.03:
/usr/local/www/pfblockerng/pfblockerng_category_edit.php
Solution for me
And this line: 391 and 1517
$list = array('Disabled' => 'Disabled') + array_combine(range(1, 17, -1), range(1, 17, -1));
Changing both instances to:$list = array('Disabled' => 'Disabled') + array_combine(range(1, 17, 1), range(1, 17, 1));
Fixed the issue and allows editing, etc, -
-
@anthonys Yea, resolved this problem. But now dns filtering not working at all
-
@Antibiotic said in Crash report on 24.03:
But now dns filtering not working at all
Can you clarify "not working"?
FWIW, my lab (in which I had experimented making the same change as you) is blocking as I would expect in browsers, and reporting blocks in the dashboard widget:
and also seeing the blocked DNs reported in the Firewall->PFblockerNG->Reports->Alerts
-
@anthonys In my case DNSBL category did not block nothing. Log was dead and no any records of blocking. Anyway for now stop using 24.03 and downgrade to stable realease
-
@Antibiotic I don't know. After editing lines 391 and 1517, it has been working as normal for me since I first tried the Beta release, as well as for the 2 Release candidates to date.