Sending forgot password link in clearance

In these kinds of situations, I think it can be useful to have a stacktrace, which helps you see what methods were being called by what other methods before the problem happened. You can sign up for a free developer account on several of the popular error handler services (Airbrake, Rollbar, Honeybadger, etc.).

Another way to follow the trace is to tail the logs as you cause the exception. You can do this with the Parity command or by using heroku logs --tail.

Examing the stacktrace can save you from a lot of “fumbling in the dark” trying to figure out why you’re getting that confusing sorry page.