A few years ago I posted a video showing how to do this. You need to configure Alternate authentication credentials. Fix 4: If you are in a Windows 7 or using Git outside Visual Studio In the other scenario, I had to copy all the binaries from the bin folder to the git-core root folder. I had two diferent scenarios for this fix, the first one I copied the bin folder and pasted it inside the git-core folder. To \Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\TeamExplorer\Git\mingw32\libexec\git-core\ To handle this, you need to copy the right binaries to the right folder like the following:įrom \Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\TeamExplorer\Git\mingw32\bin\ This seems to be a bug in the Visual Studio 2017 instalation witch is loading a few Git binaries in a wrong folder/version. Fix 3: Copy VS Git binary files to another folder Fix 1: Git proxy configuration Fix 2: Visual Studio proxy configurationĮdit the file in %ProgramFiles(x86)%\Microsoft Visual Studio\2017\Common7\IDE. You may don’t need to apply all the fixes, try to apply one and test if it worked. For more information, see ' Working with support for GitHub Codespaces. If you still cannot connect, you may need to contact support. Follow some fixes I found and used to made it work in a few different VS versions. If possible, check any logging for rejected connections on your device. VS 2017 has a few updates, depending on the updating you are, the fix can be different. This problem was just happening with VS 2017 fatal: unable to access ‘ port 443: Timed out’ When I was trying to do anything with Git I was being prompted with the following error: fatal: unable to access ' port:443: Timed out'Īfter a TFS migration to VSTS, I had a few issues related to Git within Visual Studio 2017. Visual Studio 2017 - Git failed with fatal error
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |