Check the firewall logs, check the state table, see if the traffic is getting through on the correct port(s) or being blocked.

The squid cache is going to cause more writes than anything in /var or /tmp would, so it's a wash if you put the cache on your SSD. If you are worried about writes, get a higher quality SSD.

Thank you, I did that and it all works great now!

Same problem happened to me.

Although I blocked ALL traffic to specific IPs at firewall rules, squid proxy (I am using transparent) let pass the port 80 traffic.

So I entered the IPs (or alias) separated by semi-colons to "Bypass Proxy for These Destination IPs" and it worked.

It is an old topic but if anyone have similar problem, this is a way to fix it.

Cheers

PS: Makesure your alias is typed exactly (if there is capital letters, type as it is). If you do not follow correct capitals when entering the alias, the proxy stops working.

That wasn't quite it either, one of the servers in the pool wasn't keeping up to date. It'll be fixed momentarily.

I Just reinstalled it and it´s ok now.

Try changing the redirect mode from int page to ext URL error page and then supply the full URL with IP address.

No idea then, sorry.

Hi there,

I found it…..... hopefully it will helpful to you in case if  you are stuck.

In squid guard you cannot put the IP address and username in the custom created Group ACL, it will only pick the username.

So I have created a same ACL twice , one with the client source as username, and other with the client source as IP only.

Regards,

Deepak

Yeah I just felt uneasy seeing that. I believe nothing has to have +x except for those that need to be executed. Everything else should be only readable for those that need to read it.

@nib01:

Am I missing something here?

I don't think so, except perhaps to explain what is then the behaviour from client perspective.
Any error message, time-out?

SquidGuard is not a service.  It's a helper app that gets called per URL by squid.

If you're having problems with squidGuard, enable logging and then check the logs.

I made a test, and only worked on internet explorer… i dont know why firefox not apply blacklist, maybe some function not standard , someone know why this happening ???