Mintplex-Labs/anything-llm · error
Invalid auth for user.
Error message
Invalid auth for user.
What it means
Auth guard in validateMultiUserRequest: the JWT decoded successfully but User.get for its embedded user id returned null, meaning the token references a user that no longer exists, so authentication is refused with 401.
Source
Thrown at server/utils/middleware/validatedRequest.js:95
if (!token) {
response.status(401).json({
error: "No auth token found.",
});
return;
}
const valid = decodeJWT(token);
if (!valid || !valid.id) {
response.status(401).json({
error: "Invalid auth token.",
});
return;
}
const user = await User.get({ id: valid.id });
if (!user) {
response.status(401).json({
error: "Invalid auth for user.",
});
return;
}
if (user.suspended) {
response.status(401).json({
error: "User is suspended from system",
});
return;
}
response.locals.user = user;
UserMetaCache.setFromRequest(request, user.id);
next();
}
module.exports = {View on GitHub (pinned to 3aec848f28)
Solutions
- The user encoded in the token no longer exists; log in again with a valid user account.
- Verify the user was not deleted from the system.
Defensive patterns
Strategy: validation
When it happens
Trigger: Invalid auth for user. Triggered when user-scoped token validation fails in validatedRequest (validatedRequest.js:95).
Common situations: See trigger scenarios.
AI-assisted analysis of Mintplex-Labs/anything-llm@3aec848f28 (2026-08-18).
Data as JSON: /api/errors/b4d32820a3c0fe9e.
Report an issue: GitHub.