0

I have been having issues with copilot in VScode, regardless of which model is used. The issues arise especially in agent/edit mode. The error message im getting in the output logs: ConnectTimeoutError: Connect Timeout Error (attempted address: proxy.individual.githubcopilot.com:443, timeout: 10000ms)

My configuration

GitHub Copilot Chat

  • Extension Version: 0.31.3 (prod)
  • VS Code: vscode/1.104.2
  • OS: Linux
  • Remote Name: wsl

Network

User Settings:

  "github.copilot.advanced.debug.useElectronFetcher": true,
  "github.copilot.advanced.debug.useNodeFetcher": false,
  "github.copilot.advanced.debug.useNodeFetchFetcher": true

Connecting to https://api.github.com:

  • DNS ipv4 Lookup: 140.82.121.5 (25 ms)
  • DNS ipv6 Lookup: Error (19 ms): getaddrinfo ENOTFOUND api.github.com
  • Proxy URL: None (1 ms)
  • Electron fetch: Unavailable
  • Node.js https: HTTP 200 (177 ms)
  • Node.js fetch (configured): HTTP 200 (174 ms)

Connecting to https://api.individual.githubcopilot.com/_ping:

  • DNS ipv4 Lookup: 140.82.112.22 (22 ms)
  • DNS ipv6 Lookup: Error (18 ms): getaddrinfo ENOTFOUND api.individual.githubcopilot.com
  • Proxy URL: None (0 ms)
  • Electron fetch: Unavailable
  • Node.js https: HTTP 200 (367 ms)
  • Node.js fetch (configured): HTTP 200 (380 ms)

Documentation

In corporate networks: Troubleshooting firewall settings for GitHub Copilot.

some more imfo on my setup: im coding in WSL2 (debian)

I tried pinging the copilot server directly which seems to have variable performance.

4
  • 1
    Please provide more information about your networking setup. Are you able to use GHCopilot in VSCode directly in Windows? Are you on a company device and/or network? If you are, have you talked to your company's networking team about this? Commented Sep 29 at 16:19
  • The information you provided is enough to diagnose the issue, however, you are having an issue connecting to IPv6 via WSL. This is a bug a reoccurring bug that makes using VS Code w/ wsl near impossible. Check the WSL github repository, the issues on these topic are endless. Commented Sep 30 at 11:59
  • i voted to close, not because the question is a bad question, but its off topic. This is a WSL issue, not an issue with VS Code, therefore it cannot be answered as such. I suggest either asking on superuser (which this question is already being asked on the sister site) or opening an issue w/ the WSL github repo (which an issue (several infact) has already been submitted). Considering all things, I want this to get fixed to, its not that your question is bad, its just a bit off topic, as VS Code isn't the problem WSL is, and no one can answer this except the WSL team. Commented Sep 30 at 12:04
  • Regarding the further questions: I am using copilot directly in VSCode I am on a company laptop but i have talked to the tech department in my company and they say they dont change any network configurations. The issue is persistent wether im on my home wifi, cable or the internet at work. The issue has not occured today. Ill leave the question open until later this week, if no solutions get posted or the problem does not arise again ill close it and post my problem on the WSL github repo. Thanks allready for the advice!! Commented Sep 30 at 16:05

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.