i had to leave it off as well. the file mods suggested in the forum did not work for me. waiting for a package upgrade

@marcelloc: @aaronouthier: So, I'm using DansGuardian and Squid together. I need to port forward ports 80 & 443 outgoing to port 8080 (DansGuardian) for a type of transparent Proxy Proxy use. SSL port will not work on dansguardian for transparent proxy. :( I am looking for help with Dansguardian SSL support with Squid3-dev on Non-transparent mode.  I am still on pfsense 2.1.5, using the DG and Squid3-dev packages as they come with the pfsense packages. The HTTPS sites are blocked succesfully and access succesfully when allowed.  The problem is that when blocked, it does not redirect to the access denied HTML template page, as done with the HTTP sites, but the browsers return a generic error connection page. Please tell me what information do you need from me, in order to be able to help me. I tried to start a thread for this, but I did not get any reply. https://forum.pfsense.org/index.php?topic=91012.msg505084#msg505084 At least tell me if this can not be solved.

Well i guess it was just too late for me to play with Squid. SNI is working indeed, the right client certificate is selected even on servers with multiple SSL certificates per vhost. Sorry for the post here :)

Anything in /var/squid/logs/cache.log?

Yes, I recreate the cache and deactivate the cron. Since that no more problem on squid except that the cache is not clearing each day ;-). I'll retry the command once I will have less traffic

1.  Squidguard requires Squid. 2.  You only need to install one instance of SquidGuard: the one that goes with your version of squid. You have three SquidGuards installed and no Squid.  No wonder it doesn't work. Here is what to do: 1.  Install Squid3. 2.  Install SquidGuard-squid3.

I've just come back to the forum hoping to find that the transparent proxy issue has been fixed, but apparently not. Worked beautifully up until 2.2 and then a massive step backwards. The issue seems to be that redirection is not working (see HERE), not that squid isn't working. Does nobody test releases on i386? Part of the attraction of pfsense is (was) that it would run perfectly on older hardware. Please let's see this resolved. Steve

system seems ok now…

You probably want to click every box that looks like it might "stealth" a proxy.

We stopped officially requiring 2.0.x compatibility for packages quite some time ago. Please upgrade to a supported release.

Yes , I just wiped all and installed a fresh copy. Hope it works better :)

I have the same issue.  Clamd is working great (and taking external checks from our mail server), but the clamd.log remains at 0bytes.

I have no idea about any of your questions, sorry.

You need to use haproxy 1.5, 1.4 did not support ssl.

The config like you have should allow you to access the website with: https://192.168.172.251:443  , though i do find it strange that the frontend has a private ip, and your backend seems to point to a public ip.. The backend server is usually on the lan/dmz network and likely using a private ip.. The frontend should be listening on the wan-ip (or where you want to accept connections) firewall rule is needed to allow access to this port. Not sure if this answers your question..? I couldnt make complete sense of it.

:o  I found a work around for my problem. The Dansguardian inserts the user name in the log if the authentication mode is Proxy-Basic (Maybe other modes will do it).  I was using Proxy-NTLM.  (Authentication was successfull with NTLM and it was connecting to LDAP successfully also)

Yes, it's been like that as long as I can remember.

All right, I'll try the first option to see if it suits my needs :) Thank you for your help.

By default squid will only allow 5 connections to squidguard if u have more than 5 users at the same time u are doom.   Now that u are in your shell check cache.log and see if u have something like this: 2013/10/25 09:44:24| WARNING: All redirector processes are busy. 2013/10/25 09:44:24| Consider increasing the number of redirector processes in your config file. If this is your case, just remember a formula: of Squidguard threats x memory size each one=RAM memory for squidguard. Because squidguard depends on RAM that is why is fast. Hope this is your case and hope this helps!!!