> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/troubleshooting/sign-in-problems.md).

# Sign-in Problems

You can sign in to TestVibe with an email and password, with GitHub, or with Google. Sign-in is identity-only — TestVibe never asks for repository permissions at sign-in. If sign-in does not finish, the issue is usually email verification, browser state, or signing in with a different account than you expect.

## Quick Checks

1. Confirm which sign-in method you used when you created the account.
2. For email accounts, confirm the address is verified before the first sign-in.
3. Make sure popups and redirects are allowed for TestVibe.
4. If your browser opens GitHub or Google in a different profile, sign out of that provider there and try again.
5. Refresh TestVibe after sign-in completes.

## Email And Password Accounts

Local accounts must verify their email address before the first sign-in.

* After signing up, check your inbox (and spam folder) for the verification email and open the link.
* If the email never arrives or the link has expired, use the resend option on the sign-in screen to get a fresh link.
* Forgot your password? Use the password reset link on the sign-in screen — a reset link is emailed to your verified address.

## GitHub And Google Sign-In

OAuth sign-in only confirms who you are; no repository or account permissions are requested.

* If the provider opens but you land back on the sign-in screen, refresh TestVibe and complete the full authorization prompt again.
* If nothing happens when you click sign in, allow popups and redirects.
* If the wrong account is used, sign out of GitHub or Google in that browser profile, then sign in with the correct account.

## One Account, Several Sign-In Methods

TestVibe links sign-in methods by verified email. If your GitHub or Google account uses the same verified email address as your TestVibe account, all methods sign you in to the same user — you do not get a duplicate account. If you end up in an unexpected empty workspace, you probably signed in with a provider whose email differs from your usual account.

## Common Symptoms

| Symptom                                          | What to try                                                                                             |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------- |
| "Verify your email" blocks sign-in               | Open the verification link, or resend it if it expired.                                                 |
| Verification or reset email never arrives        | Check spam, confirm the address, then resend.                                                           |
| Provider opens but returns to the sign-in screen | Refresh TestVibe, then sign in again and complete the prompt.                                           |
| Nothing happens when you click sign in           | Allow popups and redirects, then try again.                                                             |
| The wrong GitHub or Google account is used       | Sign out of the provider in the browser profile, then retry.                                            |
| You signed in but see no projects                | You may be in the wrong workspace. See [Can't see a project](/troubleshooting/missing-repositories.md). |

## Related Help

* [Can't see a project](/troubleshooting/missing-repositories.md)
* [GitHub connection issues](/troubleshooting/github-app-permissions.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/troubleshooting/sign-in-problems.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.