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

    Single public IP, 2 Domain reverse proxy

    Scheduled Pinned Locked Moved Cache/Proxy
    14 Posts 7 Posters 3.4k 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.
    • T
      toddos
      last edited by

      Why not Squid3's reverse proxy?  That's what I'm doing with multiple no-ip.org domain names on different domains (name1.no-ip.org, name2.ddns.net, etc).

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        @toddos:

        Why not Squid3's reverse proxy?

        Some people prefer small working packages to broken monstrosities. :P

        1 Reply Last reply Reply Quote 0
        • W
          warren
          last edited by

          Thanks for all your help guys,

          Does anyone have an example of how to get HAproxy up and running with multiple domains?
          I have searched the PfSense forum but seem to be getting lost with all the different advice.

          1 Reply Last reply Reply Quote 0
          • P
            PiBa
            last edited by

            I've put a small example together: https://docs.google.com/document/d/1YflytSq7P8oZBSCVUKWS1v2P0CdShbxeCsbTZ59JCRo/pub

            1 Reply Last reply Reply Quote 0
            • W
              warren
              last edited by

              Thanks for taking the time to write a quick guide PiBa, your a star!

              1 Reply Last reply Reply Quote 0
              • W
                warren
                last edited by

                @PiBa:

                I've put a small example together: https://docs.google.com/document/d/1YflytSq7P8oZBSCVUKWS1v2P0CdShbxeCsbTZ59JCRo/pub

                Hi PiBa, for some reason your example has been removed from google docs.
                Could you please post the document again?

                Thanks,
                Warren

                1 Reply Last reply Reply Quote 0
                • P
                  PiBa
                  last edited by

                  For some reason the example was taken offline by google, ive asked them for verification why it was 'inappropriate'.. Anyway hereby attached as PDF..

                  Edit 2015-07-02:
                  Ive updated the document 'pfSenseHAProxy v2.zip' to include some information about HTTPS / SNI configuration for the backend selection.

                  [pfSenseHAProxy v2.zip](/public/imported_attachments/1/pfSenseHAProxy v2.zip)

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

                    Same thing for squid3 reverse proxy (which doesn't seem that monstrous to me).  I skipped the parts about adding the Web Servers and Mappings, those guides are already written.

                    –
                    Andy

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

                      @PiBa, I have been looking at your guide, and was wondering the ports you use on the Backend servers, are not standard ports, 80/443.
                      When using HTTP you set the ports for 301+302 I see those 2 servers are on the same IP, but port 301 and 302, are they the listening ports on your actual webserver ??

                      Thanks
                      /Michael

                      1 Reply Last reply Reply Quote 0
                      • P
                        PiBa
                        last edited by

                        Hi Michael,

                        Yes those are listening on my 'webserver' / testbox.. When writing the guide i was using only 2 machines (1 pfSense & 1 webserver), where i indeed had the webserver listening on multiple ports with a different index.html served on each one just to check if the haproxy side of things was working properly. When using different webservers you could use port 80 or 443 on all of them and make the difference by their ip's. Or you could actually host multiple webapplications on different ports from 1 machine, while serving all of them on the 'outside' on the standard 80 / 443 ports. But a webserver could likely also accomplish that with configuring some virtualhosts..

                        Anyway i hope this helps understand the screenshots a little better.. Sorry for the confusion.

                        Latest 'doc' is currently available here (im still using those non standard ports there though ;) ): https://github.com/PiBa-NL/pfsense-haproxy-package-doc/wiki

                        Regards,
                        PiBa-NL

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