Solid Backups

Kadence Backups FAQs

Coming soon: Solid Backups is becoming Kadence Backups. Both names may appear across product interfaces and support documentation during the rebranding period.

How do I create a local destination for my backups?

Kadence Backups does not use third-party cloud destinations (Dropbox, S3, and similar) or store backup archives on your host’s disk by default.

Backups are stored in Kadence cloud storage. When you need a local copy, download an archive from Kadence Central’s Timeline. See Managing Your Backups for more details.

For legacy on-site destinations (BackupBuddy-style), see Handling Kadence Backups — Legacy vs NextGen.

How long are backups retained?

The backups created with Kadence Backups are retained based on your selection during enrollment. You can store backups for 7 days, 30 days, 120 days, or 1 year. See Kadence Backups Settings for more details.

If you disconnect a site from Kadence Central that was enrolled in Kadence Backups, backup data for that site is retained for 7 days and then permanently deleted.

Can I change the data center region used to store my backups?

Kadence Backups supports both US (default) and EU data center regions. You can update your region if needed—for example, to meet compliance requirements or adjust to new business needs.

How to change your backup region:

  1. Log in to Kadence Central.
  2. From the Sites list, select the site you want to update.
  3. Open the site’s Kadence Backups tab.
  4. Choose a new data center region (US or EU) and save your changes.

All scheduled and manual backups initiated after this change will be stored in the selected region.

Important: Changing regions permanently removes backups stored in the previous region. Download your latest archive from the Timeline before switching.

Can I migrate a site with Kadence Backups?

There is no dedicated migration wizard, but sites can be moved using the following workflow:

  1. Enroll a site in Kadence Backups and allow at least one backup to complete.
  2. Update the enrolled site’s server credentials in Kadence Central to point to the destination server. The destination server must already contain a valid WordPress installation with a wp-config.php file.
  3. Start a restore to the connected server from the Kadence Central Timeline.

For host-specific SSH/SFTP setup, see Getting Started with Kadence Backups.

Why do you need SSH/SFTP access?

Kadence Backups connects to your server via SSH or SFTP to read files, securely export the database, run required CLI steps, and automate backups and restores. These protocols are standard for encrypted server access and large transfers.

SSH and SFTP also efficiently handle large backup and restore transfers and offer the flexibility to automate the process.

Why can’t I connect as root?

For security reasons, Kadence Backups does not support SSH access as the root user. It should never have root-level access to your server.

Create or use a non-root SSH/SFTP account provided by your host for the site, then enter those credentials in Kadence Central.

Could server firewalls and other threat mitigation mechanisms cause problems with Kadence Backups? 

Yes. Firewalls, WAF rules, ModSecurity, Imunify360, Cloudflare, and security plugins can block Kadence infrastructure even when your own computer can SSH in.

Allowlist Kadence Backups and Kadence Central IP addresses on the server (and on Cloudflare or your CDN when traffic is proxied). See the next question and Kadence Backups Troubleshooting SSH/SFTP Connection Issues.

On cPanel servers with ConfigServer Security & Firewall (CSF) in WHM, use Quick Allow or your host’s documented method for the IPs below.

What IP address(es) might need to be added to an allow list?

Kadence Backups (SSH/SFTP from Kadence infrastructure):

  • 207.246.255.233
  • 207.246.255.133

Kadence Central (site connection, API, and related services):

  • 207.246.254.118
  • 207.246.255.233
  • 207.246.255.133
  • 207.246.255.60

If both the Central connection and backups fail, follow the guide in Tips for troubleshooting Kadence Central.

Cloudflare Firewall vs Server Firewall

Cloudflare (or a similar CDN/WAF) filters web traffic before it reaches your server, while a server-level firewall manages direct access to your server, including SSH.

Use both layers when applicable: allowlist trusted Kadence IPs in Cloudflare so WAF/DDoS rules do not block legitimate Central traffic, and allowlist the same IPs on the server for SSH/SFTP used by Kadence Backups.

Error: “Solid Backups could not verify the license for your site.” Failed to perform license check

This error indicates that wp-cli is either not installed or the user account provided to Kadence Backups lacks the required permissions to run wp-cli, specifically this command:

wp ithemes-licensing show solid-backups

Contact your host to confirm that wp-cli is properly configured and that the command can execute using the SSH/SFTP user provided to Kadence Backups.

Other possible causes:

  • The server’s PHP environment is missing the Phar extension. This extension is required for wp-cli to operate in non-interactive connections. Ensure that your host enables the Phar extension in the default PHP environment for all connection types.
  • The wp-config.php file contains require 'wp-salt.php';, which prevents WP-CLI from running properly outside the WordPress root directory. Update the line to require DIR . ‘/wp-salt.php'; or ask your hosting provider to update it to allow non-interactive execution.

For detailed troubleshooting steps, see Troubleshooting Kadence Backups Errors.

Error: Solid Backups could not complete the requested backup. Solid Backups did not complete backing up your database.

If Kadence Central is connected but the backup fails on the database step, the failure usually occurs during MySQL export or related file processing.

Common Causes:

  • The database user lacks permission to LOCK TABLES or read required data.
  • The server drops the connection during large table exports.
  • PHP memory or execution limits interrupt the export.

Note: Detailed logs contain internal error reference numbers. If a backup fails repeatedly, provide the reference number to Software Support for review.

For detailed troubleshooting steps, see Troubleshooting Kadence Backups Errors.

What should I do if the site enrollment process halts?

If enrolling a site results in no error message or confirmation, the onboarding process may be looping because the site is already connected.

Navigate to the Kadence Central dashboard and check if the site is listed on the Sites screen. If listed:

  1. Select the domain to open the site’s settings.
  2. Open the Kadence Backups tab to verify enrollment.
  3. If enrolled, complete any pending server credential configurations.

If the site is not listed, complete the Kadence Central site connection first (see “Getting Started with Kadence Backups”). For Central disconnects, see Tips for troubleshooting Kadence Central.

Last updated: October 31, 2026
Was this page helpful?
Thanks for the feedback!