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

    Webserver acces from LAN

    Scheduled Pinned Locked Moved NAT
    9 Posts 4 Posters 483 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.
    • F
      foravis
      last edited by

      Hello,

      I have a dynamic public IP but I have a functional Dynamic DNS service. The webserver is an Apache server... WAMP on a Windows 10 VM in esxi. PFsense is also a VM in the same esxi.

      I've added NAT Port Forward rule.
      84856837-fcac-48d4-861a-40441186fc6d-image.png

      I've added the port in windows firewall also.

      I have a problem in accessing the server from inside the network through dynamic DNS domain name. From outside the network there is no problem. Also in LAN the http://192.168.1.20:12323 is working.

      I have the same problem with the FTP service (filezilla server in windows 10).

      Thank you

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

        Add a DNS override for your public host name.

        V 1 Reply Last reply Reply Quote 0
        • F
          foravis
          last edited by

          @viragomann said in Webserver acces from LAN:

          Add a DNS override for your public host name.

          I've just checked the access through the public IP and is not working... so is not only the dynamic dns name...

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

            @viragomann said in Webserver acces from LAN:

            Add a DNS override for your public host name.

            1 Reply Last reply Reply Quote 0
            • GertjanG
              Gertjan
              last edited by

              First of all : this https://docs.netgate.com/pfsense/en/latest/nat/port-forward-troubleshooting.html captures all possible issues.

              If it still doesn't work : capture all the traffic on the incoming WAN interface, and see for yourself if the traffic actually reaches pfSense. (check point 8 on the list on the trouble shoot page above ).
              The WAN interface handles all incoming and outgoing traffic, the capture file will contain a lot of packets. So, in your case, you could focus on your NAtted incoming traffic by selecting only "port 12323" traffic.

              You should check all 15 points on the list.

              Btw :
              05bbc0d9-cd67-44e3-b269-4ff97b908b17-image.png

              Not very important, but you should consider making this "TCP" only. Web servers do not use UDP traffic.

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              1 Reply Last reply Reply Quote 0
              • F
                foravis
                last edited by

                Thank you, I'll try and let you know.

                1 Reply Last reply Reply Quote 0
                • F
                  foravis
                  last edited by

                  I've checked all 15 items from the list and I couldn't find the problem.

                  The states looks like this:

                  98d7c564-aecf-4df5-bf08-8295d8a63d59-image.png

                  The problem is when I'm trying from LAN to public IP or domain name. From LAN to LAN IP is all good... also from WAN to Public IP is working.

                  1 Reply Last reply Reply Quote 0
                  • RicoR
                    Rico LAYER 8 Rebel Alliance
                    last edited by

                    Have you checked https://docs.netgate.com/pfsense/en/latest/nat/accessing-port-forwards-from-local-networks.html ?

                    -Rico

                    1 Reply Last reply Reply Quote 0
                    • F
                      foravis
                      last edited by

                      It worked with NAT Reflection. Thanks

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