"HTTP request status Fails" error

Last updated May 27, 2010. Created by Francewhoa on September 25, 2009.
Log in to edit this page.

Your Status report page located at admin/reports/status returns the following error

HTTP request status Fails
Your system or network configuration does not allow Drupal to access web pages, resulting in reduced functionality. This could be due to your webserver configuration or PHP settings, and should be resolved in order to download information about available updates, fetch aggregator feeds, sign in via OpenID, or use other network-dependent services.

Error screenshot. Under section HTTP request status

The most likely cause of this error is

You did nothing wrong. This is a well known issue in Drupal since around version 6.9. The community knows about it and is working on it. If you want to help fix this go to http://drupal.org/node/245990
A files format (character set) has been changed. For example when editing then saving your file your text editor changed the file format from UTF-8 Unicode to Latin1. Some text editor will change the file format without asking. Sometime inserting line brake or changing some characters.
A file got corrupted during transfer. For example while uploading a file via FTP.
A contributed module.

To fix this here are a few things you could try

Deactivate all contributed modules. Test if error is still there. If error is no longer there isolate the error by reactivating only one contributed module at a time. Test each contributed module if error is still there. When error shows you will know which contributed module causes the error. Replace appropriate contributed module file(s) with fresh file(s).
Install the module 'http_request_fail_reset'
Add a line of code at the bottom of your settings.php file
Add domain name to the list of host addresses.

For coders

Explanation of the error: http://drupal.org/node/245990#comment-909263
Error source: http://drupal.org/node/245990

Comments

php.ini

Posted by Observer8 on May 19, 2010 at 6:26am

Check your php.ini settings. disable_functions shouldn't contain fsockopen. If you see in php.ini:

disable_functions = something, fsockopen, something

change it to

disable_functions = something, something
or
disable_functions = 

It help's for me.

Of cause, it should also be
allow_url_fopen = On

And you can try to add
allow_url_include = On

HTTP request status

Posted by ingvarolsen on December 6, 2010 at 11:07am

Where do I find this php.ini?

Firewall configuration can trigger error

Posted by jewald on April 20, 2011 at 6:44pm

If your site is sitting behind a firewall, verify the web server can send and receive HTTP traffic to itself, using it's public URL.

In this scenario, the host server has an IP address in a private network space (10.x.x.x). The Drupal site attempts to contact itself using the URL designated for the site, for example, www.mysite.com. The traffic leaves the host web site, through the firewall and returns back to the same host. Some firewalls will see this as an attack and block the packets.

The workaround was to add the site name to the /etc/hosts file on the host server to force the traffic back through the host server's network interface.

Example host file entry:

10.0.0.34 www.mysite.com

That did it, thanks

Posted by roberthernandez on June 25, 2011 at 9:57pm

Thanks, I had that problem on some dev virtual boxes and this resolved it.

Port Forwarding

Posted by Siripong on November 18, 2011 at 8:34am

Host OS = Debian Wheezy

Guest OS = Drupal7
+ Apache (running on 80)
+ Debian Squeeze
+ NAT Network Adapter (forward host port 8888 to guest 80)
(Because of NAT limitation on UNIX host, I cannot configure 80 to 80)

After change Network Adapter to Bridge, the error gone.

http://drupal.org/node/245990#comment-909263 gave me the clue

Update on fixes

Posted by ekes on December 23, 2011 at 12:28pm

A patch has been added to both D7 and D6 - see linked issue in article.

Present fixes are:

Webserver can actually access out: add line to settings.php, see link in article
DNS: see the hosts file fix linked in article
Firewall: preventing out going traffic, see comment above
SE Linux: if you're running SE Linux (common default on Fedora, Redhat... systems) it prevents access by default. setsebool -P httpd_can_network_connect=1 will permit httpd to access the network.
Something else is breaking it: follow disable modules process in article above

Views 3.0

Posted by Aurochs on December 31, 2011 at 2:37am

I had this issue after creating a filter in a view. I made a view which showed all termsfrom a volcabulary (restricted about 10 terms) After that i created another filter NOT TO SHOW several of the terms and that was the problem. Maybe the filter came too heavy?
ps - sorry for commenting on "reply", did not notice "add comment" link.

http://gamepart.ru
http://temerhouse.ru
http://zubril.in