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

    Cannot access pfSense GUI. When I portscan only open ports from LAN are only 53 and 22

    Scheduled Pinned Locked Moved General pfSense Questions
    8 Posts 3 Posters 567 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.
    • B
      BobAce
      last edited by

      I need help -I am new to pfSense and I cannot access the pfSense GUI. When I portscan, the only open ports from LAN are 53 and 22.
      Can I use the console menu or SSH command to open the LAN port for WEB GUI?
      Thank you.

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @BobAce
        last edited by

        @BobAce
        When you reconfigure the interface in the console (option 2), pfSense aks you to use HTTP or HTTPS to access the webGUI.
        After finishing this process, it displays the URL. This should work at least.

        So depending on what you've chosen before, port 80 or 443 should be open.

        B 2 Replies Last reply Reply Quote 1
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          SSH is not enabled by default so can we assume you enabled it? If not you may not actually be scanning the pfSense IP address.

          B 1 Reply Last reply Reply Quote 0
          • B
            BobAce @viragomann
            last edited by

            @viragomann Thank you so much When reassigning the same LAN IP (or different IP) it gives me an option to enable the Web interface but then errors as below. And it will not apply changes. Thank you.

            Enter an option: Do you want to revert to HTTP as the webConfigurator protocol? (y/n) y

            Note: the anti-lockout rule on lan has been re-enabled.

            Please wait while the changes are saved to LAN...
            Fatal error: Uncaught TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given in /etc/inc/config.lib.inc:1070
            Stack trace:
            #0 /etc/inc/config.lib.inc(1070): fwrite(false, 'a:31:{i:1706134...')
            #1 /etc/inc/config.lib.inc(660): backup_config()
            #2 /etc/rc.initial.setlanip(495): write_config('lan IP configur...')
            #3 {main}
            thrown in /etc/inc/config.lib.inc on line 1070
            PHP ERROR: Type: 1, File: /etc/inc/config.lib.inc, Line: 1070, Message: Uncaught TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given in /etc/inc/config.lib.inc:1070
            Stack trace:
            #0 /etc/inc/config.lib.inc(1070): fwrite(false, 'a:31:{i:1706134...')
            #1 /etc/inc/config.lib.inc(660): backup_config()
            #2 /etc/rc.initial.setlanip(495): write_config('lan IP configur...')
            #3 {main}
            thrownNetgate pfSense Plus - Netgate Device ID: 73754f273b187cf7b140
            Netgate pfSense Plus - Netgate Device ID: 73754f273b187cf7b140

            1 Reply Last reply Reply Quote 0
            • B
              BobAce @stephenw10
              last edited by

              @stephenw10 Thank you. Yes, I have enabled ssh from the console directly not from SSH. Now I can access the console using Putty from the LAN side open command /etc/rc.initial and get to the menu.

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

                Hmm, does restarting the webgui from the console menu (option 11) also throw that error?

                Does it still reboot correctly? That could be a drive issue.

                B 1 Reply Last reply Reply Quote 0
                • B
                  BobAce @viragomann
                  last edited by

                  @viragomann Thank you so much. Instead of SSH then the console menu I pugged in my video cable, keyboard, and mouse, connected to the console directly from the firewall hardware, ran option 2 and it worked. Thank you again. I was pulling my hair all day today finally I have access.

                  1 Reply Last reply Reply Quote 0
                  • B
                    BobAce @stephenw10
                    last edited by

                    @stephenw10 Thank you @viragomann 's solution worked directly connecting to the firewall hardware console using video cable, keyboard and mouse.

                    Thank you again!

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