What you see
You press Continue with Google, Continue with Microsoft or Continue with GitHub (or Continue with Apple, where it shows), and you land back on the sign-in page with a message instead of your account. Find it below. Every way in is described in signing in.
The button is not there
Provider buttons only appear when that provider is configured. A button you can see is a button that works, so if one is missing from /login and from the sign-in sheet, that route is not switched on and there is nothing to retry.
Use the email link or a password instead: signing in.
"Google sign-in doesn't work inside the ... app"
Google refuses to sign anybody in inside another app's built-in browser, such as Instagram's, Facebook's or TikTok's. Open the page in Safari or Chrome (look for Open in browser in the app's menu), or use your email.
"That sign-in timed out, or it started in another tab"
The round trip carries a random value twice: in a short-lived cookie on your browser, and signed with our own key in the request to the provider. Both have to agree when you come back. That is what stops somebody forging the return trip, and it is the commonest reason a sign-in that looked fine is refused.
It happens when:
- the cookie was blocked or cleared part way through, which is usual in a hardened private window or with a cookie blocker set to its strictest;
- the round trip took more than ten minutes, because the cookie lasts ten minutes and no longer;
- you started in one browser and finished in another, for example because the provider opened its page in an app's built-in browser.
The fix in every case is the same: go back to /login, press the button again, and complete it in one go in one browser.
The other messages
- "Sign-in was canceled." You pressed cancel on the provider's page, or declined to share. Choose a way to sign in again.
- "We couldn't finish signing you in." The provider's answer could not be used. Try again.
- "That account uses a temporary email." Sign in with an account that has an address you keep, or with your email.
- "That sign-in already belongs to another Mokxi account." Sign in to that account instead.
- "That account is suspended, so it can't sign in." Write to us from /support.
- "Lots of people are signing in right now." Repeated attempts slow down on purpose. Wait a minute and try again.
It signed me in, but to a new empty account
An identity is only ever attached to an existing account on a verified email match. If the address the provider gave us is different from the one on your account, or if the one on your account has never been confirmed, the safe answer is a separate account, not a merge.
Sign in to the original account and add the provider from the How you sign in section of Settings. That is the place where linking is a deliberate act rather than a guess.
If GitHub is not handing over an address at all, check that your GitHub account has a verified email address it is willing to share.
Still stuck
Write to us from /support, with the browser you used and roughly when. A person reads every message.