# We're sorry, but something went wrong

**URL:** <https://www.ruby-forum.com/t/were-sorry-but-something-went-wrong/246364>\
**Category:** NGINX\
**Created:** [October 2, 2013, 4:29pm UTC](https://www.ruby-forum.com/t/were-sorry-but-something-went-wrong/246364 "2013-10-02T16:29:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sadaf\_N](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/858c86/32.png) [@Sadaf\_N](https://www.ruby-forum.com/u/Sadaf_N)\
**Post date:** [October 2, 2013, 4:29pm UTC](https://www.ruby-forum.com/t/were-sorry-but-something-went-wrong/246364/1 "2013-10-02T16:29:23Z")

</div>

So I’m in the early stages of rolling out a system to production, and a  
few app errors are cropping up that didn’t get caught in testing, and it  
occurs to me: it would be nice if the default “we’re sorry, but  
something went wrong” error page could include a timestamp.

–  
Scott R.  
removed\_email\_address@domain.invalid  
[http://www.elevated-dev.com/](http://www.elevated-dev.com/)  
(303) 722-0567 voice

---

<div class="post-metadata">

**Author:** ![scottrutherford](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/d07c76/32.png) [@scottrutherford](https://www.ruby-forum.com/u/scottrutherford)\
**Post date:** [October 2, 2013, 5:08pm UTC](https://www.ruby-forum.com/t/were-sorry-but-something-went-wrong/246364/2 "2013-10-02T17:08:34Z")

</div>

That sounds like a RoR app acting up and not the nginx server itself.

L.

---

<div class="post-metadata">

**Author:** ![scottrutherford](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/d07c76/32.png) [@scottrutherford](https://www.ruby-forum.com/u/scottrutherford)\
**Post date:** [October 2, 2013, 5:20pm UTC](https://www.ruby-forum.com/t/were-sorry-but-something-went-wrong/246364/3 "2013-10-02T17:20:52Z")

</div>

On Oct 2, 2013, at 9:08 AM, Lasse L. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> That sounds like a RoR app acting up and not the nginx server itself.

Ah… Yes it is an error in RoR, but I had mistakenly thought that RoR  
was failing to return a result to nginx, and nginx was serving up that  
page. I see that in fact RoR’s exception handling is returning that page  
to nginx.

So I know exactly what to do 😉

–  
Scott R.  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

> **[Elevated Software Development, Inc.](http://www.elevated-dev.com/)**

(303) 722-0567 voice