It may happen that Squid with QuintoLabs Content Security does not seem to block ads as expected. Should we blame the developers right away? Not always. Here are the possible reasons why it might happen:
- Check we are using Squid as the proxy set in the browser. Pretty obvious but you never know 🙂
- Check that Squid is set up correctly to forward HTTP requests/responses to the ICAP server. This is typically set up as
- Check that Content Security (
qlproxyd) daemon is started by
ps aux | grep qlproxyd
- Check that
qlproxydlistens on ICAP port
netstat -a -p | grep 1344or
netstat -a -p | grep icap
- Check the
/var/opt/quintolabs/qlproxy/logs/error.logfor possible errors and warnings
- Check if the log file
/var/opt/quintolabs/qlproxy/logs/access.logcontains at least some entries.
- Check that ad blocking module is enabled in
/opt/quintolabs/qlproxy/etc/qlproxyd.conf… there should be
adblockenabled = yes.
- Check the subscription database file at
/opt/quintolabs/qlproxy/etc/adblock.confand actual subscriptions at
If everything is running properly try to reset the browser cache and if still nothing works – kick those responsible at firstname.lastname@example.org.
We’ll be happy to help you!