Did you use the config from this page?
http://wiki.sogo.nu/nginxSettings
Make sure you have both "X-Real-IP" and "X-Forwarded-For" headers.
Like these:
# set headers
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forward-For $proxy_add_x_forwarded_for;
# Optional:
# Let the web service know that we're using HTTPS, otherwise
# it will generate URL using http:// and not https://
# proxy_set_header X-Forwarded-Proto https;
On 2/22/2015 12:43 PM, Infoomatic wrote:
hi,
I wanted to use nginx with sogo and apply the fail2ban rules. Basically,
everything is working fine with nginx, but:
with the suggested nginx config (including "proxy_set_header X-Real-IP
$remote_addr;" from the sogo wiki) and nginx version 1.6.2, the
logfile only creates entries like:
SOGoRootPage Login from '127.0.0.1' for user 'afd' might not have worked -
password policy: 65535 grace: -1 expire: -1 bound: 0
The same host, with the suggested apache2 configuration gives me:
SOGoRootPage Login from 'XXX.XX.XX.XXX' for user 'aasd' might not have worked -
password policy: 65535 grace: -1 expire: -1 bound: 0
with my real IP and thus fail2ban working.
Is there a workaround or some variables to change in source and recompile to
have this working? Or better: a configuration option I did not see?
regards,
infoomatic
--
[email protected]
https://inverse.ca/sogo/lists
