I tried going on the Stack Overflow chat and got the following notice:

The console shows:

Failed to load resource: the server responded with a status of 500 (Internal Server Error)

Update #1

It seems like this issue intermittently occurs.

Update #2

Browser: Chrome (60.0.3112.113)

Access Type: HTTPS


Country: UK

  • Specific browser? Are you using TOR, a VPN service? In which part of the world are you? If you switch ISP's does the same issue occur? You did load over https, right? Are you hitting a specific url? – rene Sep 2 '17 at 18:44
  • @rene How am I supposed to switch ISP? – Script47 Sep 2 '17 at 19:02
  • Maybe use your mobile phone as a WiFi AP and use your mobile data provider – rene Sep 2 '17 at 19:04
  • Most likely your account was merged at some point, this screws up the chat profile, always did. SE employee (developer or a Community Manager) must manually re-create your chat account. – Shadow Wizard is Ear For You Sep 2 '17 at 20:41
  • Yup, found it. This is your other account, most likely your chat profile is still there, deleted, and not merged into your new account. Next time you can save time by saying that's the case. – Shadow Wizard is Ear For You Sep 2 '17 at 20:45
  • 1
    @ShaWizDowArd: I can't figure out how a 500-error chat access heisenbug can possibly be a dupe of a 100% repeatable 404-error chat profile access error. – Nathan Tuggy Sep 3 '17 at 3:41
  • @Nathan sorry thought the other one was 500 error and not 100% reproduceable. Anyway this is a better dupe and confirms what I said in the comment. Since it is case by case, better just leave all those reports open anyway. – Shadow Wizard is Ear For You Sep 3 '17 at 5:10
  • Yeah... @ShaWiz got the cause here. I've deleted the orphaned chat account so if you try and join chat now it should recreate you a new chat account that works. – Jon Clements Sep 3 '17 at 6:15
  • @Jon oh, thought only SE employee can handle those cases as it involves merging... cheers! – Shadow Wizard is Ear For You Sep 3 '17 at 6:28
  • @ShaWiz in the case where it's an unused 5 year old chat (or a very infrequently used one) it's easier for a mod to just nuke the chat account to let the system create a new one. For frequent chatters with a large amount of chat history then yeah - best to get an employee involved so chat history is associated and retained correctly. – Jon Clements Sep 3 '17 at 6:32

You must log in to answer this question.

Browse other questions tagged .