"SELF_SIGNED_CERT_IN_CHAIN" error behind self-signed SSL network

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:

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 [e-mail] if don’t want to post it here.

2017-12-12T22.45.02.250Z.log

[ditori1976]

Had the same issue. Spent ages trying to find the error and solution for a windows machine in a company network. Thanks for pointing this direction. For windows my solution was:

>doskey lepton=c:\path_to_dir\Lepton.exe
> set NODE_TLS_REJECT_UNAUTHORIZED=0

Starting from cmd by simply typing “lepton” made it work like a charm 😃

[mgrebenets]

@marvinbelfort The best I could do so far is this shell alias:

alias lepton='NODE_TLS_REJECT_UNAUTHORIZED=0 /Applications/Lepton.app/Contents/MacOS/Lepton'

Then I can just run it in terminal as lepton& or just lepton and keep the terminal tab open, or there are other ways.

Ideally though, Lepton should allow turning of SSL verification or specifying self-signed certs in ~/.leptonrc or accept the Chromium’s --ignore-certificate-errors. Or I don’t know, trust the certs if they are marked “always trust” in OS X keychain 🤷‍♂️