I posted a similar problem here: https://forum.pfsense.org/index.php?topic=132939.0 My problem had nothing to do with rules, but everything to do with certificates and Windows browsers detecting the Squid SSL filter!

@doktornotor: Great. Now, did you configure anything on the clients? Because, with the proxy NOT being transparent, I cannot figure out how on earth you imagine the clients to be forced to use it?!?!  (And, BTW, if going through Squid is required, you'll need to block all IPv6.) I know this is already an old post, but can I ask for your assistance, how do we block all IPv6? TIA! ast

I'm also new to pfsense, I believe you can do this via firewall rules and schedules.

The problem I Have is different. Most of the websites work just fine. But some don't. especially Google websites and subdomains. and another strange thing: when I search something in the browser without going to google.com (but using Google as default search engine) it never works with this setup.

That's not what I asked.

Uncheck it???

Sorry i read my reply again, and of-course the proposed change should have read "http-check expect status 403" so it sees that code as valid.. Anyhow if your willing to dig further into the problem, lemme know, ill try and help.

Unrestrict users bypass authentication, squid has integration with captive portal. So, it's possible. take a look on resulting config and create your own acls to complete your configuration.

So it is not possible for the captive portal and squid in non-transparent mode to work together?

Having it like: messages.mydomain.com to point to 192.168.1.1 clients.mydomain.com to point to 192.168.1.152 Should probably work nicely.. As for the frontends make sure to make them 'shared' as the webgui calls it. Or use just use one frontend it the gui, and use the acl+action to select the second backend for the second domain.

I find it useful, I get blocks every so often especially from the game sites my son browses to. It may not be the BEST a/v solution, but it is useful…

I am not using SSL intercepting / filtering at this time.  I wanted to get a better sense of the software before diving into that.

in case anyone else has trouble there is two ways to do this.  the first is from the front end the alternative is globally.  1.  front end - edit - advanced settings - advanced pass thru 2.  settings - Global Advanced pass through - custom options I also have a rule in my global advanced pass through settings to explicitly deny SSL 3.0 and TLS1.0. ssl-default-bind-options no-sslv3 no-tlsv10 even with that I was not getting good results when I would scan my subdomains using https://www.ssllabs.com/ssltest.  it noted many deprecated ciphers were in use.  I found some posts by others who were doing something close to what i wanted to do. Ex: http://wolfspyre.com/?p=207 This was close but I still found that I was having trouble with the 3DES cipher on TLS 1.1 and 1.2. https://www.ssllabs.com/ssltest, directed me to use the cipher list that mozilla outlined (https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_configurations).  Because all of my remote devices are newer i opted to use the Modern cipher assortment.  I added a lin underneath my default bind options eliminating support for SSL 3.0 and TLS1.0.  it is the following: ssl-default-bind-ciphers ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256 Currently, these ciphers seem to rule out TLS 1.0 and force TLS1.2 only.  This could be a problem for older browsers and smart devices.  SSLLabs' ssltest does a pretty good job of enumerating which systems are likely to have trouble.  I have confirmed that all my devices work without issue given my configuration.

@vielfede: @Pontiac_CZ: vielfede: I have read that thread but I am still sorf of confused. What was the key setting for getting the squid to work in transparent mode? Sorry, my mistake! I missed to clear proxy settings in client pc, hence I was suposed to use transparent mode. Indeed it does not! Or better: splice all + transparent mode: http works, https sometimes works and sometimes it does not, no idea about the causes splice all + NON transparent mode works (flawlessly) http+https (you have to set proxy client settings) Vielfede, What about the "block page" while using HTTPS/Non-Transparent mode? Is it showing your "block page" normally? do you have your pfsense web-console using Https as well? Thanks! fabricio.

It seems the old known problem ( http://https* ) is still present on version 2.3.4 Also, for some reason, when using HTTPS for pfsense console, Squidguard is not redirecting the error page for Https, but http. Still investigatin it here…