Connecting Storivo to WHM/cPanel or Plesk

Both WHM/cPanel and Plesk support S3-compatible storage as a remote backup destination out of the box, which means Storivo works without a plugin or custom script; you just need an endpoint, an access key, and a bucket.

Before you start

Have these ready from your Storivo account:

• Access key ID and secret access key
• Your region's endpoint (for example https://s3.storivo.com)
• The name of the bucket you want backups written to

WHM/cPanel setup

1. In WHM, go to Backup Configuration and enable backups if you haven't already.
2. Under Additional Destinations, choose Amazon S3 Compatible as the destination type.
3. Enter a name for the destination, then your Storivo access key, secret key, bucket name and endpoint (uncheck "Use SSL" only if instructed otherwise; Storivo requires SSL).
4. Click Save and Validate Destination: WHM will attempt a test upload to confirm the credentials and bucket are reachable.
5. Once validated, assign the destination to your backup schedule under Backup Configuration → Additional Destinations, and set retention/frequency as normal.

Plesk setup

1. Go to Tools & Settings → Backup Manager → Remote Storage Settings.
2. Choose Amazon S3 as the storage type (Plesk's S3 connector accepts any S3-compatible endpoint, not only AWS).
3. Enter your Storivo endpoint in the custom endpoint field, along with your access key, secret key and bucket name.
4. Save, then run a manual backup to confirm the connection before relying on the schedule.
5. Set your backup schedule and retention under Backup Manager → Scheduled Backup Settings, selecting the Storivo remote storage you just configured.

Hosting companies: use a sub-account per client

If you're an MSP or hosting company running this setup across multiple client servers, create a separate Storivo sub-account (and access key) per client rather than reusing one set of credentials everywhere. That way a leaked key on one server can't expose every client's backups. See the white-labeling guide for the full sub-account setup.

Troubleshooting a failed validation

• "Access Denied": double-check the access key and secret were copied without extra whitespace, and that the key has write permission on the target bucket.
• "Could not resolve endpoint": confirm the endpoint URL includes https:// and matches your account's region.
• "Bucket not found": bucket names are case-sensitive; confirm it matches exactly what's shown in your Storivo dashboard.