I ran into the same error above, app was crashing on heroku (running fine in dev) but error logs on heroku were not revealing any clues. I read other answers on this page and broke out in a sweat after seeing "rebuilding the app." I figured maybe I could get in the heroku console and look around. I did and even the console crashed, but this time it told me why. It was some obscure variable I forgot to delete during a troubleshooting session hours earlier. I am not saying you will run into the same problem, but I found more info when I tried to go through the console. Hope this helps.
$ heroku run rails console
I was having the same issue. Logs weren't giving me any clues either. So I scaled down and scaled back up the dynos. This solved the problem for me:
heroku ps:scale web=0
Waited a few seconds...
heroku ps:scale web=1
$heroku run rails console
This is the best option since it will give you an error in your terminal which will be much more detailed than the 'app crashed' error in your Heroku logs.
$ heroku restart
helped me get my dyno running again. I'm new to Heroku but glad I know now.
this happened to me when I was listening on the wrong port
I changed my listen() to "process.env.PORT" so:
http.listen((process.env.PORT || 5000), function(){
console.log('listening on *:5000');
});
instead of
http.listen(5000, function(){
console.log('listening on *:5000');
});
Had same problem this evening. Not a very helpful error so I tried running in the console
heroku run rails c
it failed and gave me a much more helpful error. I had neglected to delete a method call in production. Once I fixed that, the app worked fine.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With