Too many attempts — try again in about {seconds} seconds
UI shows a timed cooldown (auth.rateLimitSeconds) using retryAfterSec from the API or a local cooldown (e.g. resend verification). {seconds} is replaced with the remaining wait.
Why this happens
Generic client template for 429-style auth limits when the server (or client) provides a retry-after value. Used on register, resend verification, and similar panels — not the same string as download password rate limits.
Diagnose and fix
1. Wait for the countdown to finish; retry once.
2. Do not hammer the endpoint — limits protect against abuse.
3. If it never clears, check clock skew and that Retry-After / retryAfterSec is honored.
4. Admin: review rate-limit settings if legitimate users are blocked too aggressively.