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

    Cant access to webgui from WAN

    Scheduled Pinned Locked Moved webGUI
    10 Posts 6 Posters 4.1k 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
      muadib
      last edited by

      Hello!

      We are running pfsense to work as wireless proxy server.

      The problem as that we are only be allow to access to webgui from LAN interface and not by WAN.

      WAN IP is a private network IP too.

      We are running the latest pfsense, 1.0.2 rc2

      In firewall/rules a http rule for the webgui is enabled (auto created i think)

      Some bug?

      Best reggards
      Pedro

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

        You will need to untick the "Block private networks" box on your WAN interface if the WAN is on an RFC1918 (10/8, 172.16/12, 192.168/16) network.

        1 Reply Last reply Reply Quote 0
        • GruensFroeschliG
          GruensFroeschli
          last edited by

          the autocreated rule allows access to the webgui from the LAN not from WAN.
          if you want access from WAN to the webgui you need to creat a rule that allows traffic on the WAN.

          We do what we must, because we can.

          Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

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

            thanks morbus but i already do that :)

            GruensFroeschli the auto created rule iam talking as been created when i made a NAT rule (i just remember) when i was trying to redirect all wan traffic to pfsense lan ip. I have tryed to made the rule but it is not working, the webgui is https (i have open https) could be some issue regarding https?

            1 Reply Last reply Reply Quote 0
            • GruensFroeschliG
              GruensFroeschli
              last edited by

              can you post a screenshot of your allow rule on the WAN interface?

              We do what we must, because we can.

              Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

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

                screenshot ready :)

                rule.JPG
                rule.JPG_thumb

                1 Reply Last reply Reply Quote 0
                • Y
                  yoda715
                  last edited by

                  @muadib:

                  screenshot ready :)

                  You need to specify the destination as 'Wan address'

                  1 Reply Last reply Reply Quote 0
                  • S
                    sullrich
                    last edited by

                    #1.  Change the protocol to TCP only. 
                    #2.  Change the destination address to "WAN IP Address"

                    1 Reply Last reply Reply Quote 0
                    • K
                      KaYs3r
                      last edited by

                      Thanks :)

                      I'm muadib's friend, this is working now

                      Thank you :)

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

                        kaY3r is learning from me..lol

                        thanks for all the help from all of you! :)

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