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

    Squid gurad stops after restarting the firewall in pfsense latest version 2.3

    Scheduled Pinned Locked Moved Cache/Proxy
    3 Posts 2 Posters 997 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.
    • S
      shehan31
      last edited by

      Dear all,
      I have upgraded my pfsense fireewall into the latest version (previous 2.6). Therafter I installed Squid, SquidGard, Lightsquid and Cron. I installed the commonACL from shallalist.de. Also created a new target cateogory and added into that list as adiviced. It has two interfaces LAN and WAN.  Without enabling proxy, Internet works fine. When I enable proxy it does not work and the state of the squid guard shows as "stop". Cannot restart the service either.  This problem was there in 2.6 but leagacy squid helps to proceed with the squid implementation. But now there is no legacy squid. Please refer to the atachments.
      syncingfirewall.jpg
      syncingfirewall.jpg_thumb
      20160420_171446.jpg
      20160420_171446.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Full install or NanoBSD?

        If it's a full install, do you have the option set to make /var a RAM disk? (See System > Advanced, Misc tab)

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • S
          shehan31
          last edited by

          Hello Jimp,
          Sorry for the late reply. Actually I upgraded and its not a NanoBSD. I didn't set the RAM disk option. Any how I upgraded another 64 bit server and had the same issue. I add proxy authentication and it started to work. Now users have to enter proxy authentication in heire web browsers.  Is there a solution.

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