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

24.03-DEVELOPMENT - PHP Fatal error: Uncaught ValueError: range(): Argument #3

pfBlockerNG
8
29
3.3k
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.
  • S
    SwissSteph @pst
    last edited by SwissSteph Apr 24, 2024, 9:44 AM Apr 24, 2024, 9:28 AM

    @pst

    Thank you for your reply.

    I was right... BUT I have a big spit next if I want to edit

    login-to-view

    With or without the patch I get the same error

    [24-Apr-2024 11:22:58 Europe/Zurich] 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 {main}
    thrown in /usr/local/www/pfblockerng/pfblockerng_category_edit.php on line 391
    [24-Apr-2024 11:25:46 Europe/Zurich] 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 {main}
    thrown in /usr/local/www/pfblockerng/pfblockerng_category_edit.php on line 391
    [24-Apr-2024 11:28:32 Europe/Zurich] 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 {main}
    thrown in /usr/local/www/pfblockerng/pfblockerng_category_edit.php on line 391

    EDIT

    I finally followed the very clear information from "graphene" in this post

    https://forum.netgate.com/topic/187604/24-03-r-20240416-0005-unable-to-add-an-ipv4-entry-to-the-pfblockerng-configuration/6

    and manually edited the two lines by removing the "-" before the "1".

    It's all good, no more crashes when editing a line.

    I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
    ... And now I'm living with a Netgate 8200
    ... And sorry for my bad English...

    P 1 Reply Last reply Apr 24, 2024, 9:48 AM Reply Quote 1
    • B
      Bob.Dig LAYER 8 @pst
      last edited by Apr 24, 2024, 9:45 AM

      @pst said in 24.03-DEVELOPMENT - PHP Fatal error: Uncaught ValueError: range(): Argument #3:

      I have updated my post

      That looks perfect.

      1 Reply Last reply Reply Quote 0
      • P
        pst @SwissSteph
        last edited by pst Apr 24, 2024, 9:49 AM Apr 24, 2024, 9:48 AM

        @SwissSteph said in 24.03-DEVELOPMENT - PHP Fatal error: Uncaught ValueError: range(): Argument #3:

        With or without the patch I get the same error

        Did you press Apply after adding the patch in System Patches? It doesn't get applied just by adding it. The patch is the same code as you manually edited so it should have worked, if applied. The system patch works for me, and others.

        S 1 Reply Last reply Apr 24, 2024, 9:52 AM Reply Quote 0
        • S
          SwissSteph @pst
          last edited by SwissSteph Apr 24, 2024, 9:53 AM Apr 24, 2024, 9:52 AM

          @pst

          precisely ... no "apply" button, very strange indeed

          login-to-view

          login-to-view

          I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
          ... And now I'm living with a Netgate 8200
          ... And sorry for my bad English...

          P 1 Reply Last reply Apr 24, 2024, 10:00 AM Reply Quote 0
          • P
            pst @SwissSteph
            last edited by Apr 24, 2024, 10:00 AM

            @SwissSteph Two of the fields are not correct, change to

            Path Strip Count: 0
            
            Base Directory: /usr/local/www/pfblockerng/
            
            S 1 Reply Last reply Apr 24, 2024, 10:04 AM Reply Quote 0
            • S
              SwissSteph @pst
              last edited by Apr 24, 2024, 10:04 AM

              @pst

              I really suck ... and am very sorry to have taken up your time unnecessarily by poor handling and understanding on my part!!!!

              Thank you for understanding my error put forward where I had made a mistake.

              😊

              I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
              ... And now I'm living with a Netgate 8200
              ... And sorry for my bad English...

              P 1 Reply Last reply Apr 24, 2024, 10:20 AM Reply Quote 0
              • P
                pst @SwissSteph
                last edited by Apr 24, 2024, 10:20 AM

                @SwissSteph No worries :)

                S 1 Reply Last reply Apr 24, 2024, 10:34 AM Reply Quote 0
                • S
                  SwissSteph @pst
                  last edited by Apr 24, 2024, 10:34 AM

                  @pst

                  To make something "clean", I re-edited the two lines, put all the "-" in front of the "1".

                  Created a "patch" with YOUR very clear instructions (thanks again!) and "applied" this patch.

                  So I confirm that your corrections also work very well for me.

                  THANKS

                  I started with two "no-name" pfsense, one for use at home and the other as a backup in case of problems (which can happen when you're new to pfsense).
                  ... And now I'm living with a Netgate 8200
                  ... And sorry for my bad English...

                  N 1 Reply Last reply Apr 24, 2024, 1:03 PM Reply Quote 2
                  • N
                    N0m0fud @SwissSteph
                    last edited by Apr 24, 2024, 1:03 PM

                    @SwissSteph just wish the code would get fixed permanently.

                    S 1 Reply Last reply Apr 25, 2024, 12:09 AM Reply Quote 0
                    • C crucialguy referenced this topic on Apr 24, 2024, 10:56 PM
                    • S
                      SteveITS Galactic Empire @N0m0fud
                      last edited by Apr 25, 2024, 12:09 AM

                      I skimmed this but don’t see anyone put in a pfBlocker bug report at Redmine.pfSense.org.

                      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                      Upvote 👍 helpful posts!

                      D 1 Reply Last reply Apr 25, 2024, 12:12 AM Reply Quote 0
                      • D
                        DefenderLLC @SteveITS
                        last edited by DefenderLLC Apr 25, 2024, 12:15 AM Apr 25, 2024, 12:12 AM

                        @SteveITS There’s actually several entries for it with different descriptions.

                        https://redmine.pfsense.org/issues/15419
                        https://redmine.pfsense.org/issues/15365

                        S 1 Reply Last reply Apr 25, 2024, 2:09 AM Reply Quote 0
                        • S
                          SteveITS Galactic Empire @DefenderLLC
                          last edited by Apr 25, 2024, 2:09 AM

                          @DefenderLLC I wrote my note poorly...I meant, it wasn't linked on this page. I was on my phone and didn't dig into it, thanks for linking the reports.

                          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                          Upvote 👍 helpful posts!

                          1 Reply Last reply Reply Quote 1
                          • P pst referenced this topic on Apr 25, 2024, 4:01 PM
                          • G Gertjan referenced this topic on May 10, 2024, 12:18 PM
                          27 out of 29
                          • First post
                            27/29
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.