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

    Local httpd

    Scheduled Pinned Locked Moved DHCP and DNS
    8 Posts 5 Posters 2.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.
    • G
      gordon
      last edited by

      Hello,

      I have a httpd with a domain name xxx.com the http have ip adress 192.168.1.2 everything work perfect from outside (officel ip adress port 80 forwarded to 192.168.1.2).
      But when I try to browse my domain name from my computer on the same subnet have I problem to connect….

      How can I solve this? I have not had this problem with my old linksys router.

      Thank you for respons.

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        So your trying to go to www.xxx.com that resolves to your public IP from behind pfsense?  You need to enable nat reflection to do that.  Or better method is to have your local hosts directly resolve www.xxx.com to your private IP 192.168.1.2

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        • G
          gordon
          last edited by

          @johnpoz:

          So your trying to go to www.xxx.com that resolves to your public IP from behind pfsense?  You need to enable nat reflection to do that.  Or better method is to have your local hosts directly resolve www.xxx.com to your private IP 192.168.1.2

          Thank you for using time on me problem. I wil l try to explain another way:

          xxx.com  - offical IP adress 166.54.223.2 (example).
          httpd server have 192.168.1.2 (local network)

          I have port forwarding on 166.54.223.2 on port 80 to 192.168.1.2 port 80

          When people use xxx.com they are abel to reach my httpd server,
          but when I try from my computer who are into the same subnet I can`t connect.
          It must have something with the DNS server todo?

          I hope you understand me here :)

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by

            You need to enable nat reflection to do that.  Or better method is to have your local hosts directly resolve www.xxx.com to your private IP 192.168.1.2

            This is the answer - do one of these. An easy way is to add a host override in DNS Forwarder to define xxx.com to be 192.168.1.2

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • A
              adolfo_rodrigues
              last edited by

              @phil.davis:

              You need to enable nat reflection to do that.  Or better method is to have your local hosts directly resolve www.xxx.com to your private IP 192.168.1.2

              This is the answer - do one of these. An easy way is to add a host override in DNS Forwarder to define xxx.com to be 192.168.1.2

              It is like phill said, I had the same issue here, the workqround was enabling DNS Forwarder to resolve the host and domain to my internal IP from my internal machines.

              On your case see attached.

              Hope it helps. Regards.

              dnsforwarder.PNG
              dnsforwarder.PNG_thumb

              1 Reply Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator
                last edited by

                Phil just quoted and agreed with what I said ;)  But sure give phil the credit!! rofl

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.8, 24.11

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

                  This wiki page lays out the various possibilities you have:
                  https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks%3F

                  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
                  • G
                    gordon
                    last edited by

                    @adolfo_rodrigues:

                    @phil.davis:

                    You need to enable nat reflection to do that.  Or better method is to have your local hosts directly resolve www.xxx.com to your private IP 192.168.1.2

                    This is the answer - do one of these. An easy way is to add a host override in DNS Forwarder to define xxx.com to be 192.168.1.2

                    It is like phill said, I had the same issue here, the workqround was enabling DNS Forwarder to resolve the host and domain to my internal IP from my internal machines.

                    On your case see attached.

                    Hope it helps. Regards.

                    It is working, thank you very much!

                    I have many vhost like test.xxx.com bla.test.com etc… Can I set up so every vhost work also?
                    I have tested it works to add manually each vhost, but is their a way I can take all at the same time?

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