Step by Step Guide to solve n8n User Not Found Error
Who this is for: n8n administrators, DevOps engineers, and developers who manage self‑hosted n8n instances and need to resolve login failures caused by missing users. We cover this in detail in the n8n Authentication Errors Guide.
Quick Diagnosis
- Open Settings → Users in the n8n UI (or query the DB).
- Confirm the exact email/username you’re using.
- If the account is missing, create it via the UI or run the CLI:
n8n user:create --email you@example.com --password StrongPass123!
4. Restart n8n if you edited the database directly, then log in again.
If the user exists but the error persists, clear your browser cache or verify that the authentication method you’re using (Basic Auth vs. JWT) matches the credential you send.
1. What Triggers the “User Not Found” Error
If you encounter any password policy violation resolve them before continuing with the setup.
| Trigger | Typical Symptom | Why It Happens |
|---|---|---|
| Incorrect email/username | “User not found” pop‑up | n8n looks up the identifier in the User table; no match → error |
| User deleted but credential still references it | Automated workflow fails on first run | Credential points to a non‑existent user |
| Case‑sensitivity mismatch | Same error despite user existing | n8n stores emails lower‑cased; mismatched case prevents lookup |
| Database desynchronisation (e.g., after migration) | All logins return “User not found” | `User` table not reachable or connection string is wrong |
EEFA note: n8n hashes passwords with bcrypt. Creating a user via the CLI guarantees a proper hash.
2. Verify the User Actually Exists
If you encounter any two factor auth failure resolve them before continuing with the setup.
2.1 Using the n8n UI
- Log in with an admin account.
- Navigate to Settings → Users.
- Search for the email/username you’re trying to use.
If the user is absent, you must create it (see Section 3).
2.2 Direct DB Query (Advanced)
When to use: No UI access (headless deployment) or bulk audit.
SELECT id,
email,
"isActive"
FROM "User"
WHERE LOWER(email) = LOWER('you@example.com');
Interpretation
– Rows returned → user exists (note the id).
– No rows → user truly missing.
EEFA warning: Run queries against a read‑only replica in production whenever possible. Never modify the
Usertable directly; always use n8n’s CLI or API.
3. Create the Missing User
3.1 Via the UI (recommended for small teams)
- Click Add User.
- Fill in Email, Password, and optional First/Last name.
- Choose a Role (
Owner,Member,Viewer). - Click Save.
3.2 Using the n8n CLI (ideal for automation)
# Basic creation n8n user:create --email you@example.com --password StrongPass123! # Add a specific role (e.g., Member) n8n user:create --email you@example.com --password StrongPass123! --role Member
The CLI hashes the password and updates the User table automatically.
3.3 Programmatic Creation via the REST API
Step 1 – Set request line and headers
POST /rest/users HTTP/1.1 Content-Type: application/json Authorization: Bearer <admin-jwt>
Step 2 – Provide the JSON payload
{
"email": "you@example.com",
"password": "StrongPass123!",
"role": "member"
}
EEFA tip: Use HTTPS and store the admin JWT securely (e.g., in a vault). Never expose admin credentials in CI pipelines.
4. Align Your Authentication Method
n8n supports several auth flows. Choose the one that matches your integration.
| Method | When to use | Common pitfalls that cause “User not found” |
|---|---|---|
| Basic Auth (username + password) | Direct UI login, simple scripts | Sending the *password* instead of *email* as the username |
| JWT (Bearer token) | API calls from external services | Token generated for a user that was later deleted |
| OAuth2 (Google, GitHub, etc.) | SSO environments | Provider returns an email that doesn’t match any n8n user |
Basic Auth example with curl – note that the username must be the exact email stored in n8n (lower‑cased).
curl -u you@example.com:StrongPass123! \
https://n8n.example.com/rest/workflows
5. Debugging Checklist
| Check | How to Verify |
|---|---|
| Email spelling & case | Re‑type or copy‑paste from the Users list |
User status (isActive) |
UI → Users → check “Active” toggle |
| Password correctness | Reset via UI → “Forgot password” and retry |
| Correct auth header | Use curl -v or browser dev tools to view Authorization |
| Database connection | Confirm DATABASE_URL points to the right DB |
| n8n version | n8n -v – versions < 0.215 had case‑sensitivity bugs |
| Cache | Clear browser cookies or restart the n8n container if using an in‑memory session store |
If all checks pass and the error persists, inspect the n8n logs:
docker logs <n8n_container_name> # or, if using PM2: pm2 logs n8n
Look for messages such as User lookup failed for email: you@example.com.
6. Production‑Ready Recommendations
- Enforce lower‑casing of emails at creation (CLI does this automatically).
- Audit orphaned credentials weekly – script a query that lists credentials referencing non‑existent users.
- Enable login throttling (
N8N_LOGIN_RATE_LIMIT) to mitigate brute‑force attempts that flood logs with “User not found”. - Rotate admin JWTs regularly; store them in a secret manager.
Conclusion
The “User Not Found” error is almost always a data‑validation issue: the supplied email doesn’t match any record in n8n’s User table. By confirming the exact email, ensuring the account exists (via UI, CLI, or API), and aligning your authentication method, you can resolve the error in seconds. Apply the production‑ready practices above to keep user data consistent, prevent orphaned credentials, and maintain a secure, reliable n8n deployment.
