H14 error in heroku - "no web processes running"

Question

error H14 happen while deploying to heroku this is my procfile:

web: gunicorn -w 4 -b 0.0.0.0:$PORT -k gevent main:app

log on heroku:

2017-01-23T10:42:58.904480+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=meetcapstone.herokuapp.com request_id=df88efb5-a81a-4ac0-86dc-4e03d71266bb fwd="81.218.117.137" dyno= connect= service= status=503 bytes=
2017-01-23T10:42:59.009135+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=meetcapstone.herokuapp.com request_id=21cea981-36b0-4410-891f-548bbc29f0ee fwd="81.218.117.137" dyno= connect= service= status=503 bytes=

requirements:

Flask==0.11.1
passlib==1.7.0
SQLAlchemy==1.1.5
Werkzeug==0.11.15
gunicorn==19.0.0
gevent==1.2.1

Please show the whole log from the time you deployed. Were there any errors starting gunicorn? — Daniel Roseman, Jan 23 '17 at 11:07

score 215 · Answer 1 · answered Jan 23 '17 at 16:57

215

The issue here is that you're not running any web dynos. You can tell Heroku to do this via:

$ heroku ps:scale web=1

This will force Heroku to spin up a web dyno, thereby executing your gunicorn command.

answered Jan 23 '17 at 16:57

rdegges

32,786
20
85
109

17

should i write it in the procfile? – Ron Miles Jan 24 '17 at 10:32
3

amazing! i got this issue to trigger after putting in a malformed procfile and then correcting it – Luke May 31 '17 at 10:49
1

Weird, the dyno in the Heroku dashboard had to be disabled first. Thanks! – Stéphane Bruckert Mar 15 '18 at 16:53
Thanks! For some reason the embedded tomcat tutorial did not require me to do this, yet the webapprunner tutorial did. No clue why the difference. – KANJICODER Jul 11 '18 at 08:46
Man! One day trying to fix this, I am deploying a container to Heroku and I changed the `web` in `build` to my app's name, I didn't think that mattered... Heroku should be more clear on their tutorials. – jpenna May 21 '19 at 12:03
@jpenna please how did u deploy your containers to heroku. Been trying to do that for weeks. – medobills May 26 '19 at 08:45
@medobills I ran `heroku stack:set container` and then I created the `heroku.yml` file with `build: docker: web: Dockerfile`, and deployed it to Heroku using the `git push heroku master`. The problem was that I changed the `web: Dockerfile` to `myApp: Dockerfile`... Check this: https://devcenter.heroku.com/articles/build-docker-images-heroku-yml, I think it should work fine if you follow these steps and you have your Dockerfile correct and your containers are running fine locally. Tell if it works. – jpenna May 28 '19 at 04:24
wow thanks! i had this problem after downgrading the dyno and this one liner works! – Vina Feb 14 '20 at 09:14
72

Scaling dynos... ! ▸ Couldn't find that process type (web). – Charles Thayer Feb 24 '20 at 04:22
2

(ah ok, was missing a Procfile --very confusing unless you use their example code) – Charles Thayer Feb 24 '20 at 04:30
If you have already deployed without and dynos and are getting the error "Couldn't find that process type (web).", then you need to remove your buildpacks first, then set ps:scale, and then put the buildpacks back. See: https://help.heroku.com/W23OAFGK/why-am-i-seeing-couldn-t-find-that-process-type-when-trying-to-scale-dynos – Mark Hansen May 10 '20 at 20:24
I had the "Couldn't find that process type (web)" issue. The fix was to create a Procfile. I'm deploying a Django app so the file contained "web: gunicorn .wsgi". Full docs are here: https://devcenter.heroku.com/articles/procfile – Dylan Apr 16 '21 at 23:53
1

! Couldn't find that process type (web). – kushagra-aa Aug 20 '21 at 16:27
1

Doesn't work any more if you come from a free plan. You are forced to eco now. – Wolfgang Fahl Dec 18 '22 at 14:41

Yaakov Bressler · Answer 2 · 2022-10-19T19:50:27.960

47

After 3 hours of debugging, I've figured out why my app was causing this error:

My Procfile was incorrectly cased
gunicorn wasn't installed in my venv

IMO, this error should be raised on Heroku's end. As a beginner, this sort of error is difficult to trace.

Update: To clarify, Procfile is correctly cased and procfile is not correctly cased. It should start with a capital "P".

More info on dyno configuration – more on initializing your heroku app.

edited Oct 19 '22 at 19:50

answered Jan 19 '20 at 19:00

Yaakov Bressler

9,056
2
45
69

2

To clarify, `Procfile` is correctly cased and `procfile` is **not** correctly cased. It should start with a capital P. – NecipAllef Oct 19 '22 at 19:41

score 20 · Answer 3 · answered Aug 14 '21 at 02:20

20

I ran into the same problem but from a different cause. I had the hobby tier, but then canceled it and reverted back to the free tier. Doing this caused the error and how I fixed it was just re running the command from the cli:

heroku ps:scale web=1

answered Aug 14 '21 at 02:20

Maxwell

224
2
4

6

Getting an error when running this command ..`Scaling dynos... ! Couldn't find that process type (web).` – Pavindu Aug 09 '22 at 10:18
1

heroku ps:scale web=1 --app APP_NAME_IN_HEROKU worked for me! – PedroTNascimento Nov 03 '22 at 00:29

score 15 · Answer 4 · answered Jul 10 '19 at 10:01

15

Before this command:

heroku ps:scale web=1

I had to remove and add buildpacks again and empty commit it and redeploy it to heroku.

heroku buildpacks:clear
heroku buildpacks:add --index heroku/python

answered Jul 10 '19 at 10:01

bsh

161
1
5

1

I got `Error: Expected an integer but received: heroku/python` with your last command – Revolucion for Monica Jul 03 '21 at 14:17
heroku buildpacks:set heroku/python – Ammar H Sufyan Jul 31 '21 at 06:50
1

! Couldn't find that process type (web). – kushagra-aa Aug 20 '21 at 16:25

score 9 · Answer 5 · answered Dec 15 '22 at 06:28

9

My issue is that Heroku removed the free plans. To solve such an issue go to Heroku and select/change your free plan to for example "eco" plan.

answered Dec 15 '22 at 06:28

Khalid Seflan

71
1
6

score 7 · Answer 6 · answered Apr 16 '20 at 17:54

7

I was having an issue here too. My problem was that my Procfile was "Procfile.txt" . What solved my issue was to remove the file extension from Procfile, then recommit and push stuff to heroku

answered Apr 16 '20 at 17:54

theMikus

71
1
1

score 7 · Answer 7 · edited Sep 08 '20 at 08:09

7

Login to your Heroku dashboard and open your projects.
Go to Settings.
Delete heroku/python from the list of buildpacks
Then click Add buildpack → Choose "Python" → Save Changes.
Activate your environment in your code.
Run heroku ps:scale web=1.

And you're done!

edited Sep 08 '20 at 08:09

double-beep

5,031
17
33
41

answered Sep 08 '20 at 07:40

Aris Laode

81
1
3

17

what do you mean by activate your environment in your code? – Ken Jan 13 '21 at 21:30

score 7 · Answer 8 · answered Feb 27 '21 at 21:42

7

This isn't the problem with your code, but I've gotten this error message a couple of times now and the mistake that I've made that has caused it has been writing

web:gunicorn

instead of

web: gunicorn

That space can really cause a lot of issues.

answered Feb 27 '21 at 21:42

Austin Fischer

71
1
1

score 7 · Answer 9 · answered Feb 19 '22 at 17:00

7

I have a UAT version I only enable during client development.

I have a custom dyno script but it's turned to the free version. So the app was not starting as my script was not running. When I enabled the Dyno the toggle was still off :rolleyes:

answered Feb 19 '22 at 17:00

Garry Taylor

940
8
19

1

after few hours of debugging I have found out that this slider was disable in my heroku app – Andrey Mazur Apr 21 '22 at 18:43

score 2 · Answer 10 · answered Dec 03 '20 at 14:13

I don't have the reputation to reply to the correct comment, but for me the issue was that I didn't have the run.gunicorn.sh file in my root directory, this resulted in the same "No web processes running" error.

If you don't have this file, create it with contents:

gunicorn -b :5000 --access-logfile - --error-logfile - build:app

Where 'build' is the name of your python file (build.py in this case) and app is the name of your app in the code.

Also make sure that gunicorn is included in requirements.txt, like others have already pointed out.

score 2 · Answer 11 · answered Aug 24 '21 at 09:22

2

Yeah I was also using web heroku-php-apache2 dyno and reverted it back to free tier and that caused the dyno to sleep fortunately executing heroku ps:scale web=1 -a <app name> did the magic.

answered Aug 24 '21 at 09:22

Divyanshu Rawat

4,421
2
37
53

score 1 · Answer 12 · answered Feb 08 '21 at 17:45

1

Change your Procfile file from web:gunicorn to web gunicorn (remove the ':')

answered Feb 08 '21 at 17:45

Prince

11
1

score 1 · Answer 13 · answered Feb 14 '21 at 11:06

1

I fixed the issue by going to Configure Dynos and enabling the only dyno I had manually.

answered Feb 14 '21 at 11:06

santaclos

326
3
4

score 1 · Answer 14 · answered Sep 21 '21 at 09:56

1

uff..that took some time,so the fixes i had to make were:

'Procfile' with upper case P.
web: gunicorn wsgi:app (with a space after web: in procfile)
Making sure the requirements.txt are in the root project folder.

answered Sep 21 '21 at 09:56

Shyam

37
5

score 1 · Answer 15 · answered Jun 15 '23 at 04:21

1

Sometimes running heroku ps:scale web=1 does not fix the issue, a workaround i found useful is scaling up the dynos then scaling them down to your initial price i.e bumping it to 25$ then scaling it back to 7$

answered Jun 15 '23 at 04:21

Sunday Ømwami

41
4

score 0 · Answer 16 · answered Feb 18 '21 at 11:10

I was missing dynos on the web gui. The cli command to scale did not work. I also may have had an incorrect run:web declaration with missing $PORT. To fix:

heroku.yml must have a web declaration using the $PORT var:

build:
  docker:
    web: Dockerfile
run:
  web: uvicorn main:app --reload --host 0.0.0.0 --port $PORT

I then pushed to heroku.

After that it must have added the web dyno, I could then run:

heroku ps:scale web=1

And now the fastapi uvicorn runs.

score 0 · Answer 17 · answered May 29 '21 at 08:22

Pay attention to the Procfile naming and location (https://devcenter.heroku.com/articles/procfile) The Procfile is always a "simple text file" that is named Procfile without a file extension.(Procfile.txt not acceptable!) The Procfile must live in your app's root directory. It does not function if placed anywhere else.

score 0 · Answer 18 · answered Nov 16 '21 at 14:13

0

Faced the exact same problem turns out I had the Profile in .gitignore

answered Nov 16 '21 at 14:13

Fahim

1

score 0 · Answer 19 · answered Dec 09 '21 at 08:49

I was placing my django Procfile in the directory with settings.py and not the root directory and that gave me the H14 error. I fixed the error with this and I didn't need to do anything else they say.

Procfile

web: gunicorn <django-root-name(containing wsgi)>.wsgi

score 0 · Answer 20 · answered Jun 26 '22 at 02:08

0

There are many things that can go wrong here. Its a combination of poor shepherding by heroku and ambiguous use between flask & gunicorn.

Here is a good guide that will get you up and running:

answered Jun 26 '22 at 02:08

Sergio Bost

2,591
2
11
29

score 0 · Answer 21 · answered Dec 08 '22 at 01:34

To anyone who may come across this...

delete your Procfile
create 'Procfile' with upper case P.
in your Procfile type: web: gunicorn <nameOfRootFile>:app (with a space after web: in procfile) mine for example was web: gunicorn app:app another way I wrote it that worked was this: web: gunicorn -w 4 "app:create_app()" -t 120
Making sure the requirements.txt are in the root project folder. (you can run pip freeze > requirements.txt if you do not have the file created
deploy to heroku
heroku ps:scale web=1 (you can specify app name to like this heroku ps:scale web=1 -a appname
finally in terminal run heroku restart
heroku open

these are all the steps i took to get mine to work

score 0 · Answer 22 · edited Jan 07 '23 at 20:13

0

web: gunicorn weather.wsgi --log-file -

this worked for me, just make sure your Procfile is in the right format, and specify the app you are connecting to, in my case it's the weather app. Enjoy

edited Jan 07 '23 at 20:13

Julia Meshcheryakova

3,162
3
22
42

answered Jan 06 '23 at 11:58

Adeniran Tobi

1
1

Hatem Gadallah · Answer 23 · 2023-03-11T06:47:21.673

0

I faced the same issue because my application was deployed on the free plan before and its size was more than 300MB. The application worked fine again when I did the following:

Upgrade account to eco plan
Deleted the application
Create new application on heroku for the same project and deployed it.

edited Mar 11 '23 at 06:47

answered Mar 03 '23 at 07:26

Hatem Gadallah

1
1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Blue Robin Mar 07 '23 at 21:15

score 0 · Answer 24 · answered Jul 02 '23 at 23:02

0

Try scale down the dyno first.

heroku ps:scale web=0

Then scale it up.

heroku ps:scale web=1

answered Jul 02 '23 at 23:02

Gundam Meister

1,425
2
19
29

score -1 · Answer 25 · edited Aug 30 '22 at 11:43

-1

What worked for me was adding on the second line of the procfile:

heroku ps:scale web=1

The first line must contain:

web: gunicorn "filename":"main method name"

edited Aug 30 '22 at 11:43

Webdeveloper_Jelle

2,868
4
29
55

answered Aug 23 '22 at 19:03

LIOC

1
2

H14 error in heroku - "no web processes running"

25 Answers25

Linked

Related