On 05/23/2015 08:29 PM, Chris wrote: > Hi list, > > i'm currently running fail2ban 0.8.13-1 on Debian Jessie and trying to > use it to ban failed logins on ownCloud 8.0.3. The following pastebin > contains all done configurations as well as the successful output of > fail2ban-regex and a log sample from a failed ownCloud login: > > http://pastebin.com/q1EuMgYg
Can you also provide fail2ban-client status, fail2ban-client status <JAIL> and fail2ban-client -d ? If fail2ban-regex catches the log lines and they are within `findtime`, fail2ban should both behave the same. > > Unfortunately it seems that fail2ban-server is not detecting the failed > logins from the owncloud.log when logging into the GUI with wrong > credentials (maxretry is currently set to 3 as a default). > > There are other fail2ban jails like dovecot or ssh banning failed logins > without any problems. The main difference between those jails and the > ownCloud one are the different time/date detected by fail2ban-regex: > > dovecot: > [14821] MONTH Day Hour:Minute:Second > > owncloud: > [725] ISO 8601 As reported by fail2ban-regex, the ISO 8601 format is supported and identified properly. > > I'm currently completely stuck how to debug this further to see why > fail2ban-regex is successfully where fail2ban-server is failing. > > Thanks in advance for a reply / hints. > ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Fail2ban-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fail2ban-users
