Error map
storage full Cloud SQL instance storage full — instance becomes read-only / suspended
Google Cloud / Firebase · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (12). 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 (12)
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.
Azure Storage: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature (AuthenticationFailed)
The storage request’s signature or SAS token is invalid — wrong/rotated account key, expired SAS, or clock skew.
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…
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.
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.
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.
Cloud SQL: failed to connect to `host=PROJECT:REGION:INSTANCE user=app database=db`: dial error (timeout) / Cloud SQL Auth Proxy: failed to connect to instance
Your app or the Cloud SQL Auth Proxy couldn't open a connection to the instance — IAM, networking or configuration.
ERROR: could not extend file "base/…": No space left on device
The disk holding the PostgreSQL data directory (or WAL) is full.
Browser: Access to fetch at 'https://storage.googleapis.com/bucket/file' from origin 'https://app.example.com' has been blocked by CORS policy
A browser upload/download to Cloud Storage was blocked because the bucket's CORS configuration doesn't allow your origin, method…
StorageAccountAlreadyTaken: The storage account named x is already taken
Storage account names are globally unique across Azure; another customer (or you elsewhere) already uses the name.
Cloud SQL: FATAL: remaining connection slots are reserved / MySQL: ERROR 1040 (08004): Too many connections
The instance's maximum connections was reached, often because serverless instances each open their own connection pool.
Two steps away (36)
net::ERR_BLOCKED_BY_CLIENT
A browser extension (ad blocker, privacy tool) blocked the request.
net::ERR_CONNECTION_REFUSED (This site can't be reached — refused to connect)
The browser reached the host but nothing was listening on that port.
net::ERR_NAME_NOT_RESOLVED (This site can't be reached — server IP address could not be found)
DNS couldn’t resolve the hostname in the browser.
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.
Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required
A Conditional Access policy requires MFA, but the sign-in flow (often a script, legacy client or ROPC password grant) can’t compl…
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…
AWS S3: AccessDenied (403) when calling GetObject / PutObject
An IAM policy, bucket policy, ACL/ownership setting, Block Public Access or KMS key policy denied the S3 request.
HTTP 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
Azure: AuthorizationFailed — The client does not have authorization to perform action
The signed-in identity (user, service principal or managed identity) lacks an Azure RBAC role for that action on that scope.
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
HTTP 503 Service Unavailable
The server is temporarily unable to handle the request — overloaded, in maintenance, or has no healthy backends.
MySQL ERROR 1040 (08004): Too many connections
MySQL reached `max_connections` and refuses new clients.
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.
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
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…
invalid mount config for type "bind": bind source path does not exist
A -v/--mount or Compose volume points at a host path that doesn’t exist (from the Docker daemon’s point of view).
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.
Permission denied writing to a mounted volume inside a Docker container
The process inside the container runs as a user (UID) that doesn’t own the bind-mounted host folder, so reads/writes fail with EA…
Docker Desktop: Mounts denied: The path is not shared from the host and is not known to Docker
Docker Desktop (macOS) can only bind-mount folders listed under Settings → Resources → File sharing.
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.
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…
Azure: SkuNotAvailable / QuotaExceeded when creating a VM or resource
The VM size isn’t offered in that region/zone for your subscription, or you’ve hit the vCPU quota.
FATAL: sorry, too many clients already / remaining connection slots are reserved for non-replication superuser connections
PostgreSQL reached max_connections.
FATAL: too many connections for role "x"
The role reached its per-role CONNECTION LIMIT (often set by hosting providers or free tiers).
INSTALL_FAILED_INSUFFICIENT_STORAGE: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
The device or emulator doesn’t have enough free internal storage to install the APK.
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).
TypeError: 'str' object is not callable
You used parentheses on something that isn’t a function — often a variable shadowing a built-in.
BucketAlreadyExists: The requested bucket name is not available
S3 bucket names are global across all AWS accounts, and someone else already uses this one.
CloudFormation: Resource ... already exists (AlreadyExists / already exists in stack)
The template tries to create a resource with a fixed name that already exists — created manually, by another stack, or left over…
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…
BigQuery: Not found: Dataset my-project:analytics was not found in location EU
BigQuery looked for the dataset in the wrong location (region) or the dataset doesn't exist.
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.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError