No web process type after doing heroku push

[schmich]

Thanks for this very cool project. Unfortunately, it does not appear to be working for me. I've tried pushing a vanilla Rails project as well as a simple Sinatra project to my Cedar-based Heroku app.

I run heroku push --app qcp and everything appears to work normally:

Checking for app files to sync... done, 0 files needed
Launching build process... done
Preparing app for compilation... done
Fetching buildpack... done
Detecting buildpack... done, Buildkit
Fetching cache... done
Compiling app...
Writing .profile.d/buildpack.sh... done
Putting cache... done
Creating slug... done
Uploading slug... done
Success, slug is https://api.anvilworks.org/slugs/756ec5cc-b97e-43ec-ad9d-ee8b7c76e251.tgz
Releasing to qcp... ..done, v17

However, navigating to my app (http://qcp.herokuapp.com/), I get Heroku's Application Error page. Looking through the logs, I see:

2013-02-18T12:34:05+00:00 heroku[api]: Release v17 created by xxxxxx@gmail.com
2013-02-18T12:34:05+00:00 heroku[api]: Pushed by xxxxxx@gmail.com by xxxxxx@gmail.com
2013-02-18T12:34:22+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path=/ host=qcp.herokuapp.com fwd="71.227.249.252" dyno= queue= wait= connect= service= status=503 bytes=
2013-02-18T12:34:22+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path=/favicon.ico host=qcp.herokuapp.com fwd="71.227.249.252" dyno= queue= wait= connect= service= status=503 bytes=

To corroborate this, when I look at the Heroku dashboard, I see no web dyno resource for my app, and running heroku ps:scale web=1 --app qcp gives me:

Scaling web processes... failed
 !    No such type as web

Even if I explicitly create a Procfile and define a web process with the following, it does not work.

web: bundle exec rails server thin -p $PORT -e $RACK_ENV

Everything works just fine if I turn the project into a full-blown git repo and push it normally using git. I feel like I'm missing something simple. Let me know how I can help.

Thanks again,
Chris

[xixixao]

I have the exact same issue, spent an hour trying to get it work with no success.

[Zopitirik]

Same here

[CooperSystems]

Same here, was there no solution?

[wisemanIV]

same issue

[btsai]

same issue, unable to find anything that makes it work.

[imurakenichi]

same issue.

C:\MyAppDir>heroku ps

C:\MyAppDir>heroku ps:scale web=1
Scaling web dynos... failed
! No such type as web.

C:\MyAppDir>foreman check
valid procfile detected (web)

C:\MyAppDir>more Procfile
web: bundle exec rails server -p $PORT

C:\MyAppDir>heroku config
=== MyApp Config Vars
PORT: 80

C:\MyAppDir>foreman start
18:19:43 web.1 | started with pid 6808
18:19:50 web.1 | [2013-06-26 18:19:50] INFO WEBrick 1.3.1
18:19:50 web.1 | [2013-06-26 18:19:50] INFO ruby 1.9.3 (2013-05-15)
[i386-mingw32]
18:19:50 web.1 | [2013-06-26 18:19:50] INFO WEBrick::HTTPServer#start:
pid=7208 port=80

C:\MyAppDir>heroku push
Checking for app files to sync... done, 0 files needed
Launching build process... done
Preparing app for compilation... done
Fetching buildpack... done
Detecting buildpack... done, Buildkit
Fetching cache... done
Compiling app...
Writing .profile.d/buildpack.sh... done
Putting cache... done
Creating slug... done
Uploading slug... done
Success, slug is
https://api.anvilworks.org/slugs/29eba1f5-d7ca-4f2e-afad-0236289e642f.tgz
Releasing to MyApp... ..done, v10

C:\MyAppDir>heroku logs

2013-06-26T09:34:53.191683+00:00 heroku[api]: Release v10 created by
2013-06-26T09:35:01.359737+00:00 heroku[router]: at=error code=H14 desc="No
web processes running" method=GET path=/ host=te
uapp.com fwd="122.216.73.66" dyno= connect= service= status=503 bytes=

C:\MyAppDir>heroku ps

C:\MyAppDir>heroku ps:scale web=1
Scaling web dynos... failed
! No such type as web.

[secretwind]

same here

[andrejguran]

7 months later, bug is still here...

[shadowyn]

I also have this issue but only using Windows/CMD. Terminal on OSx works fine.

[lox5773]

it is due to 0 web process is running... got to resource and set dyno from 0 to 1 by sliding the cursor and hit apply

[kjarex]

in .heroku\plugins\heroku-push\vendor\anvile\lib\anvil\manifest.rb - comment this line 170:
# next unless path =~ /^[A-Za-z0-9-_./]*$/
Then it should work maybe under Windows, too.

I got then also some error, that there was no access to .anvil/buildpack
After skipping lines 31-33 of ........\anvil\helpers.rb I was finally able to push my files to Heroku.

The first change is necessary because otherwise "Windows files" (because of the ":") are skipped - there you shouldn't fear anything at all.
The second change might have some unwanted effects (I was too lazy and annoyed to check what there should be written to that file - but up so far I don't see any unwanted behavior, so it might be okay).

And now everyone: Enjoy finally Heroku without git!

[ddollar]

Hello. I apologize for the delayed response. I am currently declaring issue bankruptcy. If this issue still applies to you please feel free to re-open and explain. Thanks :)

[ramkeshvats]

Same happing with me, stuck from last 2 days

[kirbyfern]

Hello I have the same issue on hosting jekyll however I cant seem to find the solution for this,

It appears the errors are coming from my jekyll data

2017-01-24T23:16:29.267268+00:00 heroku[slug-compiler]: Slug compilation started
2017-01-24T23:16:29.267287+00:00 heroku[slug-compiler]: Slug compilation finished
2017-01-24T23:16:29.065252+00:00 app[api]: Release v6 created by user heybisayangdako@gmail.com
2017-01-24T23:16:29.065252+00:00 app[api]: Deploy 2a247b0 by user heybisayangdako@gmail.com
2017-01-24T23:17:28.363105+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=kirbyjames.herokuapp.com

[ChandraKoduru]

Got same issue.
I was trying to setup a web application following this blog post.

http://fosskers.ca/blog/deploying-haskell-en.html

[bransfieldjack]

Same issue here, absolutely no idea why!

[cefimenda]

I had the same issue, but it resolved when I manually added node.js as a buildpack on heroku. You can do this by going to heroku dashboard>settings>buildpacks>add buildpack>nodejs

[bransfieldjack]

Hmm... I'm using Python with Flask in my app. I have tried removing and re-adding the python build pack but still no joy.

Application Logs:

2018-09-24T07:16:58.316374+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=data-centric-recipe-app.herokuapp.com request_id=03f98cc2-b536-4da4-b6a9-5359fb0a04b0 fwd="1.152.108.234" dyno= connect= service= status=503 bytes= protocol=https

2018-09-24T07:16:59.337861+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=data-centric-recipe-app.herokuapp.com request_id=aa4505a2-f25d-4e46-8629-7c14a6ac73b4 fwd="1.152.108.234" dyno= connect= service= status=503 bytes= protocol=https

2018-09-24T07:16:59.369850+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=data-centric-recipe-app.herokuapp.com request_id=5665ee4c-4e7d-4289-b062-e5aae0c55512 fwd="1.152.108.234" dyno= connect= service= status=503 bytes= protocol=https

2018-09-27T00:20:21.271745+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=data-centric-recipe-app.herokuapp.com request_id=ee1f2f91-062c-4ae1-b06b-d8b72fd35a39 fwd="49.255.209.198" dyno= connect= service= status=503 bytes= protocol=https

2018-09-27T00:20:21.727543+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=data-centric-recipe-app.herokuapp.com request_id=5f41414a-da1f-4ebb-8664-c42eecf056d6 fwd="49.255.209.198" dyno= connect= service= status=503 bytes= protocol=https

[warcrow88]

I had success resolving this error by deleting my local git file and doing a new git init. The issue for me was that I initially called my Procfile "procfile" by accident and this was affecting something called a dyno formation on Heroku. The app worked fine locally, but bugged out on Heroku. Changing the name, saving and recommitting had no effect, even after deleting the app on Heroku! Turns out, this issue was that the git file itself refused to change the file name to a version that included a capitol "P" ...in other words, the git file retained the memory of the initial error. Pushing it to Heroku again therefore resulted in the same bug.

There may be a different way to do it (perhaps using a branch), but if this is any evidence - I would check the Procfile contents, location, filename, and changes with respect to time and the git file. It may resolve the issue.