Follow

tara shinn

February 01, 2018 18:29
Updated

This means that you do not have the correct permissions setup for modsecurity to work correctly. Please make sure you have followed all the setup and installation instructions in the Atomic ModSecurity Rules wiki article. Specific guidance is provided in this section of the Setting Up Modsecurity guide:

https://www.atomicorp.com/wiki/index.php/Atomic_ModSecurity_Rules#Step_3:_Set_permissions_for_directories

Comments

0 comments

Please sign in to leave a comment.

ModSecurity: Multipart parsing error
Request body no files data length is larger than the configured limit
Request body (Content-Length) is larger than the configured limit
ModSecurity: SecRemoteRules: ModSecurity was not compiled with SecRemoteRules support.
Reporting False Positives when not running ASL
Failed deleting collection
module security2_module is already loaded, skipping
Syntax error on line 1 of /etc/httpd/conf.d/security2.conf: Cannot load /etc/httpd/modules/mod_security2.so into server: /etc/httpd/modules/mod_security2.so: cannot open shared object file: No such file or directory
module unique_id_module is already loaded, skipping
Installing custom modsecurity rules

Related articles

Articles in this section