-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Crashes on Heroku, error code H10 #1589
Comments
Here is the build log.
|
Jumped on the machine (
|
From what I can tell, the desired module is in |
That's because the lib folder is not under version control and you're deploying a fork of the repo directly to heroku, which is not the preferred way to deploy parse-server. Heroku recommendes using parse-server-example. Please look at the recommended deployment in the documentation (README and wiki) |
Thanks a ton, deploying parse-server-example fixed it! |
Hey guys, im having a similar problem after deploying the parse-server ago. trying to login/ signup and I keep getting this 2016-04-23T21:20:33.968881+00:00 heroku[router]: at=info method=POST path="/parse/1/login" host=intense-hollows-60991.herokuapp.com request_id=5b792331-09c2-49b1-aa4c-48bd18f8f161 fwd="94.11.105.106" dyno=web.1 connect=1ms service=4ms status=403 bytes=466 |
That seems very different from the problem I was facing. Do you have the output from |
Yes from the heroku logs 2016-04-23T22:25:04.118548+00:00 heroku[router]: at=info method=POST path="/parse/1/users" host=intense-hollows-60991.herokuapp.com request_id=e546e91e-e45b-4e1d-a2c0-2bf7bd77ff1c fwd="94.11.105.106" dyno=web.1 connect=0ms service=8ms status=403 bytes=466 I can’t pinpoint any issues with the config as I have an android app that points to the same endpoints and that works
|
Have you double checked your API keys? A 403 seems to imply a permissions issue. What does the log look like for a successful transaction from your Android app? |
The request URL seems off with /parse/1, is that your mountPath? |
Parse.serverURL = 'https://intense-hollows-60991.herokuapp.com/parse/' https://intense-hollows-60991.herokuapp.com/parse/' I didn’t add that manually. I believe that come from Parse.User sdk.
|
I just checked the SDK and there don't seem to be any places where the SDK would add a trailing 1 to your server URL... If you run a query, does the path look the same? |
Hmm.. Please could you have a look @ this http://www.mobileparadigm.co.uk/urls/cft_access/services/cft/ http://www.mobileparadigm.co.uk/urls/cft_access/services/cft/ view source and click the ft_main.js you will find Parse.User.signUp(username, password, { ACL: new Parse.ACL() }, { I havne’t appended anything to the serverUrl
|
Seems that you're using an outdated version of parse.js, can you try with 1.6.14? I tried injecting the code into your app and still face an unauthorized error... |
and example is
|
I tried that version and I get TypeError: Parse.Collection is undefined..Looked @ the source code for both versions and everything to do with Parse Backbone is non existent in 1.6.14, even parse-lastest
|
THIS SOLUTION IS FOR GO When you deploy an app through heroku, it does not allow you to specify the port number.
What you can do is, getting the runtime port of heroku.
|
How you did this? Can you explain little bit. I am facing this problem also. |
@chowdhuryshakur that was 4 years ago, but looks like this guidance helped:
Not sure what the current deployment and docs look like. |
Just deployed to Heroku and I'm getting this crash error:
I was following the instructions here:
https://devcenter.heroku.com/articles/deploying-a-parse-server-to-heroku
After I forked the repo and connected to Heroku in the "Connect to Github" section, it crashed immediately.
Last commit from forked repo:
6e9529f81c081d5967aa0ba5126e25591cd528f2
Exposes the loggerAdapter as log to Cloud Functions and Triggers (#1565)
Any other information I can provide?
The text was updated successfully, but these errors were encountered: