• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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