Read the detail from Test Connection before treating a saved provider account as ready for VM orders. A successful project read can be accompanied by incomplete permission or quota information.

Identify what was checked

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

The check reads the Compute Engine project, probes selected creation and service-account-use permissions, and tries to read regional CPU quota. It does not create resources. A role probe can be skipped when its API is unreachable, and quota information can be absent without a failed connection.

The default module-level quota detail concerns europe-west2. It is not a quota assessment of every product zone, machine family, disk, IP address or project-wide resource limit.

Review the reported stage

1. For a missing or invalid credential, review the complete original JSON on the intended saved account. A project ID, email or key fragment is insufficient.
2. For an API-disabled message, have the project administrator inspect Compute Engine API in the intended project.
3. For a permission message, have the administrator inspect the exact permission, role and resource scope. The module’s Compute Admin and Service Account User hints do not establish a complete permission audit.
4. If the detail says the role check was skipped, resolve the probe’s reachability or verify permissions independently; do not treat the general success message as proof that those roles were checked.
5. If quota is low or missing, inspect the applicable quota in the actual target region and machine family. CPU headroom in the default test region is insufficient for a different offering.
6. For reachability errors, review outbound HTTPS to Google’s Compute Engine, authentication and permission-check services. Keep certificate verification enabled.

Separate quota from availability

A quota increase can resolve a quota refusal, but does not reserve capacity in the chosen zone. A resource-availability error needs review of the requested machine type and zone rather than repeated quota requests. Google explains quota and resource availability.

The module’s provisioning quota preflight can also proceed if its quota read fails. An absent quota warning is not proof of sufficient quota or successful VM creation.

For an uncertain provisioning attempt, reconcile the existing service and provider resources before creating another server. Do not send credentials or full customer records.

See the PD Google Compute Engine WHMCS guide for related setup, or explore PD Google Compute Engine.