Elementor shows a 500 error when saving changes

When saving changes with Elementor, Server Error (500 error) may appear. The 500 code confirms an internal failure during the request, but does not by itself identify whether memory ran out, PHP failed or another component was involved.

1. Identify the failing request

Open the browser tools, save once and find the request returning 500 in Network. Note its URL, time and response. Avoid several attempts in a row so the logs do not get mixed up.

Check the PHP log for that same time. If you do not have one, temporarily enable the private debug log; do not show errors to visitors or add php_value directives without knowing whether the server supports them.

2. Act on the first error

For example, the log may show:

PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 233472 bytes) in wp-includes/wp-db.php on line 2022

In that example, memory did run out. Check the effective PHP limit, the amount requested and the component that appears in the stack trace. wp-db.php may be where memory ran out without being what caused all the consumption.

Only then adjust WP_MEMORY_LIMIT or WP_MAX_MEMORY_LIMIT within the maximum allowed by memory_limit, using the lowest value that is enough. If the limit is already adequate, repeatedly raising it up to 512 MB can hide a faulty query, widget or extension without fixing it.

If the first error identifies an Elementor plugin or extension, update it and repeat the test without that component on staging. If there is no PHP error, check the server log and any security event with the same time and path.

3. Verify

Save the same page and confirm that the request no longer returns 500 and that no new error appears in the log. Check the public page, restore the isolated components and disable debugging. If the problem persists, give support the time, URL, response and first fatal error, not just a screenshot of the Elementor notice.

Keep your editor work

Before reloading or closing the editor, keep any changes you can export or copy and check whether a saved revision exists. An error message when receiving the response does not prove that the server saved nothing: check the latest revision and the published page before repeating the operation.

If you try Elementor's safe mode, remember that it isolates the editor environment; it is not the same as disabling all components for visitors. Check saving and the public page separately, with the same combination of Elementor, Pro and extensions.