Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

ModSecurity File Upload Error With SecRequestBodyNoFilesLimit

by | Mar 18, 2021

Are you facing ModSecurity File Upload Error With SecRequestBodyNoFilesLimit? We can help you in resolving it.

When the ModSecurity parameter SecRequestBodyNoFilesLimit has reached the limit, you will not be able to upload any files. As a result, it will throw some errors.

Here at Bobcares, we have seen several such ModSecurity-related errors as part of our Server Management Services for web hosts, cPanel users, and online service providers.

Today, we will take a look at how our Support Engineers resolve this error message relating to ModSecurity.


How to resolve ModSecurity File Upload Error With SecRequestBodyNoFilesLimit

Recently, one of our customers approached us telling us that he was not able to upload files to the Plesk server. Here received the below error message when trying to upload the files.

Request Entity Too Large
The requested resource
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.

Also, the following error was present in /var/www/vhosts/ file:

[:error] [pid 21701] [client 2xx.0.1xx.2] ModSecurity: Request body no files data length is larger than the configured limit (1048576).. Deny with code (413) [hostname ""] [uri "/wp-admin/admin-ajax.php"]

This happens when the WAF_SECREQUESTBODYNOFILESLIMIT parameter value reached its limit.

Now let us see how our Support Engineers resolve this error message for our customer.

In order to resolve the error, we first, we log into the server via SSH.

Next, we open /etc/asl/config file. For that, we use the vi text editor.

Here, in the file, we increase the value for the WAF_SECREQUESTBODYNOFILESLIMIT directive, for example to the value as below:


Then we save the file and exit from it.

Finally, we execute the command below to update the rulesets:

# for i in daily weekly monthly; do /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f UpdateModSecurityRuleSet --period "${i}"; done

[Need any further assistance in fixing ModSecurity errors? – We are here to help you.]



In short, this upload problem arises when the ModSecurity parameter SecRequestBodyNoFilesLimit has reached the limit. Today, we saw how our Support Engineers resolve this ModSecurity error.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

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

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.