Version 1.8 can not install Extensions in proxy env.

[yinay]

• VSCode Version:1.8
• OS Version:win 7

Steps to Reproduce:

1. settting the proxy .
   { "http.proxy": "",
   "http.proxyStrictSSL": false
   }
2. try to seach the extensions. can not work .

[joaomoreno]

Did you correctly set your proxy? Empty value seems wrong. Did you restart Code after changing those settings?

[yinay]

Oh , the http.proxy is not empty 。I just keep it empty in this.
the same settings can be work ,on version 1.7.
did some one know the http agent changed on v 1.8?

[joaomoreno]

@yinay Just to confirm: can you search for extensions?

[joewood]

I'm seeing this too on Ubuntu. Looks like a regression as it was working before 1.8. In verbose mode I see:

[10483:0106/190618:ERROR:cert_verify_proc_nss.cc(942)] CERT_PKIXVerifyCert for marketplace.visualstudio.com failed err=-8172
[main 7:06:18 PM] IPC#vscode-workbenchLoaded
[10483:0106/190619:INFO:CONSOLE(94)] "An unknown error occurred. Please consult the log for more details.", source: file:////usr/share/code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (94)

Which seems to be related to a chromium bug 30891. This relates to a cert with an AIA extension - which I think is essentially a missing cert in the chain loaded dynamically.

[joewood]

I found a workaround: -

After a bit of hacking around I found that Chromium uses its own (local) store for self-signed certs (not sure if this is a new thing). If I load the set of root CA certs using the tool described here everything starts working.

Basically, for each .crt I do a:

certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n <FILENAME> -i <FILENAME>

[xapienz]

I have the problem #18920, which shows the same log as in this bug. After today's update of vscode-insiders (when #21879 was merged) not only extensions, but also check of updates stopped working.
joewood's workaround worked well, thank you joewood!
I think this problem and #18920 may be the same.

[joaomoreno]

Please check out #22214

Closing this a duplicate

@joewood Thanks for the certutil tip