Fix 413 request entity too large error in Plesk with a little help from our experts. Our Plesk Support team is here to help you with your questions and concerns.

413 request entity too large Plesk | Fixed

If you have been having trouble with the following error, you are in luck. Our experts are here to help you resolve this issue in just a few simple steps.

413 (Request Entity Too Large).

This error occurs when a client tries to send a request larger than the default 1 MB. This results in the above error message in the error logs.

We can easily resolve this issue by increasing the client request size body. This is done by modifying the client_max_body_size parameter in the nginx.conf file.

The client_max_body_size parameter sets the maximum allowed size of the client request body, specified in the “Content-Length” request header field.

In case the size of a request is more than the configured value, an error is returned to the client. However, browsers do not display this error correctly.

Furthermore, we can disable checking the client request body size by setting the parameter value to 0.

How to change the  client_max_body_size value

1. First, open the nginx.conf file with this command:

   sudo vi /etc/nginx/nginx.conf
2. Then, change the client_max_body_size to a value we prefer as seen here:

   client_max_body_size 12m;

   Our experts recommend increasing client_body_buffer_size to 16MB in case the client is sending large requests.
3. Now, save and exit the file.
4. Finally, we must restart the Nginx server fpr the changes to take effect.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Techs demonstrated how to fix 413 request entity too large error in Plesk.