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

SSL errors after 1.5.1 update #11774

Closed
polizz opened this issue Sep 9, 2016 · 6 comments
Closed

SSL errors after 1.5.1 update #11774

polizz opened this issue Sep 9, 2016 · 6 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@polizz
Copy link

polizz commented Sep 9, 2016

- VSCode Version:
1.5.1
- OS Version:
El Capitan

Steps to Reproduce:

  1. Open Vscode and message is displayed "unable to get local issuer certificate".
  2. Click close and open extensions panel and message is displayed "Marketplace returned 'ECONNREFUSED'. Please check the 'http.proxy' setting."

I had already set my strict settings in the prior versions to get around corporate firewall.

"http.proxyStrictSSL": false

Another person sitting next to me (with same system) also has this issue after updating to 1.5.1.

@Arithmeticae
Copy link

I also have this same issue using windows 7. The circumstances are almost identical.

It worked previously in 1.4 using "http.proxyStrictSSL": false however I now get the same error messages you do.

@swaminathanvetri
Copy link

After upgrading VS Code to 1.5.1 on Mac (El Capitan), searching for any extensions in Extension Manager window, throws up the same error.

@jacob2512
Copy link

Just updated to 1.5.1 and this issue popped up. Was fine in 1.4.

@gmf002
Copy link

gmf002 commented Sep 9, 2016

I also have this issue after upgrading to 1.5.1 on Ubuntu 16.04. I have not tested on Windows yet.

"http.proxy" is set, and "http.proxyStrictSSL" is set to false. I had been getting a certificate error at first, but now it returns "Marketplace returned 'ECONNREFUSED'. Please check the 'http.proxy' setting." with no certificate error.

@ramya-rao-a
Copy link
Contributor

@joaomoreno related to #11702 ?

@joaomoreno
Copy link
Member

Duplicate of it.

A fix will be delivered very soon in 1.5.2. Until then, you can use the Insiders release.

@joaomoreno joaomoreno added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 11, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

7 participants