Closed (duplicate)
Project:
Drupal core
Version:
6.9
Component:
update.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Mar 2008 at 09:57 UTC
Updated:
7 Feb 2009 at 00:21 UTC
Drupal 6.1 says it's "unable to fetch any information about available new releases and updates" (HTTP Server Request Fails) while the site is off-line (maintenance mode). It works fine when "on-line".
Comments
Comment #1
ekerazha commentedMoved to the correct "project" (I hope)
Comment #2
visual commentedhi all,
I have the same problem.
anyone knows how to fix it?
When I browse my web site. it's ok
but when I click admin, it will be very slow.
and i see error message in report.
It said "Unable to fetch any information about available new releases and updates."
Comment #3
gumdrop commentedI am getting the same issue. It was fine until I added the Feed Aggregator, CAPTCHA modules and Forum.
However, when I went back to "maintenance off-line mode" it was fine.
Comment #4
gregglesI have this problem as well with two sites on the exact same server using a multisite installation (so I know the code is the same). They have different modules installed, so I will see if that is the problem.
Comment #5
gregglesThere's a lot more information and help on #245990: HTTP request testing unreliable and may be undesirable so I'm marking this a duplicate of that. For what it's worth, the solution for me was just to get rid of the drupal_http_request_fails variable and let it get regenerated.
Comment #6
kenwright commentedPlease can someone tell me how to fix this.
Comment #7
greggles@kenwright - See http://drupal.org/node/245990
Comment #8
tryitonce commentedWell, the answer to this is easy - when you are off-line Drupal will not be able to look at the outside world.
So, when you are back "on-line" and have no problems connecting to check for updates and RSS feeds - then you are lucky.
There are so many discussions about the HTTP request status fails problem that some people must be going up their tree (looking for bananas ;) ) - including me that I started a node trying to structure the problem in the hope of finding an answer for all those many conditions why we might be getting this problem and help is greatly appreciate in finding this holy grail of the failing HTTP request. - http://drupal.org/node/370434.
At least there you can find a list of where else the problem is discussed - when you get lucky report back there. Thanks.
I also think if everyone would clearly state their set-up (host, local development host at home, etc.) everyone else might find it easier to relate to the various solutions - plus of course slightly more detailed explanations on how solutions came about would help beginners like me as well.