Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: unable to get local issuer certificate #1072

Closed
Govindmallurwar opened this issue Mar 7, 2019 · 3 comments
Closed

Error: unable to get local issuer certificate #1072

Govindmallurwar opened this issue Mar 7, 2019 · 3 comments
Labels

Comments

@Govindmallurwar
Copy link

Repro steps:

Action: azureFunctions.deploy
Error type: UNABLE_TO_GET_ISSUER_CERT_LOCALLY
Error Message: unable to get local issuer certificate

Version: 0.15.0
OS: win32
VS Code Version: 1.31.1

Call Stack
TLSSocket.onConnectSecure (_tls_wrap.js:1055:34)
TLSSocket.emit (events.js:182:13)
TLSSocket._finishInit (_tls_wrap.js:635:8)
@ejizba
Copy link
Contributor

ejizba commented Mar 8, 2019

@Govindmallurwar are you behind a corporate proxy or something similar? We've been mostly relying on VS Code to fix this for us, which is tracked here: microsoft/vscode#60773. I believe most situations are fixed already, but perhaps not all.

@ejizba
Copy link
Contributor

ejizba commented Mar 14, 2019

Note to self: Could try something like this: microsoft/vscode-docker#627

@ejizba ejizba added the bug label Mar 14, 2019
@ejizba ejizba added this to the 0.16.0 milestone Mar 14, 2019
@ejizba
Copy link
Contributor

ejizba commented Mar 18, 2019

I was debugging with Fiddler and was able to repro this bug since it inserts a cert to decrypt https traffic. However, it's fixed for me on VS Code insiders - see here for more info: microsoft/vscode#52880

Closing as external

@ejizba ejizba closed this as completed Mar 18, 2019
@ejizba ejizba removed this from the 0.16.0 milestone Mar 18, 2019
@ejizba ejizba added external and removed bug labels Mar 18, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators May 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants