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

    Squid3 reverse proxy issues

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    8 Posts 3 Posters 3.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.
    • P
      Pakken
      last edited by

      Hey there, in pfsense 2.1.5 I've got a pretty simple setup (2 wans, 3 lans and a dmz) with a couple of web servers, and multiple websites, behind a pfsense virtual firewall (ESX) and squid3 set to work in reverse proxy mode. Everything's fine.

      Same setup on a 2.2 setup won't work. Neither does with the last squid3 release/package.
      Everytime I try to bind it to listen on port 80, I get an error message saying I need to lower net.inet.portrange.first from 1024 to 0, which I did at least 20 times ;D with no results, tried restarting squid-restarting the entire vm, no results.
      In the squid's log all I get is a permission denied when trying to bind on port 80.

      Is this a known issue?
      Thank you for all your hard work, everything but squid is running great on 2.2RC.

      Luca

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

        On your 2.2 setup, did you do an upgrade from 2.1.5 to the RC or was it a fresh install?

        1 Reply Last reply Reply Quote 0
        • C
          Cino
          last edited by

          Did you try the NAT redirect setup?

          https://forum.pfsense.org/index.php?topic=84638.msg474999#msg474999

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

            Fresh install, didn't try the NAT redirect setup yet, but when trying to bind everything above port 1024 doesn't seep to pop up errors.
            The strange thing is that the above mentioned system tunable seems to have no impact even if the reverse proxy clearly states that lowering the value to 0 should solve the problem.
            Thank you.
            :)

            1 Reply Last reply Reply Quote 0
            • C
              Cino
              last edited by

              I take you rebooted after changing the system tunable value?

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

                Thank you for your answer, yes I did. Looks like a bug tbh

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

                  I've tried setting the tunable value from the pfS web config AND in sysctl at the console, but it refuses to change.  This has got to be something weird with the base.

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

                    That's the problem then… :)

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