Use Test Connection to investigate the saved Google Cloud credential without creating a database instance. Record the exact redacted result so you can identify which stage needs attention.

Identify the account and test

Open PD Modules → GC MySQL and choose Test Connection after saving the provider account. This module-level action uses the first active saved account for the module; it does not check every account or automatically follow the last product, package or service viewed.

The check authenticates using the saved JSON key and reads the instance list in the project identified by that key. Success confirms that read worked. It is not a test of instance creation, billing readiness, quota, regional capacity or database sign-in.

Review the reported condition

1. For a missing or invalid credential, check that the complete JSON was saved on the intended account. Use the original JSON key rather than just a project ID, email or private-key fragment.
2. For an authentication error, ask the project administrator to check the service account and key’s current status. A copied key can be revoked or replaced independently of the saved module record.
3. For a disabled-API message, review Cloud SQL Admin API in the intended project. An API-enabled state in another project does not resolve this connection.
4. For 403 or a permission-denied message, have the administrator check the named service account’s role and project scope. Review the actual error rather than assuming every 403 has one cause.
5. For a billing message during provisioning, have the project administrator inspect the target project’s billing status. The read-only connection check alone does not establish that provisioning is permitted.
6. For a reachability error, review outbound HTTPS from the billing-system host to Google’s authentication and Cloud SQL endpoints. Do not disable certificate validation to clear a connection error.

Handle key-creation policy separately

A policy preventing a new key from being created is an administrator decision, separate from a successful read using a key that already exists. Ask the organisation administrator to assess the module’s JSON-key requirement and any approved project exception. Do not apply a broad policy change merely because an error message suggests one.

Confirm the result without duplicate provisioning

After resolving the reported issue, repeat the relevant connection check and review the intended offering’s account assignment. If an earlier activation has an uncertain outcome, reconcile the existing service and provider result before creating another instance.

Keep credential JSON, private keys, database passwords and full customer records out of shared screenshots.

See the PD Google Cloud MySQL Blesta guide for related setup, or explore PD Google Cloud MySQL.