Yup, basic auth on my server. I think however I might have found the
culprit. Twitter Tools WP plugin still had my old password and may
have been attempting to check my tweets. I've not had any problems
since, but will let you know if it starts happening again.
On Nov 17, 6:51 pm, Mark McBride <mmcbr...@twitter.com> wrote:
> To clarify, it happens when you log in using basic auth via your own server?
> On Tue, Nov 17, 2009 at 1:57 AM, artesea <ryancul...@gmail.com> wrote:
> > Still happening to me, and it only occurs when I login via my own
> > server (184.108.40.206). I've started using oauth which works fine, but
> > worried that other people using my site are also having issues.
> > Thanks
> > Ryan
> > On Nov 17, 5:59 am, Mark McBride <mmcbr...@twitter.com> wrote:
> >> Is this still occurring? We saw a spike in odd authentication issues,
> >> but it appears to be a transient thing that sorted itself out. If
> >> this is still an issue I will investigate further.
> >> ---Mark
> >> On Sat, Nov 14, 2009 at 6:43 PM, Dewald Pretorius <dpr...@gmail.com> wrote:
> >> > I am also getting complaints from users who cannot authenticate via
> >> > the API with the same credentials that they use when logging on to
> >> > twitter.com.
> >> > Has the change, which limits invalid credentials lockout to a specific
> >> > IP address, perhaps been accidentally rolled back?
> >> > Dewald
> >> > On Nov 14, 5:55 am, artesea <ryancul...@gmail.com> wrote:
> >> >> I'm still using HTTP requests to login via the API with a private dabr
> >> >> install I've got running. However I'm getting a large number of "401 -
> >> >> Could not authenticate you" when I try to sign in.
> >> >> I recently changed my password on Twitter, however I have no problems
> >> >> login on the main site, viahttp://dabr.co.uk/andotherstill using
> >> >> HTTP.
> >> >> I see able to login with other usernames fine on my own install, and
> >> >> the 401 don't always appear.
> >> >> It's happening on every machine I use, and all the cookies have been
> >> >> wiped multiple times.
> >> >> Before I end up pulling my code apart, are they any issues with
> >> >> changed passwords and HTTP auth requests?