lm-sys / lm-sys/FastChat

Sign in error: "Too many requests. Please try again later." Confusing issue, no clear requirements.

Open
#3,651 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
39.5k
Forks
4.8k
PR merge metrics
No merged PRs in 30d

Description

Issue: Misleading "Too many requests" error during first-time login

Disclaimer: this issue text was improved with Chatbot arena.

Current Behavior

When attempting to sign in for the first time at Chatbot Arena, I encountered a confusing flow:

  1. Create new account
  2. Redirected to login page
  3. Attempt to login → Receive error: "Too many requests. Please try again later."
  4. Receive verification email (not clearly prompted) - although, I only checked by accident.
  5. After verifying email and retrying login → No error, but no visible change
  6. Only after closing and reopening the site → Successfully logged in

image

Expected Behavior

The login flow should:

  • Clearly indicate that email verification is required
  • Show appropriate error messages (not "Too many requests" for unverified accounts)
  • Provide clear feedback when email verification is successful
  • Redirect back to home page after successful login
Additional Context

I think this error is very misleading. I wonder if this whole process could be improved slightly? [Chatbot generated response: The "Too many requests" error is misleading as it suggests a rate-limiting issue rather than an unverified account status. This can confuse users and create an unnecessary troubleshooting loop.]

Environment
  • Browser: Edge Version 131.0.2903.112 (Official build) (64-bit)
  • OS: Windows 11 Pro Version 10.0.26100 Build 26100

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the first-time sign-in flow at https://chatbot-arena.web.app/login, including email verification and reopening the site. Trace the authentication and verification feedback involved, then clarify the desired behavior before changing it. Done should include an accurate unverified-account message, clear verification feedback, and a visible redirect after successful login.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, frontend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.