We're sorry, but something went wrong Heroku -

don't start app @ heroku. migrate do, don`t work anyway... please anyone

2015-07-17t08:27:11.996879+00:00 app[web.1]: => booting puma 2015-07-17t08:27:11.996906+00:00 app[web.1]: => rails 4.2.1 application starting in production on http://0.0.0.0:15906 2015-07-17t08:27:11.996909+00:00 app[web.1]: => run `rails server -h more startup options 2015-07-17t08:27:11.996910+00:00 app[web.1]: => ctrl-c shutdown server 2015-07-17t08:27:16.038259+00:00 heroku[web.1]: state changed starting 2015-07-17t08:27:15.924000+00:00 app[web.1]: puma 2.11.3 starting... 2015-07-17t08:27:15.924095+00:00 app[web.1]: * min threads: 0, max threads: 16  2015-07-17t08:27:15.924199+00:00 app[web.1]: * environment: production 2015-07-17t08:27:15.924281+00:00 app[web.1]: * listening on tcp://0.0.0.0:15906 2015-07-17t08:27:18.702571+00:00 heroku[router]: at=info method=get path="/" host=shrouded-eyrie-5960.herokuapp.com request_id=7976700d-bee7-4e6f-b20a-67d60a5d5e8a fwd="176.104.8.251" dyno=web.1 connect=1ms service=210ms status=500 bytes=1669 2015-07-17t08:27:18.819798+00:00 heroku[router]: at=info method=get path="/favicon.ico" host=shrouded-eyrie-5960.herokuapp.com request_id=23341143-bd39-46ed-a48a-736533558ccd fwd="176.104.8.251" dyno=web.1 connect=1ms service=2ms status=200 bytes=143` 

this error comes app's code. however, app sending it's logs local filesystem, means don't see exception in heroku logs.

you need configure app send logs stdout or stderr able see them.
can add rails_12factor gem app, change configuration that.

once have added gem app , redeployed it, raised exception should show in logs , can fix in app's code.