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

    500 - Internal server error on one interface's Firewall rules.

    Scheduled Pinned Locked Moved General pfSense Questions
    4 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
      mrevil
      last edited by

      So tonight I was doing a bit of experimenting with my personal PFSense box and I may have  inadvertently made a defective firewall rule on a new interface.  When I go to the Firewall rules page and click on the tab for my interface (and only that interface) I get a 500 - Internal Server error.  As such I can't remove the defective rule and am having a pickle of a time getting rid of it without having to scrap my entire config.

      Here's the relevant lines from my lighttpd.error.log

      2013-02-24 00:38:11: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fa stcgi process died): pid: 708 socket: unix:/tmp/php-fastcgi.socket-1
      2013-02-24 00:38:11: (mod_fastcgi.c.3282) child exited, pid: 708 status: 0
      2013-02-24 00:38:11: (mod_fastcgi.c.3329) response not received, request sent: 9 76 on socket: unix:/tmp/php-fastcgi.socket-1 for /firewall_rules.php?if=opt1, cl osing connection
      2013-02-24 00:41:20: (log.c.166) server started
      
      

      I probably made some bone-headed newbie mistake, but thankfully the only person put out by this is me.  So forgive a guy for making a mistake on the path to understanding.  Thanks for any help you guys can spare.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        One option here would be to manually edit your config.xml file to remove the rule and then restore it. That is however open to error!  ;)
        I have a hard time believing that entering any rule, no matter how wrong, should cause an error like that.

        Steve

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

          Thanks for the reply, I was really hoping it wouldn't come to that.  I too believe that the error is just coincidental.

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

            Well, it looks like "Have you tried turning it off and on again?" Has succeeded after a 2nd reboot.

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