Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to select instance - Server Error 500 #248

Closed
rpetit3 opened this issue Feb 1, 2021 · 7 comments
Closed

Unable to select instance - Server Error 500 #248

rpetit3 opened this issue Feb 1, 2021 · 7 comments

Comments

@rpetit3
Copy link

rpetit3 commented Feb 1, 2021

Hello!

When trying to select an instance type, I'm getting a 500 error code. I am unable to select an instance to launch Galaxy.

I've attached a screenshot.

cloudlaunch
cloudlaunch2

Here's console log in Chrome incase something sticks out
console

Please let me know if there's any info I can provide to help out

@nuwang
Copy link
Member

nuwang commented Feb 15, 2021

@rpetit3 Has this been resolved? Can you let us know which cloud this is on. Also can you try reentering and revalidating your credentials?

@rpetit3
Copy link
Author

rpetit3 commented Feb 16, 2021

Hi @nuwang

After reentering my credentials I am getting the same errors as my previous issue #242 again.

Error: The credentials you have entered could not be validated.

ERROR Details: Authentication with cloud provider failed: CloudBridgeBaseException: An error occurred (AuthFailure) when calling the DescribeKeyPairs operation: AWS was not able to validate the provided access credentials from exception type: <class 'botocore.exceptions.ClientError'>

I've tried entering credentials as aws and aws-us

@almahmoud
Copy link
Member

If you can possibly find out like before, is it still hitting ap-northeast-1 or is this another issue?

@nuwang
Copy link
Member

nuwang commented Feb 17, 2021

The ap-northeast-1 issue should be resolvable since @almahmoud added this cloud option:
image

Perhaps your credentials are invalid? Can you check with boto perhaps?

@nuwang
Copy link
Member

nuwang commented Feb 17, 2021

Just in case, can you also try deleting all existing credentials from cloudlaunch, and entering afresh? You can view your credentials in the top right hand corner under your username -> My Credentials.

@rpetit3
Copy link
Author

rpetit3 commented Feb 17, 2021

I'm following up with IT to see if they are getting the requests.

Haha I would love to try with Boto, but in addition to being region locked the credentials are also IP locked to 149.165.157.211 which I got from dig launch.usegalaxy.org

I'll update soon

@rpetit3
Copy link
Author

rpetit3 commented Feb 17, 2021

Good news, it's us. The credentials I was given were deleted by an automated process.

Going to close this. Thanks for the help.

@rpetit3 rpetit3 closed this as completed Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants