CODEWITHSUNDEEP
node.jsherokunpm
John Lee
John Lee

Reputation: 1251

Heroku Error H14 (No web processes running)

Pretty sure some people encountered this problem before.

Followed all the instructions to setup node and npm. When pushing to heroku there were no errors. But when I open the app, it shows "Application Error"

heroku ps

returns

Process  State      Command       
-------  ---------  ------------  
main.1   up for 1m  node main.js

while

heroku logs

returns

Error H14 (No web processes running) -> GET mewtwo.herokuapp.com/ dyno= queue= wait= service= status=503 bytes=

I tried restarting the app with heroku restart but still get the same error. Google around and there were no other solution other than heroku restart. Anyone tried other methods ?

Upvotes: 36

Views: 23994

Answers (4)

Tristan Newman
Tristan Newman

Reputation: 426

Full disclosure, I solved this problem by turning it on.

Heroku Application Overview tab > click Configure Dyno > click the pencil icon > click toggle switch to On position > click confirm

Upvotes: 3

sudip modi
sudip modi

Reputation: 11

I guess my problem was this, i had a python script in my node application which led heroku to believe that it is a python app, also i did not add a procfile since i expected the build bots to automatically detect that its a node app, so after setting up the procfile , then specifying the node and npm versions inside engines key in package.json, and changing the buildpack type to heroku/node, i got my app running.

Upvotes: 0

Neil Middleton
Neil Middleton

Reputation: 22240

The name of your web process must be web, and this is the process that Heroku will always scale to '1' on initial deploy.

Other services in the Procfile can be called what you want, but you need to scale them initially (so you can have dev only processes in there if you want).

More information here: http://neilmiddleton.com/the-procfile-is-your-friend/ (the cached version: https://web.archive.org/web/20130926005616/http://www.neilmiddleton.com/the-procfile-is-your-friend)

Upvotes: 17

Jeff Dickey
Jeff Dickey

Reputation: 5034

I had the same problem, but for me it was because I needed to run heroku ps:scale web=1

Upvotes: 83

Related Questions