Issue 413 Request Entity Too Large

[bluangel77]

Hi everyone. Sorry for my english. I am sad because for days now I have not solved the problem. No support from my hosting provider. They simply say that the server is self-managed. I can understand this but it is not my fault if I change the records because as they said they are old and damaged. In any case, I sincerely thank those who can help me. Still sorry for my bad english.

THE PROBLEM

I can't upload my backup saved on my computer because the server tells me that the file is too big as indicated in the object. Following your guides or used putty.

I accessed the server using and modifying the following parameters to set the file upload without limits.

I saved everything and restarted the server but it doesn't work.

---------------------------------------------------------
myservername:~# vi /usr/local/psa/admin/conf/php.ini
short_open_tag = On
y2k_compliance = Off
output_buffering = Off


max_execution_time = 1200
max_input_time = 1200
memory_limit = 256M
max_file_uploads = 99999
max_input_vars = 2000

error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED
log_errors = On
display_errors = Off
warn_plus_overloading = Off
expose_php = Off

variables_order = "ECGPS"
register_argc_argv = On
post_max_size = 2147483647
magic_quotes_gpc = Off
magic_quotes_runtime = Off

upload_tmp_dir = "/tmp"
upload_max_filesize = 2147483647

psasem.semfile = "/opt/psa/var/psasem.sem"

opcache.enable=1
opcache.memory_consumption=128

; setting fast_shutdown to 1 might cause segmentation faults
; (PHP :: Bug #65590 :: Apache segfaults and reports zend_mm_heap corrupted)
opcache.fast_shutdown=0

include_path = "/opt/psa/admin/plib"

zend_extension = "/usr/lib/x86_64-linux-gnu/php/modules/sw-engine/opcache.so"
~


---------------------------------------------------------------------------------------------------------------




Websites & Domains
Apache & nginx Settings for
j have add this on

Additional directives for HTTPS whit

<IfModule mod_fcgid.c>
FcgidMaxRequestLen 1073741824
FcgidMaxRequestsPerProcess 100
FcgidProcessLifeTime 7200
</IfModule>



Additional directives for HTTP whit

<IfModule mod_fcgid.c>
FcgidMaxRequestLen 1073741824
FcgidMaxRequestsPerProcess 100
FcgidProcessLifeTime 7200
</IfModule>

----------------------------------------------------

Many thanks to those who can help me.

 

[hostking]

You try this yet? Did a quick google for that error with IIS appended to end as its windows

Solution for “Request Entity Too Large” error

IIS has a limit for the size of the files users can upload to an application. If the file size exceeds the limit, the application will throw “Error in HTTP request, received HTTP status 413 (Request Entity Too Large)” error. The default file upload size is 49 KB (49152 bytes). The application...

techcommunity.microsoft.com

.

 

[esfahanhost]

Error :
The page was not displayed because the request entity is too large.
or
413 Request Entity Too Large plesk

Best Solution :

Please See This Link for Upload File Larger than 2 GB in Windows OR Linux Server by Command-Line :

https://support.plesk.com/hc/en-us/articles/115002362654

Thanks
Masoud Saeidi
esfahanhost.com

 

[jesussuarez]

In my case, I was using Plesk to host a PrivateBin instance. When uploading files, I noticed in the logs that it was failing with an error similar to this:

[client IP] ModSecurity: Request body no files data length is larger than the configured limit (1048576).. Deny with code (413) [hostname "website.com"] [uri "/"] [unique_id "asdlkawlwqerewrwe"]

After some research, I found that the issue was related to an Apache configuration combined with Imunify360, which was blocking these transactions even if ModSecurity was disabled at the domain level.

I solved it by adding the following configuration under "Additional Apache directives" in Plesk:

<IfModule mod_security2.c>
SecRequestBodyLimit 4294967296
SecRequestBodyNoFilesLimit 4294967296
</IfModule>

Additionally, I adjusted the "Maximum allowed size of the HTTP request body" (client_max_body_size) in the same section to 4G. After saving the changes, I restarted Apache (Ubuntu 22 server).
This completely fixed the problem.