• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Issue In Plesk GUI we need combined apache log option for all sites.

Hi,
Fail2ban performance and server load if all vhost logs are scanned using wildcard on log files. This is also warned.
No we manually add sites to Fail2ban log settings.
In General Settings -> Apache Web Server Settings would be nice have a such an option.
One combined access log for all sites ssl or non ssl.
This would even ban IP's faster on those that try on multiple sites same time.
 
You could enable "piped logs" in Tools & Settings => Apache Web Server Settings.
This will create a combined log file for all domains in /var/log/httpd (or /var/log/apache2) which you can use with Fail2ban
 
I don't know why Plesk is still using different logfiles for http and https for websites - as well as different webstats (AWStats/Webalizer) for that matter...

As for fail2ban and the "to many logfiles", go with Monty and enable piped logs for Apache2
 
Back
Top