Symptoms
When you install ModSecurity3 via the experimental repo, this will cause ModSecurity Tools to stop reporting the ModSecurity rules that were being hit.
Description
We've opened an internal case for our development team to investigate this further. For reference, the case number is CPANEL-35339. Follow this article to receive an email notification when a solution is published in the product.
Workaround
The Apache logs still log the occurrence of ModSecurity hits on the server; you would need to review the /etc/apache2/logs/error_log for what rules are being hit and for what domain.
Comments
1 comment
Update: We would like to thank you for your interest in this article/case and encourage your submissions as they are valuable to the ever-expanding development of cPanel & WHM. At this time, this particular issue has not been selected for action from our Development Team, as it may require more development resources than we can allot, or alters the direction cPanel envisions for the product. Submissions persist in our Issue Tracking System in the event the impact of the related issue grows or product direction changes. If you feel that this defect requires direct action, we strongly encourage you to submit a Feature Request to allow the cPanel Community to vote and support your cause.
Thank you again for helping us make cPanel & WHM the hosting platform of choice.
Article is closed for comments.