I have tried using my openID and some of the other options and it always says it's an invalid ID...any idea what may be happening?
migrated from meta.stackoverflow.com Jul 22 '10 at 17:59
This was very likely due to a period when the OpenID provider let their security certificate expire. (You are/were using openid.org, I'll bet, Proxify — this has happened more than once, with them.)
When that happens, the Stack Exchange network servers fail to make the HTTPS connection to openid.org, and the signon attempt fails somewhat cryptically. (It'd actually be kind of nice if the site(s) here recognized that it was an HTTPS certificate rejection that was blocking the openid authentication attempt, and returned a more-explanatory message to the user.)
We just went through another period like that, with openid.org, which has fortunately now ended. As of 2012-03-11 openid.org once again has a valid security certificate.
Of course, because their new certificate expires in just 1 year, come 2013-03-13 we'll be in the same mess all over again... unless someone is more on the ball next time, that is.
Personally, now that I finally have access to my stackexchange account again, the very first thing I did was go to "my logins" and add a secondary signon method. Openid.org obviously can't be trusted as a sole provider, which is a shame. (Though it was definitely my fault for making them a single point of failure for my login, in the first place.)