NodeBB not working on heroku but works on local machine #2544
Comments
|
It's happening the same thing here. |
|
Post the config file that is not working. |
|
nevermind... And it's working fine now. 👍 |
|
as a suggestion update the tutorial |
|
@wladiston Running NodeBB directly (via If v0.6.0 is broken on Heroku because of a configuration change since v0.5.7, we'll have to look into the reason for it. @barisusakli It may be related to Heroku sending in the port via |
|
Adding |
|
I am still using v0.5.7 and not v0.6.0 014-12-29T12:16:13.566237+00:00 heroku[web.1]: State changed from crashed to starting I even added mongoose as a dependency but still get the error on the server where as my local machine seems to be working fine. Any clue on this? |
|
Try adding mongodb and connect-mongo to package.json and running npm install? |
|
I did try that and well that error was gone thank you @barisusakli. But now I am getting the error from earlier again: 2014-12-30T13:51:46.690150+00:00 heroku[web.1]: Starting process with command don't what is going wrong...I've been trying to make this run for 5 days now and haven't been able to do it even after following the tutorial properly |
|
Please show us the output of the heroku log
|
|
That's the output of heroku logs |
|
No, this is the execution log from heroku. I need the log from NodeBB Heroku details how to get this log, I don't remember at the moment.
|
|
Sorry about that I guess this is the one that you are asking. 2014-12-30T20:32:39.774515+00:00 app[web.1]: 2014-12-30T20:32:39.770Z - info: NodeBB v0.5.7 Copyright (C) 2013-2014 NodeBB Inc. |
|
@julianlam Any clue what the problem might be? I need to get this up and running as soon as possible. Thank you |
|
Well I tested with openshift, just to see what is happening and it works perfectly without having to think twice. |
I don't think the URL should be shown here. Please post your config as @barisusakli suggested. |
|
{ |
|
Remove |
|
@julianlam That works like a charm! thanks a lot. It would be nice if you could add this particular point in the tutorial itself. Thanks a lot again! |
|
I've the same issue as above, but I don't have the // config.json
{
"url": "https://[HIDDEN].herokuapp.com",
"secret": "[HIDDEN]",
"database": "redis",
"redis": {
"host": "[HIDDEN].redistogo.com",
"port": "[HIDDEN]",
"password": "[HIDDEN]",
"database": "0"
}
}It works with the Profile set to Branch v0.6.x, Mac OS |
|
@harianus I had the same issue with v0.6.1 and was able to get this running by making a simple change to the loader.js file. I changed the getPorts routine to first check for heroku's PORT env variable. line 185 (should be in the getPorts())
to
|
|
I fixed it by doing the following:
|
|
Hmmm... yes it looks like |
|
Heroku doesn't work on |
|
Out of curiosity, what happens when you have the ? |
|
Make change according @Lwdthe1 , but still get error like this |
|
run |
|
Yeah, I never ran into the lookup error @stillli is facing, but I ran into another issue before I ran |
|
@julianlam It just breaks Heroku because it can' find necessary files that loader.js needs because of file path issues. |
|
@julianlam, I am running nodebb under dokku (which is similar to heroku) and Regarding your request "Out of curiosity, what happens when you have the Procfile contents as: |
|
Interesting I think I might have to move my part to another issue, as this is dealing with dokku not heroku |
Ji everyone. Now I have this problem.(( |
Hi,
I've been trying to follow the process of installing NodeBB on Heroku, and I have been able to successfully run it in my local machine(Ubuntu 14.04). But, it seems like on the heroku server I am getting errors... Following is my output of "heroku logs"
2014-12-22T14:28:38.968514+00:00 heroku[web.1]: Starting process with command
node loader.js --no-daemon2014-12-22T14:29:39.355080+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2014-12-22T14:29:39.355331+00:00 heroku[web.1]: Stopping process with SIGKILL
2014-12-22T14:29:40.152569+00:00 heroku[web.1]: Process exited with status 137
2014-12-22T14:29:40.168501+00:00 heroku[web.1]: State changed from starting to crashed
2014-12-22T14:29:40.169139+00:00 heroku[web.1]: State changed from crashed to starting
2014-12-22T14:29:42.978814+00:00 heroku[web.1]: Starting process with command
node loader.js --no-daemon2014-12-22T14:30:43.197962+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2014-12-22T14:30:43.198156+00:00 heroku[web.1]: Stopping process with SIGKILL
2014-12-22T14:30:43.949869+00:00 heroku[web.1]: Process exited with status 137
2014-12-22T14:30:43.964372+00:00 heroku[web.1]: State changed from starting to crashed
Could you please help me with the problem.
Thank you
The text was updated successfully, but these errors were encountered: