Copilot not working inside WSL #1380
Comments
github-actions
bot
added
the
triage-needed
lramos15
removed
the
triage-needed
|
There is a new stable version GitHub Copilot Chat 0.17.1 improving the error reporting. Could you retry with that and run the diagnostic command |
Copilot
Environment
Feature Flags
Node setup
Network Configuration
Reachability
VS Code Configuration
Extensions
Authentication
|
|
This suggests that Kerberos authentication is required for the network proxy, but is not set up in WSL: |
|
We can look up the Kerberos auth on the host when it failed in WSL. |
chrmarti
added
bug
|
How shall I update the fetcher , i think it is trying to authenticate from the old cache. I updated the Github copilot extension to a newer version (v1.213.0) but that didn't help. Still getting the same error: |
|
@BinaryFusion-00 and @mofa65: Could you try the latest VS Code Insiders release (https://code.visualstudio.com/insiders/)? That comes with a fix that will query Kerberos on Windows when it fails in WSL. |
|
Apologies for the delay. I get this error in the Insiders build inside WSL: |
|
@BinaryFusion-00 Could you rerun the diagnostics commands? |
Copilot
Environment
Feature FlagsNode setup
Network Configuration
Reachability
VS Code Configuration
Extensions
Authentication
|
|
Could you also run |
GitHub Copilot Chat
NetworkUser Settings: "github.copilot.advanced": {
"debug.useElectronFetcher": false,
"debug.useNodeFetcher": false
}Connecting to https://api.github.com:
|
|
Could you rerun it and give it more time? It should run a similar test for |
|
Apologies for the delay GitHub Copilot Chat
NetworkUser Settings: "github.copilot.advanced": {
"debug.useElectronFetcher": false,
"debug.useNodeFetcher": false
}Connecting to https://api.github.com:
Connecting to https://api.githubcopilot.com/_ping:
DocumentationIn corporate networks: Troubleshooting firewall settings for GitHub Copilot. |
|
any updates on this, facing the same issue |
|
I also need help with this! any updates? |
|
@BinaryFusion-00 Could you set Proxy Support to @AashishKumar-3002 @amanda-natallie Please check the output of |
|
Related: #1577 |
|
From authentication-with-kerberos when executing klist: No credentials cache found (filename: /tmp/krb5cc_1000) I don't even have this file. |
|
Hi @chrmarti, I have checked the internet connection, and it's correct my home's internet. It's just happened with the WSL because I use the autocomplete totally fine with both VS Code and PyCharm on Windows so I believed that the firewall is fine (It's worked when I use my company's internet also but only on Windows workspace). Here is the diagnostics from Windows workspace: GitHub Copilot Chat
NetworkUser Settings: "github.copilot.advanced": {
"debug.useElectronFetcher": true,
"debug.useNodeFetcher": true
}Connecting to https://api.github.com:
Connecting to https://api.githubcopilot.com/_ping:
DocumentationIn corporate networks: Troubleshooting firewall settings for GitHub Copilot. ==EDIT== |
|
@Adrian43211234 Are you behind a network proxy with Kerberos authentication? Are you using WSL? @Pumbaazz The Electron fetcher is expected to not be available in WSL. Does |
|
@chrmarti Seem it's work, I can see that |
Yes @chrmarti to both and in my VSC without WSL the copilot is also working. |
|
@Adrian43211234 Please check the output of |
|
@amanda-natallie Looking at the diagnostics you posted in #1380 (comment) I realize the setting probably won't solve the issue because the Node fetcher is shown as failing with a 407 (proxy auth missing). Does it work on Windows? |
GitHub Copilot Chat
NetworkUser Settings: "github.copilot.advanced": {
"debug.useElectronFetcher": true,
"debug.useNodeFetcher": true
}Connecting to https://api.github.com:
Connecting to https://api.githubcopilot.com/_ping:
DocumentationIn corporate networks: Troubleshooting firewall settings for GitHub Copilot. |
|
Hello I am having the same problem Here is my diagnostic, I really appreciate if this is solved since this is not working at all GitHub Copilot Chat
NetworkUser Settings: "github.copilot.advanced": {
"debug.useElectronFetcher": true,
"debug.useNodeFetcher": false
}Connecting to https://api.github.com:
Connecting to https://api.githubcopilot.com/_ping:
DocumentationIn corporate networks: Troubleshooting firewall settings for GitHub Copilot. |
|
@Adrian43211234 Could you try adding the following to your user settings JSON ( "github.copilot.advanced": {
"debug.useNodeFetcher": true
}@dimun This looks like your WSL distro does not have network at all. Does it work on Windows? Are you behind a network proxy? |
|
The same issue. I have a virtual windows workstation with WSL at work that uses a proxy. GitHub Copilot Chat
NetworkUser Settings: "github.copilot.advanced": {
"debug.useElectronFetcher": true,
"debug.useNodeFetcher": true
}Connecting to https://api.github.com:
Connecting to https://api.githubcopilot.com/_ping:
DocumentationIn corporate networks: Troubleshooting firewall settings for GitHub Copilot. |
Hi @chrmarti This is already my setting - the Connecting to https://api.github.com:
Connecting to https://api.githubcopilot.com/_ping:
DocumentationIn corporate networks: Troubleshooting firewall settings for GitHub Copilot. |
|
@Adrian43211234 Indeed, I would expect it to work then. Could you check @Adrug The diagnostics you posted confirm your observation, the requests go through, but take very long. Does |
|
@chrmarti thanks for your help! copilot chat seems to work for now: copilot: |
Unfortunately yes, via curl it takes 5secs or more. I guess my issue is not due to copilot. Just now I have realized all remote endpoints have about 5 second delay. |
|
@Adrian43211234 This looks like Copilot Chat might work, does the Chat viewlet work for you? The ghost text completions from Copilot (not Chat) show an error, @devm33 I don't think there is a way to switch that to using the Node.js https module as a workaround? @Adrug Maybe post the same diagnostics from when you are using a Windows folder, that will show us the Windows side. (E.g., I wonder if the DNS lookups succeed there.) I suggest you also check with your IT admins for a solution as this seems to be related to how networking is set up on your machine / WSL. |
|
@chrmarti yes the chat do work (sometimes) Compared without WSL: |
Yeah, I've raised a ticket to IT support. GitHub Copilot Chat
NetworkUser Settings: "github.copilot.advanced": {
"debug.useElectronFetcher": true,
"debug.useNodeFetcher": true
}Connecting to https://api.github.com:
Connecting to https://api.githubcopilot.com/_ping:
DocumentationIn corporate networks: Troubleshooting firewall settings for GitHub Copilot. |
|
@chrmarti yes that's correct, we don't yet have a http2 module fetcher yet. Looking at the per domain resolution, it looks like some domains are getting through ok. Presumably excepted by the proxy rules: The Kerberos error returned indicates the proxy is returning a 407 response. |
|
@Adrian43211234 You could check with your IT admins if they could apply the same exceptions that seem to apply for |
We've tried this and still have the issue. |
|
I confirmed the issue still happen. I've added domains in this article to Windows proxy whitelist setting. Update: it works after I set |
|
@tranghvfpt That (HTTP 200 and HTTP 407 for the two URLs together with setting If you want to investigate further yourself, you could install the Network Proxy Test extension (https://marketplace.visualstudio.com/items?itemName=chrmarti.network-proxy-test) and run |
|
you're right, it's use different connection for After I add an internal cert the Copilot [Chat] work as expected. |
|
@tranghvfpt Just for my own understanding (and maybe others who face the same issue): What kind of certificate did you have to add to make this work? Did you not need to change the proxy setting anymore? |
|
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! |
vs-code-engineering
bot
closed this as not planned
|
@chrmarti they send me a document with steps:
|
|
Hi there, I have reported this issue recently. For me it was completely WSL issue. |
Github copilot works on my Windows, but it does not work inside WSL. I see the following error in the GitHub Copilot log
[info] [fetcher] Using Helix fetcher, Electron fetcher is not available.
[info] [auth] Sucessfully authenticated
[error] [default] Error sending telemetry FetchError: No credentials were supplied, or the credentials were unavailable or inaccessible: No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_1000)
GitHub Copilot chat log:
[info] [extension] Error: Unable to resolve chat model with family selection: gpt-4
The text was updated successfully, but these errors were encountered: