copilot stopped working

[shaulispitzer]

Select Topic Area

Question

Body

Hi, I subscribed to github copilot about 2 weeks ago and it was working fine in my vscode till yesterday, it doesn't show me any suggestions any more, in the output it logs this when I type: [INFO] [default] [2023-09-27T12:19:26.258Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex [INFO] [default] [2023-09-27T12:19:26.430Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex [ERROR] [ghostText] [2023-09-27T12:19:28.693Z] Error on ghost text request: (FetchError) Client network socket disconnected before secure TLS connection was established. my vscode is connected to my github account, I am using the latest version of vscode and copilot and I tried switching to previous versions and it didn't help, does anyone have any suggestions?

[Akash1134]

Hi @shaulispitzer ,

Please troubleshoot your network and proxy settings from the network troubleshooting docs and if you are behind a firewall, check out this section.

Let us know how it goes.

[yannclaveau]

I have exactly the same problem. it was working but not anymore.

I am using Ubuntu, both VSCode and copilot are up to date. I tried to downgrade. The copilot chat is still working. I am behind a company proxy, that is configured in VSCode (and also available in http_prox environment variable). I have a teaching / research licence. Here is the diagnostics:

## Copilot

- Version: 1.162.0
- Build: prod
- Editor: vscode/1.86.1

## Environment

- http_proxy: http://XXXXXXXXXXX
- https_proxy: http://XXXXXXXXXXXXX
- no_proxy: n/a
- SSL_CERT_FILE: n/a
- SSL_CERT_DIR: n/a
- OPENSSL_CONF: n/a

## Feature Flags

- Custom Certificates: disabled
- Send Restricted Telemetry: disabled
- Chat: enabled

## Node setup

- Number of root certificates: 137
- Operating system: Linux
- Operating system version: 6.5.0-17-generic
- Operating system architecture: x64
- NODE_OPTIONS: n/a
- NODE_EXTRA_CA_CERTS: n/a
- NODE_TLS_REJECT_UNAUTHORIZED: 0
- tls default min version: TLSv1.2
- tls default max version: TLSv1.3

## Network Configuration

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

## Reachability

- github.com: HTTP 200 - 
- copilot-proxy.githubusercontent.com: Client network socket disconnected before secure TLS connection was established
- api.githubcopilot.com: HTTP 200 - 
- default.exp-tas.com: HTTP 200 - 

## VS Code Configuration

- HTTP proxy: http://XXXXXXXXXX
- HTTP proxy authentication: n/a
- Proxy Strict SSL: false
- Extension HTTP proxy support: override

## Extensions

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

## Authentication

- GitHub username: XXXXX

the command curl --verbose -x http://myproxy:port -i -L https://copilot-proxy.githubusercontent.com/_ping gives:

* Connected to (nil) (XXXXXXXXX) port XXXXX (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to copilot-proxy.githubusercontent.com:443
> CONNECT copilot-proxy.githubusercontent.com:443 HTTP/1.1
> Host: copilot-proxy.githubusercontent.com:443
> User-Agent: curl/7.81.0
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 200 Connection established
HTTP/1.1 200 Connection established
< 

* Proxy replied 200 to CONNECT request
* CONNECT phase completed!
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.0 (OUT), TLS header, Unknown (21):
* TLSv1.3 (OUT), TLS alert, decode error (562):
* error:0A000126:SSL routines::unexpected eof while reading
* Closing connection 0
curl: (35) error:0A000126:SSL routines::unexpected eof while reading

[davecheney]

• copilot-proxy.githubusercontent.com: Client network socket disconnected before secure TLS connection was established

Your employer's network is blocking copilot-proxy.githubusercontent.com. This is the required host for code completions.

[yannclaveau]

I've checked this, the address is not blocked. And it was working few days ago. besides, curl can go through the proxy. Did something change regarding the port ? My employer allows only 443 and 80, maybe the problem is there ?

[davecheney]

There have been no changes to the service.

[yannclaveau]

well, it is a bad news then. The ITs don't know what to do and it doesn't come from github copilot either...

[yannclaveau]

I reply to myself. No update on my side, no update on my employer's network but suddenly it works again.

I guess something has indeed changed (twice) on copilot side.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