hackjutsu/Lepton

"SELF_SIGNED_CERT_IN_CHAIN" error behind self-signed SSL network

Open

#250 opened on Dec 12, 2017

View on GitHub
 (14 comments) (0 reactions) (0 assignees)JavaScript (9,902 stars) (502 forks)batch import
help wantedmore information needed

Description

The more we know about your system and use case, the more easily and likely we can help.

Environment info

  • OS: Win 10

  • App Version (Command/Ctrl + ,): Who knows / Doesn't matter: Who knows: Theres no way to tell from the application when its stuck not logging in Doesn't matter: The behavior is the same between 1.5.0 and 1.5.1-alpha

Description of the problem / feature request / question:

No version of Lepton has never logged in to GitHub for me. I have deleted the C:\Users<username>\AppData\Roaming\Lepton\ folder multiple times - it has zero effect

If possible, provide a sample gist or screenshot:

image

If possible, provide the log files

  • Mac: ~/Library/Application Support/Lepton/logs
  • Windows: C:\Users\<username>\AppData\Roaming\Lepton\logs
  • Linux: ~/.cached/Lepton/logs

The debug mode is recommended when producing the logs. You can send your log file to cosmo.lepton@gmail.com if don't want to post it here.

2017-12-12T22.45.02.250Z.log

Contributor guide

Tech stack
javascriptnodejselectron
Domain
authenticationdesktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Node.jsElectron basicsSSL/TLS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the error handling in Lepton's network requests, particularly in the GitHub authentication flow. The log file shows the certificate error; check if the app uses the `request` library or Node's `https` module. Consider adding an option to ignore self signed certificates or use environment variable `NODE TLS REJECT UNAUTHORIZED`. Refer to the log file attached in the issue and any related discussions in the comments.
"SELF_SIGNED_CERT_IN_CHAIN" error behind self-signed SSL network · hackjutsu/Lepton#250 | Good First Issue