Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Working with BOA ( Barracuda / Octopus / Aegir ) , I've installed a few Drupal sites without any problems and following the same process for all.

BOA is running on Nginx. All sites are going thru Cloudflare's network , where I set the same DNS settings.

A points to IPADDRESS A www points to IPADDRESS

the nameservers of each domain are pointing to Cloudflare's respective nameservers.

It all works , except for one site that works perfectly without "www" , but with "www" returns the typical database error if Drupal can't find the site's database.

Site off-line The site is currently not available due to technical problems. Please try again later. Thank you for your understanding.

If you are the maintainer of this site, please check your database settings in the settings.php file and ensure that your hosting provider's database server is running. For more help, see the handbook, or contact your hosting provider.

In BOA, all sites have the same alias, basically a symlink, redirecting like this... ->

share|improve this question
Are the different requests hitting the same server in nginx? Are you certain there's no browser caching occurring for one site or the other? – Shane Madden Mar 28 '12 at 16:42
Yes, same server. Also I've cleared every cache I could find ( Cloudflare purge cache too ) the same thing happens on various computers. When I clone the site , I can't reproduce the problem!!! – PatrickS Mar 29 '12 at 0:39

Something isn't configured properly on your server & you should contact your hosting provider for assistance. A database error wouldn't be coming from CloudFlare & would be some sort of configuration issue directly on the server.

share|improve this answer
up vote 0 down vote accepted

Actually, it seems to have been a Drupal issue. I'm basically trying to bring up to date a Drupal website that's still at version 6.16 with loads of out of date modules.

With the exact same configuration and a different Drupal version, the error went away. I couldn't identify the issue, but knowing that it was an update problem was sufficient.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.