0

I have recently been trying to deploy my application to Heroku. I was following the documentation and everything but I'm getting this error now.

2020-03-12T21:46:36.154267+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=semsar-flask.herokuapp.com request_id=8c7e6604-97a5-4f5c-ae62-6c2edb73a4bb fwd="217.164.64.29" dyno= connect= service= status=503 bytes= protocol=https

This is my Procfile:

web: gunicorn wsgi: app

Wsgi.py:

from wbp import app

Did I make a mistake filling in those two files or what? Please do explain since I'm relatively new to this.

davidism
  • 121,510
  • 29
  • 395
  • 339
abood bah
  • 154
  • 3
  • 17

2 Answers2

1

An H10 error could mean many possibilities and answering all solutions here would be tedious. You should also read here and see if any of those are helpful.

Also try to avoid empty spaces in Procfile. So try changing from this

web: gunicorn wsgi: app

To this

web:gunicorn wsgi:app

and see if it works.

AzyCrw4282
  • 7,222
  • 5
  • 19
  • 35
  • The Procfile format is `: `, not `:` see: https://devcenter.heroku.com/articles/procfile – Tin Nguyen Mar 13 '20 at 07:19
  • 1
    Removing those two spaces seems to somehow fix my issue but now I'm getting this error ' at=error code=H14 desc="No web processes running" ' – abood bah Mar 13 '20 at 07:38
  • please do update the new error trace to the question. See this https://stackoverflow.com/questions/41804507/h14-error-in-heroku-no-web-processes-running – AzyCrw4282 Mar 13 '20 at 09:13
  • 1
    @Tin_Nguyen True. The format just illustrates with placeholders and doesn't say anything about spaces. Believe it or not, I had this error and fixed it with doing just that. A similar incident also [here](https://stackoverflow.com/a/54790377/6505847). – AzyCrw4282 Mar 13 '20 at 14:12
  • Oh I fixed that error too.. I just didn't know about the whole dynos thing. I didn't have any assigned for my app. anyways thanks a lot man. – abood bah Mar 18 '20 at 06:16
1

For the app crashed h10 error check that your SECRET_KEY is added to Heroku. Also when logged in to Heroku, click on 'More' in the top right of the page and then 'Restart all dynos'. Both have helped me in the past with this specific error.

ad28
  • 9
  • 3
  • How do I go around adding my SECRET_KEY to Heroku though? shouldn't it be automatically detected when the app is deployed on the platform? – abood bah Mar 13 '20 at 07:41
  • No, you'd need to add it to Heroku. In the Settings tab click on Reveal Config Vars and you'll you can enter it there. – ad28 Mar 18 '20 at 00:18