question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fatal Error Message When Attempting to Fetch/Pull From Remote Origin

See original GitHub issue

Describe 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

  1. Select repository and branch
  2. Click on “Fetch origin” (also fails if attempting to pull files after they are fetched via other means)
  3. 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:closed
  • Created 2 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
stevewardcommented, Aug 30, 2021

Glad to hear this was resolved! I’m going to close this out.

0reactions
spnanoncommented, Aug 27, 2021

It’s fixed for me, now, too. I made no changes, either.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to fix 'fatal: remote origin already exists' Git error - Komodor
Resolving 'fatal: remote origin already exists' · 1. Remove the Existing Remote · 2. Update the Existing Remote's URL · 3. Rename the...
Read more >
How to resolve the fatal error when i try to pull or fetch a git repo
git pull. I get this error message. fatal error: Cannot fetch both refs/heads/pr/339 and refs/pull/339/head to refs/remotes/origin/pr/339.
Read more >
Failed to fetch from the remote repository.
Fetch feature I get the error: Fetching from origin. Error encountered while fetching: Failed to fetch from the remote repository. See the Output...
Read more >
Solved: How to resolve the fatal error of git pull command...
Solved: Hello, Can anyone please help resolve this issue. I am trying to run git pull command to pull the files to the...
Read more >
Fix Git's 'fatal: repository not found' error quickly | TheServerSide
If the repository was deleted or renamed, you'll obviously hit a Git repository not found error when you attempt to clone or fetch...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found