UNABLE_TO_GET_ISSUER_CERT_LOCALLY in Copilot Chat #525

pawsaw · 2023-11-01T17:18:04Z

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 · 2023-11-01T21:38:07Z

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 · 2023-11-02T11:53:44Z

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 · 2023-11-03T15:25:59Z

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

You may want to try disabling http.proxyStrictSSL

Ron024 · 2023-11-04T13:13:08Z

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 · 2023-11-06T13:17:06Z

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.

I tried to modify the setting as indicated above, it does not work.
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 · 2023-11-06T15:24:52Z

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

gil31 · 2023-11-07T07:24:20Z

Hi Logan,

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

Have a good day
Gil

lramos15 · 2023-11-15T17:19:01Z

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

pawsaw · 2023-11-16T06:49:13Z

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 · 2023-11-16T13:33:55Z

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 · 2023-11-18T17:05:28Z

Yes, this is still an issue

aaronlippold · 2023-11-18T17:17:04Z

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 · 2023-11-19T16:45:35Z

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 · 2023-11-20T00:37:29Z

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 <#525 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALK42BOFLKVWLYZVVEG2KLYFIZTTAVCNFSM6AAAAAA6ZTRUDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXHEYTCNZVGU> . You are receiving this because you commented.Message ID: ***@***.***>

wimvc1 · 2023-11-21T14:11:45Z

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 · 2023-11-22T04:57:59Z

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 · 2023-11-22T07:38:23Z

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 · 2023-11-22T14:12:09Z

@balexandermunoz What error do you see using the advanced setting

balexandermunoz · 2023-11-22T14:41:21Z

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

lramos15 · 2023-11-22T15:59:58Z

@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 · 2023-11-22T16:10:51Z

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 · 2023-11-27T15:51:02Z

@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 · 2023-11-27T19:30:13Z

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 <#525 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALK42BLN4PL4OLHQZF3UMLYGSZHBAVCNFSM6AAAAAA6ZTRUDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRYGEYDIMZSHE> . You are receiving this because you commented.Message ID: ***@***.***>

joelzeal · 2023-12-29T17:32:03Z

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 · 2023-12-30T14:20:02Z

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

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

data-stack404 · 2024-01-09T09:28:40Z

"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 · 2024-01-31T08:00:21Z

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 · 2024-02-06T18:32:19Z

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

globaltrickster · 2024-02-12T23:32:00Z

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

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

kevinthenard · 2024-02-22T09:25:41Z

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 · 2024-02-25T13:04:33Z

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

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

j-avila · 2024-03-04T13:37:33Z

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 · 2024-03-05T14:38:30Z

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 · 2024-03-06T07:22:17Z

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 · 2024-03-22T19:10:26Z

Hello! For anyone still having this issue, turning this setting on:

solved it for me (http.experimental.systemCertificatesV2)

EliiseS · 2024-04-05T14:18:19Z

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 · 2024-04-05T14:32:32Z

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

chankung9 · 2024-04-10T06:04:49Z

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 · 2024-04-10T10:00:05Z

@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 · 2024-04-10T20:31:34Z

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 · 2024-04-11T16:32:30Z

@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)

devm33 · 2024-04-11T16:36:28Z

@EliiseS hm strange, just to sanity check, is that where you have it in your settings json file?

  "github.copilot.advanced": {
    "debug.useElectronFetcher": true
  },

Also in the GitHub Copilot (not chat) output panel do you see [info] [fetcher] Using Electron fetcher, debug flag is enabled.?

alexdima · 2024-04-12T11:07:36Z

@EliiseS Are you using VS Code remote like SSH, WSL, Dev Containers or Tunnels ?

EliiseS · 2024-04-15T13:27:12Z

@alexdima I am using that exactly, for good measure I even set all other fetchers to false. I only get the log message of: [info] [FetcherService] Using Helix fetcher

@devm33 Ah, I am using a tunnel to a devcontainer, which runs through WSL.

On regular windows the copilot chat actually works perfectly:

