Resolving Authentication Errors for Projects Bound to Flare Online

Article #: SCC1010F-A Product: Flare Version: All

Before You Begin

Complete Part 1 of Git / Source Control Authentication Errors before following the steps in this topic. Resetting the credential and configuration environment is required in every scenario.

Flare Online projects are not rebound through Project Properties. You must either bind the project from the Flare Online window pane or import a fresh copy from Flare Online. Either action re-establishes credentials and allows Git for Windows to save them in GCM, which writes to Windows Credential Manager.

If your project shows a large number of files pending commit, use Option 1. Credential steps alone will not resolve that symptom.

Option 1: Import the Project From Flare Online (recommended)

Importing a fresh copy is the most reliable resolution and is required if your project shows a large number of files pending commit. Delete or rename the existing local project folder before importing so the new copy does not conflict with it.

Reference: Importing Projects From Flare Online

  1. Select View > Flare Online. The Flare Online window pane opens.
  2. Log in if you are not already logged in.
  3. Click the Import Project button. If the button is disabled, click inside the window pane first, then try again.
  4. In the Import Project dialog, select the project from the My Projects field.
  5. Next to the Destination folder field, browse to the folder where you want the imported project stored on your computer.
  6. Click OK. When the import finishes, click Open to launch the project.
  7. Verify that you can push and pull without errors.

Note: You must be associated with the project in Flare Online in order to import it.

Note: If your project is dual-bound to Flare Online and a third-party Git repository, import from Git rather than from Flare Online. Importing from Flare Online gives you only the Flare Online binding, and you will not be able to push to or pull from your main Git repository. In that case, follow Projects Using Git or Other Remote Providers.

Note: If your project is dual-bound to Flare Online and a non-Git provider such as Perforce Helix Core, Subversion, or Team Foundation Server, the Import button in the Flare Online window pane is disabled. Import the project from that provider instead, then use Option 2 below to re-bind to Flare Online.

Option 2: Bind the Project to Flare Online

Use this option if you already have a local copy you want to keep, if you imported from a non-Git provider and need to re-establish the Flare Online connection, or if you are recreating the binding from scratch to clear a pending-commit backlog.

Reference: Binding a Project to MadCap Flare Online

  1. Open the project in Flare Desktop.
  2. Select View > Flare Online. The Flare Online window pane opens.
  3. Log in if you are not already logged in.
  4. Click the Bind Project button. If the button is disabled, click inside the window pane first.
  5. In the Bind Project dialog, confirm the Enter project name field. If you are re-establishing a connection to a project that already exists in Flare Online, enter the exact name of the project as it currently exists there.
  6. Optionally, enter a short description in the Enter project description field, then click OK.
  7. If a message asks whether you want to bind to the existing project, select Yes. This re-establishes the existing connection rather than creating a new binding.
  8. Click OK in the success message, then attempt to push or sync.

Note: MadCap Software does not support the SSH protocol when connecting Flare Desktop to Flare Online. Use HTTPS.

Note: If your project is dual-bound, check in or push your files to your third-party source control provider after binding to Flare Online, so other users importing the project get the most recent version.

Note: If you are binding to resolve a pending-commit backlog, the local repository must be recreated rather than reused. Delete the hidden .git folder in the project directory before binding, so Flare creates a new repository and initial commit rather than carrying the previous history forward.

Still Need Help?

If the issue persists, contact MadCap Software Support and include your Flare version and build number, the exact error message and error number, and whether the project is single-bound or dual-bound.

Attribution:

Last updated:
September 8, 2026		 Author:
Ian Hinkle		 Contributions by: