• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Fail2Ban logging

ulitre

New Pleskian
I am running Fail2Ban on several CentOS 6 containers with several active jails (apache-noscripts, plesk-apache etc.). The Fail2Ban.log provides the IP address which was banned; however, what I would like to see is which subscription the offender hit so that I can quickly open that specific subscription’s error_log and determine the activity associated with the banned IP address prior to the ban action. Is this possible (as it is not feasible to open 75+ error logs searching for a Banned IP address each time I would like to investigate further)?

Error logs for each subscription are being checked, so it seems there should be a way to have this information displayed in the fail2ban.log or elsewhere.
fail2ban.filter [1170]: INFO Added logfile = /var/www/vhosts/system/example.com/logs/error_log

I have been looking for an answer to this for sometime. Any help is appreciated.
 
I am running Fail2Ban on CentOS 6.6 with several jails (apache-noscripts, plesk-apache etc.). The Fail2Ban checks the access and error logs for each subscription and successfully reports the IP Addresses which are being banned.

Is there a way to force reporting of the subscription being attacked by each offending IP address? I would like to be able to quickly identify which subscription was attacked by a specific IP to enable me to investigate that subscription's log files. Without this information I am forced to search individual subscription logs hoping to find the right log which is not feasible.
 
Back
Top