Currently the chat.meta.stackoverflow.com site is down.

It is also giving the default ASP.Net error page, not the friendly custom one.

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 
  • 6
    Yeah, not even a lolcat :) Looking into it. – balpha Sep 9 '10 at 13:33
  • 1
    Man, I thought it was just me! The fact that the "Server Error in '/'" page came up fooled DownForEveryoneOrJustMe. And apparently their URLs confuse the Markdown parser, so: downforeveryoneorjustme.com/http://chat.meta.stackoverflow.com EDIT: and now it is correctly reporting that chat is down. How odd. – Pops Sep 9 '10 at 13:37
  • @Popular Demand:downforeveryoneorjustme.com/http://chat.meta.stackoverflow.com says "It's not just you" for me. EDIT: nevermind :p EDIT2: re following: agreed – Tobias Kienzler Sep 9 '10 at 13:40
  • @Tobias, yes, I retested after I posted my comment and just updated while you were commenting; thanks! EDIT: we should keep posting replies in edits while the other person replies in a new comment simultaneously. – Pops Sep 9 '10 at 13:41
  • I'm confused. Is the bug report because the chat is down? Or is the bug report because there is no custom error page? – Rebecca Chernoff Sep 9 '10 at 13:51
  • @rchern Because the error page is missing. Chat being back up would be nice, but I expect this because it's beta. – C. Ross Sep 9 '10 at 13:56
  • 2
    There is a custom error page - the error was too terminal for the error page to work... – Marc Gravell Sep 9 '10 at 14:02
  • @Marc Gravel That's some bad juju there. – C. Ross Sep 9 '10 at 14:43

OK; we're back up. Still investigating what happened, but the unicorns and the pixies have stopped fighting for long enough to serve requests instead.

  • Rrgh, refreshing takes you to the kitten page, because the URL still says error. (Typing the URL in directly works, of course.) @Marc, do you need the pixies? Can this be a unicorn-only operation? – Pops Sep 9 '10 at 14:07
  • Now I'm getting the lolcat error page. – badp Sep 9 '10 at 14:07
  • @badp really? are you sure your browser isn't just left on the /error url? (the last logged error was a little while ago) – Marc Gravell Sep 9 '10 at 14:11
  • yeah, that was it. – badp Sep 9 '10 at 14:20
  • 3
    @Popular - can't do it. The union got involved and everything. – Marc Gravell Sep 9 '10 at 14:33

Reproduced, URL is then (FF3.6) http://chat.meta.stackoverflow.com/error?aspxerrorpath=/


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .