Chrome has a Certificate Pinninng feature. This feature takes the Google certs and checks their finger prints against the good known.
AFAIK this is an issue with all HTTPS proxies from at least BlueCoat, Cisco, SonicWall and Checkpoint. The suggested solution is to bypass SSL filtering those sites. Depending on your organizational policy, you may block them all together. Regards, Yaroslav On Nov 2, 2017 11:00 AM, "Roberto Carna" <robertocarn...@gmail.com> wrote: > People, I have pfSEnse 2.4 with Squid and Squidguard. > > I enable HTTP transparent proxy and SSL filtering with Splice All. > > From our Android cell phones, if we use Firefox TO NAVIGATE everything > is OK, but if we use Chrome we can't go to Google and some other HTTPS > sites. > > We reviewed firewall rules, NAT and denied target categories and > everything seems OK. > > What can be the problem with Chrome ??? > > Thanks a lot, > > ROBERTO > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
