Git Client Setup

git.eu authenticates HTTPS git operations with a personal access token (PAT) or OAuth - never your account password. If TortoiseGit or the Windows credential prompt is asking for a password, or every operation fails with Authentication failed right after you typed your account password, this guide walks through the fix for the two most common Windows setups: TortoiseGit and the Windows Git Credential Manager (GCM) dialog that plain git (Git for Windows) pops.

This guide covers where to paste the credential in each client. For the underlying PAT mechanics, see Clone and Push over HTTPS; for the full OAuth/PAT/device-flow walkthrough and git config setup, see Git Access.

Create a Personal Access Token

Both TortoiseGit and GCM need the same thing in the password field: a personal access token, not your account password. Create one first from Settings → Tokens:

Copy the raw value immediately after creating it - it is shown exactly once. See Git Access - Method B for scopes and the full token lifecycle.

TortoiseGit

TortoiseGit shells out to the same git binary you have installed, so it uses the same credential prompts as the command line.

• Step 1 - Clone or push

  Start a normal TortoiseGit action against your instance - Git Clone... or Push... - using the repository URL from git.eu:

  Copy

  https://<INSTANCE>.git.eu/<owner>/<repo>.git
  

• Step 2 - Enter credentials

  TortoiseGit (or the underlying Windows credential prompt it delegates to) asks for a username and password:

  Field	Value
  Username	Your git.eu account name
  Password	The personal access token you created above - not your account password

  Check the "save"/"remember" option if offered - it stores the credential in the Windows Credential Store so you are not prompted again on the next operation.

• Step 3 - Verify

  The clone or push completes without another prompt. If it fails immediately with an authentication error, see Troubleshooting below.

Windows Git Credential Manager (GCM)

Git Credential Manager ships by default with Git for Windows - it is what pops the credential dialog when plain git clone, push, or fetch runs from PowerShell, cmd, or any terminal.

• Step 1 - Trigger the prompt

  Run a normal command against your instance:

  Copy

  git clone https://<INSTANCE>.git.eu/<owner>/<repo>.git
  

• Step 2 - Enter credentials

  A GCM dialog (or an inline terminal prompt on older configurations) asks for a username and password:

  Field	Value
  Username	Your git.eu account name
  Password	The personal access token - not your account password. git.eu is not a GCM-recognized OAuth provider, so the prompt falls back to Basic authentication and the PAT is the only credential that works here

  GCM caches the credential after the first success - you should not be prompted again for the same host.

• Step 3 - Clear a bad cached credential

  If you already typed your account password and GCM cached it, every later operation fails with Authentication failed until the bad entry is cleared:

  Copy

  printf 'protocol=https\nhost=<INSTANCE>.git.eu\n\n' | git credential-manager erase
  

  Or remove it by hand: open Control Panel → Credential Manager → Windows Credentials, find the entry starting with git:https://<INSTANCE>.git.eu, and remove it. The next git operation prompts fresh.

Troubleshooting

Next Steps