Troubleshoot QCSB Google Drive Connections

This article shows how to diagnose redirect mismatch, invalid client credentials, missing consent, expired/revoked OAuth state, Shared Drive configuration, root-access, and provider API failures.

Troubleshooting procedure

  1. Verify the Google Drive API is enabled and the OAuth consent/application settings permit the intended account.
  2. Compare the Authorized redirect URI in Google Cloud with the exact read-only URI shown by QCSB, including any fixed query string.
  3. Verify Client ID/Secret, account authorization, My Drive vs Shared Drive selection, Shared Drive ID when used, and exact root.
  4. Reconnect the Google account when tokens/consent changed, then run Test Connection.
  5. If the connection works at root but a folder fails, verify the configured exact root and subdirectory setting rather than attempting to traverse a parent.

Verify the result

  • Test Connection succeeds.
  • The displayed/usable root is exactly the intended root and no parent folder is reachable.
  • A normal authorized user can perform only the operations intended for that connection/Workspace role.

Important limits and mistakes to avoid

  • Never broaden a connection root merely to work around a permission or provider error; fix the actual root/credential/hosting problem.

If it still fails

  • Change one variable at a time and repeat the same small test after each correction.
  • Use QCSB sanitized errors/Status/Test Connection before changing unrelated provider or Joomla settings.
  • If the issue remains, collect version, provider type, Workspace/user role, task state where relevant, and sanitized messages for support. Never include secrets.

Community Discussion

For practical QCSB workflows and discussion with other Joomla site owners, visit the QC Storage Bridge Community. For private support, bug reports, account-specific entitlement issues, or feature requests, use the QuantaCade support system.