2024-04-15 15:20:18.925 [info] [FetcherService] Using Helix fetcher
2024-04-15 15:20:18.925 [info] [gitExtensionService] Initializing Git extension service.
2024-04-15 15:20:18.925 [info] [gitExtensionService] Successfully activated the vscode.git extension.
2024-04-15 15:20:18.925 [info] [gitExtensionService] Enablement state of the vscode.git extension: true.
2024-04-15 15:20:18.925 [info] [gitExtensionService] Successfully registered Git commit message provider.
2024-04-15 15:20:19.655 [info] [auth] Logged in as EliiseS
2024-04-15 15:20:19.979 [info] [chat] copilot token chat_enabled: true
2024-04-15 15:20:19.983 [info] [chat] Registration of interactive providers failed:,Error: Extension 'GitHub.copilot-chat' CANNOT use API proposal: aiTextSearchProvider.
Its package.json#enabledApiProposals-property declares: handleIssueUri, interactive, terminalDataWriteEvent, terminalExecuteCommandEvent, terminalSelection, terminalQuickFixProvider, chatParticipant, chatParticipantAdditions, defaultChatParticipant, chatVariableResolver, chatProvider, mappedEditsProvider, aiRelatedInformation, codeActionAI, findTextInFiles, textSearchProvider, contribSourceControlInputBoxMenu, newSymbolNamesProvider, findFiles2, extensionsAny, authLearnMore, testObserver but NOT aiTextSearchProvider.
 The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api GitHub.copilot-chat
2024-04-15 15:20:19.983 [info] [githubTitleAndDescriptionProvider] Initializing GitHub PR title and description provider provider.
2024-04-15 15:20:19.983 [info] [githubTitleAndDescriptionProvider] GitHub.vscode-pull-request-github extension is not yet activated.
2024-04-15 15:20:19.991 [info] [auth] Got Copilot token for EliiseS
2024-04-15 15:20:27.520 [info] [chat fetch] url https://api.githubcopilot.com/chat/completions
2024-04-15 15:20:27.520 [info] [chat fetch] modelMaxPromptTokens 3072
2024-04-15 15:20:27.520 [info] [chat fetch] modelMaxResponseTokens 4096
2024-04-15 15:20:27.520 [info] [chat fetch] chat model gpt-4
2024-04-15 15:20:30.417 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 2896 ms
2024-04-15 15:20:30.440 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-04-15 15:20:30.441 [info] [streamChoices] request done: requestId: [8e03e798-97ff-46ad-8d10-a29303d2e942] responseId: [8e03e798-97ff-46ad-8d10-a29303d2e942] model deployment ID: []
2024-04-15 15:20:30.445 [info] [chat fetch] url https://api.githubcopilot.com/chat/completions
2024-04-15 15:20:30.445 [info] [chat fetch] modelMaxPromptTokens 7168
2024-04-15 15:20:30.445 [info] [chat fetch] modelMaxResponseTokens 4096
2024-04-15 15:20:30.445 [info] [chat fetch] chat model gpt-3.5-turbo
2024-04-15 15:20:31.510 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 1065 ms
2024-04-15 15:20:31.543 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-04-15 15:20:31.544 [info] [streamChoices] request done: requestId: [17e35bac-66d0-46b3-a979-0b6d58375af5] responseId: [17e35bac-66d0-46b3-a979-0b6d58375af5] model deployment ID: [x4dff5e5d11fc]
2024-04-15 15:20:46.327 [info] [chat fetch] url https://api.githubcopilot.com/chat/completions
2024-04-15 15:20:46.327 [info] [chat fetch] modelMaxPromptTokens 3072
2024-04-15 15:20:46.327 [info] [chat fetch] modelMaxResponseTokens 4096
2024-04-15 15:20:46.327 [info] [chat fetch] chat model gpt-4
2024-04-15 15:20:49.819 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 3491 ms
2024-04-15 15:20:49.857 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-04-15 15:20:49.857 [info] [streamChoices] request done: requestId: [9400238c-4450-4996-a89c-67cb9a6d3897] responseId: [9400238c-4450-4996-a89c-67cb9a6d3897] model deployment ID: []
2024-04-15 15:20:49.863 [info] [chat fetch] url https://api.githubcopilot.com/chat/completions
2024-04-15 15:20:49.863 [info] [chat fetch] modelMaxPromptTokens 7168
2024-04-15 15:20:49.863 [info] [chat fetch] modelMaxResponseTokens 4096
2024-04-15 15:20:49.863 [info] [chat fetch] chat model gpt-3.5-turbo
2024-04-15 15:20:50.701 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 837 ms
2024-04-15 15:20:50.723 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-04-15 15:20:50.724 [info] [streamChoices] request done: requestId: [eb166036-3202-4e56-b392-5ad9bb0cfd4b] responseId: [eb166036-3202-4e56-b392-5ad9bb0cfd4b] model deployment ID: [x4dff5e5d11fc]

On just WSL, it won't even let me log in:

2024-04-15 13:41:54.223 [info] [fetcher] Using Helix fetcher, Electron fetcher is not available.
2024-04-15 13:44:07.656 [error] [auth] Extension activation failed: "tunneling socket could not be established, cause=connect ETIMEDOUT 127.0.0.42:9000"

On just devcontainer, I get the same error as in devcontainer w/ tunneling.

caoshuai619 · 2024-04-18T07:19:20Z

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

thanks very much. This works for me when using copilot chat in wsl2.

tlewers01 · 2024-05-01T04:11:18Z

"debug.useNodeFetcher": true

I am also behind Zscaler and this seams to have fixed the issue for me.

ChrisKibble · 2024-05-08T14:55:00Z

Just to add to the solution and description, I'm also behind Zscaler.

The reason it's not working out of the box is that your companies are using SSL inspection which involves replacing the certificate you're using on some or all sites so they can decrypt/re-encrypt the traffic, usually to log or analyze. You can confirm this by visiting https://api.githubcopilot.com/ and looking at the parent of the issued cert, it'll be Zscaler. The same is likely true for other proxy or VPN solutions that work similarly.

The internal (to the company) fix would be to stop SSL inspection on the domains identified here.

For me, the solution to use the pre-release of the GitHub Copilot and GitHub Copilot Chat along with the latest version of VSCode resolved the issue. I did not need to modify the Proxy SSL or the NodeFetcher values.

Version: 1.89.0 (user setup)
Commit: b58957e67ee1e712cebf466b995adf4c5307b2bd
Date: 2024-05-01T02:09:22.859Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631

xaviervv · 2024-05-28T08:38:02Z

I had this issue on the newest version of 0.15.2, rolling back to 0.15.1 solved it for me
just in case I had also rolled back GitHub Copilot extension from 1.195.0 to 1.194

GitHubCanada · 2024-06-05T20:39:26Z

#525 (comment)

this work for me.

sairaghavak · 2024-09-26T20:58:49Z

This comment worked for me.

I am behind Zscaler and in WSL. And this has worked in my case

Updated the following in ~/.vscode-server/data/Machine/settings.json

"http.proxyStrictSSL": false,

And in workspace settings.json Updated the following

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

jejamnicki-fadv · 2024-10-31T14:15:04Z

@sairaghavak thank you! same on WSL behind Zscaler

in my case http.proxyStrictSSL was true by default and it was working anyway

This comment worked for me.

I am behind Zscaler and in WSL. And this has worked in my case

Updated the following in ~/.vscode-server/data/Machine/settings.json

"http.proxyStrictSSL": false,
And in workspace settings.json Updated the following

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

simonezambettiabb · 2024-11-11T13:33:54Z

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.

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

Worked for me thanks.

github-actions bot added the triage-needed Issues needing to be assigned to the prospective feature owner label Nov 1, 2023

github-actions bot assigned roblourens Nov 1, 2023

