You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using app-builder (via electron-builder) so I'm not sure where to submit a bug request.
I'm behind a corporate firewall using self-signed certificates. Is there a way to pass in a custom certificate via environment so that this error will go away:
Hi,
I was facing the same problem. Browsing the source code, it shows that the developer made a function to handle the proxy, func NewDownloader() *Downloader { return NewDownloaderWithTransport(&http.Transport{ Proxy: util.ProxyFromEnvironmentAndNpm, MaxIdleConns: 64, MaxIdleConnsPerHost: 64, IdleConnTimeout: 30 * time.Second, }) }
I've set the environment variables and npm config for the proxy and it's works perfectly. Hope it'll help you.
This issue is back on Windows since it seems the x509.SystemCertPool() is broken on Windows (see golang/go#16736).
This means that for Windows we end up ignoring all the other CAs known by the system.
The issue was introduced in this pull: #28
If I manually change to
return &tls.Config{
RootCAs: nil,
}
in downloader.go:getTlsConfig() it will start to work for me on Windows again. But of course this ignores the NODE_EXTRA_CA_CERTS variable...
I'm not a Go expert so I don't know how to properly get a RootCA that contains all known system CAs on Windows (RootCAs = nil will let TLS use those somehow), but I'll try to look into it.
If anyone knows more about this I'd be grateful.
Currently this is a big issue stopping our builds unless we do the "workaround" above.
I'm using app-builder (via electron-builder) so I'm not sure where to submit a bug request.
I'm behind a corporate firewall using self-signed certificates. Is there a way to pass in a custom certificate via environment so that this error will go away:
I currently do have the vars: SL_CERT_DIR and SSL_CERT_FILE set correctly.
(If this is an electron-builder issue and not an app-builder issue i apologize).
The text was updated successfully, but these errors were encountered: