-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent login failure #8
Comments
It seems a little more than intermittent to me. |
It seems to get better and worse over time. I've gone more than a day without hitting it, then hit it almost constantly for a while, then had it go away again. We can handle the error more gracefully (a LoginError rather than a TypeError), but the real solution is going to be when we generalize our retrying logic, so it can automatically back off and try again. |
I have never gotten this to work because of this error. |
@Red-Green maybe it's a different issue? Are you providing the correct login, and how? Also, if your IP is not stable, this can easily happen, since SE's login requires a stable IP for a small amount of time. |
@Manishearth I'm not sure. Do i use my Email, or my username, or my display name? |
@Red-Green You use your StackExchange openid credentials. (email+password). Try it out here GMail login is not yet implemented. You can create a StackExchange openid and attach it to your account by the "my logins" link on your profile. |
@Manishearth I can confirm that I am logging in by looking at the SE OpenID website. The app crashes after a successful login. |
Crashes with what message? -Manish Goregaokar On Sat, May 10, 2014 at 7:24 PM, red-green [email protected] wrote:
|
@Manishearth It crashes before it sends a message. Here is the full output of the
|
So this has to do with SE's login mechanism. Go to Stackexchange.com, and instead of using the SE login, enter https://openid.stackexchange.com in the "custom openid" box. You will have to authorize it to use the openid. This API isn't yet ready for public consumption, these kinks are still present. We'll sort these out as time passes. |
I receive this error as well (with adjusted line numbers, presumably because of 9 months of development from when this issue was originally open). Prior to today, I was able to log in and have been utilizing this project for about 6 months with no login issues.
|
Kinda invalided by now as OpenID is now replaced. But on the new login, you may run into a captcha after too many recent logins which blocks you for 5 - 10 minutes. |
Probably due to throttling
The text was updated successfully, but these errors were encountered: