Activation and login
Fix email verification and sign-in problems.
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Activation and login
Sign-up, email verification, and session checks behave differently on Cloud, local dev, and self-host without mail.
Verification link does not work
When EMAIL_ENABLED is on, new accounts must confirm email before full access. Links point to /verify-signup with a token and email query.
| Problem | What to try |
|---|---|
| Link opens My Dashboard with no success message | Token missing, expired, or already used. Request a new email from the sign-in or verify page. |
| Truncated link | Copy the full URL from the message. Mail clients sometimes break long lines. |
| Wrong browser | Open the link in the same browser profile you used to sign up when possible. |
I cannot sign in after sign-up
- Confirm email when verification is enabled.
- Reset password from the login page if you forgot it.
- On self-host, check DISABLE_REGISTRATION if sign-up itself is closed — Docker Compose.
Logged-out API responses
When you are not signed in, some session checks return empty or not-found style responses by design. The web app uses that to show the login screen. That is normal in the network tab while logged out.
Note
If you are signed in but the app keeps asking you to log in, the browser may be hitting the wrong API host. On self-host, align VITE_BACKEND_DOMAIN_URL with BACKEND_DOMAIN_URL and CORS — Vite configuration.
CLI device login
The redpanda CLI uses a browser step at /cli/device/verify. If the code page fails to load, confirm BROWSER_ORIGIN and auth server URLs — CLI authentication.