By toddgeist on

Hello

I just moved to a new server and upgraded to 6.2 and now I am getting this in the status report.

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.

Can anyone shine any light on this

Thank you

Todd

⋅ Categories: Drupal 6.x

Comments

toddgeist’s picture

toddgeist commented

This does seem to be related to the upgrade to 6.2

I have another site on the same server that is running 6.1 and it does not throw this error in the status report

toddgeist’s picture

toddgeist commented

Taking the site out of maintenance mode fixed this.

Todd

izmeez’s picture

izmeez commented

I had this problem appear on Drupal 6.1 after working for several days. There is another thread on this subject http://drupal.org/node/227791 that offers more thoughts but I have not found a resolution that works for me, yet.

I have upgraded to Drupal 6.2 but this has not helped.

The problem may have started when I first put the site into offline mode and then back online. But, it does not fix it. I have gone back to Site maintenance and checked offline and emptied the cache and then back to online but still no luck. Is some variable not being set back?

Izzy

izmeez’s picture

izmeez commented

I have submitted the HTTP request status fails as an issue. http://drupal.org/node/245990

I am wondering if the problem is related to taking the site offline and then back online and some item that is altered is not being reset.

Izzy

izmeez’s picture

izmeez commented

I have posted the same message to the issue post that I created a few days back.

My humblest apologies to everyone.

I have discovered that my problem with the HTTP request status fails was a result of the .htaccess redirect to a secure site. When I commented out the .htaccess redirect lines the problem was resolved. I then removed the comments and was still able to update the feeds. I will keep an eye on this over the next few days and see if there is anything else I can learn.

Sorry for raising unwarranted concerns. I hope others did not spend too much time pondering my problem.

Thanks,

Izzy

parzoe’s picture

parzoe commented

I have our site locked down with a protected directory through our plesk control panel and am receiving this error after getting the cron job to see through the security:

lynx -auth=user:password -source http://oursite.com/cron.php > /dev/null 2>&1

I hate to sweat it but it would be nice to sort out for development purposes.