Error map
CORS: No Access-Control-Allow-Origin (Cloud Storage) Browser: Access to fetch at 'https://storage.googleapis.com/bucket/file' from origin 'https://app.example.com' has been blocked by CORS policy
Google Cloud / Firebase · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (11). 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 (11)
Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition
The kubelet couldn’t mount one of the pod’s volumes, so the pod stays in ContainerCreating.
PersistentVolumeClaim stuck in Pending (no persistent volumes available / waiting for first consumer)
The PVC hasn’t been bound to a volume, so pods using it can’t be scheduled.
Multi-Attach error for volume: Volume is already exclusively attached to one node and can't be attached to another
A ReadWriteOnce volume (EBS, Azure Disk, PD) is still attached to another node, so the new pod on a different node can’t use it.
INSTALL_FAILED_INSUFFICIENT_STORAGE: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
The device or emulator doesn’t have enough free internal storage to install the APK.
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.
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.
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…
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.
Cloud Storage: 404 Not Found — The specified bucket does not exist / No such object: bucket/object
The bucket or object name in your request doesn't exist (typo, deleted, wrong project, or a leading slash issue).
Cloud Storage: SignatureDoesNotMatch — The request signature we calculated does not match the signature you provided
A signed URL was generated with different parameters than the request used (headers, method, content type, host, expiry or clock…
Firebase Storage: Firebase Storage: User does not have permission to access 'images/photo.jpg'. (storage/unauthorized)
Firebase Security Rules for Cloud Storage denied the request for this path and user.
Two steps away (27)
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
You’re accessing blob/queue data with Microsoft Entra ID, but the identity has only management roles (Owner/Contributor) — not a…
Kubernetes: CreateContainerConfigError — secret / configmap not found
Kubernetes can’t build the container’s configuration — usually a referenced Secret, ConfigMap or key doesn’t exist in that namesp…
Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available
The scheduler can’t find a node that satisfies the pod’s resource requests, selectors, taints or volume constraints.
QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value exceeded the quota
localStorage/sessionStorage is full (about 5 MB per origin) or storage is disabled.
MySQL ERROR 126 (HY000): Incorrect key file for table; try to repair it
MySQL can’t use a table’s index file — usually a full tmp disk during a query, or MyISAM corruption.
Stack is in ROLLBACK_COMPLETE state and can not be updated
The stack’s first creation failed and rolled back; a stack in ROLLBACK_COMPLETE can only be deleted, not updated.
CloudFormation stack in UPDATE_ROLLBACK_FAILED
An update failed, and then the rollback also failed, leaving the stack stuck until you continue the rollback.
Elastic Beanstalk: Environment health has transitioned from Ok to Severe
Most instances in the Elastic Beanstalk environment are failing health checks or returning errors.
Android: INSTALL_FAILED_UPDATE_INCOMPATIBLE
An app with the same package name but a different signing key is already installed on the device.
MySQL ERROR 1114 (HY000): The table 'x' is full
MySQL couldn’t extend the table — disk full, a size limit, or a MEMORY table hitting max_heap_table_size.
ERROR: could not extend file "base/…": No space left on device
The disk holding the PostgreSQL data directory (or WAL) is full.
denied: requested access to the resource is denied (docker push)
You’re logged in, but not allowed to push to that repository — usually the image isn’t tagged with your own username/organisation.
Cloud Run: Revision 'svc-00005' is not ready — Image 'gcr.io/proj/app:latest' not found / Permission 'artifactregistry.repositories.downloadArtifacts' denied
Cloud Run cannot pull the container image — it doesn't exist, the tag is wrong, or the service identity lacks access to the regis…
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.
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…
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.
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: 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.
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.
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.
Firebase Auth: auth/invalid-credential (auth/wrong-password, auth/user-not-found, auth/invalid-login-credentials)
Firebase rejected the email/password sign-in — wrong password, no such user, or a provider credential that’s malformed/expired.
Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
Firestore Security Rules denied the read/write — the user isn’t signed in, the rule conditions don’t match, or test-mode rules ex…
Firebase CLI: Error: Authentication Error: Your credentials are no longer valid. Please run firebase login --reauth
The Firebase CLI's saved login expired or was revoked.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError