R11 - Bad bind

[Filirom1]

R11 - Bad bind

A process performed an incorrect TCP socket bind. This error is often caused by binding to a port other than the assigned $PORT. It can also be caused by binding to an interface other than 0.0.0.0 or *.

2011-05-03T17:38:16+00:00 heroku[web.1]: Starting process with command: bundle exec ruby web.rb -e production
2011-05-03T17:38:18+00:00 app[web.1]: == Sinatra/1.2.3 has taken the stage on 4567 for production with backup from Thin
2011-05-03T17:38:18+00:00 app[web.1]: >> Thin web server
2011-05-03T17:38:18+00:00 app[web.1]: >> Maximum connections set to 1024
2011-05-03T17:38:18+00:00 app[web.1]: >> Listening on 0.0.0.0:4567, CTRL+C to stop
2011-05-03T17:38:18+00:00 heroku[web.1]: Error R11 (Bad bind) -> Process bound to port 4567, should be 43411 (see environment variable PORT)
2011-05-03T17:38:18+00:00 heroku[web.1]: Stopping process with SIGKILL
2011-05-03T17:38:18+00:00 heroku[web.1]: Process exited
2011-05-03T17:38:20+00:00 heroku[web.1]: State changed from starting to crashed

https://devcenter.heroku.com/articles/error-codes#r11-bad-bind

[Filirom1]

Related to #1

[Filirom1]

Useful resource: http://serverfault.com/questions/388113/limit-which-ports-a-user-can-bind

[Filirom1]

Was started here : 02f3627...ee33028

But reverted because of #9