rails: "We're sorry, but something went wrong." in development mode

Rails throws

We're sorry, but something went wrong.
If you are the application owner check the logs for more information.

But in development mode (log level is debug, all_requests_considered_local) it should display backtrace with informations.

Problem occurs when render is called fom controller or view and view (or partial) is misformatted (tested on slim, haml and erb) or somehow throws error. Does this with RC2 and master as well.

Whole log for request look like this:

Started GET "/admin/" for 127.0.0.1 at 2013-06-23 16:22:18 +0200
  Vega::Setting Load (0.1ms)  SELECT "vega_settings".* FROM "vega_settings" WHERE "vega_settings"."type" = 'global' AND "vega_settings"."name" = 'title' LIMIT 1
  Vega::Setting Load (0.1ms)  SELECT "vega_settings".* FROM "vega_settings" WHERE "vega_settings"."type" = 'global' AND "vega_settings"."name" = 'language' LIMIT 1
Processing by Vega::Admin::DashboardController#index as HTML
  Rendered /home/hrdina/liaheň/vega/app/views/vega/admin/dashboard/index.html.erb within layouts/vega/admin (18.2ms)
  Rendered /home/hrdina/liaheň/vega/app/views/vega/general/_admin_menu.html.haml (1.1ms)
Completed 500 Internal Server Error in 61ms

About this issue

Original URL
State: closed
Created 11 years ago
Comments: 32 (11 by maintainers)

Most upvoted comments

It is not big deal you have to run: (name of ur project)(master)$ heroku run rake db:migrate it will resolve your issue

ArtoriusXIII on Apr 19, 2015

Hey everyone. I had the same problem and Yes ArtoriusXIII you are right. Just run the following command in your terminal, icloud9 terminal whatsoever:
(name of your project)(master)$ heroku run rake db:migrate and hit enter. Refresh your app url and it should work perfectly well again.

Joshhortt on Feb 3, 2018

Finally I know why… problem is ‘ň’ in the path. I tried few non-acsii characters (ľ, á) and none worked. Also tried every combination of ruby 1.9.3, 2.0.0, rvm and rbenv.

I don’t know, if this is issue, but I thought Ruby (or Rails?) is UTF-8 compatible and behaviour is really weird.

See for yourself: http://i.imgur.com/sg1chbG.png

@senny what do you think?

istana on Jun 23, 2013

I had the same problem but only on some routes in the app. In my case, this was because it had special characters in the respective controllers. To fix this, I add at the beginning of each controller the next line # encoding: utf-8

Sorry if this is not the best solution, but it worked for me. (for now)

cristianferrarig on Oct 9, 2013