Help: Server unauthorized, not account?
42 views
Skip to first unread message
Darren Cook
Apr 14, 2013, 7:00:46 AM4/14/13
to phireho...@googlegroups.com
I have a couple of 24/7 filter processes running (different set of
keywords). They are on different servers, in fact one in the U.S., one
in the U.K.
The one in the U.K. has been fine; the one in the U.S. stopped working
Saturday (2013-04-13 00:00:00 UTC). The error is 401 unauthorized[1].
I logged in as the user, to twitter.com. No problems. So, here are
things I tried, each with no change:
* Switched from the /1/ to the /1.1/ API (and latest git version of
Phirehose at the same time)
* Recreated the app keys.
* Deleted the app, and created a new one.
* Created a new user, with a new app.
* Waited 10 hrs and tried again.
The thing that *did* work was running it from my notebook. First time,
no problems!
So, it appears the "unauthorized" is referring to the IP address of my
U.S. server, not to my account. Does anyone know anything about this? Is
it a rate-limiting thing and it will start working again? Or do I need
to abandon that server and set up a new one?
Or, my other guess was a DNS thing: maybe the U.S. server gets a
different IP address from DNS than my other servers, and there is
something wrong with one of the Twitter servers.
But this has actually happened a few times before, every 6 months or so.
The only fix each time has been a new user account, but that has always
fixed it. (Incidentally, the UK server has never had this problem, only
the U.S. server.)
I'm at a bit of a loss, so if anyone has any knowledge about what the
401 refers to, please let me know!
Darren
P.S. Both U.S. and U.K. servers are Rackspace cloud servers.
[1]:
HTTP failure 1 of 20 connecting to stream: HTTP ERROR 401: Unauthorized
(<html><head><meta http-equiv="Content-Type" content="text/html;
charset=utf-8"/><title>Error 401
Unauthorized</title></head><body><h2>HTTP ERROR: 401</h2><p>Problem
accessing '/1.1/statuses/filter.json'. Reason:<pre>
Unauthorized</pre>). Sleeping for 10 seconds.
--
Darren Cook, Software Researcher/Developer
http://dcook.org/work/ (About me and my work)
http://dcook.org/blogs.html (My blogs and articles)
keywords). They are on different servers, in fact one in the U.S., one
in the U.K.
The one in the U.K. has been fine; the one in the U.S. stopped working
Saturday (2013-04-13 00:00:00 UTC). The error is 401 unauthorized[1].
I logged in as the user, to twitter.com. No problems. So, here are
things I tried, each with no change:
* Switched from the /1/ to the /1.1/ API (and latest git version of
Phirehose at the same time)
* Recreated the app keys.
* Deleted the app, and created a new one.
* Created a new user, with a new app.
* Waited 10 hrs and tried again.
The thing that *did* work was running it from my notebook. First time,
no problems!
So, it appears the "unauthorized" is referring to the IP address of my
U.S. server, not to my account. Does anyone know anything about this? Is
it a rate-limiting thing and it will start working again? Or do I need
to abandon that server and set up a new one?
Or, my other guess was a DNS thing: maybe the U.S. server gets a
different IP address from DNS than my other servers, and there is
something wrong with one of the Twitter servers.
But this has actually happened a few times before, every 6 months or so.
The only fix each time has been a new user account, but that has always
fixed it. (Incidentally, the UK server has never had this problem, only
the U.S. server.)
I'm at a bit of a loss, so if anyone has any knowledge about what the
401 refers to, please let me know!
Darren
P.S. Both U.S. and U.K. servers are Rackspace cloud servers.
[1]:
HTTP failure 1 of 20 connecting to stream: HTTP ERROR 401: Unauthorized
(<html><head><meta http-equiv="Content-Type" content="text/html;
charset=utf-8"/><title>Error 401
Unauthorized</title></head><body><h2>HTTP ERROR: 401</h2><p>Problem
accessing '/1.1/statuses/filter.json'. Reason:<pre>
Unauthorized</pre>). Sleeping for 10 seconds.
--
Darren Cook, Software Researcher/Developer
http://dcook.org/work/ (About me and my work)
http://dcook.org/blogs.html (My blogs and articles)
Fenn Bailey
Apr 14, 2013, 3:30:34 PM4/14/13
to phireho...@googlegroups.com
Hey Darren,
That is weird. You can confirm/disprove the DNS issue by looking at the log output - Phirehose will spit out the IP address it is connecting to when it starts up. If you compare the US/UK, that should at least help you sort that out.
Other than that, it really does sound like your IP address got banned. There's two options that seem possible to me:
1) Something went wrong in your script which caused it to attempted to reconnect with bad parameters many times in a row (which can result in a ban). This shouldn't really happen as Phirehose (should) comply to proper reconnect back-off behaviour.
2) Your IP block got banned to do with someone else abusing it from Rackspace machines. ie: someone abusing the search API which triggered an automated system that caught you temporarily.
Either way, I would say the twitter developers list is actually the best place for this question, as it very much seems to be related to Twitter itself, rather than Phirehose specifically.
It'd be great if you let us know you findings - Cheers!
Fenn.
--
---
You received this message because you are subscribed to the Google Groups "Phirehose Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phirehose-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
barcla...@gmail.com
Jul 1, 2013, 10:45:38 AM7/1/13
to phireho...@googlegroups.com
Did you get a solution to this? I have the same issue from AWS - it just stopped working, I've checked the server time and it is in UTC and correct....
Darren Cook
Jul 1, 2013, 6:45:33 PM7/1/13
to phireho...@googlegroups.com
> Did you get a solution to this? I have the same issue from AWS - it just
> stopped working, I've checked the server time and it is in UTC and
> correct....
I started up a new virtual host (and new twitter account).
> stopped working, I've checked the server time and it is in UTC and
> correct....
That account had had quite a lot of restarts, over the space of months,
so I'm guessing the IP address hit some internal Twitter limit and got
banned?? (See my thread about "statusUpdate not being called regularly"
for why I got so many restarts.)
Darren
P.S. By "quite a lot" I guess maybe 10-12 each week, clustered at weekends.
Reply all
Reply to author
Forward
0 new messages