-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Can't login to GitHub #949
Comments
I have a similar problem, but the login fails verifying the 2FA code and never completes the login. |
@HisRoyalRedness is this still happening to you? If it is - the credentials are stored in the Windows Credential Manager, so perhaps something happened that cleared them. Could you open
Apologies also for the delay in replying, this got missed somehow 😕 |
@richardmatsu Could you check the log in |
Nope, nothing like that. For kicks, I deleted my saved credentials in Credential Manager but no difference. 2017-04-24 15:09:36.1679|INFO|thread: 1|RepositoryHost|Log in from cache for login '(null)' to host 'https://api.github.com/' FAILED |
I've got nothing stored in my Credential Manager. Nothing in the log looks similar to #958 |
@HisRoyalRedness we're a bit stumped here to be honest. Would it be possible to run Fiddler and take a look at the requests that are being sent? |
Also, are you still getting these errors?
These look like low-level errors unrelated to GHfVS. Does your git commandline work? |
Hi there,
Yes, I still get those errors. I can fetch and pull from the commandline
without any trouble.
I'm working on getting some Fiddler dumps for you
…On 27 April 2017 at 09:50, Steven Kirk ***@***.***> wrote:
Also, are you still getting these errors?
error: cannot spawn askpass: No such file or directory
fatal: could not read Username for 'https://github.com': terminal prompts
disabled
These look like low-level errors unrelated to GHfVS. Does your git
commandline work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#949 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADH1yBVes-Tqiwb9EQUq6Avd5qmXINClks5rz7wvgaJpZM4MyRzj>
.
|
OK, perhaps I should have checked this in the first instance ... :-) It seems that the extension is having some trouble getting through our corporate proxy. I've got the requisite global git entries.
I have CNTLM installed locally to do the NTLM auth through the corporate proxy. Complicated, I know...
I can operate through the command line, so the config must be OK. These same settings appear in the VS git extension (under Repository Settings), and are shown as global settings. When I attempt to sync my repository through the VS extension, I get the 'cannot spawn askpass' errors, and Fiddler shows auth errors from the corporate proxy. Could it be possible that the extension is ignoring the git proxy settings and picking up the proxy from Internet Options (which would be the corporate proxy)? |
@HisRoyalRedness did you get any further with this issue? Apologies for not replying earlier, but we were unable to repro here. |
Yup, still the same behaviour. Generally I stage and commit from Visual Studio, and push and pull to/from remotes from the command line using the standard Git tools. Yes, it's a pain, but I manage to get by with this workflow. I've since upgraded to a new PC, running Windows 10 (old one was Windows 7), upgraded to Visual Studio 2017, and I still get the exact same error from Git (i.e. error: cannot spawn askpass). Git command line works fine. |
Hey guys - just landed on this page trying to search for this same issue (VS2017, behind corp firewall but with correct HTTP and HTTPS proxies set in my environment variables). I am able to use Git add-in for VS2017 to connect to my GitHub account and clone my repositories but when I try to push a change via VS Git add-in, I get the same error as HisRoyalRedness (cool username btw ;)). |
@HisRoyalRedness @MuqadderIqbal so the problem occurs when pushing/pulling from team explorer? Are you able to log into GitHub using the Team Explorer "Connect" section, as described here? https://github.com/github/VisualStudio/blob/master/docs/getting-started/authenticating-to-github.md When you've logged in there, a dialog shouldn't appear when pushing and pulling. |
@grokys I am able to successfully connect to my GitHub repo and authenticate. I am also able to successfully clone my library. However, after committing a change, an attempt to push it to GitHub repo results in an error. Here is the error stack trace:- Opening repositories: |
@grokys Ditto for me. I can connect and authenticate to GitHub. I can see the list of my repositories from within Visual Studio. Just can't push or pull. My error message is a little different. This was after attempting a pull
And this after a push:
If I push from a command prompt (just the standard Windows cmd, not git bash), I'm asked to enter my user name and password, and the push succeeds
|
OK, I've got it working now. I thought I'd try get some Fiddler traces for you, couldn't get it to work through Fiddler (with the complex arrrangement of corporate proxies and my local CNTLM proxy, its no wonder), and then put it all back together again. Then hey presto, it all just worked! So, I'm guessing that I got one of these steps wrong at some point. Anyway, this is what I did
I can now push and pull from my repository I've got a sneaky suspicion that I configured my https proxy setting with an http url. I did notice this when messing with the settings and corrected it. I've since set it back to http to see if I could get it to fail again, but was unsuccessful. Something to check anyway if you still have problems Hopefully it all continues to work. I'll post an update in a day or two. |
Glad you got it working @HisRoyalRedness. As I suspected, it was a proxy issue. Does the information above help you @MuqadderIqbal? One thing to note is that GitHub for Visual Studio doesn't actually supply the git push and pull functionality - this is part of Team Explorer, so if the login works then the problem was actually on Microsoft's side. I'm going to close this issue now as it looks like there's a fix and it's also not actually our functionality that's exhibiting the problem. |
I faced the same issue guys, it appears when I have only TLS1.2 enabled on my PC. After enabling TLS 1.1, SSL.x the issue was resolved. For enabling and disabling I used IISCrypto software. Hope that helps the team and other users. |
Thanks for letting us know @vCillusion - that will be helpful information for anyone experiencing this problem in future. Looks like we might need to look into why this is the case, maybe we can fix it on our end. I've opened an issue to track this over in #1443. |
Thanks @HisRoyalRedness |
I've tried most of the suggestion list above. I am still not able to Push. Here is the output from the extension.log: 2016-09-28 19:38:48.3619|INFO|thread: 1|RepositoryHost|Log in from cache for login 'davidehnis' to host 'https://api.github.com/' SUCCEEDED |
Hi, I was getting the same error as the original poster (when fetching)
I just reverted my GitHub extension (from 2.4.2.1331 to 2.2.0.10) and I am no longer getting those errors. |
I Just start getting this erros too. Only resolve to after force a logoff/login in GitHub Desktop. |
@willandus My problem was in win10 and Kevin solution works fine for me. |
#MicrosoftShouldNotMakeSuchStupidMistakesInTheFirstPlaceBecauseWhatIsTestingForAndTls1.2ExistsSinceALongLongTime also #UpdatesShouldBeInstalledByWindowsUpdateBecauseSomeUsersInEnterprisesDontHaveAdminPrivilegesYouStupidMorons #AndThatMeansYourStupidPolicyCondemsUsToPutPlaintextPasswordsIntoGitConfigFilesWhichIsTotallyInsecureAndApplySomeCmdLineFuEveryTimeWeCreateAnewProjectAndItLimitsUsToDotNetCore20BecauseThatsWhatsNowInstalledAndWeCannotDoUpdatesOurselvesAndOurAdminIsALazy"Person" Also #WhyDoesInstallingTheDotNetSdkAndRuntimeRequireAdminPrivileges ? #YouCanAlsoSetRegistryKeysInHKCUandYouCanAlsoSetPathEnvironmentVariablesForTheLocalUserOnlyJustInCaseYouDontKnow #FU-FU-FU #❤JetBrainsRider |
This sure taught me not to get the latest updates for Viz-Studio... I'd be using Rider (I have the JetBrains AllProductsPack) if it wasn't lacking some crucial features |
The 2018-EAP comes with publishing feature & experimental Blazor support. |
@kevinramharak it's working, thanks! |
@kevinramharak Thank you! This got me back up and running. |
Just wanted to mention that what KevinRamharak said worked for me as well! |
Latest update 15.8 broke it again |
@mpalladinru It was the one before 15.8 that first broke it for me. I'm assuming that meant you had it fixed manually somehow and it overwrote it? |
Make sure to use this path if you are using the preview of VS. Latest 15.8 update also breaks it for me, I have to do this each time.
|
The latest VS update (15.8) broke it again. |
@JoeHz yes, I unpacked archive contents and it was working until yesterday, when update arrived. So I unpacked archive contents again and it working again now |
Still broken in 15.8.1 |
@grokys and everyone else, we (Microsoft) have worked closely with Atlassian to resolve the Bitbucket authentication issue. I'd like to take a moment and thank the developers of Atlassian for the scramble they did to resolve the issue. They could have left everything broken longer, but instead took the high road, did the right thing, and fixed a bug that was negatively impacting people. I think that deserves a smile 😁. I personally (with the blessing of our gate keepers) have pushed the fix into Visual Studio, and an update will arriving as soon as the release gears can complete their turning. I, personally, do not have much insight into the timing of VS update releases, but I know we're targeting 15.8 and 15.9 (still in preview) with the fix. I do not know the exact timing but I do not think it'll be very long. I do apologize for missing the 15.8.1 release train. The fix just wasn't ready by the time the train had "left the station" and I still had to complete the steps of pulling the fixes into VS, and validating them (not just to fix Bitbucket, but also to ensure they did not break anything else 😲 - they don't 🙂). So the best I can do right now is say "hold tight" the fix is incoming - promise! Oh, and I am very sorry that we let this issue slip past. We did not have robust validation around Bitbucket authentication previously. We now have better validation, and will continue to improve all of our testing over time. Again, very sorry and the fix exists, it is on its way, and should be available soon (for some definition of soon). |
Yup, I knew that was going to happen - sorry. When VS updates itself it also fixes itself. Which means if you've replaced a file in the Visual Studio installation folder and then run update or repair, your replaced file will be replaced with the version the IDE is expecting to be there. 99.99% of the time you really want this feature and it has saved you from heartache over and over, without you even realizing it. In this one, very particular case, it undid the homebrew fix. The good news is, a soon update to VS should include the official fix. |
disclaimer: slightly off topic. Since last night, we start seeing the same issue on VSTS: This started after the fix for the Hosted Agent Issues in West Europe (not sure if this is related). Could you provide some insight on what we can do in VSTS to work around this issue,? Thanks! |
Until VS is patched, this suggestion is the only one I know for sure that will help. This is because we increased the HTTP_TIMEOUT significantly as part of the work-around for Bitbucket before we understood the root cause. The time change stuck because it would help in other areas. |
Thanks for the input; I opened a support request with Microsoft for the VSTS bug; |
Updated to version VS 15.8.2, still facing the same issue. |
I'm now able to push to bitbucket with 15.8.2 |
15.8.2 fixed it for me. Thanks! |
i was also struggeling with it . Updated VS to 15.8.9 and he issue was fixed . |
I updated to VS 15.9.3 and the problem returned!!! I discovered that simply grabbing the HTH. Sam. |
Same for me. I'm not sure if 15.9.3 broke it, but it was working for me in earlier versions of VS. |
Didn't work for me. Can you help m in this? |
Git failed with a fatal error. again and again |
I had the same issue with similar symptoms.
|
NOTE: Updating to Visual Studio 2017 15.5.7 or later should fix this. See #949 (comment)
I'm having some trouble logging on to GutHib to push new changes to my repository. I've just recently upgraded to Visual Studio 17. Everything used to work on VS 2015, but doesn't any longer.
Detailed steps:
I have 2 factor enabled on my account.
The text was updated successfully, but these errors were encountered: