[error] GitHub Copilot could not connect to server. Extension activation failed: "fetch failed"

[Deophius]

Select Topic Area

Bug

Copilot Feature Area

VS Code

Body

I believe I have a Copilot Pro subscription, and I only used 10% of the premium requests this month. But when I tried to use Copilot today, I was told that I was offline.

I ran curl --verbose https://copilot-proxy.githubusercontent.com/_ping and it gave a 200 OK status.

When I looked in the output of the Github Copilot Chat extension, I saw the following line:

[error] GitHub Copilot could not connect to server. Extension activation failed: "fetch failed"

Any help would be greatly appreciated!

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[Deophius]

Thank you, but I already solved the problem in another quite strange manner: I encountered this bug in a dev container. After making a Copilot request on my local machine, somehow the connection to Copilot in the dev container was re-established. 😂 I guess this must have something to do with the proxy settings in the dev container.