Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I have followed all the suggestions at http://drupal.org/node/549834
I have made sure that port 80 is open and that the http://updates.drupal.org IP 140.211.166.6 is not blacklisted (BH says they do not whitelist)
I made a fresh install of D 6.13 with and update fails, even when the ONLY modules enabled are dblog and update
Could it be a problem with my IP 69.89.31.246 - I have heard that Malwarebytes Anti Malware blocks it and hosts-file.net lists problems with 70 other domains on the IP http://hosts-file.net/?s=69.89.31.246
I'm planning to dump BH - but in the meantime - WTF is the problem?
Comment | File | Size | Author |
---|---|---|---|
default_recent_log_entries.jpg | 86.27 KB | decibel.places | |
default_unable.jpg | 62.78 KB | decibel.places | |
default_unable_details.jpg | 43.97 KB | decibel.places |
Comments
Comment #1
decibel.places CreditAttribution: decibel.places commentedcorrecting Issue title typo
Comment #2
decibel.places CreditAttribution: decibel.places commentedupdated to 6.14, still same problem
Comment #3
dwwSounds duplicate with #512218: Checking for available modules fails for most of the modules
Comment #4
decibel.places CreditAttribution: decibel.places commentedthe problem is that these threads do not provide solutions - people just say the problem goes away mysteriously - I suspect changes in server settings - but my concern/question is could it be a "blacklisting" by the Drupal server for certain shared IPs? I have been planning to dump Bluehost and this will just hasten that.
Comment #5
nnewton CreditAttribution: nnewton commentedRemoving this from duplicate. A lot of these issues need to be dealt with individually.
@decibel: If you could post the IP I'll see what is going on. Thanks for the report.
Comment #6
decibel.places CreditAttribution: decibel.places commentedthank you for your attention Narayan - I think more people than we know have this kind of issue - but their hosting co fixes the blacklisting and it goes away
I stated in the OP
but hosts-file.net now reports 81 suspicious domains in my IP range
Comment #7
nnewton CreditAttribution: nnewton commentedI found your IP on www4 and unblocked it. Can you please try again. Thanks.
-N
Comment #8
decibel.places CreditAttribution: decibel.places commentedyes, update is working on my site and the BlueHost test site - but I am not familiar with "www4" and I tried to Google it - what is "www4"?
Comment #9
decibel.places CreditAttribution: decibel.places commentedOk, I got the skinny from Narayan.
The main issue may have been a buggy Drupal release several versions back that creates too many requests to the update server and causes the domain to be blocked. The current releases are fine.
"www4" is a web node accessed through a load-balancer node. nobody accesses it directly - probably the reason why some of my update requests went through and others didn't. This is actually beginning to make sense.
the solution? Keep your code up to date.
(haha - but what if you can't connect to the update server, you ask? well, you can tell if you are using the latest version of core which includes the update module, just check the front page of d.o.)
Narayan advised me:
Contact the Drupal Infrastructure team. http://drupal.org/project/issues/infrastructure
Edited by dww: since we're editing this comment instead of reading the follow-up, I removed the email address. Contact the infra team via issues if you actually want something done -- email is where requests go to get lost and die. ;)
Comment #10
dwwRe: However, I'm not sure how to reach the Drupal Infrastructure team
http://drupal.org/project/issues/infrastructure
Comment #11
oliverstoney CreditAttribution: oliverstoney commentedOur server has not been able to update since 6.14 was installed. How do you get your server unbanned for updates?
Comment #12
decibel.places CreditAttribution: decibel.places commentedIf you have tried everything else - file an issue with the Drupal Infrastructure team, be sure to include your site's domain and/or IP
http://drupal.org/project/issues/infrastructure
My IP was banned on one node, so some update information was displayed and others failed - and different info was displayed each time - now it is updating fine after the block was removed.