cPanel/WHM Backup Destination Not Working? Fix Google Drive, S3, FTP & Rsync Errors

In WHM, go to Backup → Backup Configuration → Additional Destinations, locate your destination, and click Save and Validate Destination. This writes and removes a test file.

From the command line, you can also trigger the full backup transport manually:

/usr/local/cpanel/bin/backup --force 2>&1 | tee /tmp/backup_test.log

grep -i "error\|fail\|warn\|timeout" /usr/local/cpanel/logs/cpbackup_transporter.log | tail -50

Common error patterns and what they mean:

• Connection timed out — firewall blocking the port, or timeout value too low
• Authentication failed — wrong credentials, expired token, or IAM permission missing
• No space left on device — destination storage is full
• SSL certificate verify failed — TLS mismatch on custom S3 endpoints
• Permission denied — the remote user lacks write access to the target directory

In WHM → Backup Configuration → Additional Destinations, click Edit on your Google Drive destination. Click Generate Credentials — a new browser tab opens to re-authorize. Complete the OAuth flow and save.

Go to Google Cloud Console → APIs & Services → Credentials. Confirm the OAuth 2.0 Client ID you used still exists and the Google Drive API is enabled for that project.

The folder name you specified in WHM must exist inside the Google Drive of the authorized account. If the folder was renamed or deleted, WHM cannot write to it.

# Google Drive storage — check available space
# WHM does not pre-check destination quota; it fails mid-transfer if full
# Use the Google account's Storage page to verify free space

The IAM user needs at minimum:

{
  "Effect": "Allow",
  "Action": ["s3:PutObject","s3:GetObject","s3:DeleteObject","s3:ListBucket"],
  "Resource": ["arn:aws:s3:::your-bucket-name","arn:aws:s3:::your-bucket-name/*"]
}

Test from the server command line with the AWS CLI:

aws s3 ls s3://your-bucket-name --region us-east-1

If this fails, the problem is IAM — not WHM.

AWS signatures are time-sensitive. A clock drift >5 minutes causes authentication failures:

timedatectl status
# If not synchronized:
systemctl restart chronyd   # or: ntpdate -u pool.ntp.org

A bucket name containing a dot (e.g. my.backup.bucket) breaks path-style S3 requests and causes SSL errors. Rename the bucket using only lowercase letters, numbers, and hyphens.

For non-AWS S3 providers, set the S3 URL field in WHM to the custom endpoint. Example for Wasabi:

s3.wasabisys.com

For Backblaze B2:

s3.us-west-004.backblazeb2.com

Leave the region field matching the bucket's actual region. Test SSL:

openssl s_client -connect s3.wasabisys.com:443 -servername s3.wasabisys.com < /dev/null

ftp -n <<EOF
open YOUR_FTP_HOST 21
user YOUR_FTP_USER YOUR_FTP_PASS
pwd
bye
EOF

If this fails, the problem is network connectivity or credentials — not WHM.

Active FTP (PORT mode) is blocked by most firewalls. In WHM → Backup Configuration → your FTP destination, ensure Passive FTP is checked.

WHM uses an SSH key pair for SFTP destinations. Generate the key and copy it to the remote server:

# Generate key on the cPanel server (as root)
ssh-keygen -t rsa -b 4096 -f /root/.ssh/cpanel_backup_key -N ""

# Copy public key to remote server
ssh-copy-id -i /root/.ssh/cpanel_backup_key.pub user@remote-host

# Test the connection
ssh -i /root/.ssh/cpanel_backup_key user@remote-host "echo OK"

In WHM's SFTP destination config, enter the full path to the private key file.

ssh user@remote-host "ls -la /path/to/backup/dir"
# The FTP/SFTP user must own or have write access to the target directory

ssh -i /root/.ssh/id_rsa root@REMOTE_HOST "echo SSH OK"

If this fails, check:

• SSH port (default 22 — confirm in WHM destination config)
• Remote server firewall allows connections from this server's IP
• The public key is in ~/.ssh/authorized_keys on the remote

# On the cPanel server
which rsync && rsync --version

# On the remote server
ssh root@REMOTE_HOST "which rsync && rsync --version"

In WHM → Backup Configuration → your rsync destination, increase the Timeout value. For servers with 50+ cPanel accounts, set it to at least 7200 seconds (2 hours).

If WHM logs show unable to prune transport, the remote directory has permission issues. Fix:

ssh root@REMOTE_HOST "chown -R cpanel_backup_user:cpanel_backup_user /backup/path && chmod -R 755 /backup/path"