Can't install some extensions behind a corporate proxy

[bruno-brant]

• VSCode Version: 1.4.0-insider
• OS Version: Microsoft Windows [Version 6.1.7601](Windows 7)

Steps to Reproduce:

1. Open VS Code.
2. CTRL+P → ext install npm intellisense (for instance) → In the side menu, click install.
3. A clock icon appears on the extension icon in the left side of the window.
4. Nothing else happens.

I can, however, install some extensions like ESLINT. My guess is that some of those extensions are stored on a different address, and my proxy is blocking access to it. However, I can't determine the URL of the extension package so I'm unable to check if this is the case.

Thanks a lot.

[joaomoreno]

Did you configure your proxy settings in Code?

[bruno-brant]

Yes, proxy is set on the settings JSON. That's why I can see the list of available extensions, but I can't download them.

[joaomoreno]

Are you in China? Does it reproduce after restarting your machine?

All extensions come from the same place, so it doesn't make sense that some install and others don't.

[bruno-brant]

No, I'm in Brazil. My proxy (websense) may be doing something funny. Is there a log I can look into?

(my machine isn't the only one affected, everyone on my team is having the same trouble)

[joaomoreno]

Can you show me how you configured the proxy settings?

[bruno-brant]

My personal (user) settings.json contains the following lines:

    //-------- HTTP configuration --------
    // The proxy setting to use. If not set will be taken from the http_proxy and https_proxy environment variables
    "http.proxy": "https://user:password@webproxy:8080",
    "https.proxy": "http://user:password@webproxy:8080",
    // Whether the proxy server certificate should be verified against the list of supplied CAs.
    "http.proxyStrictSSL": false,

[bruno-brant]

There has to be a reason why eslint installs and other stuff doesn't. If the packages comes from the same url, maybe it's the installation process that's failing. Do I need administrative permission to install extensions? Seems silly since I can just copy them, but might be something along these lines.

[joaomoreno]

Can you figure out another extension that works? Maybe a theme...?

[bruno-brant]

Tried some themes. As you can see, spacemacs and sourlick won't install, but Markdown Theme Kit did.

[joaomoreno]

Do you get any information at all when opening the Developer Tools console (F1, Developer Tools)?

[vborzykin]

@joaomoreno I have same problem. And I configured the proxy settings by same pattern. But Developer Tools concole is empty (without errors or warnings).
Also when I open View->Problems (Ctrl+Shift+M) on my settings.json, I get a warning message "String does not match the pattern of "^https?://[^:]+(:\d+)?$|^$""

[joaomoreno]

@vborzykin You have another problem. What is the value you've put in http.proxy?

[vborzykin]

@joaomoreno No, pattern warning is second problem.
First problem is "Can't install extensions behind a corporate proxy" with same diagnostics.

my proxy setup is (from user's settings.json):
"http.proxyStrictSSL":false,
"http.proxy": "http://user:pass@webproxy:3128/",
"https.proxy": "https://user:pass@webproxy:3128/",

[joaomoreno]

@vborzykin Absolutely right about the regexp, pushed a fix.

Do you have the same problem as in you can install ESLint, but not other extensions?

[vborzykin]

@joaomoreno
Yes, I have
When I try install extention by command line, I have 407 error.
code --install-extension dbaeumer.vscode-eslint Found 'dbaeumer.vscode-eslint' in the marketplace. Installing... Server returned 407

[joaomoreno]

But you can install ESLint from the product itself (not command line)?

[vborzykin]

No, I can't install ESLint, without command line

[joaomoreno]

OK, you have another problem, since @HeavyStorm can install some extensions. Can you create another issue, showing us what exactly you see when you try to install an extension? Maybe a video recording? Thanks.

[brianary]

We also use Websense, but it isn't a proxy, it's a decrypting firewall. It functions as a MitM (manager-in-the-middle), which requires adding the Websense local cert as a trusted authority.

For some really dumb reason, VS and VS Code do not seem to use the Windows list of Trusted Authorities, where the certs were placed by group policy. Right now we can choose just not to use any SSL content (most extensions), or disable all SSL checking (strict-ssl=false in user settings), which would be wildly irresponsible. So that's a huge hassle.

We really need either VS Code to honor imported Trusted Authorities from the Windows cert store, or a way to import a trusted cert into VS Code's special, unique snowflake cert store.

[bruno-brant]

@joaomoreno I found another extension that installs successfully: jscs.

Tomorrow I'll check developer tools.

[joaomoreno]

@HeavyStorm The latest Insiders build has better error messages. Do you mind updating to that one?

[bruno-brant]

@joaomoreno I installed the latest Insiders and now all extensions seems to be installing correctly. Was anything changed in the extensions code?

[joaomoreno]

Not really... but maybe the fixes in the error handling case actually fixed something.

Glad to see you're unblocked. I'll close this, reopen pending if you see the issue again.

[brianary]

I've opened a new issue for my thing, issue #9790 .

[pendar747]

i cant install or view any extensions behind a corporate firewall