Fatal Error Message When Attempting to Fetch/Pull From Remote Origin
See original GitHub issueDescribe the bug
GitHub Desktop fails to fetch and pull files from remote origin to local repository when the “Fetch origin” option is selected. Gives the message:
fatal: unable to access 'https://gitgud.io/<user>/<name>/': schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed). More detail may be available in the Windows System event log."
Version & OS
Version 2.9.0, 64-bit
Windows 7, 64-bit
Steps to reproduce the behavior
- Select repository and branch
- Click on “Fetch origin” (also fails if attempting to pull files after they are fetched via other means)
- See error message
Expected behavior
GitHub Desktop would fetch files from origin and pull, updating the local repository on computer.
Actual behavior
Popup with the error message:
fatal: unable to access 'https://gitgud.io/<user>/<name>/': schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed). More detail may be available in the Windows System event log.
Screenshots
Can provide if necessary, but would just be an image of the error message, mostly.
Logs
Can provide if necessary, but log file just seems to read out the same error message.
Additional context
Fetching/pulling worked after setting http.schannelCheckRevoke to false in Git Bash, then fetching and pulling in Git GUI/Bash. This is what led me to believe it is a problem specific to GitHub Desktop.
Remote repository in question is located in GitLab/GitGud (I’m not familiar with the separation between them and GitHub, if any). GitHub Desktop fetched/pulled from this repository for several years without issue.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (4 by maintainers)
Top GitHub Comments
Glad to hear this was resolved! I’m going to close this out.
It’s fixed for me, now, too. I made no changes, either.