Twitter error (Continued part II)

[mending 0]

When will this bug be fixed? http://www.pagelines.com/forum/discussion/12397/twitter-error-continued#Item_5

[Simon 248]

There isnt a 'bug' with the twitter code. It uses wordpress functions to fetch your latest tweet. If your still getting this error then either twitter have blocked your API access, or your server cannot communicate with twitter.

[mending 0]

But I've got two different sites that doesn't work and API is not blocked as it every now and then does work. http://wordpress.mending.dk http://www.lenewinther.com

[Simon 248]

Right if you want me to debug this i'll need access to your site. email me your admin to [email protected] I just tested both your twitter names, they both work.

[mending 0]

I've just testet both this minute and they don't work. Testet both with Safari and Firefox on Mac.

[Simon 248]

Its nothing to do with browsers, your server is not getting the api info from twitter. If you want me to look into it, i need access to your blog.

[mending 0]

Ok, I've send you the details to your email.

[Simon 248]

I have installed 'core control' which logs all out going http requests, here is a SS of its output: [IMG]http://i.imgur.com/QD9px.png[/IMG] As you can see were getting a 400 .. if you open that url in the browser you will get a screenfull of JSON. To quote from the twitter dev page: 400 Bad Request: The request was invalid. An accompanying error message will explain why. This is the status code will be returned during [b]rate limiting[/b]. As I already said your server is rate limited. It may not be you. There are 177 other sites all sharing your IP.

[mending 0]

Hi, I am not quite sure what all this means or what I can do about it? Does it mean that the server where the website is hosted (at www.one.com) is causing the problem?

[Simon 248]

Mending, yes afraid so, there are 177 sites on that server, and looks like you are not the only one trying to access the twitter API

[mending 0]

So apparently this limitation is caused by the fact that One.com is a shared hosting facility of many websites - some or all - trying to access the Twitter API? And the solution would be either to move to a provider offering dedicated hosting - or try to convince Twitter to expand their IP access limitation?

[Rob 547]

You may just need to upgrade your shared hosting package to a higher level and ask one.com why you're being blocked. They could just have a filter on your site or on that server that could be turned off. Additionally, in your site's control panel, you may be unaware of a setting that could be changed to open your access to that API. I'd suggest calling them.

[mending 0]

One.com does not offer any other packages than a standard shared hosting environment. What kind of filter would cause the blocking at One.com ? And what settings in the WordPress control panel are you referring to that I might be unaware about?

[Simon 248]

UM You guys are confusing each other. The server you are on has ONE IP. You are on shared hosting with 177 other people and their websites. Twitter has rate limited the servers IP because it is using the API too much. There is absolutly nothing you can do apart from move to an IP that is not rate limited. Think about using a VPS they are cheap and use dedicated IP's. Shared hosting has many drawback, shared IP being the big one.

[mending 0]

Right, thanks for explaining :-)