Closed superjoefly closed 7 years ago
I'm seeing wait timeouts on the oauth2_token unless I put the timeout over 2 minutes....
I'm also getting this response on a simple search call:
search() {
var cb = new Codebird;
cb.setConsumerKey("consumer_key", "consumer_secret")
cb.__call(
"search_tweets",
"q=" + this.term,
function (reply) {
console.log(reply);
}
);
} // => Object {httpstatus: 0}
I'm wondering if this has something to do with the proxy, my server, or with Twitter. I'm almost finished with my project...hopefully we can get this fixed soon :-)
I think it's the proxy server. I left a support message for jublo.net in any case.
I left a support message too... I'll post back when I hear from them.
Hi All,
We are currently investigating this and will post an update.
Thanks,
Josh
Apologies, we now appear to have brought the API to some stability. Although we will monitor over the next 48 hours.
I also get same issue whenever i was searching for "statuses_homeTimeline"
Issue still persists, we are still getting it, any idea?
I am also still experiencing this issue with social-feed (https://github.com/pavelk2/social-feed/issues/268). Tried to upgrade Codebird but it does allow access to https://api.jublo.net/codebird/oauth2/token. Chrome says that is fails to load response data from the address.
It's not working now, giving error Failed to load resource: net::ERR_CONNECTION_TIMED_OUT api.jublo.net/codebird/oauth2/token
confirmed! is not working
Does it work in the meantime?
seems it is working again now. Thanks
It seems that the Twitter authentication is not again working. https://api.jublo.net/codebird/oauth2/token is returning Connection timed out error.
same issue here, any updates regarding this?
Same issue
Same issue.
The following call to the Twitter API is returning: Object {httpstatus: 0};
Anyone know what could be causing this?
Thanks :-)