Inspecting the blocked content it all seems local to me, can't see any other domain names in it than just the domain name the site is running.

Awesome. I can confirm that the lightsquid_web is now running after the update.

I would move webgui to a non-standard port like 1443 or something, and disable the webgui-redirect.. Then at least you wont unintentionally end up on the webgui when trying to visit the wan-ip.

Content filtering == you can see the real content. Terminology mixup I guess. You cannot filter the content you do not see. http://wiki.squid-cache.org/Features/SslPeekAndSplice

Sorry, there is no support for packages on pfSense on 2.2.x. Also, the Squid version plus related packages there are extremely outdated and not really offering any of the recent features.

Well, at least things work now. (I certainly won't be able to debug any SIGSEGV issues there, my experience is that it was a HW issue ~95% of time. If not RAM, then CPU overheating, or bad PSU with unstable voltage.) If it's a bug with Squid, you'd need to move this to Squid mailing list or generally upstream, nothing pfSene specific there.

ok finaly I had to remove my domain name in the apache virtual host tag, replacing it by *.80 dont know why it was there in the tutorial

@meruem: ya you need the first forward slash "/", otherwise your saying /root/etc , you want /etc/ This last post in quote here is to my problem, all  posts from doktornotor and myself have been removed related to my error, I had a typo user error

https://forum.pfsense.org/index.php?topic=124814.0

@doktornotor: pfSense is not a proxy appliance. Note that "disabling" IPv6 on pfSense will do nothing for the clients that get IPv6 RAs etc. from your real router and so will resolve IPv6 first. This is not a pfSense issue or Squid issue, at all. of course. i've resolve the problem adding a second network interface. So the lan is in my lan segment, and the was is in external network. now works everything (a bit slow, i'm working on it). it was a network problem definitely. Thanks to all!

Problem is with Snort, not with squid or squidguard. Try add pass list with alias (-es) in Snort. I installed clear Pfsense only with Snort and had the same errors like then, when I installed squid and SG.

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

Well…. Default Access should be set to ALLOW and not Deny, otherwise, of course, everything will be blocked...

This is a Squid/pfSense forum. If you need help with nginx, this is not the place.

I had some limited sucess with chaning the output but it seems that the function is used for other things aside from logging entries from captive portal. I had a look in the logs and noticed that the username is in them. I had a quick search for the LightSquid docs. I actually found it a little hard to follow this guide but it has sorted the issue! ??? http://webcache.googleusercontent.com/search?q=cache:oC3IJyFON78J:lightsquid.sourceforge.net/How%2520It%2520Work.html+&cd=1&hl=en&ct=clnk&gl=uk

update to 0.4.34 will fix that problem. This thread covered the issue: https://forum.pfsense.org/index.php?topic=124218.0 Enjoy!!!

It's working after updated to 0.4.34. Thank you all. :)