Error map

SecretNotFound Key Vault: (SecretNotFound) A secret with (name/id) x was not found in this key vault

Azure · layer 6, Platform & cloud

Open the full error page →

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.

SecretNotFound — Key Vault: (SecretNotFound) A secret with (name/id) x was not found in this key vault (Azure)SecretNotFo…Key Vault Forbidden — Key Vault: (Forbidden) The user, group or application does not have secrets get permission on key vault (Azure)Key Vault ForbiddenCreateContainerConfigError — Kubernetes: CreateContainerConfigError — secret / configmap not found (Kubernetes)CreateContainerConf…ResourceInitializationError — ECS: ResourceInitializationError: unable to pull secrets or registry auth (AWS)ResourceInitializat…AADSTS50020 — AADSTS50020: User account from identity provider does not exist in tenant and cannot access the application (Azure)AADSTS50020AADSTS7000222 — AADSTS7000222: The provided client secret keys for app are expired (Azure)AADSTS7000222AADSTS500113 — AADSTS500113: No reply address is registered for the application (Azure)AADSTS500113ResourceNotFound — ResourceNotFound: The Resource 'Microsoft.X/...' under resource group 'y' was not found (Azure)ResourceNotFoundEACCES — npm ERR! code EACCES — permission denied (npm)EACCESdaemon — Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (Docker)daemon403 — HTTP 403 Forbidden (HTTP)403CrashLoopBackOff — Kubernetes: CrashLoopBackOff (Kubernetes)CrashLoopBackOffKeyError — KeyError: 'x' (Python)KeyErrorFailedScheduling — Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available (Kubernetes)FailedSchedulingAccessDenied — AWS S3: AccessDenied (403) when calling GetObject / PutObject (AWS)AccessDeniedIAM AccessDeniedException — AccessDeniedException: User: arn:aws:iam::... is not authorized to perform: service:Action on resource: ... (AWS)IAM AccessDeniedExc…sts:AssumeRole denied — is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::...:role/... (AWS)sts:AssumeRole deni…AADSTS700016 — Azure AD (Entra ID): AADSTS700016 Application not found in the directory (Azure)AADSTS700016AADSTS50126 — AADSTS50126: Error validating credentials due to invalid username or password (Azure)AADSTS50126AADSTS65001 — AADSTS65001: The user or administrator has not consented to use the application (Azure)AADSTS65001invalid_client — OAuth 2.0 Error: invalid_client (Authentication)invalid_clientAADSTS50034 — AADSTS50034: The user account does not exist in the directory (Azure)AADSTS50034AADSTS50053 — AADSTS50053: Your account is locked (Smart Lockout) / sign-in blocked due to suspicious activity (Azure)AADSTS50053invalid_grant — OAuth 2.0 Error: invalid_grant (Authentication)invalid_grantredirect_uri_mismatch — OAuth Error: redirect_uri_mismatch (Authentication)redirect_uri_mismat…invalid_scope — OAuth 2.0 Error: invalid_scope / insufficient_scope (Authentication)invalid_scopeEvicted — Kubernetes: Pod Evicted — The node was low on resource: memory / ephemeral-storage (Kubernetes)Evictedexceeded quota — Error creating: pods is forbidden: exceeded quota: compute-resources, requested: limits.memory=1Gi, used: ..., limited: ... (Kubernetes)exceeded quotamust specify limits — pods is forbidden: failed quota: must specify limits.cpu,limits.memory,requests.cpu,requests.memory (Kubernetes)must specify limits

Directly related (7)

Key Vault ForbiddenAzure

Key Vault: (Forbidden) The user, group or application does not have secrets get permission on key vault

The caller authenticated but has no permission on the vault — missing access policy or RBAC role, or the vault’s firewall blocks…

CreateContainerConfigErrorKubernetes

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…

ResourceInitializationErrorAWS

ECS: ResourceInitializationError: unable to pull secrets or registry auth

Fargate couldn’t fetch the task’s secrets (Secrets Manager/SSM) or registry credentials before starting containers.

AADSTS50020Azure

AADSTS50020: User account from identity provider does not exist in tenant and cannot access the application

The signed-in user belongs to another tenant (or is a personal Microsoft account) and isn’t a guest in the app’s tenant.

AADSTS7000222Azure

AADSTS7000222: The provided client secret keys for app are expired

The app registration’s client secret has expired, so service-to-service authentication fails.

AADSTS500113Azure

AADSTS500113: No reply address is registered for the application

The app registration has no redirect URI for the platform being used, so Entra ID has nowhere to send the response.

ResourceNotFoundAzure

ResourceNotFound: The Resource 'Microsoft.X/...' under resource group 'y' was not found

The specific resource doesn’t exist in that resource group/subscription — wrong name, group or subscription, or it was deleted.

Two steps away (21)

EACCESnpm

npm ERR! code EACCES — permission denied

npm can’t write to a directory — usually global installs into a root-owned folder.

daemonDocker

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.

403HTTP

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…

CrashLoopBackOffKubernetes

Kubernetes: CrashLoopBackOff

The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.

KeyErrorPython

KeyError: 'x'

You accessed a dictionary key that doesn’t exist.

FailedSchedulingKubernetes

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.

AccessDeniedAWS

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.

IAM AccessDeniedExceptionAWS

AccessDeniedException: User: arn:aws:iam::... is not authorized to perform: service:Action on resource: ...

The IAM user or role making the call has no permission for that action on that resource — the message names both.

sts:AssumeRole deniedAWS

is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::...:role/...

The caller can’t assume the role — either its own policy doesn’t allow sts:AssumeRole, or the role’s trust policy doesn’t trust t…

AADSTS700016Azure

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.

AADSTS50126Azure

AADSTS50126: Error validating credentials due to invalid username or password

Microsoft Entra ID (Azure AD) rejected the sign-in because the username or password is wrong — or the flow can’t use passwords fo…

AADSTS65001Azure

AADSTS65001: The user or administrator has not consented to use the application

The app needs permissions that haven’t been granted for this user or tenant.

invalid_clientAuthentication

OAuth 2.0 Error: invalid_client

The OAuth server couldn’t authenticate your application — wrong client ID/secret, wrong auth method, or the client doesn’t exist…

AADSTS50034Azure

AADSTS50034: The user account does not exist in the directory

There’s no user with that sign-in name in the tenant.

AADSTS50053Azure

AADSTS50053: Your account is locked (Smart Lockout) / sign-in blocked due to suspicious activity

Too many failed sign-ins (or sign-ins from a malicious IP) triggered Entra Smart Lockout.

invalid_grantAuthentication

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…

redirect_uri_mismatchAuthentication

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.

invalid_scopeAuthentication

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.

EvictedKubernetes

Kubernetes: Pod Evicted — The node was low on resource: memory / ephemeral-storage

The kubelet removed the pod because its node ran short of memory or disk.

exceeded quotaKubernetes

Error creating: pods is forbidden: exceeded quota: compute-resources, requested: limits.memory=1Gi, used: ..., limited: ...

The namespace’s ResourceQuota doesn’t have room for the new pod’s requests/limits (or object count).

must specify limitsKubernetes

pods is forbidden: failed quota: must specify limits.cpu,limits.memory,requests.cpu,requests.memory

A ResourceQuota on the namespace covers CPU/memory, so every pod must declare those requests/limits — and this one doesn’t.