Git / Source Control Authentication Errors

Article #: SCC1010F Product: Flare Version: All

Overview

Some users experience Git and source control authentication errors that prevent them from pushing, pulling, or publishing their projects. Common symptoms include "Git Access Denied" messages and authentication prompts that loop without success. This article explains what causes these issues and directs you to the resolution path for your binding type.

Symptoms

You may be experiencing this issue if you see any of the following:

  • A message stating "Authentication failed" or "Git Access Denied" when building or syncing
  • Flare prompts you to enter Git credentials repeatedly, even though they were previously saved
  • Your project suddenly shows a large number of pending commits that did not exist before

Cause

Authentication failures are usually caused by credentials that are expired, revoked, or stored in a state Flare can no longer use. Stale application settings carried over in the Windows registry and the roaming profile can produce the same result. Flare relies on Git for Windows and the Git Credential Manager (GCM) to store and present credentials, so an outdated or misconfigured Git for Windows installation can also cause authentication to fail or loop.

In some cases, the local repository is in a state where Git no longer recognizes the existing working tree as matching the local commit history. This is what produces the large number of unexpected pending commits. Because the local repository itself is the problem, clearing credentials and re-authenticating will not correct it.

Before You Begin

Important: If your project shows a large number of files pending commit, credential steps alone will not resolve it. This symptom can only be corrected by reimporting the project or creating a brand new binding, which means deleting the local repository and recreating it.

Before deleting the local project folder, copy any uncommitted work you want to keep to a location outside the project directory. You can add those files back to the fresh copy after the import completes.

Part 1: Reset the Credential and Configuration Environment

Complete all three steps below for every scenario, then continue to the resolution path that matches your project.

Step 1: Clear stored Git credentials

  1. Open Windows Credential Manager (search for it in the Windows Start menu).
  2. Click Windows Credentials.
  3. Look for any entries related to MadCap, git.madcapcentral.com, or your Git host (for example, GitHub, Azure DevOps, or Bitbucket).
  4. Remove those entries by clicking each one and selecting Remove.

Step 2: Clear the Flare registry key and roaming application data

  1. Close Flare.
  2. Click Start, then place your cursor in the Search field.
  3. Type regedit and click OK.
  4. In the Registry Editor, go to HKEY_CURRENT_USER\Software\MadCap Software.
  5. Find the Flare folder, right-click it, and select Export. This creates a backup.
  6. Right-click the Flare folder again and press the Delete key.
  7. Navigate to C:\Users\<username>\AppData\Roaming\MadCap Software.
  8. Make a copy of the Flare directory and store it in another location as a backup. This preserves your macros and file options. To do this, right-click the Flare folder, select Copy, then paste it elsewhere.
  9. Once you have that backup, delete the Flare directory in the AppData\Roaming\MadCap Software location.

Step 3: Uninstall and reinstall Git for Windows

  1. Close Flare if it is open.
  2. Open Settings > Apps > Installed apps (or Control Panel > Programs and Features).
  3. Locate Git in the list, select it, and choose Uninstall. Follow the prompts to complete removal.

  4. Navigate to C:\Users\<username> and delete the following leftover configuration files and folders, if present:

    • .gitconfig
    • .git-credentials
    • .gitconfig.lock
    • the .config\git folder
  5. Download the latest Git for Windows installer from https://git-scm.com/install/windows and run it.
  6. Accept the default installation options unless your organization requires otherwise. Ensure Git Credential Manager is selected as the credential helper.
  7. Restart your computer, then open Flare.

Note: Deleting .gitconfig removes any custom global Git settings, such as your user name, email, and aliases. If you have customizations you want to keep, open the file in a text editor and save a copy before deleting it.

Part 2: Choose Your Resolution Path

After completing Part 1, follow the topic that matches how your project is bound:

  • Flare Online Authentication Errors — Use this if your project is bound to Flare Online. Flare Online projects are not rebound through Project Properties; you either bind from the Flare Online window pane or import a fresh copy.
  • Projects Using Git or Other Remote Providers — Use this for GitHub, Azure DevOps, Bitbucket, or a self-hosted Git server. Also use this topic if your project is dual-bound to Flare Online and a third-party Git repository.

Still Need Help?

If the issue persists after completing the steps in either path, contact MadCap Software Support and include your Flare version and build number, your Git provider, 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: