[SOLVED] zimbraHttpThrottleSafeIPs and proxy

[weblike]

Code: Select all

[zimbra@mail log]$ zmprov gs `zmhostname` zimbraHttpThrottleSafeIPs
# name mail.mydomain.com
zimbraHttpThrottleSafeIPs: 192.168.2.1
zimbraHttpThrottleSafeIPs: 10.4.1.150

Only these 2 internal ip's are shown

[L. Mark Stone]

OK, so suggest you run:

Code: Select all

zmprov ms `zmhostname` -zimbraHttpThrottleSafeIPs 192.168.2.1
zmprov ms `zmhostname` -zimbraHttpThrottleSafeIPs 10.4.1.150
zmprov ms `zmhostname` +zimbraHttpThrottleSafeIPs 10.7.1.0/24
zmprov ms `zmhostname` +zimbraHttpThrottleSafeIPs 10.4.1.0/24
zmprov ms `zmhostname` +zimbraHttpThrottleSafeIPs 244.222.5.5/32
zmprov ms `zmhostname` +zimbraHttpThrottleSafeIPs 244.222.5.6/32
zmprov ms `zmhostname` +zimbraHttpThrottleSafeIPs 192.168.2.1/32
zmprov ms `zmhostname` +zimbraHttpThrottleSafeIPs 244.222.31.94/32
zmprov ms `zmhostname` +zimbraHttpThrottleSafeIPs 10.5.1.0/24
zmprov ms `zmhostname` +zimbraHttpThrottleSafeIPs 127.0.0.1/32
zmcontrol restart

Hope that helps,
Mark

[weblike]

Hi,
Thank you for suggestion.
1.I have added these lines, restarted with "zmcontrol restart"
2. For one day all seemed fine, but another day users called back complaining about they get "An unknown error has occurred"
Searching the log with

Code: Select all

[zimbra@mail log]$  cat mailbox.log | grep -i "DoSFilter: Configured whitelist IPs"

The result is empty.

Restarting manually the zmcontrol ...again it's showing the declared IP's.

Why these problem occurs?

[L. Mark Stone]

The "configured whitelist IPs" I find doesn't always appear in the log. I wouldn't worry about that.

If your user/s is/are getting blocked, you need to get their oip from mailbox.log and see if it's in the whitelist or not.

The output of zmprov gs `zmhostname` zimbraHttpThrottleSafeIPs will give you the accurate list of whitelisted IP addresses/networks.

Hope that helps,
Mark

[weblike]

I have made several test with different users and this happens:


1. First login gives: "An unknown error has occurred".
2. Without closing the browser, re-entering user and password, 2nd login is successful.


The logins are made from a trusted IP.
Cheers