Dev server launch failing due to incorrect cloud account authentication

General
1

When trying to launch the dev server, it’s attempting to SSH into the wrong cloud account. Getting error: “The Workstation does not exist or your currently signed in account”

I have multiple accounts configured, but need it to use a specific account for launching the dev server. Looking for a way to specify which account to use without having to completely log out of all accounts.

Error details:
401: The Workstation does not exist or your currently signed in account

Has anyone encountered this issue or knows how to force it to use a specific account for dev server launches?

2

Edit: I meant wrong Google account with “cloud account”, sorry about the confusion

3

Hi, can I get some assistance on this please, as it’s quite frustrating, every time I need to start my dev server, I need to copy the ssh link to an incognito chrome tab as it’s trying to use another Google account by default

4

Are you creating a new project using IDX’s templates, or are you importing an existing project?

5

I’m importing an existing project from Github, when holding ctrl+clicking on the given localhost URL (dev server), it’s trying to launch a new tab using a different Google account from what I’m using to launch IDX.

image
image977×136 13.4 KB

6

Interesting. I wonder if this is something that @rody or @davideast have encountered and have some insights into.

7

Thank you for following up on this @kirupa

8

Hi @rody @davideast were you guys able to take a look into this?

9

Do you have a public example you can share for us to reproduce?

10

This currently happens when I’m logged into multiple Google accounts at once, you can mark an account other than what you’ve launched your IDX with as the default Google account, and then when you try to launch the dev server (any dev server) you won’t be able to access it due to the error above. Would love to help further if you’ve got more questions.

11

Will check with the dev team to see if there is a work around or fix for the issue!

12

Thank you @rody. I’ll have to always copy the “https://ssh.cloud.google.com/devshell/gateway/oauth?” link and paste it into an Incognito window to avoid it trying to use another Google account.

13

Are you perhaps able to get around this by adding a query parameter specifying the account you want to use? It wouldn’t be machine-agnostic, but it could fix it in the interim? Adding &authuser=0 to a cloud.google.com URL points to the local signed in user account that is 1st in the list, and &authuser=1 is the 2nd, etc., etc.

No idea if that works for an oauth link though. :sweat_smile:

1 Like
14

I also had the same issue when signed in to multiple accounts.

15

I had a couple additional thoughts:

Have you considered running IDX in a separate Chrome user profile, or even an entirely separate instance of Chrome, with only the needed account signed into it? (See: Google Chrome Portable (web browser) | PortableApps.com for an option to have an IDX-dedicated Chrome.)

16

Hi, thanks for the advice, this indeed works. But it would be great to have a permanent way of fixing this.

1 Like
17

When it comes to this, logging out of my other accounts or profiles is not an option for me.

1 Like
18

Right, it should be handled better by GCP or IDX or both, but I was hoping it would keep you moving for now! :+1::sparkles:

As for the 2nd message:
I’m saying you could have one window open with accounts 1 2 and 3 signed in, and then a dedicated IDX user profile that is only signed into account 2.