• Proxy causing time outs.

    29
    0 Votes
    29 Posts
    6k Views
    KOMK
    Should work fine on Windows, Mac and Linux clients.  Only mobile seems to still be an issue.
  • Upgrade from 2.2.1 to 2.2.2 has broken my squid transparent proxy

    7
    0 Votes
    7 Posts
    2k Views
    K
    clean install because im on 2.2.2 works fine. Also make sure you white list the proxy on squid see picture. Also make sure squid is running. When doing a clean  install first get squid3 configure it, then install squidGuard. [image: Clipboarder.2015.05.09.png] [image: Clipboarder.2015.05.09.png_thumb]
  • Lightsquid 2.41 not working with Novosea and novopf themes.

    7
    0 Votes
    7 Posts
    1k Views
    S
    Here you go [image: renato.PNG] [image: renato.PNG_thumb]
  • SquidGuard + Whitelist (Solved)

    3
    0 Votes
    3 Posts
    3k Views
    D
    I have manage to fix my problem by clearing Squid Cache and Firefox Cache. After I have done that the Whitelist worked as expected. So, it was a noob error.  ;)    ::)
  • Upload stable package version .pbi in Pfsense

    2
    0 Votes
    2 Posts
    963 Views
    D
    Very simple. You don't. And the "beta" does not mean what you think it means.
  • Security Issue on Squid

    4
    0 Votes
    4 Posts
    1k Views
    BBcan177B
    https://forum.pfsense.org/index.php?topic=93188.0
  • 0 Votes
    3 Posts
    768 Views
    KOMK
    The ESF guys only compile & maintain a build of squid for pfSense.  If you want new features, go to squid-cache.org and get involved with the people that actually create squid.
  • Snort with squidGuard and squid3?

    1
    0 Votes
    1 Posts
    843 Views
    No one has replied
  • HAPROXY and IPSEC problem with transparent IP in backend

    2
    0 Votes
    2 Posts
    1k Views
    P
    i dont think it matters your using ipsec.. When using transparent-client-ip feature ALL reply traffic from the webserver:port is redirected to the pfsense system ip-stack for haproxy to pick up.. This also happens when accessing a server on opt1 from the lan-network.. It is a limitation of the ipfw & pf firewall combination required to make transparent-client-ip work.. Workaround might be to portforward incoming requests over ipsec or other to haproxy. Its a known issue, also in the warning/explanation near the transparent-client-ip setting, however to get it solved a patch to pf is needed.. https://redmine.pfsense.org/issues/3943 . Not sure if/when that will get applied..
  • What are Remote Cert Checks and Certificate Adapt?

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Squidclient timeout with Squid 3

    4
    0 Votes
    4 Posts
    1k Views
    T
    Tried localhost isntead of 127.0.0.1  and it worked.  ::) ::) ::) ::)
  • Squid and squidguard not working after reboot

    4
    0 Votes
    4 Posts
    6k Views
    stephenw10S
    Not yet. When a new squidguard version is released the package version will be incremented and you will see that System > Packages. Steve
  • Squid and SquidGuard not starting

    20
    0 Votes
    20 Posts
    13k Views
    A
    thanks sir its work :D
  • LighSquid error (PERL/Open-VM-Tools)

    6
    0 Votes
    6 Posts
    2k Views
    S
    Thanks jimp, implemented the fix successfully on two machines.
  • SquidGuard 1.9.14 update?

    3
    0 Votes
    3 Posts
    979 Views
    K
    o gotcha gotcha didn't see that anyway i just reinstalled it unfortunately it need to edit the sgerror php to my liking but besides that its doing a great job Thank again
  • Lightsquid 2.39 fresh pfsense box error 404

    2
    0 Votes
    2 Posts
    656 Views
    G
    Bump Any one? I'm stuck for 2 days here :'(
  • Lightsquid configuration help

    2
    0 Votes
    2 Posts
    1k Views
    G
    same I made a post about it down, fresh install right?
  • Re: squidclamav not displaying page when virus detected. [SOLVED]

    2
    0 Votes
    2 Posts
    1k Views
    J
    Changed perl location at top of clwarn.cgi from /usr/pbi/squid-i386/local/bin/perl5.18.4/bin/perl to /usr/local/bin/perl Although both binaries seem to run fine, it prefers the second.
  • Host using specific gateway

    2
    0 Votes
    2 Posts
    728 Views
    G
    oh sorry, I think that I found answer to my question acl HOST1 src 192.168.0.114/32 acl HOST2 src 192.168.0.115/32 tcp_outgoing_address 192.168.2.91 HOST1 tcp_outgoing_address 192.168.2.91 HOST2 :) BUT is it possible to specific this just for one port ? Thanks
  • Squidguard

    1
    0 Votes
    1 Posts
    867 Views
    No one has replied
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.