This epic si tracking all issues that users face with configuring [GitLab VS Code Extension](https://gitlab.com/gitlab-org/gitlab-vscode-extension) with self-signed certificates - certificates that are not signed by a universally recognized root certificate authority. At GitLab, we don't use self-signed certificates and that makes certificate-related issues especially hard to debug for GitLab team members. ### I came here when I saw *Unsupported* label on the extension certificate configuration The `gitlab.cert`, `gitlab.certKey`, and `gitlab.ignoreCertificateErrors` settings are community-contributed (https://gitlab.com/gitlab-org/gitlab-vscode-extension/issues/26#note_61312786 and https://gitlab.com/gitlab-org/gitlab-vscode-extension/merge_requests/29#note_132284448). At GitLab, we don't use self-signed certificates and at the moment we haven't got a testing environment and capacity to support a more complex self-signed certificate setup. However, we tested that VS Code works well when you add your Self-Signed Certificate Authority (CA) to your system certificate store. See more information in [the SSL setup guide](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/main/docs/user/ssl.md).