• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved about modsecurity in fail2ban log

yaswaka

New Pleskian
After updating Plesk 18.0.35, I got a strange message about ModSecurity in the fail2ban log.
However, it is not for all ModSecurity logs.
Unfortunately,updating Plesk18.0.35 #Update1 dose not change.
Is there any solution to this problem?

********For example*****
2021-05-09 12:22:55,456 fail2ban.filter [6505]: WARNING [plesk-modsecurity] Simulate NOW in operation since found time has too large deviation None ~ 1620530575.46 +/- 60
2021-05-09 12:22:55,525 fail2ban.filter [6505]: WARNING [plesk-modsecurity] Please check jail has possibly a timezone issue. Line with odd timestamp: --f5c3ee3c-A--
2021-05-09 12:22:55,539 fail2ban.filter [6505]: INFO [plesk-modsecurity] Found 50.***.***.*** - 2021-05-09 12:22:55
2021-05-09 12:22:55,544 fail2ban.filter [6505]: WARNING [plesk-modsecurity] Found a match but no valid date/time found for u'09/May/2021:12:22:55 +0900'.
2021-05-09 12:22:55,544 fail2ban.filter [6505]: WARNING [plesk-modsecurity] Match without a timestamp: 09/May/2021:12:22:55 +0900X-Real-IP: 50.200.232.37
2021-05-09 12:22:55,545 fail2ban.filter [6505]: WARNING [plesk-modsecurity] Please try setting a custom date pattern (see man page jail.conf(5)).
***********************
 
Back
Top