CoPilot VSCode Timeout when developing in WSL

[witwit]

Select Topic Area

Question

Body

Sometimes it works, sometimes it does not. I have the extension installed both local and in remote (WSL).
When developing locally in Windows, copilot works. In WSL, however, usually I get a time-out:
GitHub Copilot could not connect to server. Extension activation failed: "connect ETIMEDOUT 140.82.121.6:443"

Sometimes it does work, though. My winows firewall is open for both VSCode and WSL.

I am still in 2-month testing period for the co-pilot. However, I will not continue to use it, because I usually develop in WSL environment.

[queenofcorgis]

Thanks for posting in the GitHub Community, @witwit !

We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Issues category is solely related to conversations around the GitHub products Issues and Projects. I've gone ahead and moved it for you. Good luck!

[github-actions[bot]]

🕒 Stale Discussion Alert 🕒

This Discussion has been labeled as stale 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 stale notification will only apply to Discussions with the Question label. To learn more, see our recent stalebot announcement.

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