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

    2.1-BETA1 (i386) built on Fri Mar 1 09:39:17 - cannot load firewall_rules.php

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    5 Posts 2 Posters 1.4k 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.
    • M
      miles267
      last edited by

      2.1-BETA1 (i386)
      built on Fri Mar 1 09:39:17 EST 2013
      FreeBSD 8.3-RELEASE-p6

      Caution - after updating to latest build, you cannot click FIREWALL > RULES.  It returns:

      Parse error: syntax error, unexpected '}' in /usr/local/www/firewall_rules.php on line 749

      EDIT: this didn't help me: https://github.com/pfsense/pfsense/commit/f7344c521dd87a6d8ad2f7b19dd8e3a96def5c96

      1 Reply Last reply Reply Quote 0
      • N
        NOYB
        last edited by

        Actually it was probably the previous commit that broke it.
        https://github.com/bsdperimeter/pfsense/commit/56dda8e089f6760fb62a61068aa796e625333dc3

        And this one will probably fix it when the next build happens.
        https://github.com/bsdperimeter/pfsense/commit/f7344c521dd87a6d8ad2f7b19dd8e3a96def5c96

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

          @NOYB:

          And this one will probably fix it when the next build happens.
          https://github.com/bsdperimeter/pfsense/commit/f7344c521dd87a6d8ad2f7b19dd8e3a96def5c96

          Unfortunately I did attempt to implement this fix without success.  Anxiously awaiting the next build :-)

          1 Reply Last reply Reply Quote 0
          • N
            NOYB
            last edited by

            Ah it see.

            Hmmm, interesting.

            Perhaps browse not fully refreshed?

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

              @NOYB:

              Ah it see.

              Hmmm, interesting.

              Perhaps browse not fully refreshed?

              DUH.  Thank you!  Yes, that was issue.  I hadn't forced Firefox to refresh.

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