Replies: 1 comment
-
Use case: Firefox on Android phone tries to login on Roundcube using existing user with wrong password.Pay attention that Roundcube received (and knows) X-Real-IP and X-Forwarded-For. So, some configuration must be done at Roundcube and DMS to use that information, X-Real-IP and/or X-Forwarded-For. At Roundcube config level, maybe one or more of this parameters must be adjusted:
Complete config file at https://github.com/roundcube/roundcubemail/blob/master/config/defaults.inc.php At DMS config level, for sure something on Dovecot, like: https://doc.dovecot.org/configuration_manual/forwarding_parameters/ and https://doc.dovecot.org/settings/core/#core_setting-login_trusted_networks Below, pertinent parts of Caddy, DMS and Roundcube logs. Caddy
DMS
Roundcube
|
Beta Was this translation helpful? Give feedback.
-
DMS/Roundcube/Caddy - fail2ban blocks docker gateway
Complex "puzzle", I suspect that needs configuration at DMS and Roundcube containers.
Caddy container appears to be doing his part: delivering X-Real-IP and X-Forwarded-For to Roundcube.
Problem occurs when someone tries to login on Roundcube... Three failed attempts and fail2ban on Docker Mailserver blocks docker gateway, 172.18.0.1; then, nobody can login on Roundcube until ban expires. Would like to pin/understand right configuration and not circunvent/disable fail2ban.
After two days of intense research, I suspect that solution may envolve:
Tried so many things that I got lost at the problem...
Caddyfile block relative to Roundcube:
Any ideas/suggestions are welcome.
One year ago I tried to solve this problem but despite some help/ideas I could not discover how to do it.
https://github.com/orgs/docker-mailserver/discussions/2603
Instead of "ressurrect" that old discussion I thought it would be better start a new topic.
Beta Was this translation helpful? Give feedback.
All reactions