Solid Backups
Kadence Backups Troubleshooting SSH/SFTP Connection Issues
Coming soon: Solid Backups is becoming Kadence Backups. You may see both names used while we update the product, documentation, and customer experience.
If you’re having trouble establishing an SSH or SFTP connection with Kadence Backups, this guide will walk you through common issues and troubleshooting steps to get you back on track.
Two different “connected” states
Kadence Backups relies on two separate connections:
- Kadence Central ↔ WordPress — The site must be connected to Kadence Central (connector plugin and application password). If this fails, fix Central connection first. See: Tips for troubleshooting Kadence Central and Application Passwords.
- Kadence Backups ↔ your server (SSH/SFTP) — After enrollment, Kadence infrastructure connects to your host with the SSH/SFTP credentials you provide. This article focuses on that server connection, which is required for backups and restores.
Troubleshooting Steps
Many failures are due to incorrect host, port, username, or firewall rules. Work through these in order:
Verify your credentials
Confirm the values in Kadence Central match what your host provides:
- Server address – The hostname or IP (some hosts require the server IP instead of the domain).
- Username – The SSH/SFTP account username (not your WordPress admin login).
- Port – Often
22; some hosts use a custom port (for example SiteGround 18765, VentraIP 2683).
- Authentication – The Public key or password, matching what you chose during enrollment.
Re-enter credentials and run Test Connection in Kadence Central. If you use a password, it must be the server account password for SSH (on many hosts this is the same as SFTP). SSH access must still be enabled on the account.
See Getting Started with Kadence Backups for host-specific credential locations (cPanel, Site Tools, Cloudways, and others).
Confirm SSH/SFTP is enabled and do not use root
Kadence Backups needs non-root SSH or SFTP access with permission to read your WordPress files and run required CLI operations on the account.
- Ask your host to confirm SSH and/or SFTP is enabled for the account you use in Kadence Backups.
- Do not connect as the
rootuser. Kadence Backups does not support root-level SSH access. Use a regular hosting account or a dedicated SSH user your host recommends.
If your host appears on the unsupported or limited list, see Supported And Unsupported Web Hosts before spending time on credential tweaks.
Test your connection manually (optional)
You can verify that SSH/SFTP works from your computer using a client such as Terminal (macOS/Linux), PuTTY (Windows), or FileZilla (SFTP).
Example (adjust username, host, and port):
ssh -p 22 your_username@your_server_hostname_or_ip
A successful login from your machine shows the host allows SSH/SFTP for those credentials. It does not by itself prove Kadence Backups can connect: backups use Kadence infrastructure, not your device.
Use manual testing mainly to rule out “SSH is disabled entirely” or obviously wrong credentials. If manual login works but Kadence Central still fails, continue with firewall allowlisting and application password checks below.
Allowlist Kadence Backups and Kadence Central IPs
Server firewalls, host WAF rules, Cloudflare, ModSecurity, Imunify360, and security plugins can block inbound SSH from Kadence systems even when your own IP can connect.
Kadence Backups connections commonly require these IPs on your server or host firewall allowlist:
207.246.255.233207.246.255.133
Kadence Central (WordPress API and site management) uses a broader set. If Central or backups both fail, allowlist the full Kadence Central list in Tips for troubleshooting Kadence Central:
207.246.254.118207.246.255.233207.246.255.133207.246.255.60
On cPanel servers with ConfigServer Security & Firewall (CSF) in WHM, use Quick Allow or your host’s documented allowlist method for these addresses.
If ModSecurity logs show blocked requests, rule 225170 has been reported to interfere with Kadence Central. Ask your host to allow Kadence IPs or adjust that rule for your domain.
Confirm Application Passwords and the Kadence Central site connection
SSH troubleshooting assumes the site is already connected to Kadence Central.
- Confirm Application Passwords are available on the site (WordPress 5.6+; some security plugins restrict them). See: Application Passwords.
- In WordPress, open Users → Profile and verify an application password exists for Kadence Central (naming may show
Kadenceon current installs; older installs may showSolidWP). - If the site is disconnected from Central, reconnect from the Kadence Central dashboard before re-testing Kadence Backups enrollment.
Kadence Security (formerly Solid Security) and other security plugins can block REST or application password endpoints (See: How to unblock Application Passwords when Kadence Security’s Two-Factor Authentication (2FA) is active). Temporarily adjust relevant settings or allowlist Kadence Central using the troubleshoot Central guide.
Check WP-CLI and non-standard hosting stacks
Kadence Backups uses WP-CLI during backup and restore operations. The wp command must be available to the same Linux user account you connect with over SSH.
Hosts with non-standard WP-CLI setups (for example some Plesk/WP Toolkit layouts) may fail with errors referencing missing wp paths.
See Supported And Unsupported Web Hosts and the Getting Started host sections for known limitations.
Review Timeline errors and contact support
Open the site Timeline in Kadence Central and note the exact error text and any reference number (Kadence Backups errors often look like #123456789:123456).
Also check Settings → Kadence Backups in wp-admin (menu may still say Solid Backups on older installs) for connection status.
If you are still stuck, contact Software Support with:
- Site URL and hosting provider
- Steps you already tried from this guide
- Timeline error message and reference number
- Whether manual SSH/SFTP from your computer succeeds