Login problems
Work through these in order. Most sign-in failures are one of four things, and the first two account for the majority.
Check these first
- Confirm the addressSign in with the address the account was created under, not a forwarding alias.
- Check service statusIf something is degraded it will be on the status page before it is anywhere else.
- Try a private windowA stale session in your normal browser is the single most common cause.
- Then work through the symptoms below
Common failures
Usually because: A stale session token, or the password was changed on another device.
Fix: Sign in from a private window. If that works, clear cookies for the dashboard domain. If it still fails, use password reset.
Usually because: Delivery delay, spam filtering, or the address does not match an account.
Fix: Wait two minutes, then check spam. Confirm the address exactly. Corporate filters frequently hold automated mail — ask IT to allow mail from our sending domain.
Usually because: Reset links are single-use and short-lived, and some mail scanners follow links automatically, consuming them.
Fix: Request a fresh link and open it yourself rather than letting a scanner reach it first. Open it in the same browser you will sign in from.
Usually because: Passkeys are tied to the device and browser profile they were created on, and only one created as a discoverable device passkey offers itself for sign-in before a password is entered.
Fix: Register a passkey from Security -> Two-step verification -> This device using the device you want to sign in from. If it was registered on another device, sign in with another method first, then add one here.
Usually because: Device clock drift. Codes are time-based and a minute of drift breaks them.
Fix: Enable automatic time on the device. If you have lost the authenticator, use a recovery method or contact support — we cannot bypass MFA for you.
Usually because: Third-party cookies blocked, or a different account than expected is active on that provider.
Fix: Allow cookies for the dashboard domain and confirm which Google or GitHub account is signed in.
Contact support
Include the address you are signing in with, which method you tried, what you saw, and roughly when. Do not send us your password — we will never ask for it.