Connect your own Cloudflare account so PD Cloudflare R2 can provision storage for customer services. The host connection uses an account API token; it is separate from each customer’s S3 access key and secret.

Prepare the account credential

Enable R2 on the intended Cloudflare account. Ask its administrator to prepare an account API token with Workers R2 Storage Edit, Account Analytics Read and the account-token management permission Account API Tokens Edit/Write, scoped to that account. Cloudflare’s account-token guidance distinguishes this from managing personal user tokens. A personal-profile token with a similarly named permission is not proof that account-token creation is allowed.

Install PD Modules, connect the account holding your licence and install PD Cloudflare R2 from the Store. Keep the Cloudflare token private.

Save the WHMCS connection

1. Open System Settings → Products/Services → Servers and add a server.
2. Choose PD Cloudflare R2 as its module.
3. Put the Cloudflare Account ID in Username and the account API token in Password.
4. Save, then assign the server to the intended server group. The hostname does not select an R2 endpoint or location.
5. Open PD Cloudflare R2 → Settings → Test Connection and inspect the result.

The panel test checks the first configured account. It reads token permission groups and the bucket list; it creates no bucket or token and does not prove every provisioning or analytics permission. With several accounts, establish which one was checked before relying on a passing result.

For failures, check the account ID, token scope and redacted error. Do not substitute a zone ID or a customer S3 key pair. Use provisioning checks before repeating an uncertain operation.

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