Private Instance Authentication issue with VSCode

I seem to have an issue that I can’t find any published reference to online. When I launch VSCode I see a error

Connection to https://sourcegraph.[our private instance] failed.
Please check your access token and network connection."

With buttons to “Get Token” and “Reload Window”. Clicking on get token opens a link to https://sourcegraph.[our private instance]/users/[my username]/settings with an input to override global and organization settings. There are no overrides defined. Switching to Access Tokens shows a valid token that I generated for VSCode. I’ve tested this token using cURL and it works, however back in VSCode the Access Token in the extension settings is readonly and appears to be pre-populated (the instance URL is editable and set to the correct value). Clicking on “Authenticate account” returns a 401 error (as seen in the extension Runtime Status in the extension manager). According to the changelog in version 2.2.17 the auth was “fixed” to not require editing settings.json but now I find myself in a state where I can’t provide an updated Auth token. Is this a thing that is managed by our private instance?

Hey @jasonsperske

Thank you for reporting this issue.
Please forward this issue over your Enterprise support channel or via support@sourcegraph.com.

Sorry for the inconvenience.

1 Like