Use the connection details issued for the customer’s PD Cloudflare R2 service to connect an S3-compatible application. The customer does not need the host’s Cloudflare account API token.

Collect the service details

1. Open the intended service in the WHMCS client area.
2. Open its storage Information or Connection details view.
3. Note the full S3 endpoint and exact bucket name.
4. Obtain the service access key ID and secret privately.
5. Review the Connect section for the tool’s suggested settings.

Keep secrets out of screenshots, tickets and shared configuration files. Do not rotate a working application’s credentials merely to redisplay them after a refused reveal action.

Configure the application

Select an S3-compatible destination, use the complete issued endpoint and service credential pair, and enable path-style addressing where requested. Use auto for the S3 signing region when the application requires it. A regional placement hint is not that signing-region value.

For EU services, preserve the EU endpoint. Do not substitute the host account ID, master token or a public/custom download domain for the issued connection details. The customer credential is restricted to the service’s allowed buckets.

Verify the intended operation

Choose a harmless test object and verify the application can perform the operations needed for its purpose. A successful connection alone does not prove a backup can be restored. Check the service’s access mode if listing or downloads work but uploads fail.

For authentication errors, compare the full current pair, endpoint, bucket and application signing settings. Credential rotation changes the secret and requires updating each tool; see the rotation guide. Never send a secret or signed storage URL in a support ticket.

See the PD Cloudflare R2 WHMCS guide for related tasks, or explore the module.