For me it happened at the very end, every time. Thank you for your issue! It seems only one side of this contract is working. Out of despair changed it now and it worked. See the manual of specific helpers for examples of their use. With only the information that is currently in the issue, we don't have enough information to take action. What authentication mechanism is your server expecting? I suspect that this problem will affect. We user git clone on a Linux client.
I recently installed GitHub for Windows for the first time so I could compile an open source project. This can be beneficial to other community members reading this thread. Are you signed into a GitHub or GitHub Enterprise account at the time of cloning? Everything was working, so didnt bother changing it. Did you run the clone command in git bash or clone the repository in Visual Studio directly? Hopefully this feedback will be helpful in making it even better. There are no spaces in path to repository.
I knew my internet connection was working. No, there is no proxy. This can be beneficial to other community members reading this thread. Is the most telling piece here. I don't see an information that it's not. But when I click on Clone, I get this error: Error encountered while cloning the remote repository: Git failed with a fatal error. Hi Limitxiao, Thank you for the reply.
Oops, I'm sorry for beeing late. Yeap, I signed in with the correct account, 100%. Other descriptions of the problem seemed to happen right at the beginning of the clone operation, or somewhere in the middle. Can you try deleting them if you see them? Once the pull is complete, I can see the credentials appear in my windows credential manager and am able to proceed normally from there. It is uncoupled from Git Credential Manager for Windows. Not a big deal, but certainly an improvement opportunity. Alberto Thanks for your answer Balazs Szakmary.
If someone looked up this thread and its not a solution for you - check out comments under the question and steps i described in question, they might be useful to you. I am currently having this issue: Git failed with a fatal error. Here is the output of the log file. Also, I need to notice that I successfully downloaded this repo again, with the same acc and via https and without any special actions with the official GitHub Desktop Chocolate-Covered Yaks 3. This can be beneficial to other community members reading this thread. Resolution 2 Check that the user can login to the web interface of Stash and answer the if prompted. Enter it, and authentication works.
What locale is your bash shell set to? Thank you for your understanding. Cause This error can have multiple causes which are outlined below. Only on Linux command line, we have this issue. For me, it defaulted to PowerShell other options were Cmd, Git Bash, and Custom. According to the error message, I suggest that you could try to: 1.
Did this issue also happen to other machines with Windows system? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. I'm a bit in the dark here. These errors usually indicate you have an old version of Git, or you don't have access to the repository. . Git will create the project directory for you. It should start in your default storage directory more on this later.
It was just my luck that the first repo I tried to clone contained such long file names. Try to set up authentication with or. So the app doesn't see this repo, although all files are downloaded. This can be done in the application settings of your Github account. There is a bug that we're tracking in Git for Windows that might be causing this issue. Maybe I have the same problem, I'm sure the username and password is correct, but it just fails to authenticate with my own repo, but it works well with github.
Git will then call the credential manager back with instructions to retain or erase the credentials. Use your username as usual. This is caused by the RequestHeader unset Authorization configuration being set. I was using our production tfs box right up to the time that I upgraded my Visual Studio. We tried this solution, but still not working.
Have a question about this project? After that I had no issues. Trying to access private corporate tfs. Cause 2 The user has been locked out of Stash because of too many incorrect login attempts. For now I found that just manually create the credential entry in the credential manager can solve the problem. Reproduces how often: 100% in my case with this particular repo. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. I'm able to clone the repo, pull from origin master, commit to changes, create and add new files but when it comes the time to push to Stash either a git push or git push origin master don't work.