**TL;DR:** Symptom: user created an account minutes ago and login fails. Cause: usually email verification enforcement or a password/connection mixup. Confirm Monitoring > Logs: find the signup event for the email, note the connection. Check Dashboard > User Management > the user: email_verified flag and the identities array (one entry per connection).

## The fix

1. Email verification required before first login.

2. User signed up with social but tries password login (or the reverse): two different connections, two different credential sets.

3. Password manager saved a typo'd password at signup.

4. Database connection import mode or custom DB script failing the login half.

5. Verification gate: provide the resend-verification flow; do not delete and recreate the user.

6. Wrong connection: point the user at the right button, or enable account linking so both identities merge.

7. Typo'd password value password reset flow.

## When to use this

- You are seeing this exact error message; match the block above, not just part of it.
- The failing call matches the scenario in the title: Signed up but cannot log in.
- You want the fastest verified fix before digging through logs.

## When not to use this

- Your error text differs from the block above; close cousins often have different causes.
- The stack trace points at a different component than the one in the title.
- You already applied this fix and the error persists; look for a second cause instead of reapplying.

## Compatibility

- Not pinned to a specific version; follows current Signed behavior.