microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
164.05k stars 29.22k forks source link

Sign in with github #178408

Closed austiLuz closed 1 year ago

austiLuz commented 1 year ago

Type: Bug

I'm trying to sign in to sync settings with github but it just keeps returning "having trouble logging in? Would you like to try a different way?" over and over and over again

VS Code version: Code 1.76.2 (Universal) (ee2b180d582a7f601fa6ecfdad8d9fd269ab1884, 2023-03-14T17:54:09.061Z) OS version: Darwin x64 21.6.0 Modes: Sandboxed: No

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i5-1030NG7 CPU @ 1.10GHz (8 x 1100)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|3, 4, 4| |Memory (System)|8.00GB (0.43GB free)| |Process Argv|--crash-reporter-id 076e5c9c-684c-471e-90b2-8d3900ef4923| |Screen Reader|no| |VM|0%|
Extensions (13) Extension|Author (truncated)|Version ---|---|--- mobileview|cir|0.0.7 es7-react-js-snippets|dsz|4.4.3 react-native-react-redux|EQu|2.0.6 prettier-vscode|esb|9.10.4 code-runner|for|0.12.0 vscode-chatgpt|gen|4.0.2 codespaces|Git|1.14.1 remotehub|Git|0.52.0 vscode-pull-request-github|Git|0.60.0 azure-repos|ms-|0.28.0 remote-repositories|ms-|0.30.0 vscode-react-native|msj|1.10.2 LiveServer|rit|5.7.9
A/B Experiments ``` vsliv368cf:30146710 vsreu685:30147344 python383cf:30185419 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492:30256859 vslsvsres303:30308271 pythonvspyl392:30443607 vserr242cf:30382550 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vsdfh931cf:30280410 vshan820:30294714 vstes263:30335439 pythondataviewer:30285071 vscod805cf:30301675 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 cmake_vspar411:30581797 vsaa593:30376534 pythonvs932:30410667 cppdebug:30492333 vsclangdc:30486549 c4g48928:30535728 dsvsc012:30540252 pynewext54:30695312 azure-dev_surveyone:30548225 pyindex848:30662994 nodejswelcome1cf:30587006 3biah626:30602489 pyind779:30671433 89544117:30613380 pythonsymbol12:30671437 vsccsb:30677849 vscodeenable:30660116 pythonb192cf:30669361 defaultazurewalk:30687958 pythonms35:30686772 ```
cheestudio commented 1 year ago

@TylerLeonhardt I am experiencing the exact same issues.

image

image

cheestudio commented 1 year ago

@TylerLeonhardt I also tried creating a brand new GitHub account to see if perhaps there was an issue on that side of the authentication, but same result as above.

cheestudio commented 1 year ago

@austiLuz and @TylerLeonhardt

I finally got to the bottom of this. It was due to a previous installation of DOCKER which set some Windows System Variables, notably this:

image

And an entry setting a 127.0.0.1:XXXX entry (sorry I did not get a screenshot of that).

I removed both these entries and GitHub was able to authenticate.

TylerLeonhardt commented 1 year ago

@cheestudio this is really invaluable information. Thanks for sharing! I want to add this to the vscode docs.

@austiLuz can you tell me a bit about your proxy setup?

cheestudio commented 1 year ago

@TylerLeonhardt You're quite welcome. It was using the VSCode Inspector Dev tools that ultimately tipped me off that there could be some kind of local environment configuration that was the culprit. When I looked up the ENOTFOUND error across the web, I noticed a lot of people discussing it in relation to Proxies and a few mentioned Docker, which provided the light bulb I needed to look at my environment variables!

@tschams mentioned in https://github.com/microsoft/vscode/issues/160649 that they added "http.proxySupport": "off" to their VSCode settings, and that also resolved it. I didn't see that before I had already removed my environment variables, but that sounds like it might also be a potential fix. It's at least something very easy to try first, and then if no success, move onto reviewing the environment variables.

TylerLeonhardt commented 1 year ago

@chrmarti is there more info you think we should gather here?

chrmarti commented 1 year ago

@TylerLeonhardt No, that all makes sense, thanks. The Network Proxy Test extension lists relevant env variables, so that could help diagnose similar issues. Maybe we should include that as built-in to make it easier to use.

vscodenpa commented 1 year ago

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!