aws / aws-toolkit-vscode

Amazon Q, CodeCatalyst, Local Lambda debug, SAM/CFN syntax, ECS Terminal, AWS resources
https://marketplace.visualstudio.com/items?itemName=AmazonWebServices.amazon-q-vscode
Apache License 2.0
1.47k stars 408 forks source link

Cannot login to Amazon Q from WSL #5317

Closed SathyaBhat closed 2 months ago

SathyaBhat commented 2 months ago

Problem

Steps to reproduce the issue

  1. From the Q Panel click on Login with Builder ID
  2. Complete auth

Expected behavior

  1. Can use Amazon Q

System details (run AWS: About and/or Amazon Q: About)

OS: Linux x64 5.15.153.1-microsoft-standard-WSL2
Visual Studio Code extension host:  1.91.1
Amazon Q:  1.14.0
node: 20.11.1

Logs

024-07-13 17:57:17.405 [debug] called startBuilderIdSetup()
2024-07-13 17:57:17.405 [info] selected AWS ID sign in
2024-07-13 17:57:17.405 [info] auth: Updating connection state of b7b9f059-d917-4f26-a1f2-82ab585213d7 to authenticating
2024-07-13 17:57:17.405 [info] codewhisperer: connection changed to authenticating: b7b9f059-d917-4f26-a1f2-82ab585213d7
2024-07-13 17:57:17.410 [debug] SSO token cache: read failed (file not found) key: b7b9f059-d917-4f26-a1f2-82ab585213d7
2024-07-13 17:57:17.410 [info] current client registration id=undefined
    expires at undefined
    key = b7b9f059-d917-4f26-a1f2-82ab585213d7
2024-07-13 17:57:17.420 [debug] auth: SSO registration cache: loaded key: {"startUrl":"https://view.awsapps.com/start","region":"us-east-1","scopes":["codewhisperer:completions","codewhisperer:analysis","codewhisperer:conversations","codewhisperer:transformations","codewhisperer:taskassist"]}
2024-07-13 17:57:17.475 [debug] auth: SSO registration cache: loaded key: {"startUrl":"https://view.awsapps.com/start","region":"us-east-1","scopes":["codewhisperer:completions","codewhisperer:analysis","codewhisperer:conversations","codewhisperer:transformations","codewhisperer:taskassist"]}
2024-07-13 17:57:17.475 [debug] AuthSSOServer: Initialized new auth server.
2024-07-13 17:57:24.019 [debug] API request (oidc.us-east-1.amazonaws.com /token): {
  clientId: '-THzwEfiztiygKWSoX44zHVzLWVhc3QtMQ',
  clientSecret: '[omitted]',
  grantType: 'authorization_code',
  redirectUri: 'http://127.0.0.1:34787/oauth/callback',
  codeVerifier: 'UYV11xxx',
  code: 'eyJraWQiOxxx'
}
2024-07-13 17:57:24.519 [error] Unable to find /home/sathya/.vscode-server/extensions/amazonwebservices.amazon-q-vscode-1.14.0/dist/src/auth/sso/vue/favicon.ico
2024-07-13 17:57:29.024 [error] API response (oidc.us-east-1.amazonaws.com /token): { name: 'TimeoutError' }
2024-07-13 17:57:29.186 [debug] API request (oidc.us-east-1.amazonaws.com /token): {
  clientId: '-THzwEfiztiygKWSoX44zHVzLWVhc3QtMQ',
  clientSecret: '[omitted]',
  grantType: 'authorization_code',
  redirectUri: 'http://127.0.0.1:34787/oauth/callback',
  codeVerifier: 'UYV11xxx',
  code: 'eyJraWQiOxxx'
}
2024-07-13 17:57:34.191 [error] API response (oidc.us-east-1.amazonaws.com /token): { name: 'TimeoutError' }
2024-07-13 17:57:34.537 [debug] API request (oidc.us-east-1.amazonaws.com /token): {
  clientId: '-THzwEfiztiygKWSoX44zHVzLWVhc3QtMQ',
  clientSecret: '[omitted]',
  grantType: 'authorization_code',
  redirectUri: 'http://127.0.0.1:34787/oauth/callback',
  codeVerifier: 'UYV11xxx',
  code: 'eyJraWQiOxxx'
}
2024-07-13 17:57:39.540 [error] API response (oidc.us-east-1.amazonaws.com /token): { name: 'TimeoutError' }
2024-07-13 17:57:39.545 [error] webviewId="aws.amazonq.AmazonCommonAuth": Error: Webview error
     -> Error: Webview backend command failed: "startCodeWhispererBuilderIdSetup()"
     -> Error: Failed to connect to AWS Builder ID [FailedToConnect]
     -> TimeoutError: Connection timed out after 30000 ms
2024-07-13 17:57:39.632 [debug] Webview called command "errorNotification" with args: [ { id: 'defaultFailure', text: 'Failed to setup.' } ]
2024-07-13 17:57:39.632 [debug] Webview called command "emitUiClick" with args: [ 'auth_continueButton' ]
2024-07-13 17:57:44.540 [debug] AuthSSOServer: Attempting to close server.
2024-07-13 17:57:44.540 [debug] AuthSSOServer: Server closed successfully.
SathyaBhat commented 2 months ago

turns out my wsl was timing out on all outgoing network connections. Restart of windows fixed it!