H14 Error In Heroku - "no Web Processes Running"
Solution 1:
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.
Solution 2:
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 myvenv
IMO, this error should be raised on Heroku's end. As a beginner, this sort of error is difficult to trace.
More info on dyno configuration – more on initializing your heroku app.
Solution 3:
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
Solution 4:
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
Solution 5:
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
Post a Comment for "H14 Error In Heroku - "no Web Processes Running""