Navigation

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

    Lightsquid - Error (1): Cannot get data. Server answered: HTTP/1.0 403 Forbidden

    pfSense Packages
    7
    8
    15765
    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
      mat1_8 last edited by

      Hi,

      When I go to Lightsquid - Proxy State I get an error saying:

      Error (1): Cannot get data. Server answered: HTTP/1.0 403 Forbidden

      Can some please tell me what the problem might be? Thanks

      1 Reply Last reply Reply Quote 0
      • T
        Topper727 last edited by

        When you go to Lightsqid you get 403, I would think the package is not installed properly. Did you try uninstall that package and reinstall?

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

          Hi,

          Yes I have re-installed pfSense dozens of time but no luck.

          I have looked around the forum and found out that no one has ever come up with a solution for this problem. I have asked it again to raise attention on this but it seems that no one knows the right answer :(

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

            @mat1_8:

            Hi,

            Yes I have re-installed pfSense dozens of time but no luck.

            I have looked around the forum and found out that no one has ever come up with a solution for this problem. I have asked it again to raise attention on this but it seems that no one knows the right answer :(

            I have installed pfsense 2.0.3 with lightsquid
            I still get the same error:

            Error(1): Cannot get data. Server answered: HTTP/1.0 403 Forbidden.

            I think there's no solution yet.

            1 Reply Last reply Reply Quote 0
            • R
              rampuji last edited by

              I tried reinstalling lightsquid many times. But no luck. I believe configuration is also good.

              1 Reply Last reply Reply Quote 0
              • Z
                zenny last edited by

                This is an outstanding bug for a long time:

                http://redmine.pfsense.org/issues/2903

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

                  In the passed, when I got this error, it was because lightsquid adds a remote access subnet for all the subnets you included in the Proxy interface you selected in the general setup.

                  If you installed squid, then installed lightsquid, then changed your selected proxy interface at the top of squid general setup then when you go to the Access control page you will probably notice that all of the subnets that would be covered by the interfaces you selected in general setup are not accounted for in the :
                  External Cache-Managers list.

                  If the External Cache-Managers field does not include 127.0.0.1 plus each subnet that corresponds to EACH LAN, OPT, WAN ect interface you selected in the general setup of squid, don't worry.  Although you can't add to the field manually without causing an error most  likely, you can select the interfaces you want by clicking them (or control + click) if you want more than one.  Then apply your squid settings.  (Don't select all the interfaces + loopback.  It causes error).

                  Basically squid has to be fully set up and the lightsquid intalled AND squid proxy interfaces NOT later modified.
                  After you apply squid settings, click the reinstall package button next to lightsquid in package manager.

                  Unless you have really broken something, it should be working after u select refresh now and then full refresh in lightsquid.

                  Worked for me anyway.

                  P.S.  I also have all of the subnets I want to allow for TRANSPARENT squid listed in access control > Allowed subnets

                  1 Reply Last reply Reply Quote 0
                  • B
                    basitkhan last edited by

                    hi..
                    i followed it and its working fine at squid 3.3.5

                    http://forum.pfsense.org/index.php?topic=65102.0

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post

                    Products

                    • Platform Overview
                    • TNSR
                    • pfSense Plus
                    • Appliances

                    Services

                    • Training
                    • Professional Services

                    Support

                    • Subscription Plans
                    • Contact Support
                    • Product Lifecycle
                    • Documentation

                    News

                    • Media Coverage
                    • Press
                    • Events

                    Resources

                    • Blog
                    • FAQ
                    • Find a Partner
                    • Resource Library
                    • Security Information

                    Company

                    • About Us
                    • Careers
                    • Partners
                    • Contact Us
                    • Legal
                    Our Mission

                    We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                    Subscribe to our Newsletter

                    Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                    © 2021 Rubicon Communications, LLC | Privacy Policy