Velvet Star Monitor

Standout celebrity highlights with iconic style.

updates

Cannot determine the organization name for this 'dev.azure.com' remote url

Writer Matthew Barrera

So i just updated to a new Visual studio version and I'm no longer able to push/pull from/to my azure git repo (cloning works fine).

The exact error I get is

Cannot determine the organization name for this 'dev.azure.com' remote url. ensure the credential.usehttppath configuration value is set, or set the organization name as the user in the remote url '{org}@dev.azure.com'.

and only the pull command shows me this error, all the others are failing with git fatal error. I messed with my Credentials Manager cos i suspected it might be the one causing the problem but no luck..

8

11 Answers

What fixed the issue for me is going to Tools > Options > Source Control > Git Global Settings, there I changed all 4 dropdowns which were still selected as "Unset":

  • Prune remote branches during fetch - False
  • Rebase local branch when pulling - False
  • Cryptographic network provider - OpenSSL
  • Credential helper - GCM Core

Source:

Note: These are the settings my organization requires. You might have to tweak them around according to your exact issue.

16

Okey, i just updated git for windows git update-git-for-windows with git bash. Then selected the new non deprecated credential manager when installing and now it works fine.

5

Check your credentials in Tools > Options > Source Control > Git Global Settings enter image description here

1

Install the latest version of Git Credential Manager to resolve this issue.

Windows:

Download here and install, it does not require admin access.

MacOS Homebrew:

To install, run the following:

brew tap microsoft/git
brew install --cask git-credential-manager-core

After installing you can stay up-to-date with new releases by running:

brew upgrade git-credential-manager-core

Linux Debian package (.deb):

Download the latest .deb package, and run the following:

sudo dpkg -i <path-to-package>
git-credential-manager-core configure

Note that Linux distributions require additional configuration to use GCM Core.

Linux tarball (.tar.gz):

Download the latest tarball, and run the following:

tar -xvf <path-to-tarball> -C /usr/local/bin
git-credential-manager-core configure

Latest Releases:

3

IDE-agnostic solution that worked for me:

  1. Open Command Prompt
  2. Run git config --global credential.useHttpPath true (the --global parameter is optional)

Git-Credential-Manager-for-Windows docsuseHttpPath

2

I encountered this error and I was able to resolve it by installing the latest version of gcm-core.

1

Under Tools> Options > Source Control > Credential Helper Select GMC for windows

VS have always being a pain with accounts

Sometimes, it happens if the git version is not updated with the latest version.

To update the git, just follow the below command depending on the type of OS you are using:

Windows: git update-git-for-windows

Linux/Unix: git update

or follow the below link to get the latest copy of the git client for your OS.

Ok, so I encountered this problem today when I updated VS2019 to 16.9.6 (from 16.8.x). I tried the recommended answer and that failed - very strangely, actually, VS refused to persist my changes to the GIT global settings (let me change them in the dialog, but fetch/push still failed, and when I looked at the settings again, they were back to "unset"). I tried another answer above, updating gcm-core, but still made no difference. In the end I removed git entirely, then reinstalled the latest version (2.31.1) - and suddenly it worked.

Since I was so frustrated by this experience, I thought I'd post what finally worked for me, in case it helps someone else.

Installing the latest version of Git Credential Manager Core resolved the issue

1

Hi I use SourceTree and have same error message, I resolved it by changing:

Open Settings / Remotes, and click edit button. Change:

.visualstudio.com/[path-to-repo]

to

@dev.azure.com/[path-to-repo]

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy