Something like https://docs.diladele.com/faq/filtering/locked_policy.html ?

I am not sure why your .* regex does not work in blacklist - most probably the squid conf that is generated expects domain names and NOT domain regex. Then try to specify something like (not tested):

acl all_others dstdom_regex .*
http_access deny all_others

See http://wiki.squid-cache.org/SquidFaq/SquidAcl

Having the same problem with proxy not working on HTTP but HTTPS working since it is not setup for transparent proxy yet.

Running pfSense 5.6.5 2.3.5-DEVELOPMENT.
Setup SQUID with Transparent Proxy.

em0 wan
em1 lan, vlan10, vlan11, vlan12, vlan99, vlan100

I can see that ALL HTTP traffic is getting blocked.  Of course, websites with HTTPS are passing through the Transparent Proxy.
My understanding is that pfs would make all necessary firewall rules and/or NAT translations to pass port 80 requests over to 3128.

If I look at /tmp/rules.debug I see port 80 rules redirect to 3128 on the loopback interface.

Setup Squid proxy redirect

rdr pass on em1_vlan11 proto tcp from any to !(em1_vlan11) port 80 -> 127.0.0.1 port 3128
rdr pass on em1_vlan10 proto tcp from any to !(em1_vlan10) port 80 -> 127.0.0.1 port 3128
rdr pass on em1_vlan12 proto tcp from any to !(em1_vlan12) port 80 -> 127.0.0.1 port 3128
rdr pass on em1_vlan100 proto tcp from any to !(em1_vlan100) port 80 -> 127.0.0.1 port 3128
rdr pass on em1_vlan99 proto tcp from any to !(em1_vlan99) port 80 -> 127.0.0.1 port 3128

BUT FIREWALL log shows ALL port 80 requests getting blocked.

HINTS.  Mainly wondering what would not be setup since it is supposed to create the necessary rules and I understand some rules are HIDDEN.

Ng

Sophos had this error with chrome too, they were able to patch it. https://community.sophos.com/products/unified-threat-management/f/general-discussion/91085/https-scanning-web-protection-ssl-error-err_cert_common_name_invalid

Hi,

You'll may want to check this out.

http://bugs.squid-cache.org/show_bug.cgi?id=4005

Avast and their security scan are known to produce similar crap as well.

Almost always, the answer is the regular version. Development happens in -devel that can make it unstable at times. It could also be built against a newer version of haproxy but with the same frontend/GUI code.

The only time to use -devel is if you know for certain that -devel contains a feature you require that is not present in the regular version, and you are OK with possible instability.

I found solution with WPAD at the moment.
So, lets see how its work.

Hi,
I have faced same issue too. I found nothing so I performed a clean install. The strange thing in my case was that if open ACL lists everythink looked fine with all changes I performed,despite system was not accept my changes :-\

My situation is the same
in addition
When I make a change to squid or squidguard, the computer's processor is running at 100% for about 30-40 seconds.
At this time, users can not connect to the web.
Then the use of processors falls slowly
Then it is possible to connect to the web.

hi!
I know that this is very old old post
but I have the same issue…
download started for example I was downloading a 4 mb file and randomly it says 0 b/s no error just stay there :(
if I disable squid it finished ok....

thanks
Chris

On a system with <4 gigs of storage? Yes that most certainly should be removed, plus run

rm -rf /var/db/ntopng/

after that.

I do not know if I would downplay this package heh.

Does anyone have anyidea why SSL_RECORD_TOO_LONG happens with blocked sites?

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.