If you put Squid 'in-line' with two interfaces then all the redirects would happen there and not at the main firewall.
You don't have to do that though, it's easier to just redirect traffic to the proxy from the firewall as I outlined. In that case whatever is running Squid is only a proxy server, it only needs one interface.

Steve

You can do that using Squid and Squidguard as you say. First up watch the hangout we did on this:
https://youtu.be/xm_wEezrWf4

Steve

@doktornotor
Well the least stated he obvious but was cause of problem. Squidguard.conf was pointing to nonexistent directory, ...log. when installation used ....logs. I think they were just so close I couldn't see the difference for the words.

@netn00b not sure if you found a good solution to this.
I do something similar with a script to update the IP's for my VPN in squid.conf

I've stripped my VPN config lines out into a seperate file (vpn.conf) and then replaced them with an include

include /usr/local/etc/squid/vpn.conf

This way the GUI is always correct and can be updated as normal and you can still keep your IP's current.

in Squid/real time
i found
TAG_NONE/200 102.132.97.27:443
when HTTPS/SSL Interception Enable SSL filtering.

Also the dns name for mydomain.ry works but hits the same page as above. when I add a prefix onto it I continue to get:

This site can’t be reached mail.mydomain.ry’s server IP address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN

@PiBa Thanks! I first placed it in the frontend, but then all my backend servers went to /webmail. I put it in actions in the backend server for my mailserver and it works like a charm!

@KOM thank you!

@akuma1x @stephenw10 only change the range of the ips ! :o thanks !

I don't know. I don't use pfB.

@KOM It was set to "uk" so I changed to "en", saved and restarted service which has fixed the issue. TA

@KOM thanks

There must be something in one of the logs:

Status - System Logs - System - General

Services - Squid Proxy Server - Realtime

Try increasing the squid debug log level by adding this to the Advanced Options - INtegrations section for squid:

Increase the value after ALL, to get more and more detailed logging.

http://www.squid-cache.org/Doc/config/debug_options/

http://etutorials.org/Server+Administration/Squid.+The+definitive+guide/Chapter+16.+Debugging+and+Troubleshooting/16.2+Debugging+via+cache.log/

TLS 1.3 will require OpenSSL 1.1.x, which is only currently available on pfSense 2.5.0 development snapshots. Though it does look like net/haproxy-devel is at 2.0-dev2 on the branch used for pfSense 2.5.0 development, but the pfSense haproxy-devel package doesn't use it (yet).

I'm not aware of any plans to switch that over yet, but it's probably just a matter of time.

@sichent This link shows what to do in CentOS or Ubuntu and clearly states (on discussion) that it is not for pfSense.