Solid Backups
Server Requirements & SSH Configuration for Kadence Backups
Coming soon: Solid Backups is becoming Kadence Backups. You may see both names used while we update the product, documentation, and customer experience.
Introduction
Kadence Backups connects to your server via SSH/SFTP and uses WP-CLI for backups and license checks. Your host must allow access from the Kadence infrastructure, and the SSH/SFTP user you provide in Kadence Central must be able to run WordPress CLI commands at your install path.
This guide covers server requirements and configuration before or during enrollment. For the full connect flow (onboarding, retention, and Test Server Connection), start with “Getting Started with Kadence Backups“. For information on where to find the hostname, port, and username on Nexcess, SiteGround, Bluehost, and other providers, see Host-Specific Configuration for Kadence Backups.
SSH and SFTP requirements
- SSH or SFTP must be enabled for the account that owns the WordPress files. Kadence Backups uses SSH for commands and file access; SFTP-only hosts may not be sufficient if WP-CLI cannot run.
- Use a non-root account. Kadence Backups does not support connecting as the
rootuser. - Credentials in Central must match the server. Server address, port, username, and key or password must be what your host expects (custom ports are common on SiteGround, VentraIP, and others). See the host guide above if you are unsure.
If Test Server Connection fails after credentials look correct, work through the rest of this article, then review the Kadence Backups Troubleshooting SSH/SFTP Connection Issues guide.
Public key and password authentication
During enrollment, Kadence Central asks how Kadence Backups should authenticate to your server.
Public key (recommended)
Public key authentication is the recommended method for security reasons. On the Kadence Backups enrollment screen, reveal and copy the public key Kadence provides for that site, then add it to your hosting control panel for the SSH user you will enter in Central.
Using a public key allows Kadence Backups to be authenticated in a way that cannot be compromised, even if someone guesses a password. It requires knowing how to add keys in your host’s panel, but it provides enhanced security.
Note: Kadence Backups provides a unique public key per site you enroll. Import and authorize that key for the correct SSH user.
For cPanel (Manage SSH Keys, Import Key, Authorize Key), see Host-Specific Configuration for Kadence Backups (Hosts that use cPanel).
Some hosts disable password-based SSH after you enable keys only. If your host has disabled password-based SSH, you must complete key authorization before the Test Server Connection will succeed.
Password
Alternatively, choose Use Password and enter your server account password for SSH. The password is stored encrypted for the connection.
Note: SSH access must still be enabled on the host. On many hosts, this is the same password used for SFTP.
Password authentication can be simpler on first setup, but keys are preferred where your host supports them.
Install WP-CLI
WP-CLI must be installed on your hosting server for Kadence Backups to function. Kadence Backups relies on WP-CLI to verify licensing and to perform backup-related tasks.
Your host may already provide WP-CLI:
- Managed WordPress hosts often install WP-CLI for each account.
- cPanel/WHM servers may need WP-CLI at the account level or server-wide.
Ask your host to confirm that the same SSH/SFTP user you use in Kadence Central can run:
wp --info
from the WordPress installation directory (or with --path= set to that directory).
If WP-CLI is missing, install it using your host’s recommended method. The official handbook is a reference source: Installing WP-CLI. On WHM/cPanel, some administrators install WP-CLI globally for all accounts; others install it per cPanel user. Your host or server admin should choose the approach that matches your server layout.
Plesk/WP Toolkit and non-standard setups: WP-CLI may not be a standard system wp binary. Kadence Backups may fail license checks until a global WP-CLI is available to the site user. See Supported And Unsupported Web Hosts and your host’s documentation.
Verify the license check command
After WP-CLI is available, the same SSH user should be able to run:
wp ithemes-licensing show solid-backups
Note: The product slug solid-backups is expected even though the product is branded Kadence Backups.
If this command fails, Kadence Central may display the following error: “Solid Backups could not verify the license of your site.” Failed to perform license check. That is often an environment problem, not a license/billing problem. See Troubleshooting Kadence Backups Errors.
wp-config.php and WP-CLI paths
If your wp-config.php file includes a line like:
require 'wp-salt.php';
WP-CLI can fail when run outside the WordPress root (as Kadence Backups does). Prefer using:
require __DIR__ . '/wp-salt.php';
Some hosting providers (such as Cloudways) provision WordPress with the shorter require 'wp-salt.php';, so you may need to ask your host to update this in their setup.
Other wp-config.php patterns (for example, loading DB credentials only via getenv() in a way that works for web but not CLI) can also break non-interactive WP-CLI. If the license command works when you SSH in manually but fails from Kadence Backups, ask your host to compare web PHP vs CLI PHP for that user.
PHP configuration for WP-CLI (Phar extension)
The PHP environment used by WP-CLI over SSH must have the Phar extension enabled. This is required for WP-CLI to work, especially for the automated (non-interactive) connections Kadence Backups uses.
Ask your host to enable Phar for the CLI PHP version tied to the wp command your SSH user runs—not only for the web-facing PHP version in the control panel.
If license checks return garbled output or “Failed to parse license data”, PHP notices or deprecations printed before the JSON can be the cause. Your host can test this command:
wp ithemes-licensing show solid-backups --format=json
Output should start with [ or { with no text before it. See Troubleshooting Kadence Backups Errors for PHP 8.4/WP-CLI version notes.
Add Kadence IP addresses to your allowlist
Server firewalls, host WAF rules, Cloudflare, ModSecurity, Imunify360, and security plugins can block Kadence infrastructure even when your own computer can SSH in successfully.
Kadence Backups (SSH from Kadence servers)
Add these IPs on your server firewall (and anywhere else that filters inbound SSH):
207.246.255.233207.246.255.133
Kadence Central (site connection and API)
If Central connection or backups both fail, also allowlist Kadence Central IPs used for WordPress API traffic:
207.246.254.118207.246.255.233207.246.255.133207.246.255.60
The full list and context (user-agent, ports) are in Tips for troubleshooting Kadence Central.
ConfigServer Security & Firewall (CSF) in WHM
If ConfigServer Security & Firewall is running in WHM:
- Navigate to Plugins → ConfigServer Security & Firewall.
- Scroll to the csf – Quick Actions section.
- Enter this IP into the Allow IP address box next to Quick Allow:
207.246.255.233 - (Optionally) Add a comment for future reference.
- Click Quick Allow to add the rule.
- Repeat steps 3–5 using this IP:
207.246.255.133
Allowlist the Kadence Central IPs above the same way if Central connectivity is blocked.
If firewall rules are managed differently on the server, add the same IP addresses using your host’s documented allowlist method.
Cloudflare vs server firewall
Cloudflare WAF (or similar) filters web traffic before it reaches your server, while a server-level firewall manages direct access to your server. Using both is recommended when applicable.
Allowlisting in Cloudflare lets trusted IPs bypass the WAF and/or DDoS protections in place, while allowlisting on the server provides the fine-grained control that Kadence Backups needs for direct SSH access.
If ModSecurity logs show blocked requests related to Kadence, rule 225170 has been reported on some hosts; your host may need to adjust that rule or allow Kadence IPs. See Kadence Backups FAQs and Tips for troubleshooting Kadence Central.
After server configuration
- Return to Getting Started with Kadence Backups and complete Step 3: Connecting to Your WordPress Host.
- Click Test Server Connection.
- When the test succeeds, confirm the first backup on Timeline in Kadence Central. See Managing Your Kadence Backups.
Running into more issues? These links may help you: