Start again with Squid3.  Don't waste time trying to debug a broken package.

i dont understand why I'm blocking port 80

You typically block ports 80/443 so that your users are forced to use the proxy.  If your proxy is optional, then you don't need to bother blocking 80/443.

Thanks KOM,

You were right killing the antivirus (and stopping the services) did make everything work.

I now know where to look!

Thanks for all of your help!

The problem is squid version 3.4 is not compiled with ldap search custom sguid package should work

I was able to get it running by going through every tab and hitting save.  I saw this in another thread on here.

thanks for you help!

Well, you could do what I asked the other guy to do…

Hello, no I dont use captive portal. I Think this is related to the newer FreeBSD base operating system on 2.2, that it cannot listen on low ports. I get same error in HAproxy. I have disabled WebGUI redirect.

I will try to do a forwarding rule from port 80 to a higher port i firewall rules settings

Ok thank for Help :D

I will forward to other sys-log server.

bump

Hi,

I'm also having the same problem on the 2.2.1 update.
i have also tried this: https://forum.pfsense.org/index.php?topic=73640.0

although the service is now starting it's not blocking website as per categories.

Have you found a solution yet?

New SquidGuard apparently doesn't always stay running unless there is work for it to do.  Have you actually tried testing its functionality?

MS FTP "client" plus MS FTP "server" -> unusable junk. Get something usable, like http://www.ncftp.com/download/

Ok, but my very first problem is to know if squidguard could read ip addresses lists from mysql db as it can do for users list.

After uninstalling installing round and round I finally got it working. :)

I believe there's and issue if you ad your 1st webserver then add 2 mapping's right away it wont allow any other connections to work. I had to add 1 webserver at a time and 1 mapping at a time then go back and add the second mapping.

I found an error on my rule set.

Netflix/hulu were using ports that were grouped together that went out my cable modem interface.

thnx for the information.

worked fine  :)