-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Push looks for credential storage in wrong directory. #1492
Comments
+1 I have this same problem Yesterday I uninstalled Git Extensions, (plus the other 2, mysysgit and kdiff), and reinstalled from scratch using the Git Extensions installer This is the error I get I noticed the problem when I tried to push to github for the first time. It never happened when I pushed to bitbucket. That may be completely unrelated though |
We support HTTP authentification using only git-credential-winstore. If it doesn't work, push will hang. Please use SSH instead. |
I solved this problem by using bitbucket. |
The problem was caused by this: Later I uninstalled using the normal uninstalled Then I reinstalled using the normal installer, but to C:\Program Files (x86) He WAS NOT SMART ENOUGH to get all references to the new install location, and this error happened When I checked my D:\Program Files directory, sure enough, there was a Git and a Git Extensions directory with a few odds and ends still hanging around The workaround was to uninstall AGAIN, and reinstall back on D drive, but this is a stupid thing to have to do, and does not give me warm fuzzy feelings if I ever have to do another uninstall |
I am experiencing this too using v2.41 on WinXP (x86). My .gitconfig file contained the I am able to push over http and receive the expected OpenSSL login using v2.33 on that x64 machine but since that is also the machine hosting the repos, it is difficult to ascertain why it works 'there' but not 'here'. Is it the version? The platform? Or because the repos are actually local? It's not the firewall or my SSL login credentials: I can connect just fine using ssh from the cmd prompt. @KindDragon, there is no subdirectory "GitCredentialWinStore" in the installation folder of either v2.33 (on my x64 machine) or v2.41 (on my x86 box). I can't find any |
You use old GitEx version. Please update to 2.43/2.44. |
WORKAROUND .....
You can now push to origin |
@sudanthaa - Great! One thing I made different was the last command, I've added "--global" after the "git config" because it's a problem that will accure in any repository and we should fix it globaly :) |
Still a problem, is looking in the wrong directory. I've installed once the gitext and then after 1 year stop working, then I've installed this new version and worked for some time. Now it doesn't work again. And only happens for a specific repo. |
Running into this issue as well, Win8.1 x64. I only found out about this because I had installed GItExtensions after I installed SourceTree. SourceTree was failing pushes. Shouldn't there be an option to use/not use this during installation? |
This also fails after uninstallation, causing git to fail un-gracefully later on. |
Why are these all being closed WITHOUT being fixed? |
This bug fixed in 2.48 |
@KindDragon - No, it isn't. I just pulled down 2.48 on a clean machine. Installed (selected the win credential store option) and ran. It give me the error: |
@DRAirey1 is right. The git-credential-winstore.exe file is not present in the 2.48 MSI installer which results in the beforementioned error message. That is, I extracted the files from the MSI using 7-zip but there's no sign of the file. |
The git-credential-winstore.exe file now only in Complete installer |
funny that. |
I can no longer push because when I push it looks for git-credential-winstore.exe underneath C:\Program Files (x86), but I don't have that directory on my machine, I just have C:\Program Files.
This is what my window reads:
EDIT:
Immediately after posting that, I found this in my .gitconfig
However, removing the " (x86)" or removing the two lines altogether just causes push to hang completely
The text was updated successfully, but these errors were encountered: