We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We are having issues with the twitter gem running 5.15.0.
The connection times out after about a minute with:
Connection timed out - connect(2) for \"199.16.156.20\" port
On a separate machine (on a separate network) we get the same error with a different IP address:
Connection timed out - connect(2) for \"199.16.156.217\" port
I am guessing that these are both IPs for stream.twitter.com (maybe they have a pool of IPs they cycle through?)
No issues reported on their API status page (https://dev.twitter.com/overview/status)
Rolling back to 5.14.0 seems to work fine on both machines.
The text was updated successfully, but these errors were encountered:
I think that this is a duplicate of #709
Sorry, something went wrong.
Apologies, looks like you're right.
On Mon, Sep 14, 2015 at 4:44 PM, David Celis [email protected] wrote:
I think that this is a duplicate of #709 #709 — Reply to this email directly or view it on GitHub #727 (comment).
I think that this is a duplicate of #709 #709
— Reply to this email directly or view it on GitHub #727 (comment).
No branches or pull requests
We are having issues with the twitter gem running 5.15.0.
The connection times out after about a minute with:
On a separate machine (on a separate network) we get the same error with a different IP address:
I am guessing that these are both IPs for stream.twitter.com (maybe they have a pool of IPs they cycle through?)
No issues reported on their API status page (https://dev.twitter.com/overview/status)
Rolling back to 5.14.0 seems to work fine on both machines.
The text was updated successfully, but these errors were encountered: