Solid Backups
Troubleshooting Kadence Backups Errors
Coming soon: Solid Backups is becoming Kadence Backups. Both names may appear in product interfaces, documentation, and customer communications during this transition.
When using Kadence Backups from Kadence Central, Timeline may show errors that contain “Solid Backups” in the message text. This guide explains what those messages mean and how to resolve them.
Check the Timeline in Kadence Central for the full error and any reference number before changing server settings.
Solid Backups could not verify the license of your site. Failed to perform license check.
This error message indicates that Kadence Backups could not run WP-CLI to verify licensing. It typically does not indicate an issue with your subscription.
The WP-CLI command Kadence Backups runs during this process is:
wp ithemes-licensing show solid-backups
Possible causes:
- WP-CLI is not installed or not available to the SSH/SFTP user configured in Kadence Central.
- The CLI PHP environment is missing the Phar extension (required for WP-CLI, especially non-interactive SSH sessions).
- CLI PHP version or
php.inilimits differ from the web PHP used by the site. wp-config.phpuses a relative path for salts (for examplerequire 'wp-salt.php';) so WP-CLI fails outside the WordPress root.wp-config.phploads database credentials viagetenv()or similar in a way that works for web requests but not CLI.- CLI PHP memory limit is too low for another plugin to load during WP-CLI bootstrap.
- Non-standard host stacks (some Plesk/WP Toolkit setups) expose a
wpbinary that does not match a normal global WP-CLI install. See Supported And Unsupported Web Hosts.
Recommended actions:
1) Ask your host to run the following as the same SSH/SFTP user Kadence Backups uses:
wp ithemes-licensing show solid-backups
Confirm WP-CLI runs without errors and that CLI PHP has the Phar extension enabled.
2) If WP-CLI works on the server but Timeline still fails, inspect wp-config.php for:
require 'wp-salt.php';
Change it to:
require __DIR__ . '/wp-salt.php';
(Or ask your host to update it.)
3) If SSH connection is unstable, fix credentials and firewalls first: Kadence Backups Troubleshooting SSH/SFTP Connection Issues.
4) After your host confirms the command succeeds, trigger a new backup from Kadence Central and watch Timeline.
Solid Backups could not complete the requested backup. Solid Backups did not complete backing up your database.
This message indicates that Kadence Backups connected to the server but failed during the database export (mysqldump), rather than during the initial SSH handshake.
Possible causes:
- The WordPress database user lacks permission to LOCK TABLES or read required data.
- The server drops the connection during export (large tables, memory limits, or timeouts).
- MySQL settings such as
max_allowed_packet,net_read_timeout, ornet_write_timeoutare too low for the dump. - Host resource limits during backup (try lowering Transfer Speed; see Kadence Backups Settings).
Recommended actions:
1) Confirm with your hosting provider or database administrator that the WordPress database user has permissions to execute:
LOCK TABLES
If needed, grant permissions on the WordPress database (replace placeholders with actual values):
GRANT LOCK TABLES ON `your_database_name`.* TO 'your_db_user'@'localhost';
FLUSH PRIVILEGES;
2) If permissions are correct but errors persist, request that your hosting provider review MySQL and system logs for:
- Timeout or memory errors during database export.
- Insufficient
max_allowed_packetor network timeout settings - Specific tables failing during export (repair or optimize as recommended).
3) On shared or resource-constrained hosting environments, set Transfer Speed to Regular or Slow and Integrity Verification Module to Normal, then retry. See Kadence Backups Settings.
4) Run another backup from Kadence Central after the host confirms changes.
Failed to parse license data (related license-check failure)
Some environments encounter a license-related failure after WP-CLI executes because Kadence Backups cannot parse valid JSON output. PHP notices, warnings, or deprecation notices printed before the JSON output are common causes (for example, running older WP-CLI versions on newer PHP releases).
Ask your hosting provider to execute:
wp ithemes-licensing show solid-backups --format=json
Valid output must begin directly with [ or { with no leading text or error output.
Recommended Actions:
- Update WP-CLI to the latest version supported by your PHP release.
- Adjust CLI
php.ini(for example, reduce noisydisplay_errors/ deprecation output for CLI). - Use a CLI PHP version below 8.4 if the host cannot update WP-CLI yet.
More context: Handling Kadence Backups — Legacy vs NextGen.
Still not sure which applies to you?
If the problem persists, contact the Software Support Team with the exact error message and reference number shown in Kadence Central Timeline, along with any troubleshooting steps already completed.