Schannel: failed to recieve handshake, SSL/TLS connection failed

[bmarshallgrowers]

The problem

Any time i try to perform any push or pull action I receive the following error "fatal: unable to access '{DIRECTORY}': schannel: failed to receive handshake, SSL/TLS connection failed

Release version

3.1.1

Operating system

Windows 11

Steps to reproduce the behavior

No response

Log files

No response

Screenshots

Additional context

No response

[sergiou87]

Hey @bmarshallgrowers 👋 Could you upload the log file from GitHub Desktop so that I could get some more information about this error? To access the log files go to the file menu in GitHub Desktop and select Help > Show Logs.
The log files are created daily -- please upload a log file as an attachment from a day where you experienced the issue.

[github-actions]

Thank you for your issue!
We haven’t gotten a response to our questions above. With only the information that is currently in the issue, we don’t have enough information to take action. We’re going to close this but don’t hesitate to reach out if you have or find the answers we need. If you answer our questions above, this issue will automatically reopen.

[bmarshallgrowers]

@sergiou87 Here is a log from today (10/18/22).
2022-10-18.desktop.production.log

[steveward]

Thanks for the log @bmarshallgrowers. Could you run git config --global http.sslBackend schannel to see if that gets things working?

[bmarshallgrowers]

@steveward I ran that as instructed

but still recieve the error even after restarting my computer

[bmarshallgrowers]

@steveward this seems to have occured when my system updated from windows 10 to windows 11 if that helps at all

[steveward]

@bmarshallgrowers do you see the same error when attempting to clone/access a repository hosted on GitHub? That should help narrow down if this is a specific issue with your Azure repository.

[bmarshallgrowers]

@steveward i did not have a problem cloning a repo from github (I cloned angular). But I have also not had any problems cloning any repo in my organization. And none of my other 12 developers in my organization have this error occur.