I cannot sign in

Summary#

Sign-in problems fall into four groups: the credentials are not accepted, the account exists but is not confirmed, the browser blocked the sign-in library, or Google handed the sign-in back with an error. The sign-in page shows a deliberately generic message for the first two, so this article tells you how to tell them apart. Every message quoted here is exactly what appears on screen.

Symptoms#

You are on the sign-in page at /login and one of these is happening:

• You enter your email and password, press Sign In, and get Invalid email or password.
• You press Create Account and get Could not create account.
• You created an account and saw Almost there — we sent a confirmation link to <your email>. Click it to activate your account, then sign in. but signing in still fails.
• You press Continue with Google and come back to the page with Google sign-in was cancelled. You can try again or use your email and password., Sign-in could not return to the site. The redirect URL is not allowed., or Sign-in failed: <reason>.
• The page shows Sign-in could not start because a required script was blocked. Disable any ad or script blocker for this site, then reload.
• You reach the dashboard but it shows Could not load the sign-in library. An ad blocker, privacy extension or network filter is the usual cause. Allow this site and reload.
• You press Forgot password? and nothing happens except Please enter your email address.
• You open the reset link and get Password must be at least 8 characters or Passwords do not match.

Diagnosis#

Invalid email or password covers more than a wrong password#

This one message is shown for every failed sign-in attempt, on purpose. It does not tell an attacker whether an email address is registered. It also means you cannot read the cause off the screen. In practice it is one of:

Could not create account also covers several causes#

Sign-up shows one message for every failure. The usual causes are an address that already has an account, a password shorter than the minimum, or a malformed email address. If the address already exists, use Sign In or Forgot password? instead of creating a second account.

The account exists but is not confirmed#

If sign-up finished with Almost there — we sent a confirmation link to <email>. Click it to activate your account, then sign in. then the account is not usable until that link is clicked. Until then, sign-in returns the generic Invalid email or password, and API calls will not recognize the address either. Check the spam folder and any corporate mail quarantine.

A blocked script, not a wrong password#

Sign-in needs a small authentication library to load in your browser. If an ad blocker, privacy extension, DNS filter or corporate proxy blocks it, sign-in cannot even start, and the page says so:

• On the sign-in page: Sign-in could not start because a required script was blocked. Disable any ad or script blocker for this site, then reload.
• On the dashboard: Could not load the sign-in library. An ad blocker, privacy extension or network filter is the usual cause. Allow this site and reload.

Either message means the app could not check your session at all. It is not a statement that you are signed out. See The dashboard is stuck loading for the loading behavior around this.

Google sign-in returned an error#

Google reports a failure by sending you back to the sign-in page with a reason attached, which the page then reads out:

A stale session key on your own device#

The sign-in page checks for a stored session before it paints the form. If it finds one, it covers the form with Taking you to your dashboard… (or Opening secure checkout… if you arrived from a pricing link). If that stored token is expired or orphaned, the check can never complete. After 5 seconds the page removes the cover, deletes the stale token and gives the form back, so this resolves itself. If you land on a covered form and it clears after a moment, that is what happened, and you can sign in normally.

Suspension does not block sign-in#

A suspended account can still sign in and open the dashboard. What fails is running anything that costs credits, with This account is suspended. Please contact support. If you can sign in but every tool returns that, this is not a sign-in problem. Contact us through Contacting support.

Resolution#

1. Reload the page once. /login is served with caching switched off, so a reload always gives you the current page.
2. Turn off blockers for this site. If either "blocked script" or "could not load the sign-in library" message appeared, allow the site in your ad blocker or privacy extension, then reload. Try a private window with extensions disabled to confirm.
3. Reset your password. Type your address into the Email Address field first, then press Forgot password?. Pressing it with an empty field only shows Please enter your email address. On success you get Password reset email sent. If sending fails you get Error sending reset email, which means the request never reached the mail provider.
4. Open the reset link and set a new password. The reset card is headed Set New Password. Enter the same value in New Password (minimum 8 characters, the field hint reads Min 8 characters) and Confirm Password, then press Save New Password. A short value gives Password must be at least 8 characters; a mismatch gives Passwords do not match. On success you see Password updated successfully! Redirecting... and land on the dashboard.
5. If you signed up with Google, add a password. Once you are in, go to Account → Security and use Set Password. The prompt reads Enter a new password (minimum 6 characters): and a short value is rejected with Password must be at least 6 characters. On success you get Password updated. You can now sign in with email + password. Full steps are in Changing your password.
6. Confirm your email address if you never did. Request a fresh reset email and use that link, or ask support to check the account state.
7. Still stuck? Contact us with the exact message on screen, the address you are using, whether you originally signed up with Google or with a password, and the browser you are in. See Contacting support.

Prevention#

• Use one sign-in method consistently. If you started with Google, either keep using Continue with Google or set an email password once from Account → Security so both routes work.
• Confirm your address the day you sign up. The confirmation link is what turns the account into a usable identity.
• Allow the site in blockers before you need to sign in urgently. The sign-in library is served from our own domain precisely so it is hard to block, but aggressive filters can still catch it.
• Do not create a second account to get around a sign-in problem. A second account has its own plan, credits and saved work, and merging them is a manual support job. There is no way to change the email address on an existing account, so the address you sign up with is permanent. See Changing your email address.
• Keep your recovery mailbox reachable. Password reset is the only self-serve recovery path.