UNABLE_TO_GET_ISSUER_CERT_LOCALLY in Copilot Chat

pawsaw commented 10 months ago

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:

Ask anything in Chat

roblourens commented 10 months ago

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 commented 10 months ago

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 commented 10 months ago

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

You may want to try disabling http.proxyStrictSSL

Ron024 commented 10 months ago

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 commented 10 months ago

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 commented 10 months ago

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

gil31 commented 10 months ago

Hi Logan,

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

Have a good day Gil

lramos15 commented 10 months ago

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

pawsaw commented 10 months ago

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 commented 10 months ago

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 commented 10 months ago

Yes, this is still an issue

aaronlippold commented 10 months ago

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 commented 9 months ago

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 commented 9 months ago

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 commented 9 months ago

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 commented 9 months ago

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 commented 9 months ago

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 commented 9 months ago

@balexandermunoz What error do you see using the advanced setting

balexandermunoz commented 9 months ago

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

lramos15 commented 9 months ago

@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 commented 9 months ago

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 commented 9 months ago

@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 commented 9 months ago

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 commented 9 months ago

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

gygelly commented 9 months ago

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 commented 9 months ago

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

gil31 commented 9 months ago

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 commented 9 months ago

@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 commented 9 months ago

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 commented 9 months ago

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

roaa108 commented 8 months ago

To request access to GitHub Copilot through your company's firewall, you'll typically need the specific URLs or domains that Copilot uses. find more here

code669 commented 8 months ago

solved my problem by in settings.json, added "github.copilot.advanced": { "debug.useNodeFetcher": true }

joelzeal commented 8 months ago

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
}

This fixed it for me

karnold1ur commented 8 months ago

Was able to get this fixed by switching to pre-release and using

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

data-stack404 commented 8 months ago

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

This also solved the issue for me.

MacOS 14.2.1 VSC 1.85.1 Copilot 1.146 Company uses zscaler v. 4.1

pexa-abruno commented 7 months ago

After upgrading to latest MacOS 14.3 many of our corporate VSCode copilot plugins fail due to SSL errors, as our company uses MITM / VPN with self signed certs.

I tried the insider version, fresh install, add the plugins, added the above settings but no luck.

Have raised a support ticket with Microsoft github service desk, and also working with Palo Alto to resolve for 100s of users.

Any ideas, help, appreciated.

sugamxp commented 7 months ago

Hi I'm facing the same issue on the latest version of VSCode and the extension.

globaltrickster commented 7 months ago

Same Zscaler attack here, had to go to pre-release and also add the settings

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

kevinthenard commented 6 months ago

Hi, I have the same issue, I try all solution here, without result: SSL in conf, set the useNodeFetcher to true, VSCode Insider or not and copilot pre-release or just release. For information, I use WSL, ZScaler and Windows 10. I have a 404 on https://api.githubcopilot.com/ with Network Proxy Test

ManoMangaldas commented 6 months ago

Same Zscaler attack here, had to go to pre-release and also add the settings

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

j-avila commented 6 months ago

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
}

This works pretty well for me. Thanks a lot!

Version: 1.87.0 (user setup) Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2 Date: 2024-02-27T23:41:44.469Z Electron: 27.3.2 ElectronBuildId: 26836302 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: 11.8.172.18-electron.0 OS: Windows_NT x64 10.0.19045

ayoubachak commented 6 months ago

I'm using Zscaler too this setting worked for me :

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

Make sure to reload the extension and VSCode if needed.

VSCode : Version: 1.87.0 (system setup) Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2 Date: 2024-02-27T23:41:44.469Z Electron: 27.3.2 ElectronBuildId: 26836302 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: 11.8.172.18-electron.0 OS: Windows_NT x64 10.0.22631

Github Copilot : Version: 1.171.0 Publisher: GitHub VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=GitHub.copilot

mwthrane commented 6 months ago

I'm using Zscaler too this setting worked for me :
"github.copilot.advanced": {
  "debug.useNodeFetcher": true
}
Make sure to reload the extension and VSCode if needed.

