• Resolved webwordwp

    (@webwordwp)


    Hi, I have a error (413 request entity too large) when adding a new section in elementor page and save

Viewing 5 replies - 1 through 5 (of 5 total)
  • It might be an issue with your hosting resource limit.

    The “413 Request Entity Too Large” error occurs when the size of a client’s request exceeds the server’s file size limit. This error typically happens if you attempt to upload an overly large file. The server responds with a 413 error message to indicate that the entity being sent is too large.

    Please check your upload & file size limit and increase according your need.

    Plugin Support marthaeli

    (@marthaeli)

    Hi @webwordwp

    Thanks for contacting Elementor.

    I confirm as well what @sulov wrote you previously.

    I found online this reference in case is of any help – https://www.wpbeginner.com/wp-tutorials/how-to-fix-the-413-request-entity-too-large-error-in-wordpress/

    Let us know if you will need additional assistance.

    Kind Regards.

    Thread Starter webwordwp

    (@webwordwp)

    Hi,

    I followed the steps but same problem , my server is local server hyper-v with 16 Ram and 2 cpu and os is linux rocky 9 + waf enabled

    Plugin Support Milos

    (@miloss84)

    Hi there,

    The “413 Request Entity Too Large” error indicates that the server is rejecting a request because the payload is too large. This is common when you’re trying to upload files or data that exceed the server’s configured limits. Here are steps to resolve this issue:1. Modify PHP Configuration

    Increase the limits in the php.ini file.

    1. Locate php.ini file:
      • If you’re on a shared hosting environment, you might not have direct access to this file. Contact your hosting provider for assistance.
      • If you have access, the php.ini file is usually located in the root folder of your server or in a folder specific to your PHP installation.
    2. Edit php.ini: Open the file and increase the values for the following directives: Copy codeupload_max_filesize = 64M post_max_size = 64M max_execution_time = 300
    3. Save and Restart: Save the changes and restart your web server (Apache, Nginx, etc.) for the changes to take effect.

    2. Modify .htaccess File

    If you cannot access php.ini, you can modify the .htaccess file in your WordPress root directory.

    1. Locate and Edit .htaccess: Add the following lines to the .htaccess Copy codephp_value upload_max_filesize 64M php_value post_max_size 64M php_value max_execution_time 300 php_value max_input_time 300
    2. Save the File: Save the .htaccess file and check if the issue is resolved.

    3. Modify Nginx Configuration (If Using Nginx)

    If your server uses Nginx, you need to modify its configuration file.

    1. Locate Nginx Configuration File: This is usually found at /etc/nginx/nginx.conf or /etc/nginx/conf.d/default.conf.
    2. Edit Configuration: Add or modify the following directive in the appropriate block:nginxCopy codeclient_max_body_size 64M;
    3. Save and Restart Nginx: Save the file and restart Nginx with:bashCopy codesudo systemctl restart nginx

    4. Contact Hosting Provider

    If you’re on a shared hosting plan and unable to make these changes, contact your hosting provider’s support team. They can usually adjust these settings for you.5. Plugin-Based Solution

    Some WordPress plugins can help manage server settings.

    1. Install a Plugin: Use a plugin like “WP Maximum Upload File Size” to adjust these settings from within the WordPress dashboard.
    2. Configure the Plugin: After installing, navigate to the plugin settings and set the desired upload limits.

    By following these steps, you should be able to resolve the “413 Request Entity Too Large” error when adding a new section in Elementor. If you continue to experience issues, double-check each step for accuracy and ensure your server configuration is correctly applied.

    Please note before you try any of this method please contact your hosting provider firsta and backup your site.

    Kind regards,

    Alain

    (@alainelementor)

    Hello @webwordwp !! It’s been quite a few days since your latest reply, so we will conclude this conversation due to inactivity, but feel free to contact us again for further questions.

    Have a good day!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.