Boost comes with a module called "Boost Crawler". Boost crawler demands another module called "HTTP Parallel Request Library"

with Boost and these 2 mentioned modules activated i am getting that error code in the Status repport :

HTTPRL - Core	drupal_http_request()
Your system or network configuration does not allow Drupal to access web pages. This could be due to your webserver configuration or PHP settings. Debug info:
    [0] => Array
            [count] => 1
            [time] => 6286.39
            [mode] => 2
            [blocking] => 
            [url] =>

    [1] => Array
            [count] => 1
            [time] => 6310.36
            [mode] => 2
            [blocking] => 
            [url] =>

    [2] => Array
            [count] => 1
            [time] => 6153.21
            [mode] => 2
            [blocking] => 1
            [url] =>

    [3] => Array
            [count] => 1
            [time] => 6128.05
            [mode] => 1
            [blocking] => 
            [url] =>


For more info go here: "HTTP request status Fails" error

what is wrong?

Members fund testing for the Drupal project. Drupal Association Learn more


bgm’s picture

Project: Boost » HTTP Parallel Request & Threading Library
Version: 7.x-1.0-beta2 » 7.x-1.x-dev
Component: Cron Crawler » Code

This seems specific to httprl, so I will move it to their issue queue.

If I understand correctly, it seems that your server does not allow outgoing http connections. Some hosting providers block outgoing connections to avoid unsecure applications from spamming the web. Another way to confirm, is if Drupal's "update" module can check for new versions of your installed modules.

bavarian’s picture

Checking for updated versions of modules, themes or drupal core itself has never been a problem on that server. been using same hosting provider for quite a few years now ...

bavarian’s picture

At the end of this message there is a link in that sentence "For more info go here: "HTTP request status Fails" error" taking you to

In that thread there are several methods listed to resolve that ... like

1 - installing the module "http_request_fail_reset"
2 - adding a certain line of code at the end of the setting.php file
3 - adding the domain to the list of host addresses

method 1: there is no drupasl version of this module
method 2: does not help not help in my case either
method 3: does not help in my case either

Bandy’s picture

The problem I have too, but never found a solution.

mikeytown2’s picture

HTTPRL is testing to see if it can make a connection to its self. For some reason this is not working on your server (it is timing out). The boost crawler won't work as a result because it can not access the server it's hosted on via http requests.

The comments on is where the real troubleshooting is happening. There are some good recommendations in there that might fix the issue.

Questions for the people who have this issue:
Who are you using for your hosting?
If you have shell access on the server that is throwing this error what happens when you wget your druapl site?

bavarian’s picture

how would a "wget" commant in command line to a drupal site look like

> wget

or something like that? would that be correct?

mikeytown2’s picture

That is correct :)

Running wget
Outputs this to the command line.

--2012-11-10 18:32:39--
Connecting to||:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: [following]
--2012-11-10 18:32:40--
Connecting to||:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html'

    [ <=>                                                                                                 ] 2,966       --.-K/s   in 0s

2012-11-10 18:32:40 (579 KB/s) - `index.html' saved [2966]
bavarian’s picture

similar result here (unfortunately text from terminal in swedish, do i need to translate) ?

# wget
--2012-11-11 01:07:06--
Slår upp 46.xx.yyy.zz
Ansluter till|46.xx.yyy.zz|:80... ansluten.
HTTP-begäran skickad, väntar på svar... 302 Found
Adress: [följer]
--2012-11-11 01:07:07--
Ansluter till|46.xx.yyy.zz|:443... ansluten.
HTTP-begäran skickad, väntar på svar... 200 OK
Längd: ospecifierat [text/html]
Sparar till "index.html".

[ <=> ] 39 596 --.-K/s på 0,03s

2012-11-11 01:07:08 (1,09 MB/s) - "index.html" sparad [39596]

mikeytown2’s picture

The interesting thing is you redirect all http traffic to https. This shouldn't cause a timeout though. On your status report admin/reports/status what does it say for HTTPRL? Do you get 4 messages with each one of them taking 6+ seconds?

You also can try setting an IP address and seeing if that fixes the issue admin/config/development/httprl

bavarian’s picture

Funny, since there was no "support" for my issue here I had this module enabled for a couple of weeks now. Now when response started here in this issue, i re-enabled the module and NOW it is not generating that error message in the status report any longer .... for unknown reasons !

mikeytown2’s picture

My best guess at to what could be causing the issue you're describing has something to do with a firewall. Hopefully it doesn't happen again.

mikeytown2’s picture

Status: Active » Closed (cannot reproduce)

reopen if this happens again

fringedgentian’s picture


David4514’s picture

I do not know if there is a way to avoid this, but after messing around with this for an hour I ran across a not so closely related issue where it was the fact that they were in maintenance mode that was causing an http request to fail. So I gave it a try. Dropping out of maintenance mode fixed the problem. It appears that the http request is being rejected, probably because it is not authenticated in some way, when in maintenance mode.

David4514’s picture

I should have reopened the issue according to #12. See #14.

mikeytown2’s picture

Title: HTTPRL - Core drupal_http_request() error in Status repport » HTTPRL - Core drupal_http_request() error in Status repport (maintenance mode)
Status: Closed (cannot reproduce) » Active
mikeytown2’s picture

This check happens in _menu_site_is_offline(). Thinking about not runing the check if the site is in maintenance mode.

mikeytown2’s picture

Status: Active » Fixed
915 bytes

This patch has been committed to 6.x & 7.x. Thanks for the feedback on this one :)

David4514’s picture

I've tested the dev release with #18 on both a test and production system. Looks good. Thanks.

Status: Fixed » Closed (fixed)

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

jbfelix’s picture

I still have this error with the last dev release (7.x-1.14+16-dev) with #18 (drupal 7.28)
i have added my domain in the hosts file
i have added in the httprl config page

What else can i check to resolve this issue ?

mikeytown2’s picture

Open a new issue as this one is dealing with sites that are in maintenance mode.

W.M.’s picture

Everything worked fine until I upgraded from PHP 5.4.x to PHP 5.6.2. After the PHP upgrade I started to get the error message mentioned above.

W.M.’s picture

One site I have used mixed mode SSL and normal port 80. When I made it 100% SSL (redirecting all traffic to SSL 443), HTTPRL started to show those error messages that it cannot connect under Status Report page.

FranciscoLuz’s picture

I fixed it by visiting http://mydomain/admin/config/development/httprl and doing the following settings:

  • IP Address to send all self server requests to: Leave blank
  • Check both boxes at "Enable background callbacks" and "Use httprl to handle drupal_http_request."
emmonsaz’s picture

Thanks @FranciscoLuz - that worked great!

W.M.’s picture

The suggestion by @FranciscoLuz #25 did not solved the issue at my site. I am running a HTTPS only website (not mixed mode), Nginx 1.6.1, PHP 5.6.4.

@FranciscoLuz && @emmonsaz

Could you please tell us:

- What server you're running ?
- PHP version ?


FranciscoLuz’s picture


Apache, http, php v5.5

G0dLik3’s picture

I fixed it by going to http://mydomain/admin/config/development/httprl and setting the "IP Address to send all self server requests to" field to -1.

AdamMMA’s picture

#29 worked for me, thanks @G0dLik3

webengr’s picture

#29 worked for me
putting -1 into the config field.

maranjo’s picture

Phew. #29 worked, thanks for that G0dLik3.

andresc75’s picture

#29 worked for me on:
- HTTPS only site
- using Apache/2.4.6 (CentOS 7)
- PHP 5.4.16

madelyncruz’s picture

Ha! #29 worked for me. Thank you so much!

delacosta456’s picture

Ooooooh my God.. for almost 3 years and G0dLik3 save us with the #29 solution.
Thanks, thanks thanks.. drupal people's spirit of sharing forever en ever.

giupenni’s picture

#29 not works for me.

The problem persist.

PHP 5.5.32

hkirsman’s picture

I had -1 in the config and still getting the error.

ianchan’s picture

peterhebert’s picture

Combination of above solutions worked for me:

IP Address to send all self server requests to: -1
Check both boxes at "Enable background callbacks" and "Use httprl to handle drupal_http_request."
added my domain to hosts file

Note in my case, Ubuntu 14.04 had this at the top of the hosts file:

# Your system has configured 'manage_etc_hosts' as True.
# As a result, if you wish for changes to this file to persist
# then you will need to either
# a.) make changes to the master file in /etc/cloud/templates/hosts.tmpl
# b.) change or remove the value of 'manage_etc_hosts' in
# /etc/cloud/cloud.cfg or cloud-config from user-data

so I added the domain info to /etc/cloud/templates/hosts.tmpl and it seemed to work

mrandy543’s picture

#29 worked for me on HTTPS only site