Tutorial by Examples

A crashed web dyno or a boot timeout on the web dyno will present this error. 2010-10-06T21:51:04-07:00 heroku[web.1]: State changed from down to starting 2010-10-06T21:51:07-07:00 app[web.1]: Starting process with command: `bundle exec rails server -p 22020` 2010-10-06T21:51:09-07:00 app[web.1]:...

When HTTP requests arrive faster than your application can process them, they can form a large backlog on a number of routers. When the backlog on a particular router passes a threshold, the router determines that your application isn’t keeping up with its incoming request volume. You’ll see an H11 ...

An HTTP request took longer than 30 seconds to complete. In the example below, a Rails app takes 37 seconds to render the page; the HTTP router returns a 503 prior to Rails completing its request cycle, but the Rails process continues and the completion message shows after the router message. 2010-...

This error is thrown when a process in your web dyno accepts a connection, but then closes the socket without writing anything to it. 2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=GET path="/" host=myapp.herokuapp.co...

This is most likely the result of scaling your web dynos down to 0 dynos. To fix it, scale your web dynos to 1 or more dynos: $ heroku ps:scale web=1 Use the heroku ps command to determine the state of your web dynos. 2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H14 desc="No web...

The dyno did not send a full response and was terminated due to 55 seconds of inactivity. For example, the response indicated a Content-Length of 50 bytes which were not sent in time. 2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H15 desc="Idle connection" method=GET path="...