DEV Community

Cover image for How to Fix the 500 Internal Server Error in WordPress & Elementor
DesignToCodes
DesignToCodes

Posted on • Originally published at designtocodes.com

How to Fix the 500 Internal Server Error in WordPress & Elementor

WordPress white screen or a 500 error? Before you start disabling plugins at random for an hour, do this one thing first — it tells you the actual cause.

Step 0: turn on the lights

Add this to wp-config.php (above the "stop editing" line):

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Enter fullscreen mode Exit fullscreen mode

Reload, then open /wp-content/debug.log. The last lines name the file or plugin that crashed. Now you're fixing the real problem instead of guessing.

The four usual suspects (in order)

  • Corrupted .htaccess — rename it, then re-save Permalinks to regenerate a clean one.
  • PHP memory limit — Elementor is hungry; add define('WP_MEMORY_LIMIT','512M');
  • Plugin/theme conflict — rename /wp-content/plugins to confirm, then re-enable one by one.
  • Old PHP — modern WordPress + Elementor want PHP 8.1+. Switch in your host panel.

The Elementor gotcha

A version mismatch between Elementor and Elementor Pro throws 500s right after an update. Always update both together — and keep your theme current alongside them.

Tired of fragile themes causing this? I hand-code WordPress and Elementor templates built to current PHP and performance standards at DesignToCodes.

What finally caused your last 500 error? Mine was a single rogue plugin update 👇

Top comments (0)