Troubleshooting · Sign-in & Access
Can't log in
Sign-in problems usually break down into email-not-received, OAuth provider issues, or account locked. Triage here.
3 min read
If you can't sign in, run this in order. Most issues fall into 4 buckets.
Bucket 1: "Wrong password" but you swear it's right
- Confirm caps lock is off (laptop fingers).
- Confirm the email is correct — case matters in some browsers' autofill.
- If you use 1Password / Bitwarden / etc., the manager might have a stale entry. Try typing the password manually.
- Still wrong? Use Forgot password — see Bucket 2.
Bucket 2: Reset email isn't arriving
- Check spam / junk / promotions.
- Wait 60 seconds — sometimes Resend takes a beat.
- Add
noreply@ritsu.aito your contacts and request again. - If your email is on a school / corporate domain, your IT may filter our emails. Ask them to whitelist
ritsu.aiandresend.com(our delivery provider). - As a last resort, try a different email address you control. If we send to that one and it arrives, the original is being filtered.
- If nothing arrives anywhere within 5 minutes: email support@ritsu.ai from the address you're trying to recover. We can manually send a reset link.
Bucket 3: OAuth (Google / Apple / Microsoft) isn't working
Symptoms: clicking "Sign in with Google" produces an error toast, redirects in a loop, or returns "consent denied".
- Sign out of the OAuth provider entirely (Google, Apple, etc.) and try again — sometimes a stale provider session breaks the handshake.
- Try a different browser. OAuth is sensitive to third-party cookie blockers.
- If you have a Google Workspace / school Google account, your admin may have blocked Ritsu. Use a personal Google account, or get the admin to allowlist us.
- "Email already in use" — you have a Ritsu account on the same email but signed up via a different method (e.g., password). Sign in with the original method instead, or use Forgot password on the password method.
Bucket 4: "Account locked" or repeated 2FA failures
We lock accounts after 10 failed sign-in attempts in 15 minutes (anti-brute-force). Lockout lasts 30 minutes and clears automatically.
If you've genuinely locked yourself out (not someone else trying):
- Wait 30 minutes
- Use Forgot password to reset — that bypasses the lockout
- Make sure your password manager has the right entry for next time
If you suspect someone else triggered the lockout (i.e., someone is trying to break in):
- Email support@ritsu.ai immediately
- We'll investigate the IPs and take action — also a good time to enable 2FA if you don't have it (Set up 2FA)
Bucket 5: Lost 2FA device + lost recovery codes
This is the worst case. Recovery requires manual verification:
- Email support@ritsu.ai with: account email, last billing receipt or statement, account ID if you remember it, secondary email
- We verify your identity over a few back-and-forth emails
- If verified, we manually disable 2FA and email you a temporary sign-in link
- After signing in, immediately reset 2FA and save the new recovery codes somewhere safe
This takes 24-48 hours typically. There's no fast-track because the alternative is anyone with your email being able to reset your 2FA.
Specific error messages
"Too many requests"
You've hit the rate limit on sign-in attempts. Wait 15 minutes.
"Email not verified"
You signed up but haven't clicked the verification link yet. Check your email; resend from the prompt.
"Account suspended"
We've manually suspended the account (TOS violation, billing dispute, etc.). Email support@ritsu.ai with the email address — we'll explain.
When to email support
After the above triage, if you're stuck: support@ritsu.ai. Include the email you're trying to use, the error you see, browser + OS, and which buckets above you've already tried. Saves a round-trip.
Was this article helpful?