VSCode : Version: 1.87.0 (system setup) Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2 Date: 2024-02-27T23:41:44.469Z Electron: 27.3.2 ElectronBuildId: 26836302 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: 11.8.172.18-electron.0 OS: Windows_NT x64 10.0.22631

Github Copilot : Version: 1.171.0 Publisher: GitHub VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=GitHub.copilot

Worked for me. Zscaler here.

Scoop2389 commented 5 months ago

Hello! For anyone still having this issue, turning this setting on: solved it for me (http.experimental.systemCertificatesV2)

EliiseS commented 5 months ago

I also have this same issue, but when I enable all the settings, I get this error in the copilot debug output:

2024-04-05 14:17:14.866 [info] [extension] Error on conversation request: Error: unable to get local issuer certificate
    at TLSSocket.onConnectSecure (node:_tls_wrap:1600:34)
    at TLSSocket.emit (node:events:517:28)
    at TLSSocket._finishInit (node:_tls_wrap:1017:8)
    at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:803:12)
    at Socket.ondata (node:internal/js_stream_socket:77:22)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:335:12)
    at readableAddChunk (node:internal/streams/readable:308:9)
    at Socket.Readable.push (node:internal/streams/readable:245:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

devm33 commented 5 months ago

@EliiseS can you try debug.useElectronFetcher instead of debug.useNodeFetcher

chankung9 commented 5 months ago

Hello! For anyone still having this issue, turning this setting on: solved it for me (http.experimental.systemCertificatesV2)

this solution solve all my problem , chat , auto suggession

EliiseS commented 5 months ago

@devm33 Unfortunately no help. The code completion co-pilot does work, which is good enough for now I suppose :)

This is the error I receive with the above settings in the output terminal:

2024-04-10 09:57:23.257 [info] [extension] Error on conversation request: aJ: unable to get local issuer certificate
    at K2e (/root/.vscode-server/extensions/github.copilot-chat-0.14.2024032901/dist/extension.js:92:29514)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Git (/root/.vscode-server/extensions/github.copilot-chat-0.14.2024032901/dist/extension.js:92:31536)
    at X8.fetch (/root/.vscode-server/extensions/github.copilot-chat-0.14.2024032901/dist/extension.js:1175:27890)
    at hCe (/root/.vscode-server/extensions/github.copilot-chat-0.14.2024032901/dist/extension.js:1143:7965)
    at wg.fetchMany (/root/.vscode-server/extensions/github.copilot-chat-0.14.2024032901/dist/extension.js:1143:12855)
    at wg.fetchOne (/root/.vscode-server/extensions/github.copilot-chat-0.14.2024032901/dist/extension.js:1143:12036)
    at aE.fetchConversationResponse (/root/.vscode-server/extensions/github.copilot-chat-0.14.2024032901/dist/extension.js:859:1235)
    at aE._provideResponseWithProgress (/root/.vscode-server/extensions/github.copilot-chat-0.14.2024032901/dist/extension.js:857:1617)
    at aE.provideResponseWithProgress (/root/.vscode-server/extensions/github.copilot-chat-0.14.2024032901/dist/extension.js:855:1830)
    at r.x (/root/.vscode-server/extensions/github.copilot-chat-0.14.2024032901/dist/extension.js:869:859)
    at i.$invokeAgent (/vscode/vscode-server/bin/linux-x64/5c3e652f63e798a5ac2f31ffd0d863669328dc4c/out/vs/workbench/api/node/extensionHostProcess.js:154:44359)

devm33 commented 5 months ago

Thanks for trying @EliiseS! That error stacks looks a bit odd to me though, did you restart VS Code after applying the setting?

You should see something like [info] [FetcherService] Using Electron fetcher in the GitHub Copilot Chat output panel.

EliiseS commented 5 months ago

@devm33 you're right, the setting doesn't seem to be having any effect. I only see info] [FetcherService] Using Helix fetcher when I enable the setting. If I change it back to node it'll says [info] [FetcherService] Using Node fetcher

I'm using:

GitHub Copilot Chat - v0.14.2024032901 (pre-release) GitHub Copilot - v1.179.817 (pre-release)

microsoft / vscode-copilot-release

UNABLE_TO_GET_ISSUER_CERT_LOCALLY in Copilot Chat #525