I can't login form vs code plugin on wsl2

Cody VS Code
1

Hello Sourcegraph community,

I’m encountering a persistent issue with Cody Pro in my development environment. Here are the details:

  1. I’ve subscribed to the Cody Pro offer.
  2. I’m trying to connect to Cody from within WSL2 (Windows Subsystem for Linux 2).
  3. I’ve attempted to use the “Switch Account” option with token.
  4. The connection fails.

I’ve already verified my WSL2 setup and VS Code installation. I’ve also checked my proxy and firewall settings to ensure they’re not interfering with the connection.

Could someone please provide guidance on how to troubleshoot this connection issue specific to the WSL2 environment? Are there any known compatibility issues or additional steps required for Cody to work properly in WSL2?

error;

CodyCompletionProvider:notSignedIn: You are not signed in.

█ GraphQLTelemetryExporter: Error exporting telemetry events: Error: ETIMEDOUT: Request timed out after 6000ms (https://sourcegraph.com/.api/graphql?RecordTelemetryEvents)

█ CodyLLMConfiguration: {}

█ ModelsService: Setting primary models:

█ telemetry-v2: recordEvent: cody.auth/failed

█ AuthProvider:signinMenu: signin http://sourcegraph.com/

█ ContextFiltersProvider: fetchContextFilters

█ GraphQLTelemetryExporter: telemetry: failed to evaluate server version: Error: ETIMEDOUT: Request timed out after 6000ms (https://sourcegraph.com/.api/graphql?SiteProductVersion)

2

Hey @vince.dev_81

is this a new issue or since a specified update?

I’m using WSL2 too and since the preview release 6 days ago, there is such an issue with login.

I solved it with closing all Cody chat windows and reloading vs code.
After the reload, there is this “Sign in” button in the Statusbar. After waiting some seconds it logged in automatically.

If all that does not help, then please re-install Cody.

3

There’s another similar report at bug: I am being repeatedly logged out. · Issue #5783 · sourcegraph/cody · GitHub.

Sorry about this issue.

I see your logs also have some ETIMEDOUT: Request timed out after 6000ms errors. I don’t know why it would have recently started being an issue, but are you on a high-latency network connection? Or a choppy connection? Regardless, we need to make it work, but that info would help us diagnose the issue.

4

Also, are you using a proxy?

5

@vince.dev_81 Can you try upgrading to v1.36.3 and see if you are still facing this?

Thank you!!

1 Like