Note that there are some explanatory texts on larger screens.

plurals
  1. POHeroku, Django app crashing on startup, "not a valid port number"
    primarykey
    data
    text
    <p>I am trying to run my first Django powered app on Heroku. I have been following <a href="https://devcenter.heroku.com/articles/django" rel="nofollow noreferrer">this guide</a>. The app is running fine using:</p> <pre><code>python manage.py runserver </code></pre> <p>When I commit any changes I made, and then try to push it to Heroku, everything seems fine until I visit the heroku URL. I receive an 'Application Error' page. Looking more in to the:</p> <pre><code>heroku logs </code></pre> <p>I get a bunch of what appears to be the same error message:</p> <pre><code>....... 2013-01-18T05:28:29+00:00 heroku[slugc]: Slug compilation finished 2013-01-18T05:28:29+00:00 app[web.1]: Error: "0.0.0.0:" is not a valid port number or address:port pair. 2013-01-18T05:28:31+00:00 heroku[web.1]: Process exited with status 1 2013-01-18T05:28:32+00:00 heroku[web.1]: Starting process with command `python manage.py runserver 0.0.0.0: --noreload` 2013-01-18T05:28:33+00:00 app[web.1]: Error: "0.0.0.0:" is not a valid port number or address:port pair. </code></pre> <p>Also if I do a foreman start: </p> <pre><code>22:39:26 web.1 | started with pid 2499 22:39:26 web.1 | Error: "0.0.0.0:" is not a valid port number or address:port pair. 22:39:26 web.1 | exited with code 1 22:39:26 system | sending SIGTERM to all processes SIGTERM received </code></pre> <p>I looked at a <a href="https://stackoverflow.com/questions/11765945/django-app-crashing-in-heroku">similar question</a> but I seem to have everything needed in my requirements.txt file.</p> <p>Thanks for the help!</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload