Error code 226 "This request looks like it might be automated." On "statuses/update" (all OVH IP blocked !)

PictaNews · 2014-02-14T05:25:33.000Z

I’m using the TwitterOAuth which allready use the SSL connection. Just tested my script on an other server and it works perfect. OVH has been blacklisted. That’s the second time this year. Last time they unblacklist us really fast but this one it seems to be longer. Hope they will fix it ASAP !

people_toptrend · 2014-02-14T13:27:44.000Z

Same problem for us, server on 213.186.33.xx
Our daily auto tweet post are blocked with an error of “226” : “This request looks like it might be automated.”

We use oauth authentication (themattharris oauth lib : tmhoauth).

What can we do ? Is it to twitter or OVH to do something?

StanMourdon · 2014-02-14T14:39:27.000Z

OVH suggested me to change my IP “country” but the result was identical.
So it seems it’s the whole set of IPs from OVH that may have been blocked (best theory so far) but without any confirmation from twitter, there is no way to be sure of what going on.

But @PictaNews test seems to prove without any doubt that the issue is related to OVH servers.

However, a word from Twitter to tell us what’s really going on would really be appreciated !

MMGLEX · 2014-02-14T15:02:42.000Z

Yes, I’m hosted at OVH too.

IP 213.186.33.xx

people_toptrend · 2014-02-14T15:08:07.000Z

Ok thanks for the reply.
Wait and see…

MMGLEX · 2014-02-14T15:12:36.000Z

I would like to specify that I get this error message using WP to Twitter plugin (for WP): “403 Forbidden: The request is understood, but it has been refused by Twitter. Reasons: Too many Tweets in a short time or the same Tweet was submitted twice, among others. Not an error from WP to Twitter.”

For this reason I suspected of recent SSL/api.twitter change, but I’m no expert.

thebluepennant · 2014-02-14T19:10:39.000Z

Same problem here !

StanMourdon · 2014-02-15T15:41:58.000Z

I confirm the exact same script is working well on dev server (home hosted) but is rejected from my production server hosted at OVH.
OVH mutualized servers have been banned somehow on twitter side.

The why is still a mistery. And how to fix it too.

PictaNews · 2014-02-16T18:26:22.000Z

That’s incredible, OVH is one of the biggest hosting in Europe! Twitter please you should do something. S’il vous plait, pour les personnes impactées par ce blocage envoyez une réclamation via le formulaire Twitter, c’est notre seule chance pour que le serveur soit enlevé de la blacklist rapidement!

StanMourdon · 2014-02-16T19:59:53.000Z

I also recommend to talk to OVH thru their support form.
At least they answer and they may try to do something on their side.

Je recommande également d’ouvrir un ticket de support chez OVH. Ils répondent (eux) et ils peuvent certainement parler à Twitter avec un autre poids que nous.

jeremy_gr · 2014-02-16T22:21:39.000Z

Same problem for me from 213.186.33.*
I use the API to post less than a tweet per day.

randotrekking · 2014-02-17T15:52:16.000Z

hello, same problem for me
i have openned a ticket at OVH support and waiting for an answer

jeremy_gr · 2014-03-03T18:04:00.000Z

A post has been opened in OVH French forums:

http://forum.ovh.com/showthread.php?97572-API-Twitter-un-blocage

lorrisb · 2014-02-19T11:57:02.000Z

It seems to be fixed Thank’s for your help

kompasito · 2014-02-20T22:26:35.000Z

C’est à nouveau bloqué.

Blocked again…

NDagnas · 2014-02-21T07:30:44.000Z

+1

StanMourdon · 2014-02-21T09:45:05.000Z

I’ve reopened my ticket at OVH…

TweetsAstuces · 2014-02-22T07:11:58.000Z

Problem solved only for one day and now API is blocked again. Is there anything that we can do at our level?

TweetsAstuces · 2014-02-22T07:15:52.000Z

Hi Stan, have you got evidence that OVH is talking / trying to solve this ssue with Twitter? Thanks, Dominique

StanMourdon · 2014-02-22T09:56:29.000Z

I have to trust what OVH support is telling me/writing on their forum : http://forum.ovh.com/showthread.php?97572-API-Twitter-un-blocage/page2

(that being said, they did not reopened their task from the first time it happend : http://travaux.ovh.com/?do=details&id=10258)