Weird auth page just since today


I’m (again just as of today) NOT getting a 401, but users are getting a very strange page when we redirect them to Twitter auth. Instead of the normal sign in to authorize to our application, they’re getting:

“Whoa there!
The request token for this page is invalid It may have already been used, or expired because it is too old…”

I’m using the 1.1 API (thru Twitter4j 3.03), and haven’t changed anything in weeks (at least).

Any help at all would be greatly welcome. I tried looking at the other discussions, but they don’t seem to apply to my case.

Thanks in advance,


We’re looking into this; thanks for reporting it.


Hmm, working again this morning. Thanks (I guess).