TROUBLESHOOTING
Find the broken step.
Keep the working parts.
Use the message on the screen and verify one stage at a time.
Google sign-in was cancelled
Return to WordPress and start Sign in with Google again. A cancelled authorization does not mean your existing media bucket has been deleted.
The pairing code was not recognized
Check the code for a typo and use the original site and user session that started sign-in. A code may already have been redeemed or expired. If retrying fails, begin a fresh sign-in and use the new code.
The project or bucket is missing
Confirm the selected Google account and project. Search by name or ID. Listing permissions may differ from access to a known bucket; the exact-name field can help when you already know the correct bucket.
Billing or provisioning failed
Verify active project billing, API availability, service-account permissions, and organization policies. Preserve the actual error when requesting help. Never include a private key or authorization code in a support post.
Upload works, but the image is broken
Check the file URL while logged out, the object’s public access, bucket name, and root directory. Confirm both the original and thumbnail objects exist. A private object or incorrect custom domain can produce a broken image even when upload succeeded.
A custom media domain does not work
DNS alone does not configure HTTPS delivery for a custom domain. Check the certificate, load balancer or CDN, origin configuration, and object paths. First verify the Google Cloud object URL independently.
A plugin expects files on disk
Use CDN mode to retain local copies while investigating compatibility. Check the addon directory and test the workflow on staging before using a mode that removes local media.