WSL: self signed certificate in certificate chain
Checklist
-
I'm using the latest version of the extension (see the latest version in the right column of this page) - Extension version: v3.40.2
-
I'm using the latest VS Code version (find the latest version here) - VS Code version: 1.64.2
-
I'm using a supported version of GitLab (see README for the supported version) - GitLab version: GitLab Community Edition 14.7.2
Summary
VERY similar to #395 (closed)
The plugin refuses to basically anything and over and over throwing the error "reason: self signed certificate in certificate chain". This happens when I try to add a repo from the plugin. But it also happens when I manually clone a git repo, add the folder and then try to reload the MR and issues in the gitlab side panel. Even if I try to validate a gitlab-ci.yml file.
Steps to reproduce
Open a WSL window. refresh the GitLab MR & Issue side panel
HOWEVER this happens only on some repos! .vscode/settings.json
for both is empty {}
I tired to find the difference between the two but I can't find one.
What is the current bug behavior?
What is the expected correct behavior?
Relevant logs and/or screenshots
[error]: request to https://gitlab.example.de/gitlab/api/graphql failed, reason: self signed certificate in certificate chain
FetchError: request to https://gitlab.example.de/gitlab/api/graphql failed, reason: self signed certificate in certificate chain
at ClientRequest. (/home/dev/.vscode-server/extensions/gitlab.gitlab-workflow-3.40.2/out/extension.js:1:19950)
at ClientRequest.emit (events.js:327:22)
at TLSSocket.socketErrorListener (_http_client.js:469:9)
at TLSSocket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21)