GitHub Community
VSCode copilot extension does not work properly in WSL2 #147219
Replies: 28 comments 25 replies
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
Having the same problem... Things were working fine mid last week. |
|
I've had the same issue and have tried reinstalling and reauthenticating and haven't had any luck there. I have, however, now got it working in WSL (V2) Ubuntu by installing these versions of the Copilot and Copilot chat extensions:
Hopefully they release a fixed version/guidance soon, but for now that seems to work for me. |
|
thanks a lot, that really works |
|
thank you！actually works！ |
|
nice! |
|
Thank you, it's useful! Just need to roll back GitHub Copilot Chat. |
|
Still running into this issue and this rollback solved it. Thanks! |
|
A colleague and I experienced the same situation except within a dev container on MacOS. Downgrading as @seanaller suggested solved the issue.
|
|
thank you for this fix |
|
same issue |
|
same issue |
|
This is actively discussed at microsoft/vscode-copilot-release#3366 |
|
same issue |
|
the same issue, however, suggestion downgrade doesn't help me |
|
the same issue, however, suggestion downgrade doesn't help me |
|
I was facing the same problem, but it looks like the issue was resolved in the last VSCode update Code v1.96.2 |
|
Same Issue. |
|
Identifier Identifier |
|
Reinstalling the extension works for me. |
|
Within the WSL terminal, run |
|
Thanks, that solved my input/output error. |
|
@krawitzzZ Does the newest version of Github Copilot work for you? |
well, yes and no. the original issue seems to be gone (version 0.23.2 is currently installed), but I can't use it due to another issue, my extension cannot load language models, which makes the extension (and my subscription) completely useless... but the language models issue seems to be related to my company's security measures, extension cannot fetch them due to some ssl weirdness - |
|
The issue might be that Docker mirrors the system proxy (e.g.,
A quick and dirty fix is to unset your system proxy before opening the workspace with VS Code. You can turn the proxy setting back on after the Docker Dev Container is up and running. Another way to fix the problem is to use TUN mode (which creates a virtual network interface) as your proxy. It means that all the traffic is going to directly send to that tunnelling virtual hardware. This way, your host system and Dockers don’t require explicit proxy configuration. |
|
Still broken |
|
workaround at least that what works "now" with me /mnt/c/Users/mine/AppData/Local/Programs/Microsoft\ VS\ Code/Code.exe mine = should be replaced by your usernameInstallation |
|
I'm having the same problem. Works fine if I'm working in a Windows project. Breaks if I'm working on a WSL project. Downgrading as suggested above works. Is anyone from Microsoft even paying attention to this issue? |
|
Having the same problem. Windows 11, WSL, GitHub Copilot (Chat) extension runs on host. While every editor, that runs directly on Windows, gets working Copilot, the editors running on WSL get error: Details
|
|
Same issue |
|
Setting the following VSCode settings have so far worked for me, "github.copilot.advanced": {
"debug.useNodeFetcher": true,
"debug.useNodeFetchFetcher": false
}This seems to bypass the problem with |
|
This works for me. Thanks a lot. |
|
Worked for me - but I did some hackery with my certificates before when looking for the fix. idk what made it work, if the combination or just the VSCode settings. |
|
In the agent mode, the files are not getting created or edited with these settings |
|
Our team managed to get this working by disabling proxy support to extensions |
|
i had to unselect use local proxy configuration also |
|
Recently enabled Copilot on my account and setting |
|
add this in settings.json, |
|
why nobody cares this issue? It's an awful experience to use copilot with wsl2. |
|
This works for me: |
|
Your method makes the chat works, but it can't edit any files whatsoever. It just assumes the code has been edited but there's no change whatsoever |
|
Works for me. thanks! |
|
Worked for me, thank you so much. |
|
its creating the files in the windows filesystem instead of the ubuntu filesystem.... |
|
This is so strange. I encountered this issue today. |
|
I experimented with various approaches, including some arbitrary actions, but ultimately found that simply closing the chat window and continuing to work without it was effective. Autocomplete remained functional, indicating the core extension was still active, but the chat interface was unresponsive. Interestingly, the chat resumed working within an hour on its own. To verify if chat is back, reopen the chat window—if the model selection dropdown appears, the chat is operational; if not, it's still unavailable. This isn’t a definitive solution, but rather a temporary workaround that proved effective in my case. |
|
My WSL environment was trying to connect to GitHub Copilot servers using IPv6. WSL’s NAT couldn’t route IPv6 traffic to GitHub causing connection timed out (ETIMEDOUT / ENETUNREACH). my temporary solution : |
|
Unistall, Reboot IDE, Install extensions. |
|
Someone else ( @aylive ) found a solution for it in microsoft/vscode-copilot-release#6861 In "http.proxy": "http://172.19.144.1:8001", # 172.19.144.1 is found by `ip route | grep default`
"http.proxySupport": "on",
"http.proxyStrictSSL": false,
"github.copilot.advanced.debug.useElectronFetcher": false,
"github.copilot.advanced.debug.useNodeFetcher": true, # have no idea, but only this way work on vscode(wsl) instead of ElectronFetcher and NodeFetchFetcher
"github.copilot.advanced.debug.useNodeFetchFetcher": false |
|
it works for me as well thanks |
Weird, actually this doesn't work for me. I didn't test it much when I sent this reply, but after that, I tried it and it straight up gives me an error that my message can't be sent. I wonder if this has to do with Ubuntu version too (22.04 LTS) |
and others
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
Bug
Body
Starting this weekend (15.12.2024) vscode extension stopped working for me in WSL 2 environment on my win 11 machine... for some reason, after opening a copilot chat, I see for a short period the chat (for like a second or two) and then the login screen pops up:
even though the same repository cloned in my windows environment works just fine:
this is the repository if it matters...
Here are the logs that I can get from the output tabs
GitHub Copilot:
GitHub Copliot Chat
VSCode info:
All reactions