Drupal Answers is a question and answer site for Drupal developers and 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

After moving a site to the final server, I cannot anymore access the site. When I go to the home page, I get a WSD on Firefox, and a 500 error on Google Chrome.

As it is a shared hosting, I cannot access the Apache error log, and I am wondering if anyone experienced that before. How did you find your way out of it?

share|improve this question
If you actually can't view your own error logs you need to get a new host. – rfay Sep 26 '11 at 5:53
You either failed to copy the .htaccess file or there could be a file like default.html in the root directory taking more precedence over index.php – Sivaji Sep 27 '11 at 17:49
Yeah good advice, but are you sure i would get a 500 error in that case ? Though i checked and i just have index.php in that particular directory. Thanks for your input – silkAdmin Sep 28 '11 at 16:59
Could it be something with different timeouts on different browsers? – john Sep 29 '11 at 15:12
up vote 6 down vote accepted

The article about The White Screen of Death (Completely Blank Page) is a good place to start.

Depending on your shared host, you can often get access to logs if you poke around your control panel, or they sometimes are copied into your home directory.

Since you explicitly mentioned shared hosting, your best best is to open a trouble ticket. They can tell you exactly what is wrong fairly easily.

If it is a true 500 error, then my guess is that one of these two lines in the .htaccess is causing the problem.

Options -Indexes
Options +FollowSymLinks

You can try commenting them out one at a time and see what happens. I suspect that your host has AllowOverride set to None and one of those is trying to set a non-default value that the host has set.

share|improve this answer
Thank you MPD, suggestion much appreciated. I can not test them right now but i should be able to very soon. I ll make sure to let every one knows how that turns out. – silkAdmin Sep 28 '11 at 16:57

To answer your main question, nothing is making the server behave differently based on your browser - it's just the browsers displaying the results of a 500 error differently.

But, as for a solution to the underlying 500 error - other things to check;

PHP version - is the final server running a different version?

PHP memory limit

share|improve this answer
Thanks for the hint Garry, as i mentioned above i have to hold on for this issue but i ll make sure to keep this question update when the time comes – silkAdmin Sep 28 '11 at 16:58

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.