If the whole site displays “Error establishing a database connection,” check the WordPress database credentials and server first. If the site and WP Admin work but Elementor cannot load, save, or update a page, the main database connection is probably working. Focus on the failed request, server logs, Elementor data, and plugin conflicts before considering database repair.
A working homepage and an active Elementor installation do not confirm or reproduce an Elementor database failure. You need the error from the affected request to determine whether the problem involves JavaScript, PHP, the database, or another plugin.
Back up the site files and database before changing credentials, repairing tables, disabling plugins, or applying updates.
Identify the scope of the failure
Open these areas in a private browser window:
- The site homepage
/wp-admin/- A page that does not use Elementor
- The affected page in the Elementor editor
A site-wide database error points to WordPress configuration, an unavailable database service, damaged tables, or exhausted hosting resources.
When only Elementor fails, note exactly what happens:
- The editor remains on its loading screen.
- Saving returns a 500 error.
- One page fails while other Elementor pages work.
- The browser console reports a JavaScript
TypeError. - The server log reports a failed SQL query or missing table.
A console error involving querySelector() is a JavaScript error, not proof of a database problem. Open the browser’s Network panel, clear the existing entries, and reproduce the failure once. Record the failed request’s endpoint, status code, response, and timestamp.
Compare that timestamp with the host’s PHP, web-server, and database logs. Account for any timezone difference between the browser and server. The matching log entry may reveal a PHP fatal error, blocked REST API request, timeout, or failed query that is not visible in the browser response.
Check the WordPress database connection
WordPress reads its database settings from wp-config.php. Compare these values with the credentials shown in your hosting control panel:
define( 'DB_NAME', 'database_name' );
define( 'DB_USER', 'database_user' );
define( 'DB_PASSWORD', 'database_password' );
define( 'DB_HOST', 'database_host' );Do not replace DB_HOST with localhost unless your host specifies it. Some providers use a separate hostname, port, or socket.
The WordPress configuration documentation explains these settings. Do not share wp-config.php; it contains database credentials and security keys.
If the settings are correct but neither the site nor WP Admin can connect, check the database service in your hosting dashboard or contact the host. Ask whether the server is running and whether the configured user still has access to the database.
Check reported table errors with WP-CLI
Use this step for a site-wide database failure or a log entry that specifically reports a table problem. Elementor loading or saving slowly is not enough reason to repair the database.
If you have SSH and WP-CLI access, run:
wp db checkThis command requires the mysqlcheck client utility to be installed and available to WP-CLI on the server. Managed hosts sometimes omit database client tools or restrict their use. In that case, ask the host to run the check.
The command uses the credentials in wp-config.php. See the official wp db check documentation for its options.
Use the reported error to choose the next step:
- Access denied: Recheck the username, password, and database-user privileges.
- Unknown database: Confirm
DB_NAMEand verify that the database exists. - Cannot connect to server: Check
DB_HOSTand the database service. - Damaged table: Restore a recent backup or consider a repair.
If a table is explicitly reported as repairable, take a fresh database backup before running:
wp db repairThis command also requires mysqlcheck. The official wp db repair documentation explains how WP-CLI passes the configured database credentials to that utility.
If the repair fails, restore the affected table from a known-good backup or ask the host to inspect it. Do not keep rerunning the repair against a failing database.
Clear stale Elementor files and caches
When WordPress and other admin pages work, clear Elementor’s generated files before changing the database.
Open Elementor’s Tools screen in WP Admin and run Clear Files & Data. Elementor documents the current location and procedure in its Clear Files & Data guide.
Then clear any applicable caches:
- Elementor cache
- WordPress caching plugin
- Hosting or reverse-proxy cache
- CDN cache
- Browser cache
Retry the affected page in a private window. This is most relevant after an Elementor, add-on, or theme update, or when the editor and published page show different content.
Test for a plugin or theme conflict
Perform conflict testing on a staging copy when possible. Deactivating plugins on a live site can interrupt forms, checkout, security controls, and caching.
Temporarily deactivate all plugins except Elementor and Elementor Pro, then test the editor. With WP-CLI, run:
wp plugin deactivate --all --exclude=elementor,elementor-proThe wp plugin deactivate documentation covers the available options.
If Elementor starts working, reactivate plugins one at a time until the failure returns. Check Elementor add-ons, optimization and security plugins, and plugins that modify queries or REST API requests first.
If disabling plugins does not help, temporarily switch to a default WordPress theme. Restore the original theme after the test.
Elementor’s Safe Mode can help determine whether the editor is being disrupted by the active theme or another plugin. It is a diagnostic tool, not a permanent fix.
Capture the PHP or query error
Use debug logging briefly on staging or during a controlled troubleshooting window. Before editing wp-config.php, record the existing values of WP_DEBUG, WP_DEBUG_LOG, and WP_DEBUG_DISPLAY.
Edit existing definitions rather than adding duplicates. Add a constant only if it is not already defined. Duplicate definitions can produce warnings and may leave the original value in effect.
Set the constants above the “stop editing” line:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reproduce the failure once. Match the failed Network request’s timestamp and endpoint with entries in wp-content/debug.log and the host’s server logs. WordPress explains these settings in Debugging in WordPress.
Relevant messages include:
Table ... doesn't existUnknown columnDuplicate entryDeadlock foundMySQL server has gone awayAllowed memory size exhausted- A fatal error naming an Elementor add-on or theme
The message determines the fix. A missing table or column can indicate an incomplete plugin update or migration. A deadlock or lost connection requires database-server investigation. A PHP memory error belongs in the hosting PHP configuration and will not be fixed by repairing tables.
After collecting the error, restore each debugging constant to its original value. Do not automatically set all three to false if the site previously used a different debugging configuration.
Delete or protect the debug log when finished because it can contain sensitive request and server information.
Handle update and migration failures
If the error began immediately after an update, check that Elementor, Elementor Pro, and Elementor add-ons are compatible and fully updated. Take another backup before applying pending updates.
When only one page fails, duplicate it and remove recently added widgets or templates in small groups. A third-party widget may generate the failed request even though the error appears inside Elementor.
For errors mentioning missing columns or tables, do not create database structures manually from copied SQL. Restore the pre-update database or send the exact logged error to the plugin vendor. Manual schema changes can interfere with later migrations or leave the database in an unsupported state.
Restore all plugins, the original theme, and normal caching after conflict testing. Keep the backup until the affected page loads, saves, and displays without another server or database error.