UNABLE_TO_GET_ISSUER_CERT_LOCALLY in Copilot Chat

[pawsaw]

• VS Code Version: Version: 1.84.0-insider (Universal) Commit: d037ac076cee195194f93ce6fe2bdfe2969cc82d Date: 2023-11-01T10:18:23.824Z (6 hrs ago) Electron: 25.9.2 ElectronBuildId: 24603566 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Darwin arm64 23.1.0

• OS Version: macOs 14.1 (23B74)

• Logs: n/A

Steps to Reproduce:

1. Ask anything in Chat

[roblourens]

I assume you're using a corporate proxy or some other non-standard network environment? Can you tell me what you know about it?

[pawsaw]

Let me check soon, as my current working environment is quite new to me too.

What I can say for now is, that a fresh npm/ yarn installation works out of the box, without the need to configure proxy etc. Also vanilla VSCode "networking" seems to work.

However, what I researched so far is: the error code most probably is sourced from node. But this is just a guess.

Kind, Pawel

[lramos15]

This normally means you have a self signed certificate in your certificate chain.

You may want to try disabling http.proxyStrictSSL

[Ron024]

Go into settings (ctl+,) and search for "http proxy". Then deselect the check box on "Http: Proxy Strict SSL". This allowed me to use copilot through a Zscaler proxy.

[gil31]

Hi,

I have been using copilot for a long time without any problems. I installed the latest version of VSC (1.84 for win32 X64). Since then I have had exactly the same problem.

1. I tried to modify the setting as indicated above, it does not work.
2. I reverted to version 1.83. Everything is working properly again.

Have a nice day Gil.

Version: 1.83.1 (user setup) Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc Date: 2023-10-10T23:48:05.904Z Electron: 25.8.4 ElectronBuildId: 24154031 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.19044

[lramos15]

@gil31 Can you share your logs and some information about your network setup?

[gil31]

Hi Logan,

Unfortunately when installing version 1.83.1, I lost information related to the current problem.

Have a good day Gil

[lramos15]

Is anyone still blocked on this before I close the issue out?

[pawsaw]

Is anyone still blocked on this before I close the issue out?

Why do you want to close it? This is an issue reported by many people out there.

[lramos15]

Why do you want to close it? This is an issue reported by many people out there.

Are you still blocked? We've made some changes here

[aaronlippold]

Yes, this is still an issue

[aaronlippold]

Go into settings (ctl+,) and search for "http proxy". Then deselect the check box on "Http: Proxy Strict SSL". This allowed me to use copilot through a Zscaler proxy.

I am behind zscaler and this did not seem to resolve the issue. NODE EXTRA CERTS is set as well

[lramos15]

Yes, this is still an issue

Can you try adding this to your settings.json to try out some new experimental fetcher code we're working on

"github.copilot.advanced": {
  "debug.useNodeFetcher": true
}

[aaronlippold]

I will give that a try when I’m back at my desk

On Sun, Nov 19, 2023 at 11:45 Logan Ramos @.***> wrote:

Yes, this is still an issue

Can you try adding this to your settings.json to try out some new experimental fetcher code we're working on

"github.copilot.advanced": { "debug.useNodeFetcher": true }

— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode-copilot-release/issues/525#issuecomment-1817911755, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALK42BOFLKVWLYZVVEG2KLYFIZTTAVCNFSM6AAAAAA6ZTRUDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXHEYTCNZVGU . You are receiving this because you commented.Message ID: @.***>

[wimvc1]

Yes, this is still an issue

Can you try adding this to your settings.json to try out some new experimental fetcher code we're working on

"github.copilot.advanced": {
  "debug.useNodeFetcher": true
}

Works for me! (GitHub Copilot Chat - v0.11.2023112001 - Pre-Release)

[balexandermunoz]

Same issue here. I'm using Zscaler. OS: Windows 10 Enterprise 22H2 Vscode Version: 1.84.2 Copilot Chat Version: 0.10.2

I have tried all the solutions here and nothing worked. (Downgrade Vscode, add "github.copilot.advanced", change "Http: Proxy Strict SSL")

[poychang]

I get the same issue here. I'm using Zscaler. Disabling http.proxyStrictSSL and adding debug.useNodeFetcher can fix this issue.

