# FAILSAFE preventing errors from displaying? **URL:** \ **Category:** Rails\ **Created:** [January 11, 2009, 7:02am UTC](https://www.ruby-forum.com/t/failsafe-preventing-errors-from-displaying/157428 "2009-01-11T07:02:06Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![tekwiz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/dfb087/32.png) [@tekwiz](https://www.ruby-forum.com/u/tekwiz)\ **Post date:** [January 11, 2009, 7:02am UTC](https://www.ruby-forum.com/t/failsafe-preventing-errors-from-displaying/157428/1 "2009-01-11T07:02:06Z")
Used to, when I had an error in development mode, I saw a pretty stack trace in the browser and didn’t have to go the server console, and in production mode I would see the pretty 500.html error page be displayed. Since I’ve started using Rails 2.2, I no longer get either of these. I get the ugly black and white “500 Internal Server Error” message. The happens the same in Mongrel for development and with Passenger in production, so I figure it has to do with some kind of configuration snafu. In the logs I see something like /!\ FAILSAFE /!\ Sat Jan 10 23:51:45 -0600 2009 Status: 500 Internal Server Error (followed by the error message and stack trace) I didn’t used to see anything like this, so I suspect it might have something to do with what’s going on. I think this is also preventing exception\_notification from performing its duties properly. Any suggestions? – Travis W. ---
**Author:** ![tekwiz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/dfb087/32.png) [@tekwiz](https://www.ruby-forum.com/u/tekwiz)\ **Post date:** [February 2, 2009, 1:31am UTC](https://www.ruby-forum.com/t/failsafe-preventing-errors-from-displaying/157428/2 "2009-02-02T01:31:44Z")
Do you use rspec-rails ? I had it required in environment.rb. The problem went away when I removed “config.gem ‘rspec-rails’, :lib =\> ‘spec/rails’”. That’s also what also prevented my exception notifications to work correctly. Cheers ! Alexandre