Webzstore
A 500 Internal Server Error is a generic server error that doesn't offer much information about the root cause. However, when it comes to the Elementor plugin for WordPress, there are a few common reasons why this error might occur. Follow these steps to diagnose and resolve the issue.
Before you change anything: take a full backup of your files and database, and if you can, work on a staging copy of the site rather than the live one. Several steps below (changing PHP, switching themes, deactivating plugins, deleting Elementor) can take a live site offline or change how it looks, so you need a way back. Start with the steps that only read information (the logs), and make one change at a time so you know which one made the difference. Checked against WordPress and PHP documentation on 3 October 2026.
Check server logs
Your server logs may provide more information about the cause of the error, and reading them changes nothing on your site. Most hosting providers offer access to the PHP and web server error logs through their control panel. Look for a fatal error message and note which file and plugin or theme it names (for example a file inside wp-content/plugins/elementor or another plugin). That tells you which of the steps below is relevant, so do not skip this step.
Increase PHP memory limit
Insufficient PHP memory can cause a 500 Internal Server Error, typically shown in the log as an "allowed memory size exhausted" message. If that is what the log shows, you can raise the limit in the wp-config.php file. First search the file for an existing WP_MEMORY_LIMIT line and change that one; defining the same constant twice makes PHP raise a warning, and the first definition is the one that stays in effect. If there is none, add the line above the comment that reads "That's all, stop editing!":
define( 'WP_MEMORY_LIMIT', '256M' );Elementor's system requirements list a WordPress memory limit of at least 256 MB, and recommend more for sites that also run heavy plugins such as WooCommerce. Some hosts do not let you raise the limit from wp-config.php; in that case ask your host to raise it. WordPress's own documentation also warns that raising the limit can hide the underlying problem, so if the error returns, look for the plugin or process that is using the memory rather than raising the number again.
Save the file and refresh your site to see if the error is resolved.
Update PHP version
An unsupported PHP version can cause problems, but so can jumping versions without testing. As of 3 October 2026, php.net lists PHP 8.2, 8.3, 8.4 and 8.5 as supported branches, and lists PHP 8.1 and earlier as end of life with no security fixes. PHP 8.2 is in security-only support until 31 December 2026. WordPress's requirements page recommends PHP 8.3 or greater, and notes that PHP 7.4 and some other older versions have reached end of life and may expose your site to security vulnerabilities. Elementor's own requirements say it still runs on PHP 7.4 but strongly recommend PHP 8.x. A minimum that a plugin still runs on is not the same as a version that still receives security fixes.
If your site is on an end-of-life version, plan a move to a currently supported one, preferably the one WordPress recommends, using this order:
- Take a full backup and note your current PHP version so you can switch back.
- Check that your theme and every active plugin (not just Elementor) support the new PHP version. Their changelogs or documentation usually say.
- Change the PHP version on a staging copy first, from your hosting control panel or by asking your host, and test your key pages, forms and checkout.
- Only then change the live site, at a quiet time, and keep the previous version available as a rollback.
Changing PHP is also the step most likely to expose an old plugin or custom code that was only working by accident, which is another reason to test it away from the live site.
Disable conflicting plugins
Another plugin may be conflicting with Elementor. If the log names a different plugin, start with that one. Otherwise, on a staging copy (or on the live site only at a quiet time, after a backup), deactivate all other plugins except Elementor. If the error is resolved, reactivate the plugins one by one to find the conflicting plugin. If the error stops you from reaching the WordPress admin, you can deactivate a plugin by renaming its folder inside wp-content/plugins using SFTP or your host's file manager; rename it back afterwards. Do not deactivate security, backup or payment plugins on a live store without a plan, since orders and protection are affected while they are off.
Check the theme: a theme conflict can also cause a 500 Internal Server Error. To test, switch to a default WordPress theme on a staging copy. Switching the theme on a live site can change menus, widgets and the layout visitors see, so avoid doing it there. If the error is resolved with a default theme, contact the theme developer for support or use a different theme.
Check file permissions
Incorrect file permissions can cause server errors. WordPress's hardening guide recommends:
- Directories should have a permission of 755.
- Files should have a permission of 644.
wp-config.phpshould be readable only by you and the web server, which generally means 400 or 440.
Never use 777 (writable by everyone) to try to fix an error. You can check and modify file permissions using an SFTP client (like FileZilla) or through your hosting control panel's File Manager. Ownership problems (files owned by the wrong user) also cause errors, and those usually need your host to fix.
Enable WordPress debugging
If the server logs do not show the cause, you can use WordPress's debug log. WordPress's developer documentation says the debug tools are meant for local testing and staging installs and are not recommended on live sites, so use a staging copy where possible. If you must turn it on briefly on the live site, edit wp-config.php (after taking a backup) and add or change these lines above the "That's all, stop editing!" comment, using a single definition of each constant:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Save the changes and reload your website. WordPress then writes errors to a debug.log file, by default in the wp-content folder. Examine it for fatal errors related to Elementor, another plugin or your theme.
Keep the log private: a debug.log inside wp-content may be reachable from the web, and it can contain file paths and other details you do not want to share. Check that yoursite.com/wp-content/debug.log does not open in a browser, or set WP_DEBUG_LOG to a file path outside your public web folder. When you have finished, set WP_DEBUG back to false, and delete the log file.
Reinstall Elementor plugin
If the error log shows a fatal error inside Elementor's own files, and the steps above do not resolve it, a clean copy of the plugin may help. This is a last resort, so take a full backup (files and database) first, and do it on a staging copy if you can:
- Deactivate and delete the Elementor plugin from your WordPress admin dashboard, or rename its folder in
wp-content/pluginsif you cannot reach the admin. - Download the latest version of the Elementor plugin from the WordPress plugin directory or the Elementor website.
- Install and activate the plugin, then check your key pages.
If you use Elementor Pro, make sure the free Elementor plugin and Elementor Pro are updated to compatible versions, because a mismatch can also cause fatal errors.
Contact hosting support
If you've tried the steps above and the issue persists, contact your hosting provider's support team. Give them the exact time of the error and the fatal error line from the log if you have found one. They may have additional insights or may need to adjust server configurations (for example PHP memory, execution time or security rules) to resolve the issue.
Reach out to Elementor support
If the issue is still unresolved, contact Elementor's support team for assistance. Provide them with all the troubleshooting steps you've taken and any relevant error messages or log entries. They will guide you further in resolving the 500 Internal Server Error.
