• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue ModSecurity Atomicorp not logging to modsec_audit.log

Jonathan B

New Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
Plesk Obsidian 18.0.70. #2
Hi guys, i have Plesk installed on AlmaLinux 8.10 (Cerulean Leopard) with Plesk Obsidian 18.0.70.

For some days now, ModSecurity (Atomicorp) has not been logging events for some domains to the modsec_audit.log file.
However, the WAF is working correctly, as its actions are clearly shown in the error_log files of the individual websites.

Is anyone else experiencing this problem?
 
Thank you but no, it is active.
In the website's error logs, ModSecurity logs with 403 errors returned to the client are present.

For example: ModSecurity: [file "/etc/httpd/conf/modsecurity.d/rules/tortix/modsec/20_asl_useragents.conf"] [line "187"] [id "332039"] [rev "4"] [msg "Atomicorp.com WAF Rules: Suspicious Unusual User Agent (python-requests). Disable this rule if you use python-requests/. "] [severity "CRITICAL"] Access denied with code 403 (phase 2). Pattern match "python-requests/" at REQUEST_HEADERS:user-agent. [hostname "www.xxx.it"] [uri "/"] [unique_id "aGywK5m3yJdd8tXr1OmVmAAAAII"]

The issue is only present in the main log (modsec_audit.log), which remains empty.

A few days ago there was an update error of the modsecurity rules update, then since it disappeared, this problem started.
 
Thank you for the confirmation. Could you please try executing the following commands:

/usr/local/psa/admin/bin/modsecurity_ctl -d
/usr/local/psa/admin/bin/modsecurity_ctl -e

This action should recrate the ModSecurity configuration and, hopefully, sort the entry logging issue.
 
Thank you very much, but this operation didn't solve the problem. I still see the error log, but not the detailed logs in modsec_audit.log.

By any chance, do you know which configuration file contains the directives for writing to the modsec_audit.log file?
 
Thank you very much, but searching for SecAuditLog also led to nothing, everything looks okay, and there are no directives with "off".
For now, I will keep the system as it is since the WAF is working correctly, and I hope a future update will resolve it automatically.
 
Back
Top