-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Comments
I try to analyze / debug the errors on my own now, too. maybe i can help. |
Can you provide some input in #18103 ? |
You can find the results here: #18103 (comment) Thx so much for your efforts, great idea with this http proxy unit test ;) |
any chance to get a solution soon? |
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. |
Thx joao. |
How is this issue going on? |
Please check out #22214 Closing this as duplicate |
Steps to Reproduce:
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.
The text was updated successfully, but these errors were encountered: