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

Proxy settings not working with extension gallery: net::ERR_TUNNEL_CONNECTION_FAILED #20786

Closed
FloMaetschke opened this issue Feb 17, 2017 · 9 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) proxy Issues regarding network proxies
Milestone

Comments

@FloMaetschke
Copy link

  • VSCode Version: Code - Insiders 1.10.0-insider (496b804, 2017-02-16T07:10:22.864Z)
  • OS Version: Windows_NT ia32 6.1.7601
  • Extensions:
Extension Author Version
vscode-opennewinstance chrisdias 0.0.4
npm-intellisense christian-kohler 0.1.4
vscode-npm-source dkundel 0.0.3
githistory donjayamanne 0.1.2
KillTasksButton dtrajano 0.0.4
CreateModule HookyQR 0.0.5
task-master ianhoney 0.1.37
output-colorizer IBM 0.0.8
debugger-for-phantomjs iradul 0.1.1
csharpextensions jchannon 1.1.0
csharp ms-vscode 1.5.3
debugger-for-chrome msjsdiag 2.3.2
color-highlight naumovs 1.2.1
material-icon-theme PKief 1.1.4
qub-msbuild qub 0.5.0
Material-theme zhuangtongfa 1.0.3
html-css-class-completion Zignd 1.0.3

Steps to Reproduce:

  1. Open Extension Gallery
  2. Search for 'test'

The extension gallery is no longer working.

For a longer amount of days the version gallery seems to be broken at my office pc, which is behind a corporate proxy.

I always get a net::ERR_TUNNEL_CONNECTION_FAILED when the gallery tries to fetch
https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery

My vscode was set up with proxy credentials in config before. This did work for a long time very well. i was actually able to download extensions, after @joaomoreno fixed an early version in beginning of 2016 and uploaded it here for testing (sorry i dont fint the thread right now). This bugfix got merged in the official version later and worked fine. But as of 3 Months or so its no longer working.

When using google i found this page: http://code.visualstudio.com/docs/setup/setup-overview

I tried switching to env variables. But this does not work either, so i guess its a problem with vscode itself

I switched to HTTP_PROXY and HTTPS_PROXY env variables now, which seems to be the recommended option. But this doesn't work either.

@FloMaetschke
Copy link
Author

I try to analyze / debug the errors on my own now, too. maybe i can help.

@joaomoreno joaomoreno self-assigned this Feb 17, 2017
@joaomoreno
Copy link
Member

Can you provide some input in #18103 ?

@joaomoreno joaomoreno added the proxy Issues regarding network proxies label Feb 17, 2017
@joaomoreno joaomoreno added this to the Backlog milestone Feb 17, 2017
@joaomoreno joaomoreno added the bug Issue identified by VS Code Team member as probable bug label Feb 17, 2017
@FloMaetschke
Copy link
Author

You can find the results here: #18103 (comment)

Thx so much for your efforts, great idea with this http proxy unit test ;)

@FloMaetschke
Copy link
Author

any chance to get a solution soon?

@joaomoreno
Copy link
Member

This happens due to the use of XHR in the renderer. cc @jrieken

Soon, but not this month yet, very busy with other stuff. I'll make it a priority for March.

@FloMaetschke
Copy link
Author

Thx joao.

@hh9527
Copy link

hh9527 commented Mar 7, 2017

How is this issue going on?

@FloMaetschke
Copy link
Author

#21879

@joaomoreno
Copy link
Member

joaomoreno commented Mar 8, 2017

Please check out #22214

Closing this as duplicate

@joaomoreno joaomoreno added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 8, 2017
@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
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) proxy Issues regarding network proxies
Projects
None yet
Development

No branches or pull requests

3 participants