Problems with squid3 + SquidGuard using SSL Interception

[Itg]

Friends, what is the idea of ​​enabling SSL / HTTPS Interception in squid3? When I did, I would give the SquidGuard the possibiliade making sites locks on port 443, because until then the SquidGuard bloqueiava sites only on port 80, forcing us to use firewall rules to block social media and other sites that use https, with Alias ​​containing all networks to be blocked.

Correct reasoning?

But the fact is that it is very difficult to make the SquidGuard work well with squid3 using SSL Interception, a number of minor problems appear and we have to make fine adjustments.

At this point I can not normally access the sites that use https, it informed the certificate error, have created the certificate in the CA pfSense and imported at stations, properly following all the tutorials, but the problem persists and if I click add exception and continue on the site comes another error "Unable to determine IP".

See the attached pictures and ask how to solve these problems?

Thanks !


[Itg]

I convinced myself that the best thing to do is not break the head with SquidGuard using squid3 SSL Interception, I will use the NXFilter in pfSense own, much more interesting, efficient and with various features.

What do you think ?

[Itg]

At last I decided, thank God :)
Simple, on the General tab in the Squid Proxy, the Remote Cert Checks field, leave marked the two options in this way disappear the problems with some websites loading slowly, sites that do not load all images or give DNS Resolver error.

And Intercept SSL works perfectly with SquidGuard barring access to sites that use https, like Facebook.

Thanks!

[jhonecl]

Tks.. this is the solution..  :D :D :D

[fabshdz]

and how is  the 2.3.2 release ??

I have the same problem =\