Cannot login and create account due to "Something went wrong" error about studio-lab-examples HOT 28 CLOSED

After our survey, we found that 61.5% of users face this problem and "trying to log in or create a new account several times (around 5 times)" is a temporary solution, and that 87.5% of users can log in or create a new account after several trials. Of course, we are working to solve the root cause of the issue, and we will report back to the community once the problem is fully resolved.

Thank you to @CALEB789 for showing the community the solution faster than we did! We understand that the CORS errors are related to this problem. Please wait a little while until we have a complete solution.

from studio-lab-examples.

Holy it's been fixed! Thank you!
Now I just need to monitor just in case something goes wrong again...

from studio-lab-examples.

it is caused by the cors origin policy in chrome to disable it for a short time you need to run this Open Start window Search Run and open it or press Window+ R Paste chrome.exe --user-data-dir="C://Chrome dev session" --disable-web-security and execute it This will open a new browser with web security disabled. You can now access your project in this browser without worrying about the CORS errors. but it is a problem with aws sageMaker Studio Lab

tested this and it works, but it is pretty annoying how it's hasn't been fixed yet

from studio-lab-examples.

This issue should be resolved. please let me know if anyone is still hitting it else we will close.

from studio-lab-examples.

This has happened so randomly, and yet it gets fixed if you wait for a few minutes
only problem, it wastes your runtime equals to the amount of minutes you wait which is really annoying

does anyone know this is a server issue?

from studio-lab-examples.

Thanks for the comments. I honestly do not know how to reproduce with the info given but please keep in mind that the user name is case sensitive.
Vendetta-S - I am not sure how this would waste your runtime. You need to log in before you start a runtime. can you please explain further?

from studio-lab-examples.

it's fixed for me now. After a week, I restarted my router and somehow I can log in again.

from studio-lab-examples.

Vendetta-S - I am not sure how this would waste your runtime. You need to log in before you start a runtime. can you please explain further?

Essentially, when running a runtime there is this error on the site that says the same thing as the one here, and I can't really leave it alone as it'll close my connection to the server
as soon as I refresh the page, I couldn't login and even when I try to delete the cookies it still didn't work, and waiting actually wasted the runtime

from studio-lab-examples.

it is caused by the cors origin policy in chrome

to disable it for a short time you need to run this
Open Start window
Search Run and open it or press Window+ R
Paste chrome.exe --user-data-dir="C://Chrome dev session" --disable-web-security and execute it
This will open a new browser with web security disabled.
You can now access your project in this browser without worrying about the CORS errors.
but it is a problem with aws sageMaker Studio Lab

from studio-lab-examples.

Thanks Vendetta-S for this information. We will look into this.

from studio-lab-examples.

Update, just realized, I can never login the same without using the fix that Caleb suggested, as it kept staying like the above issue's screenshot. I am using chrome so it won't probably matter but most people use them.

from studio-lab-examples.

I confirmed this error occurs not only Chrome but also Edge of the other browsers. Let us investigate to deliver the solution quickly.

from studio-lab-examples.

from studio-lab-examples.

from studio-lab-examples.

We continue to find out root cause of this issue and taking action rapidly. We will announce the progress in this issue.

from studio-lab-examples.

Oh and to anyone wanting to just not needing to run the program all over, you'll have to create a new profile in the settings, without email, just the name. Then going to chrome://settings/manageProfile, and activate create shortcut on desktop. Then, all you need to do is exit, locate it and click properties, "Target" field is where you need to remove and copy paste this: "C:\Program Files\Google\Chrome\Application\chrome.exe" --profile-directory="Profile 4" --user-data-dir="C://Chrome dev session" --disable-web-security"

from studio-lab-examples.

The profile being your own profile, for instance Profile 2 or 4 etc

from studio-lab-examples.

We have deployed a solution. We expect all users to be able to log in or create new accounts without any issues. If you encounter any problems, please don't hesitate to reach out to us!

from studio-lab-examples.

@icoxfog417 I got approval of signing up but facing same issue from many days

from studio-lab-examples.

@ahmadfalcon, you are still getting the same error? "Something went wrong. Please try again later"?
What happens if you try again?

from studio-lab-examples.

it is caused by the cors origin policy in chrome to disable it for a short time you need to run this Open Start window Search Run and open it or press Window+ R Paste chrome.exe --user-data-dir="C://Chrome dev session" --disable-web-security and execute it This will open a new browser with web security disabled. You can now access your project in this browser without worrying about the CORS errors. but it is a problem with aws sageMaker Studio Lab

But after trying this solution it says my email is not allowed, i even tried with 3 different email and the results still the same

from studio-lab-examples.

We have deployed a solution. We expect all users to be able to log in or create new accounts without any issues. If you encounter any problems, please don't hesitate to reach out to us!

umm i think i got the same problem, when i try to signing in it gives me endless captchas then when i try to request a new account, the same "something went wrong" error got me.

from studio-lab-examples.

it is caused by the cors origin policy in chrome to disable it for a short time you need to run this Open Start window Search Run and open it or press Window+ R Paste chrome.exe --user-data-dir="C://Chrome dev session" --disable-web-security and execute it This will open a new browser with web security disabled. You can now access your project in this browser without worrying about the CORS errors. but it is a problem with aws sageMaker Studio Lab

But after trying this solution it says my email is not allowed, i even tried with 3 different email and the results still the same

Hello. I think Personal Email Address are not allowed.

You have to use a business email address for example [email protected]

from studio-lab-examples.

Thanks for the reply, but unfortunately i tried my two organization email and both of them ended up the same

from studio-lab-examples.

So can you try to press CRTL + SHIFT + I TO OPEN THE DEV TOOLS. AND THEN YOU GO TO THE CONSOLE TAB. AND THEN POST A SCREEN SHOT HERE

from studio-lab-examples.

-The disabled security version

-The normal version

from studio-lab-examples.

So it is not a problem with the cors origin policy.

The contributers will look at it. It appears it is some internal thing

from studio-lab-examples.

alright then thanks, ill wait

from studio-lab-examples.