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 support for extension gallery #69

Closed
diegovilar opened this Issue Nov 18, 2015 · 118 comments

Comments

Projects
None yet
@diegovilar

diegovilar commented Nov 18, 2015

Whenever I try to install any extension, using ext install, I get a connect ETIMEDOUT 191.238.172.191:443 error.

Trying to navigate to https://191.238.172.191 in the browser produces a warning regarding the certificate being valid only for *.market.visualstudio.com, but I'm allowed to proceed.

Shouldn't VSCode try to connect to the name instead of the IP?

I'm behind a proxy, VSCode updates just fine behind it, and also lists the available extensions. The firewall here logs the invalid certificate but allows the connection to proceed. Doesn't look like a problem in my end...

OS: Windows 7
VSCode: 0.10.1

@RefractedPaladin

This comment has been minimized.

Show comment
Hide comment
@RefractedPaladin

RefractedPaladin Nov 18, 2015

I'm getting nearly the same thing although it never lists the available extensions for me. I get a "self signed certificate in certificate chain" error but I believe it is related to this issue as the rest is the same as well.

OS: Windows 8.1
VSCode: 0.10.1

RefractedPaladin commented Nov 18, 2015

I'm getting nearly the same thing although it never lists the available extensions for me. I get a "self signed certificate in certificate chain" error but I believe it is related to this issue as the rest is the same as well.

OS: Windows 8.1
VSCode: 0.10.1

@pedrosousa

This comment has been minimized.

Show comment
Hide comment
@pedrosousa

pedrosousa Nov 18, 2015

Currently using ZScaler as (company) proxy. It usually needs its own certificate (acting as a MITM) to be considered in order not to have the following error: "unable to get local issuer certificate".
There should be either a "valid certificates" configuration (accepting a folder or a file path) or a "do not validate the certificate chain" boolean setting.

pedrosousa commented Nov 18, 2015

Currently using ZScaler as (company) proxy. It usually needs its own certificate (acting as a MITM) to be considered in order not to have the following error: "unable to get local issuer certificate".
There should be either a "valid certificates" configuration (accepting a folder or a file path) or a "do not validate the certificate chain" boolean setting.

@CL0SeY

This comment has been minimized.

Show comment
Hide comment
@CL0SeY

CL0SeY Nov 19, 2015

It seems like vscode is ignoring the "http.proxy" configuration when downloading extensions. For me, it works fine when listing extensions.

So, it's getting the IP resolved and connecting directly, rather than using a proxy.

CL0SeY commented Nov 19, 2015

It seems like vscode is ignoring the "http.proxy" configuration when downloading extensions. For me, it works fine when listing extensions.

So, it's getting the IP resolved and connecting directly, rather than using a proxy.

@itbaby

This comment has been minimized.

Show comment
Hide comment
@itbaby

itbaby Nov 19, 2015

yeah, I met the same issue.

itbaby commented Nov 19, 2015

yeah, I met the same issue.

@blastmann

This comment has been minimized.

Show comment
Hide comment
@blastmann

blastmann Nov 19, 2015

same issue here, can't install extensions~

blastmann commented Nov 19, 2015

same issue here, can't install extensions~

@joaomoreno joaomoreno changed the title from Getting "connect ETIMEDOUT 191.238.172.191:443" when trying to install extensions to Proxy support for extension gallery Nov 19, 2015

@joaomoreno joaomoreno closed this in #186 Nov 19, 2015

joaomoreno added a commit that referenced this issue Nov 19, 2015

@joaomoreno joaomoreno added this to the Nov 2015 - Recovery milestone Nov 19, 2015

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Nov 19, 2015

Member

Not yet fixed.

Member

bpasero commented Nov 19, 2015

Not yet fixed.

@bpasero bpasero reopened this Nov 19, 2015

@bpasero bpasero removed this from the Nov 2015 - Recovery milestone Nov 19, 2015

@bpasero bpasero assigned bpasero and unassigned joaomoreno Nov 19, 2015

@bpasero bpasero added this to the Dec 2015 milestone Nov 19, 2015

@iamzhout

This comment has been minimized.

Show comment
Hide comment
@iamzhout

iamzhout Nov 20, 2015

suggest to reference atom's implementation, by using strict-ssl = false
https://atom.io/docs/v1.0.0/getting-started-installing-atom#setting-up-a-proxy

iamzhout commented Nov 20, 2015

suggest to reference atom's implementation, by using strict-ssl = false
https://atom.io/docs/v1.0.0/getting-started-installing-atom#setting-up-a-proxy

@sparty02

This comment has been minimized.

Show comment
Hide comment
@sparty02

sparty02 Nov 20, 2015

@bpasero Out of curiosity, is there a general timeframe for releasing changes merged into master?

sparty02 commented Nov 20, 2015

@bpasero Out of curiosity, is there a general timeframe for releasing changes merged into master?

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Nov 20, 2015

Member

Like always, we will maintain a monthly release cadence. There are plans to get an unstable update channel out there, but this might take a while.

Member

joaomoreno commented Nov 20, 2015

Like always, we will maintain a monthly release cadence. There are plans to get an unstable update channel out there, but this might take a while.

@sparty02

This comment has been minimized.

Show comment
Hide comment
@sparty02

sparty02 Nov 20, 2015

Thanks for the info!

sparty02 commented Nov 20, 2015

Thanks for the info!

@KindDragon

This comment has been minimized.

Show comment
Hide comment
@KindDragon

KindDragon Nov 23, 2015

Contributor

@bpasero Will it works with MS NTLM proxy?

Contributor

KindDragon commented Nov 23, 2015

@bpasero Will it works with MS NTLM proxy?

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Nov 23, 2015

Member

Not sure, @aeschli can you comment, it uses your proxy work.

Member

bpasero commented Nov 23, 2015

Not sure, @aeschli can you comment, it uses your proxy work.

@aeschli

This comment has been minimized.

Show comment
Hide comment
@aeschli

aeschli Nov 23, 2015

Contributor

Sorry I don't know how MS NTLM is related to HTTP proxies. Do you have more information, @KindDragon ?

Contributor

aeschli commented Nov 23, 2015

Sorry I don't know how MS NTLM is related to HTTP proxies. Do you have more information, @KindDragon ?

@KindDragon

This comment has been minimized.

Show comment
Hide comment
@KindDragon

KindDragon Nov 23, 2015

Contributor

I mean NTLM authentication for HTTP proxy. Python PIP manager for example support HTTP proxy, but doesn't support NTLM authentication.

Contributor

KindDragon commented Nov 23, 2015

I mean NTLM authentication for HTTP proxy. Python PIP manager for example support HTTP proxy, but doesn't support NTLM authentication.

@pedrosousa

This comment has been minimized.

Show comment
Hide comment
@pedrosousa

pedrosousa Nov 23, 2015

Arkady,

Have you tried cntlm (http://cntlm.sourceforge.net)? I used it a few
months ago with success in order to use several command line tools with our
NTLM-authentication based proxy.

On Mon, Nov 23, 2015 at 12:29 PM, Arkady Shapkin notifications@github.com
wrote:

I mean NTLM authentication for HTTP proxy. Python PIP manager for example
support HTTP proxy, but doesn't support NTLM authentication.


Reply to this email directly or view it on GitHub
#69 (comment).

pedrosousa commented Nov 23, 2015

Arkady,

Have you tried cntlm (http://cntlm.sourceforge.net)? I used it a few
months ago with success in order to use several command line tools with our
NTLM-authentication based proxy.

On Mon, Nov 23, 2015 at 12:29 PM, Arkady Shapkin notifications@github.com
wrote:

I mean NTLM authentication for HTTP proxy. Python PIP manager for example
support HTTP proxy, but doesn't support NTLM authentication.


Reply to this email directly or view it on GitHub
#69 (comment).

@KindDragon

This comment has been minimized.

Show comment
Hide comment
@KindDragon

KindDragon Nov 23, 2015

Contributor

Have you tried cntlm (http://cntlm.sourceforge.net)?

Yes, I use it when I have to, but it would be better without it. Just use proxy from system settings.

Contributor

KindDragon commented Nov 23, 2015

Have you tried cntlm (http://cntlm.sourceforge.net)?

Yes, I use it when I have to, but it would be better without it. Just use proxy from system settings.

@catlion

This comment has been minimized.

Show comment
Hide comment
@catlion

catlion Dec 1, 2015

Having cntlm installed, I can search and list extensions gallery, but download fails with connect ECONNREFUSED 191.238.172.191:443 error. Looks like proxy settings ignored for downloads

catlion commented Dec 1, 2015

Having cntlm installed, I can search and list extensions gallery, but download fails with connect ECONNREFUSED 191.238.172.191:443 error. Looks like proxy settings ignored for downloads

@lucax88x

This comment has been minimized.

Show comment
Hide comment
@lucax88x

lucax88x Dec 2, 2015

Someone know which version of VS Code will have this fix? with 0.10.2 and 0.10.3 still not working

lucax88x commented Dec 2, 2015

Someone know which version of VS Code will have this fix? with 0.10.2 and 0.10.3 still not working

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Dec 2, 2015

Member

Fix will only come at the end of December.

Member

joaomoreno commented Dec 2, 2015

Fix will only come at the end of December.

@Bigous

This comment has been minimized.

Show comment
Hide comment
@Bigous

Bigous Dec 11, 2015

Contributor

@joaomoreno Same problem to me... I think it should be left open until it is fixed...

Contributor

Bigous commented Dec 11, 2015

@joaomoreno Same problem to me... I think it should be left open until it is fixed...

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Dec 11, 2015

Member

Since it is fixed in code, it is closed; that is the policy. There is a milestone attributed to it which informs about when the fix is coming out in the product.

Member

joaomoreno commented Dec 11, 2015

Since it is fixed in code, it is closed; that is the policy. There is a milestone attributed to it which informs about when the fix is coming out in the product.

@FDIM

This comment has been minimized.

Show comment
Hide comment
@FDIM

FDIM Feb 5, 2016

Solution that @paulomorgado worked for me.

FDIM commented Feb 5, 2016

Solution that @paulomorgado worked for me.

@ZodmanPerth

This comment has been minimized.

Show comment
Hide comment
@ZodmanPerth

ZodmanPerth Feb 11, 2016

@joaomoreno So I'm now on 0.10.8 and I'm still getting the connect ETIMEDOUT 191.238.172.191:443 error.
However I have noticed that even Check for Updates... fails, so maybe it's just an overly restrictive environment that's the real culprit.

ZodmanPerth commented Feb 11, 2016

@joaomoreno So I'm now on 0.10.8 and I'm still getting the connect ETIMEDOUT 191.238.172.191:443 error.
However I have noticed that even Check for Updates... fails, so maybe it's just an overly restrictive environment that's the real culprit.

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Feb 11, 2016

Member

@ZodmanPerth Definitely sounds like it. Just reconfirm that the values for http.proxy and http.proxyStrictSSL are correct.

Member

joaomoreno commented Feb 11, 2016

@ZodmanPerth Definitely sounds like it. Just reconfirm that the values for http.proxy and http.proxyStrictSSL are correct.

@mponton

This comment has been minimized.

Show comment
Hide comment
@mponton

mponton Feb 11, 2016

I'm still having issues myself. I've been trying to confirm proxy is used at all and cannot. My proxy is CNTLM running locally on localhost:10080. It works very well for multiple other apps like git and Dropbox. When I start it in foreground mode with verbose logging, I see connections as they come in. Yet, I never see anything for VS Code. I tried using http_proxy and https_proxy env. variables and setting the http.proxy and http.proxyStrictSSL in settings, no luck.

Finally I disabled all proxy settings and started a Wireshark session thinking I could at least see the non-proxied query, than I would enable proxy and confirm I don't see it anymore. Surprisingly I can't see the direct attempt to connect to 191.238.172.191 at all. The following GIF shows that no proxy env. variables are set, that packets are being captured (only one interface active on my PC), and that user settings don't have proxy settings enabled. Yet, when I ext install things timeout with an error and my network trace (filtered on IP 191.238.172.191) is not showing any attempt to even connect to that IP:

vscode_ext_install_issue

Version info:

vscode_ext_install_issue-version

I might just be blind or in need of a good coffee, but if not, any idea why? Could the IP in the message not be the one where the attempt is made to connect?

In any case, thanks and great work guys!

mponton commented Feb 11, 2016

I'm still having issues myself. I've been trying to confirm proxy is used at all and cannot. My proxy is CNTLM running locally on localhost:10080. It works very well for multiple other apps like git and Dropbox. When I start it in foreground mode with verbose logging, I see connections as they come in. Yet, I never see anything for VS Code. I tried using http_proxy and https_proxy env. variables and setting the http.proxy and http.proxyStrictSSL in settings, no luck.

Finally I disabled all proxy settings and started a Wireshark session thinking I could at least see the non-proxied query, than I would enable proxy and confirm I don't see it anymore. Surprisingly I can't see the direct attempt to connect to 191.238.172.191 at all. The following GIF shows that no proxy env. variables are set, that packets are being captured (only one interface active on my PC), and that user settings don't have proxy settings enabled. Yet, when I ext install things timeout with an error and my network trace (filtered on IP 191.238.172.191) is not showing any attempt to even connect to that IP:

vscode_ext_install_issue

Version info:

vscode_ext_install_issue-version

I might just be blind or in need of a good coffee, but if not, any idea why? Could the IP in the message not be the one where the attempt is made to connect?

In any case, thanks and great work guys!

@kikokikok

This comment has been minimized.

Show comment
Hide comment
@kikokikok

kikokikok Feb 16, 2016

Hi,
I've been able to identify an unresolved issue that might help solving the issue.
when setting
"http.proxy": "http://[user]:[password]@[url]:8080",
"http.proxyStrictSSL": false

It doesn't work for the following reason:
workbench.main.js:87 getaddrinfo ENOTFOUND [user] [user]:80: Error: getaddrinfo ENOTFOUND [user] [user]:80
at errnoException (dns.js:25:10)
at GetAddrInfoReqWrap.onlookup as oncomplete

Our corporate proxy is NTLM based and can leverage on declarative authentication in the Proxy Url

Seems like the parsing of the username and password is bugged,

kikokikok commented Feb 16, 2016

Hi,
I've been able to identify an unresolved issue that might help solving the issue.
when setting
"http.proxy": "http://[user]:[password]@[url]:8080",
"http.proxyStrictSSL": false

It doesn't work for the following reason:
workbench.main.js:87 getaddrinfo ENOTFOUND [user] [user]:80: Error: getaddrinfo ENOTFOUND [user] [user]:80
at errnoException (dns.js:25:10)
at GetAddrInfoReqWrap.onlookup as oncomplete

Our corporate proxy is NTLM based and can leverage on declarative authentication in the Proxy Url

Seems like the parsing of the username and password is bugged,

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Feb 16, 2016

Member

@mponton Strange. It definitely looks like there's something else going on in your system. The request should appear in Wireshark imo.

Member

joaomoreno commented Feb 16, 2016

@mponton Strange. It definitely looks like there's something else going on in your system. The request should appear in Wireshark imo.

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Feb 16, 2016

Member

@kikokikok Authentication was fixed in #1942. Are you sure you are using the latest 0.10.8 version?

Member

joaomoreno commented Feb 16, 2016

@kikokikok Authentication was fixed in #1942. Are you sure you are using the latest 0.10.8 version?

@kikokikok

This comment has been minimized.

Show comment
Hide comment
@kikokikok

kikokikok commented Feb 16, 2016

image

Yup :)

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Feb 16, 2016

Member

When you set your actual username, password and url, what do you see?

Member

joaomoreno commented Feb 16, 2016

When you set your actual username, password and url, what do you see?

@kikokikok

This comment has been minimized.

Show comment
Hide comment
@kikokikok

kikokikok Feb 17, 2016

if I try to List the Extensions, it doesn't show anything. After a while I have an error
image

When I toggle developper mode this is what I see
getaddrinfo ENOTFOUND [mylogin] [mylogin]:80: Error: getaddrinfo ENOTFOUND [mylogin] [mylogin] :80
at errnoException (dns.js:25:10)
at GetAddrInfoReqWrap.onlookup as oncomplete

kikokikok commented Feb 17, 2016

if I try to List the Extensions, it doesn't show anything. After a while I have an error
image

When I toggle developper mode this is what I see
getaddrinfo ENOTFOUND [mylogin] [mylogin]:80: Error: getaddrinfo ENOTFOUND [mylogin] [mylogin] :80
at errnoException (dns.js:25:10)
at GetAddrInfoReqWrap.onlookup as oncomplete

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Feb 17, 2016

Member

What do you get if you run node and in its interactive prompt run require('url').parse('YOUR PROXY URL')?

Namely, do the host and auth parameters look OK to you?

Member

joaomoreno commented Feb 17, 2016

What do you get if you run node and in its interactive prompt run require('url').parse('YOUR PROXY URL')?

Namely, do the host and auth parameters look OK to you?

@kikokikok

This comment has been minimized.

Show comment
Hide comment
@kikokikok

kikokikok Feb 17, 2016

that's exactly what I tracked down while I was debugging, the parsing has something wrong and you're right i tracked it down to the https-proxy module which leverages on the node url parser.
the data is totally messed up.

I Managed to track it down to the presence of a '#' character in my password. might be worth url-encoding the content maybe

kikokikok commented Feb 17, 2016

that's exactly what I tracked down while I was debugging, the parsing has something wrong and you're right i tracked it down to the https-proxy module which leverages on the node url parser.
the data is totally messed up.

I Managed to track it down to the presence of a '#' character in my password. might be worth url-encoding the content maybe

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Feb 17, 2016

Member

Good catch. You should url encode the password before putting it in a url yeah.

Member

joaomoreno commented Feb 17, 2016

Good catch. You should url encode the password before putting it in a url yeah.

@xaqfox

This comment has been minimized.

Show comment
Hide comment
@xaqfox

xaqfox Feb 18, 2016

I'm running CNTLM with Code 0.10.8 and resolved this error by adding the protocol to the http.proxy preference.

I was attempting with "http.proxy": "localhost:3128" and I changed it to "https://localhost:3128" to get it working.

Parsing the old URL in node's interactive console gave the following output, which put me on the right track (thanks!):

require('url').parse('localhost:3128')
Url {
protocol: 'localhost:',
slashes: null,
auth: null,
host: '3128',
port: null,
hostname: '3128',
hash: null,
search: null,
query: null,
pathname: null,
path: null,
href: 'localhost:3128' }

xaqfox commented Feb 18, 2016

I'm running CNTLM with Code 0.10.8 and resolved this error by adding the protocol to the http.proxy preference.

I was attempting with "http.proxy": "localhost:3128" and I changed it to "https://localhost:3128" to get it working.

Parsing the old URL in node's interactive console gave the following output, which put me on the right track (thanks!):

require('url').parse('localhost:3128')
Url {
protocol: 'localhost:',
slashes: null,
auth: null,
host: '3128',
port: null,
hostname: '3128',
hash: null,
search: null,
query: null,
pathname: null,
path: null,
href: 'localhost:3128' }

@mponton

This comment has been minimized.

Show comment
Hide comment
@mponton

mponton Feb 18, 2016

@xaqfox Wow man, this fixed the issue on my side. I bit sad that different projects need different a syntax for http_proxy (that said I can't believe I did not try that syntax myself). Thanks for the tip! (Still not sure why I could not see any traffic in the first place but hey, I got other things to take care of).

mponton commented Feb 18, 2016

@xaqfox Wow man, this fixed the issue on my side. I bit sad that different projects need different a syntax for http_proxy (that said I can't believe I did not try that syntax myself). Thanks for the tip! (Still not sure why I could not see any traffic in the first place but hey, I got other things to take care of).

@schwarzie2478

This comment has been minimized.

Show comment
Hide comment
@schwarzie2478

schwarzie2478 Feb 26, 2016

I finally found all the pieces needed for a complete solution working behind a corporate proxy on Windows:

I use fidller as authentication proxy ( no need to set fiddler as system proxy replacement)

Set environment variables: (also usefull for other tools)
_JAVA_OPTIONS=-Dhttp.proxyHost="localhost" -Dhttp.proxyPort="8888" -Dhttps.proxyHost="localhost" -Dhttps.proxyPort="8888"
HTTP_PROXY : 127.0.0.1:8888
HTTPS_PROXY : 127.0.0.1:8888

for SSL certificate problem:

create a .coderc file in your user dir
with contents:

strict-ssl=false

I also added it to the user settings file but that didn't help with the extentions

Make sure you have updated to version 0.10.8 to have the fix for installing extentions

schwarzie2478 commented Feb 26, 2016

I finally found all the pieces needed for a complete solution working behind a corporate proxy on Windows:

I use fidller as authentication proxy ( no need to set fiddler as system proxy replacement)

Set environment variables: (also usefull for other tools)
_JAVA_OPTIONS=-Dhttp.proxyHost="localhost" -Dhttp.proxyPort="8888" -Dhttps.proxyHost="localhost" -Dhttps.proxyPort="8888"
HTTP_PROXY : 127.0.0.1:8888
HTTPS_PROXY : 127.0.0.1:8888

for SSL certificate problem:

create a .coderc file in your user dir
with contents:

strict-ssl=false

I also added it to the user settings file but that didn't help with the extentions

Make sure you have updated to version 0.10.8 to have the fix for installing extentions

@KindDragon

This comment has been minimized.

Show comment
Hide comment
@KindDragon

KindDragon Feb 29, 2016

Contributor

Hi,
I've been able to identify an unresolved issue that might help solving the issue.
when setting
"http.proxy": "http://[user]:[password]@[url]:8080",
"http.proxyStrictSSL": false

It doesn't work for the following reason:
workbench.main.js:87 getaddrinfo ENOTFOUND [user] [user]:80: Error: getaddrinfo ENOTFOUND [user] [user]:80
at errnoException (dns.js:25:10)
at GetAddrInfoReqWrap.onlookup as oncomplete

Our corporate proxy is NTLM based and can leverage on declarative authentication in the Proxy Url

Seems like the parsing of the username and password is bugged,

It's work for me we %5С as delimiter between domain and login in username: http://superuser.com/a/395177/64719

"http.proxy": "http://DOMAIN%5CUSERNAME:PASSWORD@PROXYIP:PROXYPORT"

Contributor

KindDragon commented Feb 29, 2016

Hi,
I've been able to identify an unresolved issue that might help solving the issue.
when setting
"http.proxy": "http://[user]:[password]@[url]:8080",
"http.proxyStrictSSL": false

It doesn't work for the following reason:
workbench.main.js:87 getaddrinfo ENOTFOUND [user] [user]:80: Error: getaddrinfo ENOTFOUND [user] [user]:80
at errnoException (dns.js:25:10)
at GetAddrInfoReqWrap.onlookup as oncomplete

Our corporate proxy is NTLM based and can leverage on declarative authentication in the Proxy Url

Seems like the parsing of the username and password is bugged,

It's work for me we %5С as delimiter between domain and login in username: http://superuser.com/a/395177/64719

"http.proxy": "http://DOMAIN%5CUSERNAME:PASSWORD@PROXYIP:PROXYPORT"

@kylewolfe

This comment has been minimized.

Show comment
Hide comment
@kylewolfe

kylewolfe Mar 3, 2016

I'm also having issues behind an NTLM proxy. I do not have any special characters in my password. I often do not get an error, but the list never loads. On v0.10.8.

kylewolfe commented Mar 3, 2016

I'm also having issues behind an NTLM proxy. I do not have any special characters in my password. I often do not get an error, but the list never loads. On v0.10.8.

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Mar 4, 2016

Member

@kylewolfe What do you get if you run node and in its interactive prompt run require('url').parse('YOUR PROXY URL')?

Namely, do the host and auth parameters look OK to you?

Member

joaomoreno commented Mar 4, 2016

@kylewolfe What do you get if you run node and in its interactive prompt run require('url').parse('YOUR PROXY URL')?

Namely, do the host and auth parameters look OK to you?

@KindDragon

This comment has been minimized.

Show comment
Hide comment
@KindDragon

KindDragon Mar 4, 2016

Contributor

I'm also having issues behind an NTLM proxy. I do not have any special characters in my password. I often do not get an error, but the list never loads. On v0.10.8.

Try to specify the username with your domain

Contributor

KindDragon commented Mar 4, 2016

I'm also having issues behind an NTLM proxy. I do not have any special characters in my password. I often do not get an error, but the list never loads. On v0.10.8.

Try to specify the username with your domain

@ZodmanPerth

This comment has been minimized.

Show comment
Hide comment
@ZodmanPerth

ZodmanPerth Mar 21, 2016

Just getting back to trying to resolve my particular issue again. Installing v0.10.11 and adding "http://" to my http.proxy URL fixes my issue accessing the extensions list for browsing.

Interestingly though, the traffic still doesn't show up on my Fiddler4 session.

ZodmanPerth commented Mar 21, 2016

Just getting back to trying to resolve my particular issue again. Installing v0.10.11 and adding "http://" to my http.proxy URL fixes my issue accessing the extensions list for browsing.

Interestingly though, the traffic still doesn't show up on my Fiddler4 session.

@KushagraGitter

This comment has been minimized.

Show comment
Hide comment
@KushagraGitter

KushagraGitter Apr 4, 2016

put below lines in file setting.json
"http.proxy": "http://yourproxy.com:8080",
"https.proxy":"https://yourproxy.com:8080"

KushagraGitter commented Apr 4, 2016

put below lines in file setting.json
"http.proxy": "http://yourproxy.com:8080",
"https.proxy":"https://yourproxy.com:8080"

@Barryrowe

This comment has been minimized.

Show comment
Hide comment
@Barryrowe

Barryrowe Apr 26, 2016

This was working with @joaomoreno 's fix a long time ago, but something broke it again along the way, and seems to be worse. Through an NTLM negotiated proxy, none of these work-arounds seem to work. I'm on Windows 7, VSCode Insiders v1.0.1-insider.

I have the following set (and have tried with/without each of them):

  "http.proxy": "http://myproxyhost:11111",
  "https.proxy": "http://myproxyhost:11111",
  "http.proxyStrictSSL": false

Extensions never list when using ext install, and the bar just disappears. No error message like before.

Barryrowe commented Apr 26, 2016

This was working with @joaomoreno 's fix a long time ago, but something broke it again along the way, and seems to be worse. Through an NTLM negotiated proxy, none of these work-arounds seem to work. I'm on Windows 7, VSCode Insiders v1.0.1-insider.

I have the following set (and have tried with/without each of them):

  "http.proxy": "http://myproxyhost:11111",
  "https.proxy": "http://myproxyhost:11111",
  "http.proxyStrictSSL": false

Extensions never list when using ext install, and the bar just disappears. No error message like before.

@ranjith86

This comment has been minimized.

Show comment
Hide comment
@ranjith86

ranjith86 Apr 26, 2016

@Barryrowe I have the same issue using VSCode Insiders. Which file do you have these settings?

ranjith86 commented Apr 26, 2016

@Barryrowe I have the same issue using VSCode Insiders. Which file do you have these settings?

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Apr 26, 2016

Member

@Barryrowe @ranjith86 Can you test with the latest stable 1.0.0 and let me know if it is broken there as well?

Member

joaomoreno commented Apr 26, 2016

@Barryrowe @ranjith86 Can you test with the latest stable 1.0.0 and let me know if it is broken there as well?

@Barryrowe

This comment has been minimized.

Show comment
Hide comment
@Barryrowe

Barryrowe Apr 26, 2016

@ranjith86 they are in my settings.json
It looks like this is an ongoing issue and being worked on #5596

@joaomoreno I will check, and move discussion to the open issue

Barryrowe commented Apr 26, 2016

@ranjith86 they are in my settings.json
It looks like this is an ongoing issue and being worked on #5596

@joaomoreno I will check, and move discussion to the open issue

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Apr 26, 2016

Member

Just reply here.

Member

joaomoreno commented Apr 26, 2016

Just reply here.

@ranjith86

This comment has been minimized.

Show comment
Hide comment
@ranjith86

ranjith86 Apr 26, 2016

@joaomoreno for what ever reason, I can't open VS code on my machine. Only VSCode Insiders works. My settings.json file is as below, it is currently in my project folder.... is that right location?

{
  "http.proxy": "http://localhost:8888",
  "https.proxy": "http://localhost:8888",
  "http.proxyStrictSSL": false
}

ranjith86 commented Apr 26, 2016

@joaomoreno for what ever reason, I can't open VS code on my machine. Only VSCode Insiders works. My settings.json file is as below, it is currently in my project folder.... is that right location?

{
  "http.proxy": "http://localhost:8888",
  "https.proxy": "http://localhost:8888",
  "http.proxyStrictSSL": false
}
@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Apr 26, 2016

Member

The right location can be found with:

image

Member

joaomoreno commented Apr 26, 2016

The right location can be found with:

image

@ranjith86

This comment has been minimized.

Show comment
Hide comment
@ranjith86

ranjith86 Apr 26, 2016

@joaomoreno thanks, that worked. The location of settings.json was wrong in my case.

ranjith86 commented Apr 26, 2016

@joaomoreno thanks, that worked. The location of settings.json was wrong in my case.

@Barryrowe

This comment has been minimized.

Show comment
Hide comment
@Barryrowe

Barryrowe Apr 26, 2016

I'm getting similar behavior in stable v1.0.0. The difference is that the blue loading bar doesn't scroll across the bottom of the console input. It still just disappears without an error message.

if I completely remove the http.* settings, the blue loading bar shows, and I do get a ETIMEDOUT error. So it seems the VS code is talking to the proxy when configured, but the response might be empty for some reason coming back.

Barryrowe commented Apr 26, 2016

I'm getting similar behavior in stable v1.0.0. The difference is that the blue loading bar doesn't scroll across the bottom of the console input. It still just disappears without an error message.

if I completely remove the http.* settings, the blue loading bar shows, and I do get a ETIMEDOUT error. So it seems the VS code is talking to the proxy when configured, but the response might be empty for some reason coming back.

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno Apr 26, 2016

Member

Alright, that sounds like #5596 then. Any chance I can use your proxy, btw?

Member

joaomoreno commented Apr 26, 2016

Alright, that sounds like #5596 then. Any chance I can use your proxy, btw?

@woei66

This comment has been minimized.

Show comment
Hide comment
@woei66

woei66 May 10, 2016

I had the same issue and added below lines to fix the problem
{
"http.proxyStrictSSL": false,
"http.proxy": "http://company-proxy.com:8080",
"https.proxy":"https://company-proxy.com:8080"
}

woei66 commented May 10, 2016

I had the same issue and added below lines to fix the problem
{
"http.proxyStrictSSL": false,
"http.proxy": "http://company-proxy.com:8080",
"https.proxy":"https://company-proxy.com:8080"
}

@tebeco

This comment has been minimized.

Show comment
Hide comment
@tebeco

tebeco May 24, 2016

Hi, it seems I missed something :

Here is my configuration (Domain / User / Pass are Url Encoded in the following pictures)
image
image

DevTools :
image

I've even tried to run "code" from a prompt command after a couple of :
SET HTTP_PROXY="...."
SET HTTPS_PROXY="...."

I've also tried http/https on my proxy scheme to be sure, and also with or without the encoded Domain / user / pass
The result is always the same ==> HTTP 407 (Proxy Authentication Required).

CNTLM is definitly NOT an option for multiple good reasons that i won't discuss here. I'd like to solve this issue within VsCode configuration

FYI : Visual Studio 2013 / 2015 / dotnet.exe (via command line) / npm / ... WORKS with the proxy perfectly and the URI : https://api.nuget.org/v3/index.json is also accessible from the network here

tebeco commented May 24, 2016

Hi, it seems I missed something :

Here is my configuration (Domain / User / Pass are Url Encoded in the following pictures)
image
image

DevTools :
image

I've even tried to run "code" from a prompt command after a couple of :
SET HTTP_PROXY="...."
SET HTTPS_PROXY="...."

I've also tried http/https on my proxy scheme to be sure, and also with or without the encoded Domain / user / pass
The result is always the same ==> HTTP 407 (Proxy Authentication Required).

CNTLM is definitly NOT an option for multiple good reasons that i won't discuss here. I'd like to solve this issue within VsCode configuration

FYI : Visual Studio 2013 / 2015 / dotnet.exe (via command line) / npm / ... WORKS with the proxy perfectly and the URI : https://api.nuget.org/v3/index.json is also accessible from the network here

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno May 24, 2016

Member

You should check with your proxy administrator to know how authentication should happen. Usually the http://user:password@host:port/ scheme works.

Member

joaomoreno commented May 24, 2016

You should check with your proxy administrator to know how authentication should happen. Usually the http://user:password@host:port/ scheme works.

@tebeco

This comment has been minimized.

Show comment
Hide comment
@tebeco

tebeco May 25, 2016

You're right, VsCode seems to work since this morning. I changed my password there was probably some network cache issue...
I've got access to the Store Extension

Still I encounter something funny :
On the computer I got vs2013.5 vs2015.2, vsCode (latest rtm)
I've installed the .NetCore 1.0.0 Preview 1 (NetCore RC2 + Tooling CLI preview)
online "cli-samples" does not works (some work & some don't)
New templates created from VStudio Works from VS & Command line but not on VsCode
I'm wondering if the issue comes from Nuget/Omnisharp or something else when everything is linked together

As you see in the picture it's attempting to connect to the Project instead of nuget ^^

image

tebeco commented May 25, 2016

You're right, VsCode seems to work since this morning. I changed my password there was probably some network cache issue...
I've got access to the Store Extension

Still I encounter something funny :
On the computer I got vs2013.5 vs2015.2, vsCode (latest rtm)
I've installed the .NetCore 1.0.0 Preview 1 (NetCore RC2 + Tooling CLI preview)
online "cli-samples" does not works (some work & some don't)
New templates created from VStudio Works from VS & Command line but not on VsCode
I'm wondering if the issue comes from Nuget/Omnisharp or something else when everything is linked together

As you see in the picture it's attempting to connect to the Project instead of nuget ^^

image

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno May 25, 2016

Member

That is an issue with either Nuget or the dotnet tooling... I suggest you file an issue to them instead.

Member

joaomoreno commented May 25, 2016

That is an issue with either Nuget or the dotnet tooling... I suggest you file an issue to them instead.

@joaomoreno

This comment has been minimized.

Show comment
Hide comment
@joaomoreno

joaomoreno May 25, 2016

Member

Closing this discussion as everything's been said.

Member

joaomoreno commented May 25, 2016

Closing this discussion as everything's been said.

@Microsoft Microsoft locked and limited conversation to collaborators May 25, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.