Atomic ModSecurity rule set (subscription) does not work even after Plesk 12 MU#52 is installed

Created:

2016-11-16 13:05:57 UTC

Modified:

2017-08-16 15:52:07 UTC

5

Was this article helpful?


Have more questions?

Submit a request

Atomic ModSecurity rule set (subscription) does not work even after Plesk 12 MU#52 is installed

Applicable to:

  • Plesk 12.5 for Linux
  • Plesk Onyx for Linux
  • Plesk 12.0 for Linux
  • Plesk 12.5 for Windows

Symptoms

Web Application Firewall is enabled with "Atomic ModSecurity rule set (subscription)" but does not work even when MU#52 is installed.

Cause

Rule set "Atomic ModSecurity rule set (subscription)" was enabled before installing MU#52 .

Resolution

  1. Make sure the latest Plesk updates are installed:

    #/usr/local/psa/admin/sbin/autoinstaller --select-release-current --reinstall-patch --upgrade-installed-components
  2. After installing MU#52 make sure modsecurity_get_atomic_ruleset.pyc , plesk_atomic.pyc and modsecurity_get_tortix_ruleset.pyc files are removed:

    rm -f /usr/local/psa/lib/modules/python/modsecurity_get_atomic_ruleset/modsecurity_get_atomic_ruleset.pyc /usr/local/psa/lib/modules/python/pylib-modsec-atomic/plesk_atomic.pyc /usr/local/psa/lib/modules/python/modsecurity_get_tortix_ruleset/modsecurity_get_tortix_ruleset.pyc
  3. Make sure the daily update for rule set is enabled at Tools & Settings > Web Application Firewall > Settings .

  4. Run daily maintenance script with the following option:

    # plesk php /usr/local/psa/admin/plib/DailyMaintainance/script.php -f UpdateModSecurityRuleSet daily
Have more questions? Submit a request
Please sign in to leave a comment.