• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

ModSecurity subscription rule set error;

elcopdoo

Basic Pleskian
Error when trying to set atomic subscription rule:

Failed to install the ModSecurity rule set: SecReadStateLimit is depricated, use SecConnReadStateLimit instead.
Syntax error on line 70 of /etc/httpd/conf/modsecurity.d/rules/atomic/modsec/00_asl_zz_strict.conf:
Error creating rule: Could not add entry "127.0.0.0/8" from: 127.0.0.0/8.

In directory /etc/httpd/conf/modsecurity.d/rules I have only:
atomic.new modsecurity_crs-plesk tortix tortix.backup

There is no file 00_asl_zz_strict.conf
 
What is the output of following command ?

Code:
ls -ld /etc/httpd/conf/modsecurity.d/rules/atomic/modsec/00_asl_zz_strict.conf
 
ls: cannot access /etc/httpd/conf/modsecurity.d/rules/atomic/modsec/00_asl_zz_strict.conf: No such file or directory
 
I found out that modsec/00_asl_zz_strict.conf is in atomic.new directory.

How can I update this in ModSecurity ?
 
Have you tried to copy /etc/httpd/conf/modsecurity.d/rules/atomic.new directory to /etc/httpd/conf/modsecurity.d/rules/atomic ?
 
Hello. A few words about how rule set update works.
Plesk tries to download, install new rule set and check apache configuration with it. If config check fails the plesk restores previous version of rule set and save new one in a directory with suffix ".new".
As a result, apache configuration wouldn't be broken and if you wish you may replace atomic dir with atomic.new, fix errors and restart apache.

And about the error. Looks like you faced the bug: https://github.com/SpiderLabs/ModSecurity/issues/706
We will propose update for modsecurity with fix of this bug with next plesk microupdate (in about a week).
 
Fixed mod_security packages for BR#706 are available in ASL and the Atomic repos. We also passed the patch up on to Parallels for addition to their package last week.
 
Hello,

i get this error when i try the TestLic package
i put the username and pw into the fields.
Press OK

Then ...

Failed to install the ModSecurity rule set: SecReadStateLimit is depricated, use SecConnReadStateLimit instead. Syntax error on line 40 of /etc/apache2/modsecurity.d/rules/atomic/modsec/01_asl_domain_blocks.conf: Error creating rule: Could not open phrase file "/etc/asl/custom-domain-blocks": No such file or directory

i look in the folder and yes ... the custom-domain-blocks folder doesn't exists

any idea ?
 
Back
Top