roblourens added bug Issue identified by VS Code Team member as probable bug network Network infrastructure for request/response and removed triage-needed Issues needing to be assigned to the prospective feature owner labels Nov 1, 2023

roblourens assigned lramos15 Nov 1, 2023

bajtos mentioned this issue Nov 9, 2023

Station not handling jobs: Fetch failed UNABLE_TO_GET_ISSUER_CERT_LOCALLY CheckerNetwork/desktop#1094

Open

alexdima assigned chrmarti May 16, 2024

UNABLE_TO_GET_ISSUER_CERT_LOCALLY in Copilot Chat #525

UNABLE_TO_GET_ISSUER_CERT_LOCALLY in Copilot Chat #525

Comments

pawsaw commented Nov 1, 2023

roblourens commented Nov 1, 2023 • edited Loading

pawsaw commented Nov 2, 2023

lramos15 commented Nov 3, 2023

Ron024 commented Nov 4, 2023

gil31 commented Nov 6, 2023

lramos15 commented Nov 6, 2023

gil31 commented Nov 7, 2023

lramos15 commented Nov 15, 2023

pawsaw commented Nov 16, 2023

lramos15 commented Nov 16, 2023

aaronlippold commented Nov 18, 2023

aaronlippold commented Nov 18, 2023

lramos15 commented Nov 19, 2023

aaronlippold commented Nov 20, 2023 via email

wimvc1 commented Nov 21, 2023

balexandermunoz commented Nov 22, 2023 • edited Loading

poychang commented Nov 22, 2023

lramos15 commented Nov 22, 2023

balexandermunoz commented Nov 22, 2023 • edited Loading

lramos15 commented Nov 22, 2023

balexandermunoz commented Nov 22, 2023 • edited Loading

lramos15 commented Nov 27, 2023

aaronlippold commented Nov 27, 2023 via email

joelzeal commented Dec 29, 2023

karnold1ur commented Dec 30, 2023

data-stack404 commented Jan 9, 2024

pexa-abruno commented Jan 31, 2024 • edited Loading

sugamxp commented Feb 6, 2024 • edited Loading

globaltrickster commented Feb 12, 2024

kevinthenard commented Feb 22, 2024

ManoMangaldas commented Feb 25, 2024

j-avila commented Mar 4, 2024

ayoubachak commented Mar 5, 2024 • edited Loading

mwthrane commented Mar 6, 2024

Scoop2389 commented Mar 22, 2024

EliiseS commented Apr 5, 2024

devm33 commented Apr 5, 2024

chankung9 commented Apr 10, 2024

EliiseS commented Apr 10, 2024

devm33 commented Apr 10, 2024

EliiseS commented Apr 11, 2024 • edited Loading

devm33 commented Apr 11, 2024 • edited Loading

alexdima commented Apr 12, 2024

EliiseS commented Apr 15, 2024 • edited Loading

caoshuai619 commented Apr 18, 2024

tlewers01 commented May 1, 2024

ChrisKibble commented May 8, 2024

xaviervv commented May 28, 2024

GitHubCanada commented Jun 5, 2024

sairaghavak commented Sep 26, 2024 • edited Loading

jejamnicki-fadv commented Oct 31, 2024

simonezambettiabb commented Nov 11, 2024 • edited Loading

roblourens commented Nov 1, 2023 •

edited

Loading

balexandermunoz commented Nov 22, 2023 •

edited

Loading

balexandermunoz commented Nov 22, 2023 •

edited

Loading

balexandermunoz commented Nov 22, 2023 •

edited

Loading

pexa-abruno commented Jan 31, 2024 •

edited

Loading

sugamxp commented Feb 6, 2024 •

edited

Loading

ayoubachak commented Mar 5, 2024 •

edited

Loading

EliiseS commented Apr 11, 2024 •

edited

Loading

devm33 commented Apr 11, 2024 •

edited

Loading

EliiseS commented Apr 15, 2024 •

edited

Loading

sairaghavak commented Sep 26, 2024 •

edited

Loading

simonezambettiabb commented Nov 11, 2024 •

edited

Loading