Replies: 4 comments 1 reply
-
My Copilot straight up refuses to cooperate because of this error... I might have to look for an alternative to copilot... been a while |
Beta Was this translation helpful? Give feedback.
-
My Copilot started today to have this FetchError, after the Visual Studio Code extension has been updated. It worked well before, with the same environment (WSL2 under Windows 10 Enterprise, using CNTML installed inside WSL2, Kerberos not installed).
|
Beta Was this translation helpful? Give feedback.
-
Really unfortunate that this is not seeming to get anywhere. I even have the same issue with copilot chat and have a bug request open but it's also getting no help.... |
Beta Was this translation helpful? Give feedback.
-
I'm also having the same issue. Seems like I have alternating error logs of
and
Hope this will be solved in the future. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Good day,
I am currently using GitHub Copilot Enterprise however I am having a really weird issue when connecting to copilot through a proxy. I am currently using vscode (v1.87.1) with the github copilot extension (v1.172.0) and running on a Mac M1. When I first open VS Code, I am able to use Code Suggestions and Chat without issue through the proxy however after a few minutes, the github extension attempts to send telemetry but then ends up failing due to some keberos issue. We aren't using keberos however there doesn't seem to be a way to tell the telemetry configurations to not detect this either. As soon as this error occurs it breaks the ability for copilot to communicate any longer and the only way to fix it is to restart the editor. Below is a few things I have tried as well to resolve this issue. Has anyone else experienced this issue and know of any fixes?
Things I have tried to resolve issue:
GitHub Copilot Error Log
Beta Was this translation helpful? Give feedback.
All reactions