Error Code: net::ERR_CONNECTION_RESET

[sebastianczech]

• VS Code Version: 1.89.0 (Universal)
• GitHub Copilot Chat Version: v0.15.0
• OS Version: macOS 14.4.1
• Logs:

Please check your firewall rules and network connection then try again. Error Code: net::ERR_CONNECTION_RESET.

Steps to Reproduce:

1. Connect via Global Protect or other VPN
2. Try to use GitHub Copilot Chat and then error net::ERR_CONNECTION_RESET appears (in version GitHub Copilot Chat v0.14.0 there is no issue while working via Global Protect or other VPN)

[alexdima]

@sebastianczech Did the situation improve now? We have rolled back an experiment where we tried to enable a different network stack for the extension.

[sebastianczech]

@alexdima Yes, after updating to latest versions of extensions, everything works via GlobalProtect. Thank you. We can close that issue.

[alexdima]

Thank you for the prompt answer! Yet, this is still a bit worrying, because it means that there might be a problem with the Electron Fetcher in your environment, which we plan to turn on by default with the next month's release.

Would it please be possible to help us by:

• installing the latest VS Code Insiders. This can be installed side-by-side with your main VS Code installation
• installing the Pre-Release version of the Copilot Chat Extension v0.16.2024051001 (pre-release)
• trying if it works under your environment
• if it doesn't work, trying to configure "github.copilot.advanced": { "debug.useElectronFetcher": false } and trying if it works then.

Thank you very much!

[sebastianczech]

@alexdima I was executed all steps, which you described. In environment with:

• VS Code Insider: 1.90.0-insider (Universal)
• GitHub Copilot : v1.188.867 (pre-release)
• GitHub Copilot Chat : v0.16.2024051001 (pre-release)

I have problems while working via VPN with or without config in settings.json (after each change of this settings, I was restarting VS Code Insider):

{
    "github.copilot.advanced": { 
        "debug.useElectronFetcher": false 
    }
}

[alexdima]

@deepak1556 @chrmarti What further steps can we take to troubleshoot why ElectronFetcher wouldn't work in this environment?

[devm33]

Running GitHub Copilot: Collect Diagnostics might shed some light if you don't mind @sebastianczech Also if there are any errors in the output panels for GitHub Copilot or GitHub Copilot Chat. Are inline suggestions from Copilot working for you?

[sebastianczech]

@devm33 I'm sending below results of GitHub Copilot: Collect Diagnostics:

## Copilot

- Version: 1.193.880
- Build: nightly
- Editor: vscode/1.90.0-insider

## Environment

- http_proxy: n/a
- https_proxy: n/a
- no_proxy: n/a
- SSL_CERT_FILE: n/a
- SSL_CERT_DIR: n/a
- OPENSSL_CONF: n/a

## Feature Flags

- Send Restricted Telemetry: disabled
- Chat: enabled

## Node setup

- Number of root certificates: 141
- Operating system: Darwin
- Operating system version: 23.4.0
- Operating system architecture: arm64
- NODE_OPTIONS: n/a
- NODE_EXTRA_CA_CERTS: n/a
- NODE_TLS_REJECT_UNAUTHORIZED: n/a
- tls default min version: TLSv1.2
- tls default max version: TLSv1.3

## Network Configuration

- Proxy host: n/a
- Proxy port: n/a
- Kerberos SPN: n/a
- Reject unauthorized: disabled
- Fetcher: HelixFetcher

## Reachability

- github.com: HTTP 200 - OK
- copilot-proxy.githubusercontent.com: HTTP 200
- api.githubcopilot.com: HTTP 200 - OK
- default.exp-tas.com: HTTP 200 - OK

## VS Code Configuration

- HTTP proxy: 
- HTTP proxy authentication: n/a
- Proxy Strict SSL: true
- Extension HTTP proxy support: override

## Extensions

- Is `win-ca` installed?: false
- Is `mac-ca` installed?: true

## Authentication

- GitHub username: sebastianczech

In GitHub Copilot Chat, while using it with enabled GlobalProtect, I have only:

Please check your firewall rules and network connection then try again. Error Code: ECONNRESET.

I hope it helps somehow.

[deepak1556]

We also see ECONNRESET from Node.js http stack in the above logs, the issue here is independent of the type of fetcher used.

[vs-code-engineering[bot]]

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!