Hi!
Thanks for your help.

I think my settings can't see the full URL.
because squidguard blacklist log just like this.

"play.google.com:443 Request(PROXY_BASIC/none/-) - CONNECT REDIRECT"

so how to set a method that can see the full URL?

Thank you.

Installed Version:pfSense(2.3.3-RELEASE-p1 (amd64) ) with Squid(0.4.36_2) and SquidGuard(1.16.1)

Trying to debug the thing, I decided to turn off the SSL Man In the Middle Filtering, just to see if I could get Squid and pfsense on AWS to act as a regular proxy and take it from there. Turns out that that one did not work either  :(

I tried a normal, non-ssl, site and still get Access Denied. I wonder if there is something weird with AWS and their network that is acting up on me?

On the Inbound rules I have:

HTTP            TCP 80 0.0.0.0/0 Custom UDP Rule UDP 1194 0.0.0.0/0 SSH            TCP 22 0.0.0.0/0 Custom TCP Rule TCP 3128 - 3129 0.0.0.0/0 HTTPS          TCP 443 0.0.0.0/0

And on outbound, nothing

Transparent squid will bind.to the default gateway, it does not follow policy routing

@aeleus:

I have a similar issue.

Everything was working as expected using HTTP.

I recently switched the webConfigurator (System/Advanced/Admin Access) from HTTP to HTTPS.

Now, that redirects everything to HTTPS - including SquidGuard redirects that are set to HTTP.

From squidGuard.conf:

default  {
pass Internal Allowed !in-addr !Blocked none
redirect 301:http://proxy.mydomain.net/sgerror.php?url=403%20&a=%a&n=%n&i=%i&s=%s&t=%t&u=%u
log block.log
}

That would be fine except that I have this in squidGuard.conf:

dest blk_BL_adv {
domainlist blk_BL_adv/domains
urllist blk_BL_adv/urls
redirect http://10.0.0.1:80/sgerror.php?url=blank_img&msg=&a=%a&n=%n&i=%i&s=%s&t=%t&u=%u
log block.log
}

That gives me certificate errors when it redirects to https://10.0.0.1/….

I don't know why that's the only entry - aside from the default and explicit ACL's that I set - that has a redirect.

Any thoughts on how to change it?

To get rid of the certificate errors for sgerror happens, you need to create a certificate for your server. Specify the alternative names for your server like FQDN and IP address of the server.

@doktornotor:

There is no need for MITM nor for installing certificates on clients when you explicitly set the proxy on clients. Squid will use CONNECT for HTTPS on sslports ACL to connect to HTTPS websites. If you want MITM, make the proxy transparent and stop configuring it on clients.

I want to be able to see HTTPS traffic for both inspection + caching. I've tried not configuring the proxy on clients and leaving on transparent mode. That's throwing errors too. Am I the only one having this issue?? I'm guessing the DNS alternative name isn't being mimicked by Squid properly. Since on Chrome mobile, that's an error it's saying "DNS alternative name invalid".

At the risk of stating the obvious: exemple is NOT the same thing as example. You keep producing that typo over and over and over again. When you keep obfuscating your setup and producing collateral typos in the way, it's impossible for others to debug anyway.

You've already been told how to debug in the post directly above.

thank you!!

Of course with your suggestion i am thinking in try the authenticator in my cenario. If works fine it´s the better option update the versions and use the sync.

Appreciate the location.

Are they viewed from a terminal command, or through the WebUI?

@niko2:

For those who have not reached to get it working : here is the trick (working on pfsense 2.3) :
in general settings tab of squidguard, there is an "apply" button.
it is mandatory to click after any changes, event on other tabs.
ACL groups work for me !
hopes this help :)

Work like a charm !!!

You are welcome.

We have the same problem… we have installed a diladele webfilter on our pfsense using peek-n-splice for scanning ssl trafic. WPAD does not work with the iOS devices in our wlan. The clients have to install our CA-Cert if they want to use the wlan. The default browser on the mobile devices is using the crt and we can scan the traffic. But Apps like Facebook and Whatsapp does not use DNS - they use ips to connect to there services. If you enter these IPs into the "Bypass Proxy for These Destination IPs" field on the squid config page on the pfsense they will connect directly. But i think this is a bad solution to add all ips seperated by semikolon in this one line field... so i'm trying to add these direct to the squid conf... if you say the "alway_direct" acl does not work - there must be another ACL rule for this... anybody have an idea?

Hi PiBa,

dang I thought I realised it that way myself on an 1.7 HaProxy Cluster but you're obviously right - it's still not supported.  :-X Maybe I suggest this one to the haproxy community so they'll implement it first.