Use the stage reported by Test Connection to distinguish a saved credential problem from project access or customer-key creation. This check changes the Google project, so plan it deliberately rather than treating it as a passive status lookup.

Identify the selected account

Open PD Modules → GCS → Settings after reviewing the saved provider account. The module-level test chooses the first active account for this module. With multiple accounts, confirm the intended association without disabling working accounts merely to force selection.

The test lists buckets and then creates a temporary service account and HMAC key. It attempts cleanup afterwards. A success message does not independently establish cleanup, customer bucket permissions or an application’s ability to upload and download.

Resolve the reported stage

1. For missing or invalid credentials, review the entire original JSON and the saved account it belongs to. A project ID or private-key fragment alone is insufficient.
2. For a storage-listing error, have the project administrator inspect the exact Cloud Storage permission, API and project named by the error.
3. For a service-account creation error, have the administrator review IAM access, the project’s current service-account quota and any policy restriction. Do not assume a fixed quota applies to every project.
4. For an HMAC-key error, have the administrator review key-creation permission, authentication restrictions and the organisation’s policy. A successful bucket list does not establish this permission.
5. If a key is newly created, allow its identity and permissions to propagate before judging the result. Repeated tests create additional temporary identities; do not use them as a cleanup process.
6. For reachability failures, review outbound HTTPS to Google’s storage, IAM and authentication services. Keep certificate verification enabled.

Google documents key-creation policy constraints. A blocked policy requires the organisation administrator’s review of the module’s credential requirements and any appropriate scoped exception.

Reconcile temporary credentials and earlier provisioning

If the check fails part-way or cleanup is uncertain, ask the project administrator to inspect the temporary test account and key associated with that attempt. Do not remove customer service accounts or keys based only on a similar name.

If an actual customer activation already has an uncertain result, reconcile its existing bucket and credentials before creating another service. The connection test is not a repair or reactivation control.

Keep all provider keys and customer secrets out of shared screenshots and examples.

See the PD Google Cloud Storage WHMCS guide for related setup, or explore PD Google Cloud Storage.