GitHub Community
Copilot chat doesn't work in wsl2 with vscode #147944
Answered
by
forbidden-game
Maxwowq
asked this question in
Copilot Conversations
-
Select Topic AreaBug BodyIt works fine in Windows, but when I use wsl2 with vscode remote connection, It says "You are currently offline. Please connect to the internet to use Github Copilot". But I can ping github.com with answer. And the compeletion funtion still works in editor. Following is the log of github copilot chat output. The linux version is Ubuntu 24.04.1 LTS . |
Beta Was this translation helpful? Give feedback.
Answered by
forbidden-game
Jun 11, 2025
Replies: 5 comments 2 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @Maxwowq , This looks like a potential network error based on the Thanks! |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I have run the command and here is the result. (base) maxwell@Maxwow:~/playground$ curl --verbose https://api.githubcopilot.com/_ping
* Host api.githubcopilot.com:443 was resolved.
* IPv6: (none)
* IPv4: 198.18.0.7
* Trying 198.18.0.7:443...
* Connected to api.githubcopilot.com (198.18.0.7) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
* ALPN: server accepted h2
* Server certificate:
* subject: CN=*.githubcopilot.com
* start date: Aug 1 00:00:00 2024 GMT
* expire date: Aug 1 23:59:59 2025 GMT
* subjectAltName: host "api.githubcopilot.com" matched cert's "*.githubcopilot.com"
* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
* SSL certificate verify ok.
* Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption
* Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://api.githubcopilot.com/_ping
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: api.githubcopilot.com]
* [HTTP/2] [1] [:path: /_ping]
* [HTTP/2] [1] [user-agent: curl/8.5.0]
* [HTTP/2] [1] [accept: */*]
> GET /_ping HTTP/2
> Host: api.githubcopilot.com
> User-Agent: curl/8.5.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 200
< date: Thu, 26 Dec 2024 08:24:26 GMT
< content-length: 2
< content-type: text/plain; charset=utf-8
< x-github-backend: Kubernetes
< x-github-request-id: 8A0E:3EC627:1819A71:25C49D6:676D12B9
<
* Connection #0 to host api.githubcopilot.com left intactAnd the following is the result of test to github endpoint. (base) maxwell@Maxwow:~/playground$ curl --verbose https://copilot-proxy.githubusercontent.com/_ping
* Host copilot-proxy.githubusercontent.com:443 was resolved.
* IPv6: (none)
* IPv4: 198.18.0.10
* Trying 198.18.0.10:443...
* Connected to copilot-proxy.githubusercontent.com (198.18.0.10) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
* ALPN: server accepted h2
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=*.githubusercontent.com
* start date: Jun 20 00:00:00 2024 GMT
* expire date: Jun 19 23:59:59 2025 GMT
* subjectAltName: host "copilot-proxy.githubusercontent.com" matched cert's "*.githubusercontent.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
* SSL certificate verify ok.
* Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
* Certificate level 2: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://copilot-proxy.githubusercontent.com/_ping
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: copilot-proxy.githubusercontent.com]
* [HTTP/2] [1] [:path: /_ping]
* [HTTP/2] [1] [user-agent: curl/8.5.0]
* [HTTP/2] [1] [accept: */*]
> GET /_ping HTTP/2
> Host: copilot-proxy.githubusercontent.com
> User-Agent: curl/8.5.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 200
< content-security-policy: default-src 'none'; sandbox
< content-type: application/json
< strict-transport-security: max-age=31536000
< content-length: 48
< date: Thu, 26 Dec 2024 08:23:30 GMT
< x-github-backend: Kubernetes
< x-github-request-id: A290:211CE1:577D52:595FD7:676D1281
<
{"now":1735201410,"status":"ok","ns1":"200 OK"}
* Connection #0 to host copilot-proxy.githubusercontent.com left intact |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, {"now":1735895312,"status":"ok","ns1":"200 OK"} Connection #0 to host copilot-proxy.githubusercontent.com left intact What can I do now??? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm having the same problem. Works fine if I'm working in a Windows project. Breaks if I'm working on a WSL project. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
It may work by setting it run in local. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
It does work work this solution! Before the official fixes the bug of wsl copilot-chat, running the extension on windows will be a proper substitute with only few efficiency lost. Thanks! |
Beta Was this translation helpful? Give feedback.
Answer selected by
Maxwowq
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It may work by setting it run in local.