paint said:Also once you do that, you need to make a slight change.
go to the $dbpassword= line and get your password. Then,
and make sure that the password for $dbpassword=" matches. If not, change it and save the file. Then it should show up fine for you.
/etc/cron.hourly/modsecparse.pl: DBI connect('modsec:localhost','modsec',...) failed: Access denied for user 'modsec'@'localhost' (using password: YES) at /etc/cron.hourly/modsecparse.pl line 19 Unable to connect to mysql database at /etc/cron.hourly/modsecparse.pl line 19.
SecAuditEngine RelevantOnly SecAuditLog logs/audit_log
For anyone reading this post - the same thing happened to me. Upgraded to Apache 2.2, and mod security was producing a blank screen.Following an upgrade to MySQL 5, I also have the same problem. I have checked the passwords match per the above and all is OK. I have looked at the template for modsec and find it contains
SecFilterForceByteRange 0 255
SecFilterSelective REMOTE_ADDR "^127.0.0.1$" nolog,allow
However, this material is NOT in the usr/local/apache/confhttp.conf file
One possible way to proceed would be to use whm/plugins/Mod Security and turn it off then on again. However, that choice produces only a blank screen
What has to be done?
|Thread starter||Similar threads||Forum||Replies||Date|
|V||Centos 8 - mod_security v3 not working custom rules||Security||7|
|Godaddy shared hosting get blocked out (probably by mod_security) when using some scripts.||Security||9|
|D||Mod_security fail after provision||Security||8|
|J||How to increase mod_security limit?||Security||4|
|G||See which users have mod_security disabled?||Security||1|