Fix Server Error (413 Error) -Elementor WordPress

413 server error elementor

When seeing 413 – server error in WordPress, the very first thing that comes into our mind is the maximum file upload limit settings for php. There are lot’s of tutorial on how to fix this error increasing upload file size limit, post max size and max execution time. I am sure if you are reading this post, you are here because increasing these value isn’t solving your issue.

WP multisite max file upload size value:

If you are running WordPress multisite then you might want to check on Network settings page where you can set “Max file upload size” for all the websites in your network. Please refer to screenshot below:

Wordpress Network Settings

Our Context

Recently, while working on client website with “Elementor” drag drop builder, we weren’t able to save a page with large content because of this error. We tried increasing php value for: “upload_max_size”, “post_max_size” and “max_execution_time” without any success. Went through “Elementor” requirement and set up all the settings value greater than what was needed for it but it didn’t work.

Researching more, we figured out one possible solution was to increase “LimitRequestBody” directive value for Apache servers and “client_max_body_size” for NGINX. We tried increasing these values but with no success.

Actually, we were using Plesk server with Apache so, tried researching on Plesk support docs and figured out that the default value for “SecRequestBodyNoFilesLimit” was low. You will have to increase the value for this parameter as required. File to be edited can be found at:


Finally, after increasing this value and restarting Apache server fixed this issue on our end.

We hope this article helped you learn how to fix the WordPress 413 server error when increasing basic php settings doesn’t work.

Find us on twitter and facebook for latest news on WordPress.

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.