Error map
serviceusage Caller does not have required permission to use project: serviceusage.services.use
Google Cloud / Firebase · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (10). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (10)
BigQuery: Access Denied: Project my-project: User does not have bigquery.jobs.create permission in project my-project
The principal can read data but is not allowed to run query jobs in the project used for billing.
Cloud Run: Error: Forbidden — Your client does not have permission to get URL / from this server
The Cloud Run service requires authentication and the caller has no valid identity token or the `roles/run.invoker` role.
gcloud/ADC: WARNING: Your active project does not match the quota project in your local Application Default Credentials file
Application Default Credentials bill API usage to a different project than the one you have set as active, which can cause surpri…
Google Cloud: 403 PERMISSION_DENIED — Permission 'storage.objects.get' denied on resource (or it may not exist)
The caller's identity lacks the IAM permission named in the message on that resource.
Google Cloud: 403 SERVICE_DISABLED — Cloud Resource Manager API has not been used in project 123456 before or it is disabled. Enable it by visiting
The Google API you called is not enabled for the project that the request is billed to.
Cloud Storage 400: Bucket is a requester pays bucket but no user project provided
The bucket bills access to the requester, so requests must name a project to charge.
Cloud Run deploy failed: Permission denied on secret (secretmanager.versions.access)
The service account can't read the secret that is mounted as an env var or volume.
invalid_grant: Token has been expired or revoked (application default credentials)
The stored refresh token no longer works, so library calls fail until you log in again.
Cloud Build: build failed — service account lacks permission to write logs or access resources
Since the default Cloud Build service account changed, builds fail with permission errors for logs, Artifact Registry or deploy s…
Compute Engine Metadata server unavailable: Failed to retrieve credentials from the metadata server
Code expecting a GCE/Cloud Run metadata server (169.254.169.254) is running somewhere that doesn't have one.
Two steps away (30)
GCP: FAILED_PRECONDITION: Key creation is not allowed on this service account (constraints/iam.disableServiceAccountKeyCreation)
An organisation policy forbids creating downloadable JSON keys for service accounts.
gcloud: ERROR: (gcloud.auth.print-access-token) There was a problem refreshing your current auth tokens: Reauthentication failed. cannot prompt during non-interactive execution
Your cached Google credentials expired or require a fresh login (session control or password change), and gcloud can't prompt.
Google Cloud: 403 This API method requires billing to be enabled. Please enable billing on project and retry
The project has no active billing account, and the API/service needs one.
Cloud Run: 503 Service Unavailable — The request was aborted because there was no available instance
Cloud Run could not serve the request: no instance was ready, instances crashed, or the service hit its max-instances/concurrency…
Cloud Run: Memory limit of 512 MiB exceeded with 530 MiB used. Consider increasing the memory limit
The container used more memory than the Cloud Run service allows, so the instance was terminated.
Cloud Run: 504 Gateway Timeout — The request has been terminated because it has reached the maximum request timeout
The request ran longer than the service's request timeout (default 5 minutes, max 60), so Cloud Run closed it.
Google Cloud: Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started
The Google client library found no Application Default Credentials (ADC) on this machine or environment.
GKE/Kubernetes: Pod unschedulable — 0/3 nodes are available: 3 Insufficient cpu
The scheduler found no node with enough free CPU/memory for the pod's resource requests.
kubectl: error: executable gke-gcloud-auth-plugin not found — it looks like you are trying to use a client-go credential plugin that is not installed
kubectl needs the `gke-gcloud-auth-plugin` binary to authenticate to GKE, and it is missing from PATH.
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
The docker CLI can’t talk to the Docker engine — it isn’t running, or your user can’t access the socket.
OAuth 2.0 Error: invalid_scope / insufficient_scope
The requested scope is unknown or not allowed for this client — or the token lacks the scope the API endpoint requires.
Error: listen EACCES: permission denied 0.0.0.0:80
Node isn’t allowed to bind that port — ports below 1024 need root on Linux/macOS, and some Windows ports are reserved.
Service has no endpoints (no endpoints available for service / Endpoints: <none>)
The Service’s selector matches no ready pods, so traffic to it is refused or returns 503.
spec.ports[0].nodePort: Invalid value: 80: provided port is not in the valid range. The range of valid ports is 30000-32767
A NodePort Service asked for a port outside the cluster’s NodePort range (default 30000–32767).
Context.startForegroundService() did not then call Service.startForeground() / ForegroundServiceStartNotAllowedException
A foreground service didn’t call startForeground() within a few seconds, or the app tried to start one from the background where…
Cloud Storage: 403 Forbidden — user@example.com does not have storage.objects.get access to the Google Cloud Storage object
The identity making the request has no read permission on that bucket or object.
Firebase CLI: Error: Your project my-app must be on the Blaze (pay-as-you-go) plan to complete this command. Required API cloudbuild.googleapis.com can't be enabled until the upgrade is complete
Deploying Cloud Functions needs the Blaze plan because it relies on Cloud Build and Artifact Registry.
Cloud Storage resumable upload failed: session expired (410 Gone) or 404 Not Found on session URI
A resumable upload session URI is no longer valid, so the rest of the file can't be uploaded.
AWS: Unable to locate credentials / Could not load credentials from any providers
The AWS CLI/SDK found no credentials in any place it looks — env vars, profile files, SSO cache or an instance/task role.
Secret Manager: 7 PERMISSION_DENIED: Permission 'secretmanager.versions.access' denied for resource 'projects/123/secrets/db-pass/versions/latest'
The calling identity lacks the Secret Accessor role on that secret, or the secret/version does not exist.
Terraform: Error: creating EC2 Instance: UnauthorizedOperation: You are not authorized to perform this operation. User: arn:aws:iam::123:user/ci is not authorized to perform: ec2:RunInstances
The IAM identity used by Terraform lacks a permission needed for that resource.
Azure AD (Entra ID): AADSTS700016 Application not found in the directory
The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.
OAuth 2.0 Error: invalid_grant
The authorization code, refresh token or credentials sent to the token endpoint are invalid, expired, already used or were issued…
OAuth Error: redirect_uri_mismatch
The redirect URI in your OAuth request doesn’t exactly match one registered for the client in the provider’s console.
Cloud Build: ERROR: build step 2 "gcr.io/cloud-builders/npm" failed: step exited with non-zero status: 1
One step of the Cloud Build pipeline returned a non-zero exit code, so the whole build failed.
Docker push: denied: Permission "artifactregistry.repositories.uploadArtifacts" denied on resource "projects/p/locations/l/repositories/r"
Your identity cannot push or pull images in that Artifact Registry repository, or Docker isn't authenticated to the registry host.
Permission iam.serviceAccounts.getAccessToken denied (service account impersonation)
You tried to impersonate a service account without the Service Account Token Creator role on it.
AWS: ExpiredToken — The security token included in the request is expired
Temporary AWS credentials (STS/SSO/assumed role) have expired.
AWS: SignatureDoesNotMatch / InvalidClientTokenId — the request signature we calculated does not match
AWS rejected the request signature — wrong secret key, wrong region, clock skew, or a presigned URL used differently from how it…
UnrecognizedClientException: The security token included in the request is invalid
The access key or session token isn’t recognised — wrong/deleted key, a session token missing for temporary credentials, or a reg…
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError