"No Git repository available" when working with self-hosted instance

Checklist

The version of GitLab is controlled by my company IT, as is my VSCode version. The extension version is what VSCode installed from the public store.

Summary

My company uses a self-hosted GitLab server that I am trying to configure the VSCode extension to integrate with from a devcontainer (though the behavior is the same locally). I had some problems with a self-signed CA and proxy settings, but I believe that I have worked through them (though there may still be lingering impacts).

At this point I have been able to authenticate the extension against our GitLab instance (providing the URL and access token) but the toolbar now just shows a message of:

No Git repository available. To learn how to fix this, check the Source Control tab.

When I go to the Source Control tab I very clearly have a operational git repository that was cloned from the same GitLab instance I provided at login.

Steps to reproduce

Not sure here. I've authenticated and not seeing what I expected. I'm guessing the issue comes from deeper in the install/network architecture that would be difficult for me convey and likely to reproduce.

What is the current bug behavior?

The extension reports only the error mentioned above, without providing any insight or capability.

What is the expected correct behavior?

Documentation indicates that I should be seeing information about tickets and pipeline status.

Relevant logs and/or screenshots

image

Possible fixes

As noted above, I had some issues getting the authentication to work through the company's proxy and private cert. To accomplish this, I have implemented the following in my devcontainer.json file:

"containerEnv": {
    "http_proxy": "http://192.168.10.10:80",
    "https_proxy": "http://192.168.10.10:80",
    "no_proxy": "gitlab.mycomp.com"
}

and

"customizations": {
    "vscode": {
        "extensions": [
                "GitLab.gitlab-workflow",
	],
        "settings": {
            "http.systemCertificates": true,
            "gitlab.aiAssistedCodeSuggestions.enabled": false,
            "gitlab.duoChat.enabled": false,
            "gitlab.showPipelineUpdateNotifications": true
        }
    }
}

My other suspicion comes from a potential mismatch in the repo origin. After reading #535 (closed) I checked and the origin for the repository is

ssh://gitlab.mycomp.com:10022/my-repo

While I provided only https://gitlab.mycomp.com when I authenticated. I don't know if that custom port or ssh of it all might be causing a problem, but I would hope not.

My other frustration is that I cannot figure out how to "unauthenticate" the extension or clear the data so I can continue testing the stability of the connection or alternate host/IP options. This is the same behavior I got when setting the URL and token via the GITLAB_WORKFLOW_... environmental variables at a point where I am confident the proxy configuration was incorrect and I was not actually connected. So that could still be the case, though my last authentication entry did not error - just went to this screen.