Question regarding W&B server quick start

[ez2022]

hi folks, when I was trying to follow the instructions listed in this page (https://docs.wandb.ai/guides/self-hosted), I encountered an issue. I successfully finished step1 and step 2 under section “W&B server quick start”, however, when I was trying to do step3, it always asked me to create a new account and even I click the button “log in with another account”, it will directly forward me to the signup page again. So there is no chance for me to follow the instruction in step3.
Anyone encountered this issue before? Can you pls share how you fixed this issue ?

Thank you !

[mohammadbakir]

Hi @ez2022 ,

When attempting step 3, what is the link you are direct to initially? When attempting to login you are directed to a new link, what is this link?

[ez2022]

hi, thanks for your reply !
both the initial link and the redirect link are the same, which is http://localhost:8080/signup.
So basically no matter what I click it will forward me to http://localhost:8080/signup.
Any idea how to fix this issue ?

Thank you !

[ez2022]

hi Mohammad,

  I just checked the page again and found there is no new comment there since my last response.  Could you pls take a look?

Thanks

Edison

[ez2022]

hi, thanks for your reply !
both the initial link and the redirect link are the same, which is http://localhost:8080/signup.
So basically no matter what I click it will forward me to http://localhost:8080/signup.
Any idea how to fix this issue ?

Thank you !

[mohammadbakir]

Hi @ez2022 , signup using your existing wandb cloud credentials email/username. If you otherwise are continually prompted to login and don’t have one, perform the following:

• Stop and delete wandb docker container
• Uninstall wandb
• Delete ~/.netrc file (typically found in home directory) associated with your wandb API keys
• Reinstall wandb and go through the W&B Server Quickstart Steps again
• When prompted to signup, use your existing wandb email and username,

You should now be able to access your local instance. If not, please provide a screen recording of the steps you are taking for further review.

Thanks,
Mohammad

[ez2022]

hi Mohammad,

I tried the solution you provided, however it still doesn’t work, so I did the screen recording and sent to you via email, could you pls help take a look?

Thanks

[mohammadbakir]

Thank you @ez2022 , I requested access to the video via the link you provided. I will review immediately, thanks.

[mohammadbakir]

Thank you for the video @ez2022 . Perform the following which will prompt you to input a new password. You should now be able to login directly. Please let me know if this works.

docker exec -ti wandb-local bash
/usr/local/bin/local password <user_email@domain.com>

[ez2022]

hi Mohammad, With this solution, now I can log into the system successfully. Thanks for your kind help !

[ez2022]

Hi Mohammad,

So I just successfully logged into the system and generated a license key , however when I clicked the button "Add license" it always forwarded me to a "403" page and asked me to log in again and that log in button isn't working.  Could you help take a look ? Thank you !

Attached is a screenshot of the “403” page.

[mohammadbakir]

Hi @ez2022 , I’m glad to hear you you were able to login successfully. This 403 error isn’t directly associated with our wandb local version but rather a recent issue we had with our gmail authentication system that was fixed today. Please attempt to re login and let me know if this is still an issue.

Note: We released our newest version of local, 0.16.0 today with updated features. To update run wandb server start --upgrade.

[ez2022]

Thank you Mohammad for your instruction and kind help !

[ez2022]

Hi Mohammad, I just upgraded wandb and retried adding the license, however, I got the same page 403 issue.

Is there anything else I need to change ?

Thanks

[mohammadbakir]

Hi @ez2022 , we addressed an issue with our authentication server within past week. Are you still running into this?

[mohammadbakir]

Hi @ez2022 , since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!