Github copilot completions report temporary issues #181201
Replies: 1 comment
-
|
Thanks for providing the full diagnostics output — this helps narrow down the issue. Based on the logs, this does not appear to be a Copilot bug. Instead, your VS Code remote environment is failing to reach one specific Copilot endpoint: https://proxy.individual.githubcopilot.com/_ping All other GitHub and Copilot endpoints return HTTP 200, but this one fails with: read ECONNRESET This strongly suggests a network-level interruption rather than an issue with VS Code or the Copilot extension. What’s Actually Happening The failures indicate: Your environment is using Node fetch instead of Electron fetch (Electron fetcher not available). Requests to the main Copilot API domain succeed. Requests to the proxy endpoint are being force-closed (ECONNRESET) — typically caused by: A firewall or DPI system blocking the domain A corporate / cloud server policy A network proxy dropping TLS connections SSH-remote server restrictions Missing or outdated CA certificates This is also consistent with the log showing: Remote Name: ssh-remote If the server blocks outbound AI endpoints, Copilot completions won’t load. Recommended Fixes
Try running this on the remote server: curl -v https://proxy.individual.githubcopilot.com/_ping If it fails, the issue is at the network/firewall level. You may need to whitelist these endpoints: *.githubcopilot.com
Some enterprise Linux distros block Node.js outgoing TLS by default. To test: node -e "require('https').get('https://proxy.individual.githubcopilot.com/_ping', r => console.log(r.statusCode)).on('error', console.error)"
Run: sudo update-ca-trust
Your settings explicitly force Copilot to use a specific fetcher: "github.copilot.advanced.debug.useElectronFetcher": true, Remove all of these so Copilot can auto-select the correct method: "github.copilot.advanced.debug.useElectronFetcher": false, Or simply delete them.
Your logs show symptoms identical to MITM firewalls terminating AI-related traffic. GitHub provides guidance here: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Copilot Feature Area
VS Code
Body
output:
diagnostics:
Connecting to https://api.github.com:
Connecting to https://api.individual.githubcopilot.com/_ping:
Connecting to https://proxy.individual.githubcopilot.com/_ping:
at TLSWrap.onStreamRead (node:internal/stream_base_commons:216:20)
at node:internal/deps/undici/undici:13510:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async b3._fetch (/home/wjb/.vscode-server/extensions/github.copilot-chat-0.33.2/dist/extension.js:4418:24712)
at async /home/wjb/.vscode-server/extensions/github.copilot-chat-0.33.2/dist/extension.js:4450:190
at async Zy.h (file:///home/wjb/.vscode-server/cli/servers/Stable-bf9252a2fb45be6893dd8870c0bf37e2e1766d61/server/out/vs/workbench/api/node/extensionHostProcess.js:114:41645)
at async RG.handleItemSelection (/home/wjb/.vscode-server/extensions/github.copilot-chat-0.33.2/dist/extension.js:4043:7909)
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:216:20)
Connecting to https://github.com: HTTP 200 (275 ms)
Connecting to https://telemetry.individual.githubcopilot.com/_ping: Error (296 ms): Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:216:20)
Number of system certificates: 147
Documentation
In corporate networks: Troubleshooting firewall settings for GitHub Copilot.
Beta Was this translation helpful? Give feedback.
All reactions