Hi! My nginx configuration (which proxies to an Apache inside a Docker container) also sets `X-Forwarded-For`:
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
I didn't test what happens if you directly interface SOGo with nginx,
though.
Regards from Lake Constance, Germany,
Jens
On 22.02.2015 18:43, 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
>
--
Jens Erat
[phone]: tel:+49-151-56961126
[mail]: mailto:[email protected]
[jabber]: xmpp:[email protected]
[web]: http://www.jenserat.de
OpenPGP: 0D69 E11F 12BD BA07 7B37 26AB 4E1F 799A A4FF 2279
smime.p7s
Description: S/MIME Cryptographic Signature
