Viewing 4 replies - 1 through 4 (of 4 total)
  • I am having the same issue.

    Seems the API server is down but it only started when updated it to the lastest plugin.

    I too have experienced this in the past few days. A feed that was working no longer is. Twitter API changes perhaps?

    Plugin Author Peter Booker

    (@peterbooker)

    Hi guys,

    Thanks for letting me know, unfortunately this is my error in letting the domain expire. I am on my way home now and will see if I can get it back up quickly, if not I may need to release a plugin update later tonight with a domain change.

    Either way I will try to have it working again later tonight, sorry for the inconvenience to you all.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi again,

    I have just updated the plugin (1.5.11) to resolve this (switched domains). This should have been included in an earlier update to give people plenty of time to update, but was mistakenly not included. I updated my tests to use the new domain and so didn’t pick up on it breaking.

    I will try and get the old domain working again to resolve the issue for those who have not noticed yet, or who might take longer to notice.

    Sorry for the inconvenience caused.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Unable to connect to API – connection timed out’ is closed to new replies.