Version: 1.84.2 (user setup) Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e Date: 2023-11-09T10:51:52.184Z Electron: 25.9.2 ElectronBuildId: 24603566 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.22631

[lramos15]

@balexandermunoz What error do you see using the advanced setting

[balexandermunoz]

@lramos15 Same as before: Please check your firewall rules and network connection then try again. Error Code: UNABLE_TO_GET_ISSUER_CERT_LOCALLY.

[lramos15]

@lramos15 Same as before: Please check your firewall rules and network connection then try again. Error Code: UNABLE_TO_GET_ISSUER_CERT_LOCALLY.

Could you install the Network Proxy Test extension (https://marketplace.visualstudio.com/items?itemName=chrmarti.network-proxy-test) and check the output of F1 > Network Proxy Test: Test Connection in VS Code?

When asked for the URL enter https://api.githubcopilot.com/. This should respond with a 404 Not Found status, that is expected, but maybe you get something else. Please share the output of this (make sure to remove any sensitive information first).

[balexandermunoz]

Could you install the Network Proxy Test extension (https://marketplace.visualstudio.com/items?itemName=chrmarti.network-proxy-test) and check the output of F1 > Network Proxy Test: Test Connection in VS Code?

VS Code 1.84.2
Network Proxy Test 0.0.8
win32

Settings:
- http.proxy: 
- http.proxyAuthorization: null
- http.proxyStrictSSL: false
  - globalValue: false
- http.proxySupport: override
- http.systemCertificates: true

Environment variables:

Sending GET request to https://api.githubcopilot.com/...
Received response:
- Status: 404 Not Found

@lramos15 like this? It's a 404, but I still don't get answer

[lramos15]

@balexandermunoz Apologies I didn't realize you weren't on the pre-release version of the extension.

Could you try VS Code insiders with the latest pre-release version of the extension v0.11.2023112701 or greater. As well as the setting

"github.copilot.advanced": {
  "debug.useNodeFetcher": true
}

as that setting is not in the release version yet. It should be in the release version next week.

Based on the proxy test that should unblock you

[aaronlippold]

I didn’t move to prerelease either

On Mon, Nov 27, 2023 at 10:51 Logan Ramos @.***> wrote:

@balexandermunoz https://github.com/balexandermunoz Apologies I didn't realize you weren't on the pre-release version of the extension.

Could you try VS Code insiders https://code.visualstudio.com/insiders/ with the latest pre-release version of the extension v0.11.2023112701 or greater. As well as the setting

"github.copilot.advanced": { "debug.useNodeFetcher": true }

as that setting is not in the release version yet. It should be in the release version next week.

Based on the proxy test that should unblock you

— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode-copilot-release/issues/525#issuecomment-1828104329, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALK42BLN4PL4OLHQZF3UMLYGSZHBAVCNFSM6AAAAAA6ZTRUDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRYGEYDIMZSHE . You are receiving this because you commented.Message ID: @.***>

[spacerodent]

The proposed fixes work for me on Windows but not when using WSL.

[gygelly]

yup, I was in the same boat. Swapping to insiders, using preview of copilot chat, and putting "debug.useNodeFetcher": true in settings made it start working again.

[hughesdai]

Same problem here, tried all the recommendations except getting VS Code insiders, no luck so far, waiting for suggestions/updated release.

[gil31]

Hi , Have you somme news. I use vsc and copilot in professional context and this issue IS extremely problematic for my productivité.

Have a nice day Gil

[hughesdai]

@gil31 in settings.json, I added "github.copilot.advanced": { "debug.useNodeFetcher": true } There is a new update to VS Code, along with GitHub Copilot released today. After the update, it seems to be working.

[MullinsN]

So, I have been having this issue for many many weeks and months, when I travelled into the office. I pushed on it to get it fixed, and a chat with one of the network engineers. He looked at the network proxy output and he made the following change for now. His comment was a follows.

"The corporate firewalls do HTTPS inspection - so I have to bypass that check when you access api.githubcopilot.com"

Hopefully it helps, those who need to have a conversation with Networks, or know what to look for in their setup.

[gil31]

Hi all,

I have just installed the latest version of vsc and the latest version of the copilot and chat copilot extensions. Everything seems to be working again:

Version: 1.85.1 Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2 Date: 2023-12-13T09:49:37.021Z Electron: 25.9.7 ElectronBuildId: 25551756 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.19044