Error map
AADSTS50034 AADSTS50034: The user account does not exist in the directory
Azure · 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)
Failed to connect to bus: No such file or directory (systemctl --user / timedatectl)
The command needs the D-Bus/systemd bus, which isn’t available in this session — common over su, sudo -u, cron, containers or WSL.
Keycloak: invalid_grant — Account is not fully set up
The user has pending required actions (verify email, update password, configure OTP), so non-interactive token requests (password…
AADSTS50173: The provided grant has expired due to it being revoked, a fresh auth token is needed
The refresh token was revoked — usually because the user changed or reset their password, or an admin revoked sessions.
AADSTS50057: The user account is disabled
The account exists but is blocked from signing in.
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.
InvalidAuthenticationTokenTenant: The access token is from the wrong issuer
The token was issued by a different tenant than the one that owns the subscription/resource.
AADSTS53003: Access has been blocked by Conditional Access policies
Sign-in succeeded, but a Conditional Access policy blocked access — device, location, app or risk conditions weren’t met.
AADSTS50055: The password is expired
The user’s password expired under the tenant/on-prem password policy and must be changed before signing in.
AADSTS700082: The refresh token has expired due to inactivity
A cached refresh token wasn’t used for 90 days (the inactivity limit) and is no longer valid.
passwd: Authentication token manipulation error
passwd couldn’t update the password — the root filesystem is read-only, /etc/shadow has wrong permissions/attributes, or a PAM ru…
AADSTS70021: No matching federated identity record found for presented assertion (GitHub Actions / workload identity)
The OIDC token from GitHub Actions/Kubernetes/another IdP doesn’t match any federated credential on the app — issuer, subject or…
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.
Two steps away (32)
Job for nginx.service failed because the control process exited with error code
systemd tried to start the service, but its start command failed. The real reason is in the service’s status/journal.
Failed to start x.service: Unit x.service not found
systemd has no unit with that name — the package isn’t installed, the name differs on this distro, or a new unit file wasn’t load…
System has not been booted with systemd as init system (PID 1). Can't operate.
You ran systemctl inside an environment without systemd as PID 1 — a Docker container or older WSL.
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…
bcrypt error: Illegal arguments: undefined, string / data and salt arguments required / data and hash arguments required
bcrypt.compare/hash received undefined — the password field or stored hash wasn’t passed.
Keycloak: We are sorry... Invalid parameter: redirect_uri
The redirect_uri in the login request isn’t in the Keycloak client’s Valid Redirect URIs.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
JWT Expired / Invalid Token
The JSON Web Token sent with the request is expired, malformed or signed with a different key, so the API rejects it (usually wit…
{"message":"Missing Authentication Token"} / No authorization token was found
The request reached a protected endpoint without credentials — or, on AWS API Gateway, it hit a path/method that doesn’t exist.
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…
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.
AADSTS90002: Tenant 'x' not found
The tenant ID or domain in the authority URL doesn’t exist — or isn’t in the cloud you’re calling (public vs government/China).
Webhook signature verification failed (Stripe, Razorpay, GitHub…)
Your endpoint computed a different HMAC signature than the one the provider sent, so the webhook is rejected.
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…
SubscriptionNotFound: The subscription 'x' could not be found
The subscription ID doesn’t exist in the current tenant or the identity has no access to it.
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…
AADSTS50105: Your administrator has configured the application to block users unless they are specifically granted access
The enterprise app requires assignment (“Assignment required? Yes”) and the user isn’t assigned to it, directly or via a group.
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.
AADSTS7000222: The provided client secret keys for app are expired
The app registration’s client secret has expired, so service-to-service authentication fails.
Azure SQL: Login failed for user '<token-identified principal>' (Microsoft Entra / managed identity)
Entra ID authentication succeeded, but there’s no database user for that identity (or it lacks permission to the database).
invalid_token: The access token is invalid (JsonWebTokenError: invalid signature / jwt malformed)
A token was sent but the server couldn’t verify it — bad signature, malformed, revoked, or issued for another audience or environ…
Azure CLI: Please run 'az login' to setup account / No subscription found
The Azure CLI has no signed-in account (or its token expired), or the account has no subscriptions.
API Error: Invalid API Key / Incorrect API key provided
The API didn’t recognise the key sent with the request — it’s wrong, revoked, from another environment, or sent in the wrong plac…
user is not in the sudoers file. This incident will be reported.
Your account isn’t allowed to use sudo.
Read-only file system (EROFS) — cannot write to disk
The filesystem is mounted read-only — often because the kernel remounted it after detecting disk errors.
! [remote rejected] main -> main (shallow update not allowed)
You pushed from a shallow clone to a remote that doesn’t accept shallow history.
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.
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.
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.
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…
Map another error
Popular: 403500400TypeErrorCritical error0xC000007BNullPointerException404