• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Mod_security Bug

Josh12

Basic Pleskian
When trying to install atomic's subscription rules this error shows.

Code:
Failed to install the ModSecurity rule set: SecReadStateLimit is depricated, use SecConnReadStateLimit instead. AH00526: 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

Here is a quote from atomic's website that seems to be related
Definitely report this as a bug to Parallels, they arent installing the rules correctly. You're getting those that error because Plesk is incorrectly installing this rule file:

/etc/apache2/modsecurity.d/rules/atomic/modsec/01_asl_domain_blocks.conf

And not this one:

/etc/asl/custom-domain-blocks

As documented here:

https://www.atomicorp.com/wiki/index.ph ... locks.conf

So, if you just touch that file, this error will go away:

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

This is happening because theres some kind of bug in Plesk that causes it to bypass our rule installer altogether. So definitely report this as a bug to them as unfortunately Plesk itself is causing your broken configuration and maybe they have a fix for this.

Are we going to see a fix for this in the near future?
 
Back
Top