Squid3 and Squid Guard Issues
-
Reinstall squid3 after squidguard install. Squidguard package to pfsense is compiled to depend on squid2.
After getting squid3 running with squidguard, check dnsv4first dns option on gui to prevent some https issues.
-
I had tried that before and it didn't quite take.
What I've ended up doing is do what you said, install everything, then I removed squid and then I went in via the CLI and removed and squid remnants(like the binary in /usr/local/sbin/squid still existed even after the uninstall). Once I purged everything out then I installed squid3 again and it seems to take.
Even with this work around it would seem to be a glitch the packaging system for SquidGuard. It would be nice if there was a way to do it the correct way versus this workaround way.
-
Hi,
Having the same problems as described above, and have tried uninstalling both packages and the installing squidguard first and afterwards squid3….
Now I'm at a point where the squid3 service will start Again (which it wouldn't before) but the squidguard package won't. System is running 2.02-RELEASE
Any suggestions?
Regards,
Anders -
Ok, so got a Little further… Removed and installed both packages on both CARP nodes, which seems to have fixed something...
Have 2 issues left now:
-
When attempting to enable XMLRPC sync this error is thrown: Warning: Invalid argument supplied for foreach() in /usr/local/www/pkg_edit.php on line 423
-
When trying to open til Blacklist pane (Services\Proxy filter\Blacklist) I get this error; Parse error: syntax error, unexpected $end in /usr/local/www/squidGuard/squidguard_blacklist.php on line 102
Any ideas?
//Anders
-
-
-
-
-
Try 1-2 hours later, while github applyed the last comit.
Have completely removed both packages, and will install them again tomorrow… I'll get back with how it goes...
-
I have been looking at these 2 packages recently too…
To cut a very long story short, as marcelloc says:
Reinstall squid3 after squidguard install. Squidguard package to pfsense is compiled to depend on squid2.
After getting squid3 running with squidguard, check dnsv4first dns option on gui to prevent some https issues.
What doesn't help, is that the pfSense wiki says to do it the "wrong" way around:
http://doc.pfsense.org/index.php/SquidGuard_package::)
Anyway, now that I've found this thread (and a couple others where marcelloc says the same thing), it's all working for me (at last!)
-
Have you tried upgrading to PfSense 2.1 Beta?
I get a couple errors in the log but Squid 3.1 Beta and SquidGuard load and work well.
-
I have been looking at these 2 packages recently too…
To cut a very long story short, as marcelloc says:
Reinstall squid3 after squidguard install. Squidguard package to pfsense is compiled to depend on squid2.
After getting squid3 running with squidguard, check dnsv4first dns option on gui to prevent some https issues.
What doesn't help, is that the pfSense wiki says to do it the "wrong" way around:
http://doc.pfsense.org/index.php/SquidGuard_package::)
Anyway, now that I've found this thread (and a couple others where marcelloc says the same thing), it's all working for me (at last!)
It is not the wrong way around - it depends on the version of squid and the version of pfsense.
I updated the wiki so hopefully this will help others in the future.
