search

aws-amplify / amplify-studio

AWS Amplify Studio (Formerly Admin UI)
136 stars 31 forks source link

There were issues with logging in. If this is a new app, please try again after a few minutes. #698

Closed RoyalBosS-Ayush closed 1 year ago

RoyalBosS-Ayush commented 2 years ago

"amplify pull" open a webpage on browser. After signing in with aws account, page says "There were issues with logging in. If this is a new app, please try again after a few minutes."

vakalens commented 2 years ago

Hi, Could you provide appId and region at least as required information to check the logs, please?

RoyalBosS-Ayush commented 2 years ago

https://ap-south-1.admin.amplifyapp.com/admin/d1se69oqpdg4a6/staging/verify/?loginVersion=1

Region : ap-south-1 (Mumbai) App id : d1se69oqpdg4a6

vakalens commented 2 years ago

From logs looks like you were able to successfully delete all backends. After it's done there's no login mechanism to login from Amplify CLI to pull an application. App should be there to be successfully pulled from Amplify CLI. At this point it's not clear what exactly you're trying to do and maybe you accidentally forgot to create an app either by Amplify Studio or by pushing from Amplify CLI.

subhakundu commented 2 years ago

We are having similar issue for last two days. Our App ID is dutt92ta87d84. Our backend is working fine, but we are not being able to amplify pull or launch amplify studio.

Can someone please guide us?

avidityindia commented 2 years ago

Getting the same issue since tomorrow "There were issues with logging in. If this is a new app, please try again after a few minutes." Your app ID is d3djz3h3momk7w

amplify cli working fine! App also!

avidityindia commented 2 years ago

Looks like in my case User pool ap-south-1_GL2sR5zmX does not exist Its because the user pool that supports amplify login is being deleted!

Please check you user pools!

JianXinGao commented 1 year ago

I have the same issue.

  1. When I launch amplify studio, "There were issues with logging in. If this is a new app, please try again after a few minutes." is shown.
  2. When I try to turn off amplify studio, "ResourceNotFoundException - An error occurred while processing your request: User pool us-west-2_1C7VE7PFq does not exist." is shown.
  3. I delete and recreate the backend off the app, but amplify studio still can't be launched.
  4. I did deleted the user pool us-west-2_1C7VE7PFq from Amazon Cognito manually, what should I do to launch amplify studio again?
vakalens commented 1 year ago

@JianXinGao could you try disabling/then enabling Amplify Studio from AWS console? It should reset your authentication system. Please let us know if this helped you.

JianXinGao commented 1 year ago

I cannot disable Amplify Studio from AWS console, "ResourceNotFoundException - An error occurred while processing your request: User pool us-west-2_1C7VE7PFq does not exist." error message is shown.

------------------ 原始邮件 ------------------ 发件人: "aws-amplify/amplify-adminui" @.>; 发送时间: 2022年11月22日(星期二) 凌晨1:50 @.>; @.**@.>; 主题: Re: [aws-amplify/amplify-adminui] There were issues with logging in. If this is a new app, please try again after a few minutes. (Issue #698)

@JianXinGao could you try disabling/then enabling Amplify Studio from AWS console? It should reset your authentication system. Please let us know if this helped you.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

marx-daniel commented 1 year ago

I am experiencing the same issue or a similar issue as @JianXinGao. I cannot launch amplify studio for either of my project's back-ends, I can't disable studio, I can't see or add users in Access control settings. I'm not sure if they have this same problem, but when I try to clone the project to my local machine, it redirects me to amplify studio in the console and I cannot verify and pull the project for these reasons. My IAM has administrator access.

ykethan commented 1 year ago

Hey @marx-daniel, a fix has been rolled out and you should be able to disable studio now. Could you try disabling and re-enabling studio?

sbkomurcu commented 1 year ago

I confirm that disabling/then enabling Amplify Studio has resolved the same issue for me.

ykethan commented 1 year ago

Thank you for the confirmation. Please feel free in reaching out to us, if the issue reoccurs by creating a new issue and linking this issue. closing the issue.

marx-daniel commented 1 year ago

@ykethan I found that the reason I was unable to disable and re-enable studio was due to an issue with the user pool it was trying to access - it was deleted through incorrect configuration, so studio could not access the non-existent pool to load users, and could not turn off studio by deleting the pool.

ykethan commented 1 year ago

hey @marx-daniel, interesting. Could you let us know, how the user pool was deleted? was this via CLI or Studio? Could also provide us some additional information on the incorrect configuration as this would help us in documenting this behaviour.

marx-daniel commented 1 year ago

@ykethan I believe it was because in index.js hardcoded values for Auth were added in Amplify.configure (identityPoolId, region, userPoolId, userPoolWebClientId) instead of using AWS exports. I'm not 100% on this because the error and solution were from other people on my team but I think this is what caused the issue. It could have also been caused through the CLI, I don't think it was through Studio.

ykethan commented 1 year ago

thank you for the information @marx-daniel

Breyner-Parada commented 1 year ago

Same here as @sbkomurcu I confim that disabling and then enabling the AWS Stduio worked for me, I had many users pool and I deleted many of them maybe those actions changed something in the configuration but just disable and enable the AWS Studio solved the issue

MatijaOsojnik commented 1 year ago

Same issue here but I tried following @Breyner-Parada solution to disable and then enable AWS Studio but I'm getting this response when trying to do that:

An error occurred while processing your request: An AWS error occurred

madmaxaus commented 1 year ago

Hi,

I was experiencing the same issues. I couldn't authenticate via the CLI or login to studio using the console. I tried disabling studio and enabling it, but now i get the message:

"Failed to enable Amplify Studio for app d302ydnwml0o2j: The user does not have permissions to create triggers" and i can't enable studio. I am logged in as root user.

any ideas?

thanks,

Max

johnpc commented 1 year ago

Hi @madmaxaus - I took a look at the logs associated with the failure you experienced. We're encountering 403 errors from lamdba.createFunction.

Are you able to run aws lambda create-function using the aws cli while authenticated as the same user/role? There could be something unexpected in your IAM configuration.

hani-q commented 1 year ago

Same here. In my case i deleted an app and strarted form scratch with a new one. Get the same same error The user does not have permissions to create triggers.

aws lambda --profile haniq-main create-function --function-name my-function --zip-file fileb://function.zip --handler index.handler --runtime nodejs18.x --role arn:aws:iam::640766513655:role/lambda-ex

An error occurred (AccessDeniedException) when calling the CreateFunction operation: None

madmaxaus commented 1 year ago

Hi @madmaxaus - I took a look at the logs associated with the failure you experienced. We're encountering 403 errors from lamdba.createFunction.

Are you able to run aws lambda create-function using the aws cli while authenticated as the same user/role? There could be something unexpected in your IAM configuration.

There is something strange going on. When i log in as root user i can't see any lambdas and I also can't fire up a cloudshell instance to run the command you suggested. I'm not even sure where to begin with this.

Max

johnpc commented 1 year ago

It sounds like something is going on with lambda permissions either in your accounts or on your IAM roles. Do you have any special IAM / permissions configuration? Are you using AWS Organizations? What do you see when you run aws sts get-caller-identity?

Since this is not directly related to Amplify Studio, I can't help much with these questions unfortunately. I'd recommend opening up a support case mentioning your inability to use AWS Lambda using the AWS Support console (https://support.console.aws.amazon.com/support/home)

hani-q commented 1 year ago

Same here. In my case i deleted an app and strarted form scratch with a new one. Get the same same error The user does not have permissions to create triggers.

aws lambda --profile haniq-main create-function --function-name my-function --zip-file fileb://function.zip --handler index.handler --runtime nodejs18.x --role arn:aws:iam::640766513655:role/lambda-ex

An error occurred (AccessDeniedException) when calling the CreateFunction operation: None

NVM.. My account was restricted :|

madmaxaus commented 1 year ago

Same here. In my case i deleted an app and strarted form scratch with a new one. Get the same same error The user does not have permissions to create triggers. aws lambda --profile haniq-main create-function --function-name my-function --zip-file fileb://function.zip --handler index.handler --runtime nodejs18.x --role arn:aws:iam::640766513655:role/lambda-ex An error occurred (AccessDeniedException) when calling the CreateFunction operation: None

NVM.. My account was restricted :|

Yes, someone logged in from a different location and our account was also restricted.

hani-q commented 1 year ago

Same here. In my case i deleted an app and strarted form scratch with a new one. Get the same same error The user does not have permissions to create triggers. aws lambda --profile haniq-main create-function --function-name my-function --zip-file fileb://function.zip --handler index.handler --runtime nodejs18.x --role arn:aws:iam::640766513655:role/lambda-ex An error occurred (AccessDeniedException) when calling the CreateFunction operation: None

NVM.. My account was restricted :|

Yes, someone logged in from a different location and our account was also restricted.

Well in my case i am just a one man company. AWS support not telling me, but i think it happened because i may have had a VPN on while accessing console once. But still not sure if its a good idea to restrict the account just because of this. But ig this rant for another forum/thread :)

ykethan commented 1 year ago

hey @hani-q, just curious how were able to identify that you account has been restricted? Are you seeing an messages on you account or email. If yes, could you paste the messaging you are experiencing?

christopherdunn commented 6 months ago

I've run into essentially the same issue. My root account no longer can get into one of my amplify apps but I was able to add a full access user under studio settings in the amplify console and can log in with no issue under that user. Why would my root account suddenly run into an issue?