-
Notifications
You must be signed in to change notification settings - Fork 10.2k
Closed
Labels
bugConfirmed bugs or reports that are very likely to be bugsConfirmed bugs or reports that are very likely to be bugsmore-info-neededThe submitter needs to provide more information about the issueThe submitter needs to provide more information about the issue
Description
Description
I am running behind a corporation that self-signs its certificates, which means that I get this issue when I try to push any changes.
fatal: unable to access 'https://github.com/glenndevenish/[repo]/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.
Version
GitHub Desktop version: 0.7.2
OS version: Microsoft Windows [Version 10.0.10586]
Steps to Reproduce
(You will probably be unable to reproduce since you have to be in the corporation, although any self-signing corp. might have the same issue)
- Click publish branch
- Error message pops up.
Expected behavior: Update to occur successfully
Actual behavior: Repo was created, but no files were created.
Reproduces how often: Every time.
Logs
2017-08-15T13:38:44.759Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 1.196s)
2017-08-15T13:38:44.761Z - error: [ui] `git -c credential.helper= fetch --progress --prune origin` exited with an unexpected code: 128.
fatal: unable to access 'https://github.com/glenndevenish/[repo].git/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.
Additional Information
None.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugConfirmed bugs or reports that are very likely to be bugsConfirmed bugs or reports that are very likely to be bugsmore-info-neededThe submitter needs to provide more information about the issueThe submitter needs to provide more information about the issue