mod_security rule [Id ‘-1’] triggered! ModSecurity: Access denied with code 403 – Knowledgebase


While updating the contents in any of the CMS, I was getting a 403 error on the Litespeed server.

Below are the Error log – (tail -f /usr/local/apache/logs/error_log | grep IP address )

2016-11-02 19:55:14.148 [NOTICE] [IP Address :HTTP2-1] mod_security rule [Id ‘-1’] triggered!
[Wed Nov 2 19:55:14 2016] [error] ModSecurity: Access denied with code 403,
[Rule: ‘TX:0’ ‘[email protected] userdata_wl_content_type’]
2016-11-02 19:55:14.148 [NOTICE] [IP Address:54100:HTTP2-1] Content len: 1276, Request line:
‘PUT /ajax/api/static-pages/2 HTTP/1.1’
2016-11-02 19:55:14.148 [INFO] [IP Address49:54100:HTTP2-1] Cookie len: 36,
PHPSESSID=or0n7vj8be5vq5o61id69bgd45
2016-11-02 19:55:14.148 [NOTICE] [IP Address:54100:HTTP2-1] Redirect: #1,
URL: /index.php
2016-11-02 19:55:14.148 [INFO] [IP Address:54100:HTTP2-1] File not found
[/home/henrystb/public_html/403.shtml]

1. Find out the mod security rules which are triggered by checking apache error logs. You can also check the modsec audit logs.

Apache error logs – tail -f /usr/local/apache/logs/error_log | grep IP address
Mod security audit log location – /usr/local/apache/logs/modsec_audit.log
2. You can also check the rules which are being triggered from WHM >> Mod Security Tools.
3. Once you’ll get the rule, white-list them from WHM >> ConfigServer ModSecurity Control. You can either globally white-list the rule or can white-list for a particular user.
Globally white-listing the mod security rule – WHM >> ConfigServer ModSecurity Control >> ModSecurity rule ID list >> Enter the Rule ID >> Save Global whitelist.
White-listing the mod security rule for particular user – WHM >> ConfigServer ModSecurity Control >> Select the user from drop-down list >> Modify User whitelist >> ModSecurity rule ID list >> Save whitelist for all accessible domain.
4. If there is still error then please use the debug tool in your web browser, find out the HTTP header. HTTP Headers tell you the content type and white-list those contents type on the server on below file –

You’ll need to do below server-wide changes –


cd /usr/local/apache

Put your Content-Type in whitelist here –

cat /etc/apache2/conf.d/modsec_vendor_configs/comodo_apache/userdata_wl_content_type

Below are some example header type for your reference –

application/x-www-form-urlencoded
multipart/form-data
text/xml
application/xml
application/x-amf
application/json
application/octet-stream
text/plain
json

5. Rebulit the ‘httpdconf’ file – /scripts/rebuildhttpdconf
6. Restart the ‘Litespeed’ service – service lsws restart
Now, try to replicate the issue, it will be fixed. 

Note:- You can usually use Chome/Firefox developer tools to get the HTTP header ( right click on page >> Inspect Element).

Let me know if you’ve any thoughts

Leave a Comment

Your email address will not be published. Required fields are marked *

Hire a server Expert to resolve the issue Now.

Hire a server Expert to resolve the issue Now.

Resolve this issue in just 5$ from https://serverexpert.io

 

You have Successfully Subscribed!

Open chat