For anyone who finds this later: in your Fixing WordPress thread you mentioned that switching off ModSecurity on the server fixed it.
That fits. Elementor saves the whole page as one request, and ModSecurity has its own request-body limits, separate from PHP’s (SecRequestBodyNoFilesLimit defaults to 128 KB). A long Elementor page passes that easily, and ModSecurity then answers 413 even though PHP’s settings are fine.
Rather than leaving the whole firewall off, I’d turn ModSecurity back on and raise that limit in its configuration, e.g.
SecRequestBodyNoFilesLimit 2097152
(2 MB; also check SecRequestBodyLimit is at least as large), then reload the web server and save the page again. The error log entry for the 413 names the exact limit that was hit, if you want to raise only that one.
A dedicated server with no web application firewall is a bigger risk than the 413, especially this week with the PHP vulnerabilities being exploited.
Plugin Support
vipul78
(@vipulelementor)
Hi @biggyboss92
As I am seeing on your site, the site is using Elementor Pro.
WordPress.org rules state that commercial products are not supported here.
Since you are an Elementor Pro user, you can contact us here https://elementor.com/help/how-to-submit-a-support-ticket/
I’d also suggest you check out Elementor Community Group on Facebook. We have created it to connect Elementor users together and share knowledge, Global Elementor Community.
