My OpenID provider is a copy of phpMyId running on my server that I fiddled with a bit. Sometime in the last few weeks something changed so that the script doesn't work anymore -- I get the "Oops! Something Bad Happened" page when I try to login. I've never gotten that before; when I messed up the script I would end up back on the login page with an OpenID error instead. What changed with OpenID handling in the last few weeks? How can I debug the problem; is there a way to get an error message more specific than "Something bad happened"?

  • 1
    This triggered another openid "Really?" moment for me. Why this just isn't built into my browser is beyond me. Mar 7, 2011 at 22:07

2 Answers 2


Recent changes in PHP seem to be the culprit, the problem is that phpmyid no longer sends the header correctly. A rewrite rule, which I posted to my similar question, may solve your problem:

Unable to log in with your OpenID provider: no OpenID identifier was provided


Nothing changed on our end, but something changed on your end.

You can view source on the error page to get a tiny bit more detail. I don't see anything in our error logs.

  • Oh, that's handy. I don't suppose "An item with the same key has already been added." means anything? I haven't touched that script since I got it working months ago, but I'll fiddle later today to see if I caused it somehow Mar 7, 2011 at 21:32

You must log in to answer this question.

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