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

    Lost access to Web Configurator

    2.0-RC Snapshot Feedback and Problems - RETIRED
    3
    4
    4.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.
    • T
      torontob
      last edited by

      Hi everyone,

      Using pfSense 2.0 RC3 here. Web Configurator was working yesterday but is not working today. I have set a custom port of 20080 for it and had it set to HTTPs (I think that's done by default), now using the RS-232 cable o console I can see these filter logs while trying to access Web Configurator:

      00:00:08.280338 rule 2/0(match): block out on vr0: 192.168.0.1.20080 > 192.168.0
      .98.46549: [|tcp]
      00:00:01.328739 rule 1/0(match): block in on ovpns1: 172.16.0.6.46664 > 172.16.0
      .1.20443: [|tcp]
      00:00:01.701295 rule 2/0(match): block out on vr0: 192.168.0.1.80 > 192.168.0.98
      .46550: [|tcp]
      00:00:06.640317 rule 1/0(match): block in on vr1: 64.64.64.64.5678 > 255.255.255
      .255.5678: UDP, length 78
      ```**pfctl -d**
      
      I have done the and also Restarted Web Configurator from console and did RESET as well. None of that helped.
      
      The router functions all good but it times out and as the iptables blocks it. I thought connecting directly to it would give me access because the anti-lockout feature.
      
      Please let me know what else I can do to get access. Based on above it seems that firewall is blocking me. Is there anyway I can tamper firewall through console access?
      
      Thanks
      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        I would normally suggest:
        http://doc.pfsense.org/index.php/I_locked_myself_out_of_the_WebGUI,_help!
        But it looks like you've already tried 'pfctl -d' ?

        Steve

        1 Reply Last reply Reply Quote 0
        • T
          torontob
          last edited by

          Restart of the router fixed this. This is not good….maybe a bug?  ::) :o

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

            @torontob:

            Restart of the router fixed this. This is not good….maybe a bug?  ::) :o

            its got to be a bug.  unfortunately in my case, a restart doesn't fix it.

            try upgrading the firmware. saw that on the forums someplace and that worked for me once.

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