Mintplex-Labs/anything-llm · error

User not found.

Error message

User not found.

What it means

Lookup guard in validBrowserExtensionApiKey middleware: the API key validated but, in multi-user mode, no User row exists for the key's bound user_id (user deleted), so the session cannot be established and 403 is returned.

Source

Thrown at server/utils/middleware/validBrowserExtensionApiKey.js:31

  if (!bearerKey) {
    response.status(403).json({
      error: "No valid API key found.",
    });
    return;
  }

  const apiKey = await BrowserExtensionApiKey.validate(bearerKey);
  if (!apiKey) {
    response.status(403).json({
      error: "No valid API key found.",
    });
    return;
  }

  if (multiUserMode) {
    const user = await User.get({ id: apiKey.user_id });
    if (!user) {
      response.status(403).json({
        error: "User not found.",
      });
      return;
    }

    if (user.suspended) {
      response.status(401).json({
        error: "User is suspended from system",
      });
      return;
    }

    response.locals.user = user;
  }

  response.locals.apiKey = apiKey;
  next();
}

View on GitHub (pinned to 3aec848f28)

Solutions

1. The API key references a user that no longer exists; re-issue a new browser extension API key for an existing user.
2. Verify the user account was not deleted in multi-user mode.

When it happens

Trigger: Browser extension API key resolved to no user. Triggered when the user owning the key no longer exists (validBrowserExtensionApiKey.js:31).

Common situations: See trigger scenarios.

AI-assisted analysis of Mintplex-Labs/anything-llm@3aec848f28 (2026-08-18). Data as JSON: /api/errors/94872c7094eb93a6. Report an issue: GitHub.