Error getting Copilot to work in visual studio 2022 pro.

[yk-sd]

Select Topic Area

Bug

Body

Hello guys,

I am getting issues while trying to activate the github copilot extension in visual studio 2022 pro.

When I press Sign in to activate copilot. I get this error:

[Error] An error occurred for 'RunOperation:RunOperation': StreamJsonRpc.RemoteInvocationException: Request signInInitiate failed with message: self signed certificate in certificate chain
at StreamJsonRpc.JsonRpc.d__1451.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GitHub.Copilot.CopilotClient.<RunOperation>d__201.MoveNext()
NotSignedIn

Anyone can help me? I paid for the subscription but am unable to use copilot.

[ayim]

Hey, Aaron from Copilot team here.
I haven't run into this issue before, would you be willing to share some crash dumps/hop on a screenshare to go through this together?

Shoot me an email at [username] at github dot com and we'll get the ball rolling.

[yk-sd]

Hi,

Sure, I will record a video demostrating the issue and send it to your e-mail.

Thank you

[yk-sd]

Fixed.

Solution:

Open Microsoft Edge (or another browser that shows certificate information).
Navigate to the github.com website.
Click on the SSL lock icon next to the address bar.
Click on "Connection is secure".
Click on "Certificate (Valid)".
In the certificate window, select the top-most certificate in the chain (usually the root or intermediate certificate).
Click on "Export" and save the certificate as a .pem file.
Open a Command Prompt as an administrator.
Run the command: (setx NODE_EXTRA_CA_CERTS "C:\path\to\your\certificate.pem"). Replace "C:\path\to\your\certificate.pem" with the actual path to the .pem file that you saved.
Restart Visual Studio.
Copilot should now work.
Note: If you are using a different browser or operating system, the steps may differ slightly, but the general idea is to export the self-signed certificate and set the NODE_EXTRA_CA_CERTS environment variable to point to it.

[yk-sd]

Forgot to include documentation :) updated my comment.

[Alineol]

open visual studio and click tools>options>GitHub>Copilot> and set "Accept non-trusted certificates automatically" = true

after doing it click here to login

[nbelley]

@Alineol this doesn't work. I also tried the exta certs thing, I'll try again but for now nothing works.

[nbelley]

@yk-sd your solutioon worked! Thanks!

[tolgabalci]

@Alineol this doesn't work. I also tried the exta certs thing, I'll try again but for now nothing works.

Make sure you export the right cert from the cert list. The default one is definitely NOT the right one. I clicked on the very top (root) cert and that worked. Optionally you can have the default one (the page itself) selected, but when you export, under [Save as type] select "certificate chain" and it will add the selected cert and all parent certs to the .pem file.

Also make sure to do the above for github.com and save the cert with .pem extension (You have to manually type that)

(PS: I added the variable as a system variable, but user variable should work as well)

[NelCapeTown]

Thank you @yk-sd. Nice and succinct, and it works!

[scott-kowalczyk-mckesson]

We had to add https://*.copilot-proxy.githubusercontent.com/ as a Trusted Site in Internet Options at our company.

[epolicardo]

It worked for me also! Thanks @yk-sd !!

[tomdaniel-mensura]

Thanks @yk-sd , worked for us as well!

[borninarage]

So this has been driving me round the bend for the past month.

I finally got this working assuming something like forcepoint proxy is in your way.

1. https://*.copilot-proxy.githubusercontent.com/ needs to be in your trusted internet sites.

2. In Edge (works for me) need to go to the erroring endpoint in my case https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex

You need to go to the certificate select the uppermost cert in the chain and export. You need to save as a pem file but make sure you export the whole chain.
a. Click the padlock/cert info, expand the connection secure option and click the little certificate icon

b. Click to details, in the top window select the upper most certificate and click export

c. Make sure you change the default save as option to certificate chain, and make sure you change the extension from crt to pem.

3. In a command prompt running as admin elevation run: setx NODE_EXTRA_CA_CERTS - PATH TO YOUR CERT

[borninarage]

tada

[NeilYager]

This one worked for me (with PyCharm)

[jacksonsfaria]

Same problem here... How MS can be so bad at providing a product.