why is my github copilot not working all of a sudden?

Question

I have been using copilot for a while now, and one fine day on opening VSCode this error appeared.

"[ERROR] [default] [2022-04-09T08:38:10.995Z] GitHub Copilot could not connect to server. Extension activation failed: "certificate has expired"

I looked up for it everywhere and found nothing, it'd be a great help if someone could fix this for me!

[here's the error and how the extension looks like on the status bar]

I have the same problem just with PyCharm, all of a sudden it is not working — aqua, Apr 27 '22 at 09:12

stevec · Answer 1 · 2022-11-28T05:47:38.507

43

Three common causes:

An out of date IDE. Solution: make sure your IDE is up to date
If you're not properly signed in to GitHub CoPilot. Solution: make sure you're signed in to GitHub CoPilot

E.g. In VSCode look on the bottom left, if you see this, you might not be signed in:

Click the icon, and follow the prompts to sign in, then CoPilot should work.

Try closing and reopening your IDE (e.g. vscode), that may also help.

edited Nov 28 '22 at 05:47

answered Jul 03 '22 at 05:05

stevec

41,291
27
223
311

4

I had to restart VSCode as well – Yasha Nov 26 '22 at 01:31
Find GitHub Copilot in VSC extension, click settings icon, and check Add to workspace recommendation. This is my final resort. – tedyyu Mar 10 '23 at 02:41
Ignored his comment that the certificate has expired. what certificate? Useless answer. – C.J. Jul 14 '23 at 17:01

score 17 · Answer 2 · answered Dec 17 '22 at 02:54

17

I know its a bit late. But I encountered this problem today. If disabling and restarting doesn't help, you could try:

At uninstall, select Install another version, and select the version before the latest

Reload vscode

After doing this, my copilot started working again.

answered Dec 17 '22 at 02:54

calypso

171
1
4

Thanks man it's working fine after installed the previous version of copilot – sekhar javvadi Dec 17 '22 at 05:54
it seems that using the latest version that just came out (17 December at 4 am ET) solves this issue for me! They solved the bug I think – schlodinger Dec 17 '22 at 09:14
Changing to the previous version of Copilot worked for me. – Loïs Talagrand Apr 05 '23 at 20:12

Good Muyis · Answer 3 · 2023-05-10T09:12:04.617

7

Two things you should check:

1=> Update VSCode to the latest version

2=> Update GitHub Copilot to the latest version (Enable it from the extension section)

After the update, it MAY require that you Reload/Restart VSCode.

From the Menubar, go to View -> Output; Choose GitHub Copilot from the pulldown on the left to see the log of what is going on in the background.

Look at my pulldown here imgur.com/VVHfqwv

edited May 10 '23 at 09:12

answered Jun 03 '22 at 10:39

Good Muyis

127
9

3

I did ```View -> Output```, but I don't see GitHub Copilot in any pulldown on the left. – Kevin Weinrich Jun 21 '22 at 16:24
Try to update the **GitHub Copilot** to the latest version and Enable it from the extension section. After the update, it MAY require that you Reload VSCode. Look at my pulldown here https://imgur.com/VVHfqwv – Good Muyis Jun 23 '22 at 09:07
After updating VSCode, it works again! – Tim Yao Aug 05 '22 at 04:47

score 3 · Answer 4 · answered Dec 23 '22 at 04:38

3

Go to your Github account and check if you have paid the bill, In my case that was the problem.

answered Dec 23 '22 at 04:38

Kushagra Kumar

131
1
3

score 3 · Answer 5 · answered Apr 25 '23 at 00:40

Went to copilot extension settings and changed

    "github.copilot.enable": {

        "*": true,
        "plaintext": false,
        "markdown": false,
        "scminput": false
    }

to

    "github.copilot.enable": {

        "*": true,
        "typescript": true,
        "plaintext": false,
        "markdown": false,
        "scminput": false
    }

and it suddenly started working. I may have opted to disable it for typescript in a GUI a day or two ago - if so that would indicate more state than what is seen in the settings.json file (?).

As time passed it happened again. Checked the settings and the "typescript" property had disappeared. Set it again and all was well. — Craig Hicks, Jul 20 '23 at 23:34

score 1 · Answer 6 · answered Jan 17 '23 at 23:10

1

In Visual Studio, if you are the one that disabled the Copilot before you can enable the following way.

Either search for "Copilot". Or go to Tools>>Options>>GitHub>>Copilot

Go to Enable Globally and change from false to True.

answered Jan 17 '23 at 23:10

Vectoria

1,627
14
13

score -1 · Answer 7 · answered Aug 17 '23 at 19:44

All the above solutions didn't work for me.

What worked for me was opening VS Code as an "administrator". Then Github Copilot just started working ✅

Here's where I found that solution: https://github.com/orgs/community/discussions/6785#discussioncomment-1561804

score -2 · Answer 8 · answered Oct 31 '22 at 13:59

Given that GitHub Copilot is so fresh and well-liked, updates are made often. When encountering this kind of problem, I would advise entirely purging and reinstalling.

Installation of GitHub Copilot in Visual Studio Code

The documentation lists extensions for Visual Studio Code, Visual Studio, Neovim, and the JetBrains suite as IDEs that GitHub Copilot supports.

The installation consists of three main steps:

Create a GitHub account (if you don’t have one already).

Go to GitHub Copilot and click on “Start my free trial”. Follow the sign-up steps and make sure to cancel before your 60-day free trial is up (if you don’t want to continue using the tool).

Install the VSCode extension by searching for “GitHub Copilot” on the extensions tab. You’ll be asked to sign in to GitHub, authorize the extension, and then Copilot will be set up.

If you would like a more thorough explanation, my colleague Rafael wrote a great article based on his time with Copilot and VSCode: https://www.scalablepath.com/full-stack/ai-pair-programming-github-copilot-review

why is my github copilot not working all of a sudden?

8 Answers8