Tweets Not Updating

Hi Rick8rooke,

The error you are seeing is an internal WordPress error from the HTTP API (manages external requests). This means that it is making a request, but that nothing is received before it reaches the time limit and closes the connection.

Usually a response would be received within 500 milliseconds, so reaching 10000 ms without a response is very strange. I have just checked the server and cannot see any reason it would be preventing your connection. I have also double checked that the API is successfully returning Tweets and it is.

I think the likely culprit is something blocking the request/return, is your site hosted behind a company/organisation network?

Yes it is!

I am also seeing an error of:

11:23:31 – November 1, 2013 1 name lookup timed out

I am testing it locally, but it is also throwing up these errors on the live site – any ideas?

The live site is also showing:

09:47:08 – November 1, 2013
1 Operation timed out after 10000 milliseconds with 0 bytes received

Are both the live and local sites behind the same company/organisation network?

The ‘name lookup timed out’ means that even the basic request to get the IP address of the external domain timed out.

It seems likely from these error messages that there is either something wrong with the ability to make HTTP requests or that the network has begun blocking the requests.

I think the best course of action would be to talk to the IT department, as they could likely check that it can make successful HTTP requests easily.

You could also make sure that the network allows access to the API which the plugin runs all social requests through, which is at: 89.200.139.16

It is also worth checking the main WP Dashboard, many of the widgets there rely on external HTTP requests, so if they begin failing/having problems it could point to a general problem. They are cached and refreshed every 12 hours, so it might be a while until they are refresehed.

The domain name it is sitting on has just recently be redirected and the DNS servers reset so that may be causing the problem.

Thanks for your help, I will look into it further and post back if I get a fix.

Hi Rick8rooke,

It could well be linked to that, if it continues let me know.

I have been checking the API for errors and I cannot see any examples where no response was returned. I have also checked to make sure the bandwidth usage has not disproportionally changed compared to the number of requests. I will continue to monitor it.