next »

[ic3000]

Hi to all,

Today and i really don't know why my ebox 1.2 gateway just freezed and i had to hard reboot the server.

After the reboot everything seems to be working just fine but after, i found that squid cache is not letting me use google.com and gmail presenting the users a page saying that there are some problems with squid cache blocking the dns google.com and mail.google.com.

I think that this could be resolved just by cleaning the squid cache... but i really don't know how to do it...

On ebox interface theres no option to clear the cache but it should be possible to clean on the command line...

Anyone knows how to clean the squid cache or anyone ever had  a problem like mine with ebox 1.2?

Thanks in advance!

[Javier Amor Garcia]

Is a "Denied access" page, i nthis case it may be that you are using a "Deny all" policy either as default police or in a network object.

If this is not the case, can you post here the error your uses are getting?

[ic3000]

Hi Javier,

Thanks for your reply on this.

Its not an Access Deny page is a page from squid-cache saying that it cant resolve the DNS for google.com. It can be found on file:///usr/share/squid/errors/English/ERR_DNS_FAIL

It says something like this:

Code:

The requested URL could not be retrieved

While trying to retrieve the URL: %U

The following error was encountered:

    Unable to determine IP address from host name for %H

The dnsserver returned:

    %z

This means that:

 The cache was not able to resolve the hostname presented in the URL.
 Check if the address is correct.

Your cache administrator is %w.

When i disable http-Proxy the clients can resolve that domain with no problems. This only happens when http-proxy is enabled.

Its a default setup with transparency, filtering and permissive.

It was working just fine before, this just started from a moment to another...

I know that my users mainly use this domain because its used for gmail and maybe 60% of web traffic passing on ebox gateway is from this domain.

I found a workaround, this domain is not a big problem, but im afraid that can also be happening for other domains...

The workaround was putting the domain google.com on the exceptions list on http-proxy.

This works but i really cant find a reason for this to happen on google.com and not other domains that i tried...

Thanks once again!

[rodrigo.rosa]

I'm having the same problem.

Can anyone help me on this matter?

[kmnair]

We had the same problem. We solved it by entering such domains in the exempt from caching list.

kmnair