Gitlab Explorer cannot connect to self hosted Gitlab
vincowl opened this issue · comments
While having set up gitlab-explorer.serverAddress and gitlab-explorer.personalToken which values are the same for the working Gitlab Workflow extension, the following message is displayed in the Gitlab Project Explorer window.
There is no data provider registered that can provide view data.
Using :
- Gitlab CE 11.6.0 (075f960)
- GitLab Shell 8.4.3
- GitLab Workhorse v7.6.0
- GitLab API v4
- VS Code 1.30.1
I'm having the same error.
Using:
- VSCode 1.30.1
- V4 Api as well
- Not sure about the server version atm. It is a self hosted CE Edition but i have no access to it.
I'm sitting behind a corporate proxy though, and have a local cntlm proxy through which i have to forward all my traffic. I run VSCode using the --proxy-server for that (works at least for the marketplace and the download of extensions).
So, i found this error Message in the developer console:
Activating extension 'rrivera.vscode-gitlab-explorer' failed: Cannot find module './Providers/gitlab/api'. t._logMessageInConsole @ /usr/share/code/resources/app/out/vs/workbench/workbench.main.js:5723
which seems pretty clear about what the underlying problem is. Only thing is i have yet to figure out how to install that module into my environment. I'd guess that the module is missing from the package.json, but then alot more people would have experienced this issue!?
I am also seeing the same error when using our self-hosted gitlab instance. Any updates?
Same issue on VSCodium 1.33.1 and self hosted gitlab instance. Any updates?
I have a similar problem connecting to a self hosted gitlab-ce server.
Gitlab Explorer: Error => unable to verify first certificate
is this project still alive?
+1
The issue is with the path specified '/Providers/gitlab/api' the actual path is /providers/gitlab/api