Article ID: 126028, created on Jun 25, 2015, last review on Mar 14, 2016

  • Applies to:
  • Plesk 12.0 for Linux


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


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


  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

Search Words

"Atomic ModSecurity rule set (subscription)" does not work after Plesk 12.0.18 update 52

Atomic ModSecurity rule was enabled during installation of MU52.

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

29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7

Email subscription for changes to this article
Save as PDF