Error map
toomanyrequests toomanyrequests: You have reached your pull rate limit (Docker Hub)
Docker · 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)
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.
remote: Permission to owner/repo.git denied to github-actions[bot]. fatal: unable to access … The requested URL returned error: 403
A GitHub Actions workflow tried to push but the GITHUB_TOKEN doesn’t have write permission.
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json are in sync
package-lock.json doesn’t match package.json, so npm ci refuses to install.
Firebase Auth: auth/too-many-requests — Access to this account has been temporarily disabled due to many failed login attempts
Firebase throttled sign-in or SMS verification because of too many attempts from the device/IP or for the account.
Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress
A previous Helm operation on this release was interrupted and left it in a pending-install/pending-upgrade state, so Helm refuses…
pull access denied for image, repository does not exist or may require 'docker login'
Docker couldn’t pull the image: the name or tag is wrong, the repository is private and you’re not logged in, or it doesn’t exist…
Cosmos DB 429: Request rate is large (TooManyRequests, RU/s exceeded)
The container or database used more Request Units per second than provisioned, so Cosmos DB throttled requests.
HTTP 429 Too Many Requests
You’ve hit a rate limit — too many requests in a given time window. Slow down and retry later.
CloudFormation: No updates are to be performed
You ran an update/deploy with a template and parameters identical to what’s deployed, so there’s nothing to change.
Kubernetes: ImagePullBackOff / ErrImagePull
The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachable.
ProvisionedThroughputExceededException: The level of configured provisioned throughput for the table was exceeded
Requests exceed the table’s (or index’s) provisioned read/write capacity, or one partition is hot.
manifest for image:tag not found: manifest unknown
The repository exists, but the tag you asked for doesn’t — it was never pushed, was deleted, or is misspelled.
Two steps away (34)
Git: ! [rejected] … (fetch first) — error: failed to push some refs
The remote branch has commits you don’t have locally, so Git refuses to overwrite them. Pull (merge or rebase) first, then push.
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.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
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…
remote: error: GH006: Protected branch update failed / pre-receive hook declined
The server rejected your push because of branch protection rules or a server-side hook.
! [remote rejected] main -> main (shallow update not allowed)
You pushed from a shallow clone to a remote that doesn’t accept shallow history.
npm ERR! code EINTEGRITY — sha512 integrity checksum failed
A downloaded package’s hash doesn’t match the integrity value in package-lock.json — a corrupted cache, a changed tarball, or a l…
npm ERR! The `npm ci` command can only install with an existing package-lock.json or npm-shrinkwrap.json
npm ci needs a committed lockfile and didn’t find one.
npm WARN old lockfile — The package-lock.json file was created with an old version of npm, so supplemental metadata must be fetched
The lockfile is lockfileVersion 1 (npm 6) and npm 7+ is upgrading it.
AWS: ThrottlingException / Rate exceeded
You exceeded the request rate for an AWS API; retry with exponential backoff.
API Error: Too many concurrent requests (concurrency limit reached)
You have more requests in flight at once than the API allows for your key — even if your requests-per-minute rate is fine.
S3 SlowDown: Please reduce your request rate (503)
S3 is throttling requests to a prefix because the request rate is above what it can currently serve.
the input device is not a TTY
docker run/exec was called with -t (allocate a terminal) in a context with no terminal — CI, cron, a pipe or a script.
Error: INSTALLATION FAILED: cannot re-use a name that is still in use
helm install was run with a release name that already exists in the namespace (even a failed one).
rendered manifests contain a resource that already exists. Unable to continue with install: ... invalid ownership metadata
Helm wants to create an object that already exists but isn’t labelled as belonging to this release.
denied: Your authorization token has expired. Reauthenticate and try again. (Amazon ECR)
Docker’s login to Amazon ECR has expired — ECR tokens last 12 hours, so pushes and pulls fail until you log in again.
no matching manifest for linux/arm64/v8 in the manifest list entries
The image has no build for your CPU architecture — typically pulling an amd64-only image on an Apple Silicon Mac or ARM server.
unauthorized: authentication required (docker push / pull)
The registry needs credentials for this operation and the request had none or had expired ones.
Cloudflare Error 1015: You are being rate limited
The site’s Cloudflare rate-limiting rule blocked you for sending too many requests in a short time.
HTTP 503 Service Unavailable
The server is temporarily unable to handle the request — overloaded, in maintenance, or has no healthy backends.
Cloudflare Error 1020: Access Denied
A Cloudflare firewall/WAF custom rule blocked the request — the visitor’s IP, country, user agent or request pattern matched a bl…
HTTP 507 Insufficient Storage
The server can’t store what’s needed to complete the request — the disk, quota or mailbox is full.
ERR_PNPM_OUTDATED_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with package.json
pnpm’s lockfile doesn’t match package.json, and CI installs with a frozen lockfile.
YN0028: The lockfile would have been modified by this install, which is explicitly forbidden.
Yarn Berry’s immutable install in CI found the lockfile needs changes.
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.
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
exec /usr/local/bin/docker-entrypoint.sh: exec format error
The container tried to run a binary built for a different CPU architecture (arm64 vs amd64) — or a script with a broken shebang /…
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.
ConditionalCheckFailedException: The conditional request failed
A write’s ConditionExpression evaluated to false, so DynamoDB didn’t perform it — often exactly as designed.
DynamoDB ValidationException: One or more parameter values were invalid: Missing the key pk in the item / The provided key element does not match the schema
The item or key doesn’t match the table’s primary key schema — wrong attribute name, wrong type, or missing sort key.
DynamoDB ResourceNotFoundException: Requested resource not found (table)
The table (or index) doesn’t exist in the region/account the client is using.
Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded)
Docker couldn’t reach the registry in time — a network, DNS, proxy or firewall problem between your machine and the registry.
x509: certificate signed by unknown authority (docker pull/login)
The registry’s TLS certificate isn’t trusted by the Docker daemon — a private CA, self-signed certificate, or a TLS-inspecting co…
http: server gave HTTP response to HTTPS client (insecure registry)
Docker spoke HTTPS to a registry that only serves plain HTTP — typically a local or lab registry.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException