-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Parse on AWS 503 error when calling from Auth0 and ok from local #3131
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
Comments
Thanks for your question! We want to make sure to keep signal strong in the GitHub issue tracker – to make sure that it remains the best place to track issues that affect the development of Parse Server. Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #parse.com? We'll be happy to answer there. Post a link to your Stack Overflow question here, so that we don't lose track of it. You may also use Server Fault for questions about managing your own servers. |
This must be a parse issue. multiple gets are also failing the same way if done one after another. Second get and only 2nd get in the code below returns service unavailable. `request.get({ // Not found. Likely the user doesn’t exist, we provision one |
Regarding auth0 you should probably ask the author of the post on medium instead of here. |
No response, but the issue seems to be with parse. Its a simple attempt to login and then attempt to create if login fails? Seems like second attempt is refused. Doing 2 gets one after another, 2nd fails. Apache reports error: [pid 1150] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:1337 (127.0.0.1) failed |
The issue seems to be that your server gets killed. So provide the logs please, as described in the issue template |
HI,
I am trying to implement Auth0 integration described here. Login attempt returns 404 which is fine but POST I get
54.67.15.170 - - [28/Nov/2016:14:26:54 +0000] "GET /parse/login?username=auth0%7C0123456789&password=XXXXXX HTTP/1.1" 404 49
54.67.15.170 - - [28/Nov/2016:14:26:55 +0000] "POST /parse/users/ HTTP/1.1" 503 299
Creating user from local:
curl -X POST -H "X-Parse-Application-Id: appid" -H "X-Parse-REST-API-Key:mk" -H "Content-Type: application/json" -d '{"username":"Sean Plott","password":"aaaaaaa"}' https://tablebuds.com/parse/users
{"objectId":"2H32s7C45c","createdAt":"2016-11-28T14:29:50.515Z","sessionToken":"r:dfdasfdafd"}
works fine.
Can anyone suggest what I should look at?
The text was updated successfully, but these errors were encountered: