-
Notifications
You must be signed in to change notification settings - Fork 58
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
VS Code Copilot extension can't reach server on WSL Remotes #4065
Comments
I was also just able to login to the Codespaces plugin from within WSL without issue. |
I turned on a web proxy service and routed WSL through it and it worked. But without the proxy, it doesn't.
|
Duplicate of #3821, could you please try the steps here to provide more info #3821 (comment) ? |
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! |
Type: Bug
Copilot today stopped working in VS Code on WSL Remotes. It works fine when I'm using a local repo within Windows. But if I remote into WSL, it tells me to "Sign in to GitHub.com" and then nothing happens when I click "Sign in." This is effecting both the Chat and standard plugins in both the latest general and preview releases. I can verify that I am able to reach github.com from within the VS Code terminal on WSL.
Extension version: 0.24.2024121201
VS Code version: Code 1.96.3 (91fbdddc47bc9c09064bf7acf133d22631cbf083, 2025-01-09T18:14:09.060Z)
OS version: Windows_NT x64 10.0.22635
Modes:
Remote OS version: Linux x64 5.15.167.4-microsoft-standard-WSL2
Prompt Details
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
The text was updated successfully, but these errors were encountered: