Copilot in Windows + WSL + VSCode: sometimes doesn't work, sometimes works fine, I don't get it.

[JoannaFalkowska]

It worked fine for months, but now it suddenly stopped.

When I open a VSCode window in "vanilla" Windows, Copilot works completely fine, i.e. I can create a new file and it starts giving me suggestions as expected.

However when I open a VSCode window in WSL, Copilot extension manages to start up and authenticate, but then it gets stuck on "Synthesizing 0/10 solutions". I can see no errors in the console. It's just stuck.

I tried:

• removing password to the default keyring in WSL (using an utility called seahorse)
• deleting the entire default keyring in WSL (again, with seahorse) and re-authenticating Github
• reinstalling Copilot VSCode extension
• restarting the WSL machine

None of those helped, and I'm completely lost as to why Copilot is suddenly unable to cooperate with my WSL. I don't use any VPN, and haven't changed any settings this past week.

I'd appreciate any kind of pointers as to how I could debug this.

[davecheney]

@JoannaFalkowska I'm sorry you're having difficulties. Can you please paste the relevant parts of View -> Output; select GitHub Copilot from the pulldown.

[JoannaFalkowska]

@davecheney I'm sorry, I don't think that's possible. Whatever I type, it never returns any completions whatsoever - but only in WSL. In Windows I can get plenty of completions all the time.

In the example logged above, as you can see, I typed out an empty helloWorld() { } function and waited for a completion inside the brackets. I never got any.

[davecheney]

@JoannaFalkowska thank you for correcting me. I've passed this thread onto the engineers who are managing the experiment -d endpoint. I suggest restarting vscode to try and shake off the assignment to that experiment endpoint and hopefully get copilot working again.

[davecheney]

@JoannaFalkowska I've disabled the experiment, hopefully this should resolve itself shortly.

[JoannaFalkowska]

Hey @davecheney, thank you for your response.

2 days later, after restarting VSCode etc., it seems that I'm now assigned to experiment-e instead of experiment-d. It still doesn't return anything at all in WSL, but the same endpoint does correctly return suggestions in Windows. So I don't think it's a problem with your experiment itself.

It's probably some internal networking or auth-related issue on my side, but I honestly don't know how to debug it. Everything else works generally fine, and the extension itself seems to be thinking it's authenticated correctly.

(This is likely unrelated, but I recently had some problems accessing git:// urls when running a simple npm install, and had to switch the protocol in git global config to https://. I changed it just yesterday though, so after I already was having problems with Copilot. Do you think it could be any kind of clue?)

---

As for logs:

WSL VSCode :

[INFO] [solutions] [2022-08-16T13:29:38.447Z] prompt: {"prefix":"// Language: javascript\nhelloWorld() {\n","suffix":"","isFimEnabled":false,"promptElementRanges":[{"kind":"LanguageMarker","start":0,"end":24},{"kind":"BeforeCursor","start":24,"end":41}]}
[INFO] [default] [2022-08-16T13:29:38.510Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-experiment-e-centralus
[INFO] [default] [2022-08-16T13:30:17.243Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-experiment-e-centralus

(...zero incoming responses even after waiting for >90s)

Windows VSCode :

[INFO] [solutions] [2022-08-16T13:42:48.460Z] prompt: {"prefix":"// Language: javascript\nhelloWorld() {\n","suffix":"","isFimEnabled":false,"promptElementRanges":[{"kind":"LanguageMarker","start":0,"end":24},{"kind":"BeforeCursor","start":24,"end":41}]}
[INFO] [default] [2022-08-16T13:42:48.518Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-experiment-e-centralus
[INFO] [default] [2022-08-16T13:42:49.191Z] request.response: [https://copilot-proxy.githubusercontent.com/v1/engines/copilot-experiment-e-centralus/completions] took 673 ms
[ERROR] [streamChoices] [2022-08-16T13:42:58.875Z] Error parsing JSON stream data,{"error":{"message":"request timeout"}}
[INFO] [streamChoices] [2022-08-16T13:42:58.876Z] solution 0 returned. finish reason: [Iteration Done] finishOffset: [undefined] completionId: [{cmpl-5fr8CjNBnDaMOLyxSuuMW1zwNfia2}] created: [{1660657368}]
[INFO] [solutions] [2022-08-16T13:42:58.880Z] Open Copilot completion: [  console.log("Hello World!");
}

// Language: python
def helloWorld():
  print("Hello World!")

// Language: java
public void helloWorld() {
  System.out.println("Hello World!");
}

// Language: c++
void helloWorld() {
  std::cout << "Hello World!";
}

(...more solutions in similar vein)

I also tried to use the "Github Copilot Nightly" VSCode extension in WSL instead, and it used a different endpoint (codex), but that one also never returned anything:

[INFO] [solutions] [2022-08-16T13:37:33.176Z] prompt: {"prefix":"// Language: javascript\nhelloWorld() {\n","suffix":"","isFimEnabled":false,"promptElementRanges":[{"kind":"LanguageMarker","start":0,"end":24},{"kind":"BeforeCursor","start":24,"end":41}]}
[INFO] [default] [2022-08-16T13:37:45.718Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex
[INFO] [ghostText] [2022-08-16T13:37:45.721Z] Cancelled after requestMultiline
[INFO] [ghostText] [2022-08-16T13:37:45.722Z] Cancelled after requestMultiline
[INFO] [ghostText] [2022-08-16T13:37:45.722Z] Cancelled after requestMultiline
[INFO] [default] [2022-08-16T13:37:46.016Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex
[INFO] [default] [2022-08-16T13:37:59.616Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex
[INFO] [default] [2022-08-16T13:38:35.332Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex

---

Please let me know if you have any other ideas as to how I could debug this, I appreciate your help.

[JoannaFalkowska]

Hello @davecheney, sorry for nudging you, but since my Copilot trial has ended I'm now not sure if I should be purchasing the subscription or not. I I can't get it working in WSL, then it's no point for me. But maybe I can try to debug it even without the subscription being paid for, somehow? (Or, is it likely that I would get refunded if it didn't work?) I'm quite determined to get it up to speed again, I had a great experience with it.

I can see this thread got upvoted by a few people, so possibly it's not just me having this problem. Have you maybe heard about any new ideas why would Copilot not work in WSL in the meantime, since your last message?

[JoannaFalkowska]

This is STILL unresolved, I'm STILL struggling with the same problem, without any idea why does it happen.

On good days, I open my WSL files in VSCode and Copilot instantly works like a charm, swiftly returning completions all day.

On bad days, in exactly the same setting, it returns no completions, or manages to do so only for isolated very simple files, while completely blanking and timing out when asked for completions inside a complicated TS repo.

It's frankly ridiculous, completely unreliable, deciding to work or not work without any rhyme or reason. I'd like to understand at least why and whether I can do anything to help it function properly. Because as it is now, it's a paid feature working in a way that can hardly be considered out of beta.

[Markkos89]

Same here... totally randomly works or not.... I don't get it

[johnashu]

Another year and I am here with the same issues lol.

[Kagura-Ahad]

bruh

this is my output.
[ERROR] [default] [2023-11-26T20:56:28.487Z] Extension activation failed: "connect ETIMEDOUT 20.207.73.85:443"

what do i do??

[techybolek]

All of a sudden I'm hacing the same issue. Works on Windows, not on WSL2. HAs anyone been able to resolve this issue?

[tetthys]

Still unresolved...

[Min-Ho-Lim]

This happens to me as well. I recently formatted my pc and installed the latest windows 10 pro.
I installed Ubuntu with WSL2 to use it as my dev setup alongwith VSCode.
Also, I installed Copilot as well. It had been working fine last few days, but suddenly, from today, it stopped working.

[INFO] [default] [2022-12-01T18:01:32.028Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex

The Copilot log does not show any error as @JoannaFalkowska mentioned when I try to get any suggestion from Copilot.

[ERROR] [default] [2022-12-01T18:07:30.787Z] Request Error: connect ETIMEDOUT 20.80.64.28:443

But, If I waited long enough, it does return with the timout error.

This is the list that I have tried

1. Reinstall Copilot extension
2. Disabled Copilot and enabled it back
3. Signed out and signed in my Github account from VSCode
4. Turned off all VPN connections
5. Used Google public DNS
6. Replaced the nameserver to the Google public DNS in ~/etc/resolv.conf
7. Changed WSL2 to WSL1

I am not sure what is going on.

I will update the post if I figure out the solution.

[Min-Ho-Lim]

Alright, it has been almost a month since I posted. I do not have the exact solution, but I kinda know what is the problem.

So, Copilot does use multiple servers to get responses, but the problem is once Copilot connected to a server, it does not get changed even if the connection gets timed out.

I am not sure why Copilot does not automatically change the connection server.

But, I think sometimes the copilot server thinks some connection from "WSL" is evil, so they block the IP address for a short period time. This is why we experience such cases.

The workaround is using a VPN.

Since the communication between your IP and the Copilot server is not established, you need to changed your IP address.

[MichaelBidencopeCP]

Hey,
I also I had the same problem with WSL2, VSCode , and Copilot, I was not able to get a VPN to work as it was just causing more problems. However, I was able to use VSCode's proxy and Squid for Windows(proxy) in order to fix this problem. Here is the github post to configuring proxy settings for GitHub Copilot.

[tuirennder]

Thanks @MichaelBidencopeCP, that's working with a local proxy running on Windows.

Nevertheless I hope Github is going to fix this because that remains an annoyance.

In case Github is still reading us (@davecheney ?), the issue in this thread is NOT about having no connectivity at all without proxy:
the vscode github extention running in the WSL context do have connectivity to github. From a WSL terminal, the _ping test
to githubusercontent is always successful without proxy:

(base) user@WSL2:~$ curl https://copilot-proxy.githubusercontent.com/_ping
{"now":1676046306,"status":"ok"}

However, without proxy, the extension fails to return anything most of the time:

[INFO] [default] [2023-02-10T12:34:11.043Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex
[INFO] [ghostText] [2023-02-10T12:34:11.257Z] Cancelled during debounce
[INFO] [default] [2023-02-10T12:34:11.347Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex
[INFO] [default] [2023-02-10T12:34:11.571Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex
[INFO] [default] [2023-02-10T12:34:12.645Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex

[techybolek]

In case Github is still reading us (@davecheney ?), the issue in this thread is NOT about having no connectivity at all without proxy: the vscode github extention running in the WSL context do have connectivity to github. From a WSL terminal, the _ping test to githubusercontent is always successful without proxy:

(base) user@WSL2:~$ curl https://copilot-proxy.githubusercontent.com/_ping
{"now":1676046306,"status":"ok"}

Interesting. My issue may be slightly different. The curl won't return anything on WSL2, while it returns OK on windows. Any suggestions?

[robharding]

Here's how I set up squid proxy with docker for a workaround:

squid.conf

http_port 3128
http_access allow all
cache deny all
forwarded_for delete
via off

# Enable SSL bump
ssl_bump allow all

# Don't verify server certificates
sslproxy_cert_error allow all
tls_outgoing_options flags=DONT_VERIFY_PEER

run.sh

#!/bin/bash

CONTAINER_NAME="proxy-server-container"
IMAGE_NAME="proxy-server"
PORT=3128

# Check if the container is running
if docker ps --format "{{.Names}}" | grep -Eq "^${CONTAINER_NAME}\$"; then
    echo "Stopping running container..."
    docker stop $CONTAINER_NAME
    docker rm $CONTAINER_NAME
elif docker ps -a --format "{{.Names}}" | grep -Eq "^${CONTAINER_NAME}\$"; then
    echo "Removing stopped container..."
    docker rm $CONTAINER_NAME
fi

# Start the container
echo "Starting the container..."
docker run -d --name proxy-server-container -p $PORT:$PORT proxy-server

echo "Done."

Dockerfile

# Use the official Ubuntu 20.04 image as the base
FROM ubuntu:20.04

# Set environment variables to avoid interactive installation
ENV DEBIAN_FRONTEND=noninteractive

# Update package list and install Squid
RUN apt-get update && \
    apt-get install -y squid

# Copy custom Squid configuration file
COPY squid.conf /etc/squid/squid.conf

# Expose the Squid port
EXPOSE 3128

# Run Squid in the foreground
CMD ["squid", "-N"]

build.sh

#!/bin/bash

docker build -t proxy-server .

then set http://0.0.0.0:3128 as your proxy in vscode.

NOTE: I have to remove the proxy when installing/updating extentions

[tetthys]

This shitty issue still hasn't been resolved lol

[tetthys]

This issue also appears quite often when using paid VPN services.

At least this method seems to work for me.

https://github.com/tetthys/copilotshittyissue-wsl2vpnproxy

Try this repo.

[guaregua19]

Same issue here

[ClaraSchumann]

same

[niladri-1]

1. squid.conf:

   # Set up Squid proxy configuration
   http_port 3128
   http_access allow all
   cache deny all
   forwarded_for delete
   via off
   
   # Enable SSL bump
   ssl_bump allow all
   
   # Disable server certificate verification
   sslproxy_cert_error allow all
   tls_outgoing_options flags=DONT_VERIFY_PEER
   

2. run.sh:

   #!/bin/bash
   
   # Define container and image names
   CONTAINER_NAME="proxy-server-container"
   IMAGE_NAME="proxy-server"
   PORT=3128
   
   # Check if the container is already running or exists
   if docker ps --format "{{.Names}}" | grep -Eq "^${CONTAINER_NAME}\$"; then
       echo "Stopping running container..."
       docker stop $CONTAINER_NAME
       docker rm $CONTAINER_NAME
   elif docker ps -a --format "{{.Names}}" | grep -Eq "^${CONTAINER_NAME}\$"; then
       echo "Removing stopped container..."
       docker rm $CONTAINER_NAME
   fi
   
   # Start the container
   echo "Starting the container..."
   docker run -d --name proxy-server-container -p $PORT:$PORT proxy-server
   
   echo "Done."

3. Dockerfile:

   # Use the official Ubuntu 20.04 image as the base
   FROM ubuntu:20.04
   
   # Set environment variables to avoid interactive installation
   ENV DEBIAN_FRONTEND=noninteractive
   
   # Update package list and install Squid
   RUN apt-get update && \
       apt-get install -y squid
   
   # Copy custom Squid configuration file
   COPY squid.conf /etc/squid/squid.conf
   
   # Expose the Squid port
   EXPOSE 3128
   
   # Run Squid in the foreground
   CMD ["squid", "-N"]

4. build.sh:

   #!/bin/bash
   
   # Build the Docker image
   docker build -t proxy-server .

[tetthys]

I was inspired by this. Thank you!

https://github.com/tetthys/copilotshittyissue-wsl2vpnproxy

[PsikxCat]

Same issue

[fredpiuma]

[SOLVED] Downgrade to version v1.188.0

Problem: There is an issue in the latest version of Github Copilot that causes it to work on Windows but not WSL.

[INGCapaDev]

Thanks, that's working in my case 👍

[binbalenci]

This works in my case too. Thanks!