Applicable to:
- Plesk Onyx for Linux
Symptoms
-
Unable to upload a file to the website with the error:
CONFIG_TEXT: 413 Request entity too large
CONFIG_TEXT: Request Entity Too Large
The requested resource
/upload-a-file/
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit. -
ModSecurity component is installed on the server.
-
The following error can be found in
/var/www/vhosts/example.com/logs/error_logfile:CONFIG_TEXT: [:error] [pid 21701] [client 92.50.125.210] ModSecurity: Request body no files data length is larger than the configured limit (1048576).. Deny with code (413) [hostname "www.example.com"] [uri "/wp-admin/admin-ajax.php"] [unique_id "Wakfj-fvNMmcLKLp-n8PjQAAAAE"]
Cause
SecRequestBodyNoFilesLimit parameter value reached its limit.
Resolution
-
Log into the server via SSH.
-
Using the vi text editor open the
/etc/httpd/conf.d/mod_security.confor/etc/httpd/conf/modsecurity.d/rules/tortix/modsec/tortix_waf.conffile. -
Increase the value for the
SecRequestBodyNoFilesLimitdirective, for example to the value as below:CONFIG_TEXT: SecRequestBodyNoFilesLimit 10000000
Note: the value for
SecRequestBodyNoFilesLimitparameter is specified in Bytes. -
Execute the command below to restart Apache:
# service httpd restart
Comments
2 comments
Hi,
In CentOS 7 with Obsidian, the changes are working when modifying the file
/etc/httpd/conf/modsecurity.d/rules/tortix/modsec/tortix_waf.confThe file /etc/httpd/conf.d/mod_security.conf is no existan.
Regards
Hello Alejandro Betancor
I've checked this on my test server and agree with you.
I will pass this to the article author.
Please sign in to leave a comment.