Error map
source upload Cloud Functions deploy: Could not upload source — storage bucket permission denied
Google Cloud / Firebase · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (7). 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 (7)
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 Functions: Build failed: function.js does not exist / npm install failed with exit code 1 (Cloud Build step)
The deployment's build step (Cloud Build) failed, so no new function version was created.
App Engine deploy failed: invalid app.yaml (runtime not supported / entrypoint / handlers)
`gcloud app deploy` rejects the configuration or the app fails its health check after deploy.
Cloud Functions (2nd gen) deploy failed: Eventarc trigger permission denied
Creating an event-driven function failed because the service account or Eventarc service agent lacks permissions.
Cloud Functions: Error: Cannot find module 'X' (dependency missing at runtime)
The deployed function can't load a module that works locally.
Cloud Functions Python: ModuleNotFoundError: No module named 'X' (requirements.txt)
The deployed Python function imports a package that wasn't installed from requirements.txt.
Request is prohibited by organization's policy — VPC Service Controls perimeter violation
A VPC Service Controls perimeter blocked the API call because the caller is outside the perimeter or not covered by an access lev…
Two steps away (21)
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.
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.
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.
COPY failed: file not found in build context / "/app/x": not found
The Dockerfile COPY refers to a path outside the build context, excluded by .dockerignore, or relative to the wrong directory.
Error: error:0308010C:digital envelope routines::unsupported
An old build tool (webpack 4, old react-scripts) uses a hash algorithm that OpenSSL 3 in Node 17+ disables.
Error: @prisma/client did not initialize yet. Please run "prisma generate"
The generated Prisma Client is missing or out of date.
Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
Cloud Run started your container, but nothing listened on $PORT within the startup timeout — the app crashed, listens on another…
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.
Firebase Hosting deploy: Could not find site / hosting target not configured
`firebase deploy --only hosting` can't resolve the site or target in firebase.json.
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.
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.
Error: Cannot find module 'x' (MODULE_NOT_FOUND)
Node can’t resolve the module path — the package isn’t installed, or a relative path/extension is wrong.
ModuleNotFoundError: No module named 'x'
Python can’t find the module you import — it isn’t installed in the interpreter/virtualenv that’s running, or the import path is…
ImportError: cannot import name 'x' from 'y'
The module was found, but the name you’re importing from it doesn’t exist — usually a version change or a circular import.
Cloud Functions: Provided module can't be loaded / Function failed on loading user code. This is likely due to a bug in the user code
The function started but could not import/initialise your code, so every invocation fails.
Cloud Functions: Function execution took 60002 ms, finished with status: 'timeout'
The function ran past its timeout (default 60s for HTTP 1st gen) and was terminated.
Firebase Functions deploy failed: Node runtime/engine unsupported or build error
`firebase deploy --only functions` fails because of the Node version, dependency or build step.
Error creating: pods is forbidden: violates PodSecurity "restricted:latest": allowPrivilegeEscalation != false ...
The namespace enforces a Pod Security Standard (baseline/restricted) and the pod spec breaks one of its rules.
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! (ssh host key changed)
The server’s SSH host key differs from the one saved in ~/.ssh/known_hosts — usually because the server was rebuilt or the IP was…
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
apt can’t verify a repository’s signature because the repo’s signing key isn’t installed (or has expired/rotated).
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError