Skip to content
New issue

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

Failed to connect to api.twitter.com port 443: Timed out #475

Closed
ParagBansod opened this issue Jul 4, 2016 · 2 comments
Closed

Failed to connect to api.twitter.com port 443: Timed out #475

ParagBansod opened this issue Jul 4, 2016 · 2 comments

Comments

@ParagBansod
Copy link

ParagBansod commented Jul 4, 2016

Dear Abraham,
Thanks for your response and suggestion for my earlier issue #474 which is closed.

I followed your suggestion but I got the following error.

$connection = new TwitterOAuth($consumer_key, $consumer_secret, $access_token, $access_token_secret);
$connection->setTimeouts(10, 15);
$connection->get("statuses/retweets/748452817724022784");

Please suggest me to correct this.
Fatal error: Uncaught exception 'Abraham\TwitterOAuth\TwitterOAuthException' with message 'Failed to connect to api.twitter.com port 443: Timed out' in D:\xampp\htdocs\twitteroauth\twitteroauth\src\TwitterOAuth.php:401 Stack trace: #0 D:\xampp\htdocs\twitteroauth\twitteroauth\src\TwitterOAuth.php(333): Abraham\TwitterOAuth\TwitterOAuth->request('https://api.twi...', 'GET', 'Authorization: ...', Array) #1 D:\xampp\htdocs\twitteroauth\twitteroauth\src\TwitterOAuth.php(304): Abraham\TwitterOAuth\TwitterOAuth->oAuthRequest('https://api.twi...', 'GET', Array) #2 D:\xampp\htdocs\twitteroauth\twitteroauth\src\TwitterOAuth.php(178): Abraham\TwitterOAuth\TwitterOAuth->http('GET', 'https://api.twi...', 'statuses/retwee...', Array) #3 D:\xampp\htdocs\twitteroauth\index.php(36): Abraham\TwitterOAuth\TwitterOAuth->get('statuses/retwee...') #4 {main} thrown in D:\xampp\htdocs\twitteroauth\twitteroauth\src\TwitterOAuth.php on line 401

@abraham
Copy link
Owner

abraham commented Jul 4, 2016

It's probably a network issue on your side. Twitter servers generally respond under a second. I would suggest looking into firewalls and network filters that could be blocking requests.

@ParagBansod
Copy link
Author

Dear Abraham
Thanks for your reply.
Things are working fine as it was server issue.

@abraham abraham closed this as completed Jul 6, 2016
Repository owner locked and limited conversation to collaborators Dec 30, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants