> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/troubleshooting/login-issues.md). # Login issues What each login message means, and how to fix a login that loops, stalls or won't accept your details. ## Find your message | You see | What it means | What to do | | ------------------------------------------------------ | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Unable to log in with provided credentials.** | The email or password is wrong, or a team admin has removed you from the team. | Check the address, then use **Forgot your password?** on the [login page](https://pipefile.com/login). If you were removed, ask your team admin to reactivate you. | | **E-mail is not verified.** | You haven't confirmed your email address yet. | We've just sent a new verification email. Click the link in it, then log in. | | **Authorize this device** | You're logging in from a new browser, device or network. | Click the link in the email we sent, then log in again. See [New device verification](/team-and-account/two-factor-and-device-verification.md#new-device-verification). | | **Confirm it's you** | Your account has two-factor authentication on. | Enter the code from your app, use your security key, or **Use a backup code**. | | A prompt to set up two-factor | Your team requires two-factor authentication. | Follow the steps to add an authenticator app or security key. | | **Log in with SSO** opens instead of the password form | Your team logs in through single sign-on. | Enter your work email and click **Continue**. See [Single sign-on](/team-and-account/single-sign-on.md). | | **Too many attempts. Try again in … minutes.** | Too many wrong codes in a row. | Wait the time shown, then try again. | | **Your login expired. Log in again to continue.** | You took too long between the password and the code. | Start again from the login page. | | **Invalid reCAPTCHA Token** | The login page's bot check couldn't run. | See [the page loops or won't submit](#the-page-loops-or-wont-submit). | Can't confirm it's you because you lost your phone or key? Ask a team admin to reset your two-factor authentication, or email . See [Lost your phone or key](/team-and-account/two-factor-and-device-verification.md#lost-your-phone-or-key). ## The page loops or won't submit If you're stuck on the login page, sent back to it after logging in, or the button does nothing, the cause is usually stored cookies or a browser extension. {% stepper %} {% step %} ### Try a private window Open a private or incognito window and log in at [pipefile.com/login](https://pipefile.com/login). If that works, the problem is in your normal browser's cookies or extensions. {% endstep %} {% step %} ### Clear cookies for Pipefile only In your browser's settings, find the site data or cookies for `pipefile.com` and remove them. You don't need to clear data for other sites. Then reload and log in. {% endstep %} {% step %} ### Check extensions and blockers Ad blockers and privacy extensions can block the login page's security check (Google reCAPTCHA) or its cookies. Turn them off for `pipefile.com`, or allow cookies for the site. {% endstep %} {% step %} ### Try another browser or device If it still fails, try a different up-to-date browser. Then email with the exact message you see and your browser name. {% endstep %} {% endstepper %} {% hint style="info" %} After you clear cookies, Pipefile no longer recognizes the browser. Expect a new-device email, and a two-factor prompt if you use two-factor. {% endhint %} ## Logging in with Google If you signed up with Google, use the Google button below the login form. To log in with a password instead, set one first with **Forgot your password?**. ## Related * [Change your email or password](/team-and-account/email-and-password.md) * [Emails not arriving](/troubleshooting/emails-not-arriving.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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.pipefile.com/troubleshooting/login-issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.