Get Even More Visitors To Your Blog, Upgrade To A Business Listing >>

Heroku Error H14 (No web processes running)

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


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


heroku logs


Error H14 (No web processes running) -> GET 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 ?

Answer: (I put it here since my rep is too low to post answer yet)

Ok finally figured it out myself.

Apparently in the Procfile, I declared

main: node main.js

but Heroku uses

web: node main.js

I thought the naming can be anything you want but it is actually strict, you need to use web for it to work (heroku did not emphasize this - be wary) at least for now, until I figure out why this strictness and if I can change the name.

Problem courtesy of: John Lee


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: (the cached version:

Solution courtesy of: Neil Middleton


View additional discussion.

This post first appeared on Node.js Recipes, please read the originial post: here

Share the post

Heroku Error H14 (No web processes running)


Subscribe to Node.js Recipes

Get updates delivered right to your inbox!

Thank you for your subscription