Blocked IP range for Available Updates Report? [#2656242]

We're trying to understand why the available updates report on our Drupal instances has stopped working. The problem appeared around the 13-15th of January. Checking for avaialble updates via the gui or via drush just returns "Failed to get available update data for (all modules are listed)"

This occurs across all 3 of our Drupal hosts.

The usual fixes of clearing the cache_update table manually, adding specific host name, IP data to the /etc/host file have not fixed this.

Just wondering if perhaps our IP has been blocked at the drupal.org end of things.

The most common outward facing IP would be 129.55.200.20, though there is occasional other use of other addresses in the 129.55.*.* range.

Thanks for your help.

Bobb Menk
MIT Lincoln Laboratory Library
bmenk@ll.mit.edu

Comments

Comment #1

25 January 2016 at 14:50

bmenk created an issue. See original summary.

Comment #2

drumm

he/him

NY, US

CreditAttribution: drumm at Drupal Association commented 25 January 2016 at 15:04

This is probably #2646894: Redirect http://updates.drupal.org and http://ftp.drupal.org to https version (roll back the updates.drupal.org part?). We very rarely block IPs.

A good immediate solution might be getting the update status from https directly:

drush vset update_fetch_url 'https://updates.drupal.org/release-history' (or equivalent settings.php change)

Comment #3

bmenk CreditAttribution: bmenk commented 25 January 2016 at 15:29

A couple of observations on this I should have thought of originally.

We are behind a proxy.
This is Drupal 7

In settings.php I don't see any update_fetch_url settings at all for any of our instances.

We do use the $conf lines in settings.php to provide the proxy info to Drupal

We installed the cURL HTTP Request in one Drupal instance and altered settings.php to use either http or https. No change.

Tried the drush vset update_fetch_url 'https://updates.drupal.org/release-history' command as above. No change in either the cURL instance or the straight wget instance.

Further ideas?

Thanks

Bobb Menk

Comment #4

drumm

he/him

NY, US

CreditAttribution: drumm at Drupal Association commented 25 January 2016 at 22:28

Can you use command line curl -v https://updates.drupal.org/release-history/drupal/7.x with arguments to use the same proxy to see what the exact response is?

Comment #5

bmenk CreditAttribution: bmenk commented 26 January 2016 at 18:58

The command line curl -v https://updates.drupal.org/release-history/drupal/7.x just times out for me.

In the end here's what worked:

Installed the cURL module (chr) and checked the config box to use curl rather than wget.

Edited settings.php following the syntax used in the chr module's README. Be aware that a syntax error in that file caused us a fair amount of work till we caught it.

This worked:
$conf['drupal_http_request_function'] = 'chr_curl_http_request';

The corresponding line in the README did not work:
$conf['drupal_http_request_function'] = 'chr_curl_http_request']; (extra close bracket at the end of the line)

Also just enabling the chr module and checking the box in the configuration options did not work by itself. Presumably it makes the variables used in the revised proxy settings within settings.php available though.