I had Twitter module correctly configured in www.ignacionieto.com with my Twitter App. I created the App and filled in the OAuth Consumer key and the OAuth Consumer Secret in admin/config/services/twitter/settings. In admin/config/services/twitter I'm pulling tweets from a Twitter account, which is the only thing I was doing with the module, and everything has worked just fine, but a month ago it stopped being able to pull tweets.

Log shows the following error when running cron:

exception 'TwitterException' with message 'Connection timed out' in /home/alan/public_html/sites/all/modules/twitter/twitter.lib.php:151 Stack trace: #0 /home/alan/public_html/sites/all/modules/twitter/twitter.lib.php(114): Twitter->request('https://api.twi...') #1 /home/alan/public_html/sites/all/modules/twitter/twitter.lib.php(1226): Twitter->auth_request('https://api.twi...', Array, 'GET') #2 /home/alan/public_html/sites/all/modules/twitter/twitter.lib.php(204): Twitter->call('statuses/user_t...', Array, 'GET') #3 /home/alan/public_html/sites/all/modules/twitter/twitter.lib.php(278): Twitter->get_statuses('statuses/user_t...', Array) #4 /home/alan/public_html/sites/all/modules/twitter/twitter.inc(151): Twitter->user_timeline('963198444', Array) #5 /home/alan/public_html/sites/all/modules/twitter/twitter.module(217): twitter_fetch_user_timeline('963198444') #6 [internal function]: twitter_cron() #7 /home/alan/public_html/includes/module.inc(866): call_user_func_array('twitter_cron', Array) #8 /home/alan/public_html/includes/common.inc(5351): module_invoke('twitter', 'cron') #9 /home/alan/public_html/modules/system/system.admin.inc(2356): drupal_cron_run() #10 [internal function]: system_run_cron() #11 /home/alan/public_html/includes/menu.inc(519): call_user_func_array('system_run_cron', Array) #12 /home/alan/public_html/index.php(21): menu_execute_active_handler() #13 {main}

Do anyone have an idea of what may I be missing? Thank you very much in advanced.

Comments

DamienMcKenna’s picture

Category: Bug report » Support request
Priority: Critical » Normal

Sounds like either a network problem, or maybe the SSL certs changed and your server no longer accepts them.

Out of interest are you able to do this command on your server?
curl -I https://api.twitter.com/

What does it say?

DamienMcKenna’s picture

Status: Active » Postponed (maintainer needs more info)
stropharis’s picture

It takes a really long time, and then:

# curl -I https://api.twitter.com/
curl: (7) couldn't connect to host

DamienMcKenna’s picture

Status: Postponed (maintainer needs more info) » Fixed

That indicates there's a problem with your hosting provider blocking connections to api.twitter.com, so please check with them to find out what's going on.

stropharis’s picture

Thank you. It was indeed a firewall configuration issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.