No "Enter Your Code" during registration

[modul8com]

Issue Type: Bug

While trying to logging into LiveShare, there's no "enter your code" possibility as there is with Visual Studio Full... so I can't login into Live Share :(

Extension version: 0.3.114
VS Code version: Code - Insiders 1.24.0-insider (5799dec0ee9e7673cc013165a0132622f37b5e92, 2018-05-16T07:13:57.029Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (4 x 2400)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: disabled_software video_decode: enabled video_encode: enabled vpx_decode: unavailable_software webgl: enabled webgl2: enabled
Memory (System)	7.88GB (2.73GB free)
Process Argv	C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe
Screen Reader	no
VM	0%

[lostintangent]

@modul8com Are you having issues with signing in, that requires you to use the user code? In VS Code, we have the Live Share: Sign in With User Code command that appears when you're signed out. Could you give that a try and let us know how it goes?

[modul8com]

Aaaaah, there is now a "sign in with code" option from the F1-launcher in Code....
Though that doesn't work either, I get a 502: Server Hangup error.
I added the logs of that...
logs.zip

Seems like :

Proxy settings from env variable: http_proxy was null and https_proxy was null

Where do I define those proxy settings and in what ENV ? Since this is in my user settings of VS Code:
"http.proxy": "http://someserver:8080/",

I tried setting a Windows ENV variable http_proxy to my proxyserver but that didn't do the trick either.

[Chuxel]

@modul8com If you are behind a proxy, see https://aka.ms/vsls-docs/proxy for details. You could also be hitting #86, so if this does not work for you, it would be good to get your details added to that thread.

[modul8com]

It somehow works now for some reason after the latest update ! Thank you !

[lostintangent]

@modul8com That's great to hear! I'll go ahead and close this issue then, but please feel free to re-open it if the problem re-appears. Thanks!