• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

fail2ban empty logs

Azurel

Silver Pleskian
In the fail2ban module of plesk is a tab for "logs".
Here you can view Fail2ban logs.
No items found.

I have banned IPs, but no logs? I missed totaly a timestamp for the banned ip. How I can found out the time for the ban per IP?
 
Thanks. My fail2ban (plesk module) config is:

logtarget = SYSLOG

so I must change it to?

logtarget = /var/log/fail2ban.log
 
I have change it and restart fail2ban and get a warning:

# service fail2ban restart
Stopping fail2ban: [ OK ]
Starting fail2ban: WARNING 'ignoreregex' not defined in 'Definition'. Using default one: '' [ OK ]
 
Thank you! :)

As backup....
To start... " Starting fail2ban: WARNING 'ignoreregex' not defined in 'Definition'. Using default one: '' " is really nothing you should worry about, because Fail2ban is clever enough to use the global "ignoreregex" ( which is none )... Please have a closer look on how jails and filters are defined, to understand the warning. For example, the filter "plesk-courierlogin.conf" has an absolut correct filter - definition:
 
Back
Top