.htaccess and internal server error

Can I ask what host you are using?

I have the same problem with my debian etch.
Commenting the lines above didn't solve the problem.
What could you advice me ?

I spent a while fiddling with .htaccess until I managed to get it working. Here's the one that worked for me in the end:

#
# Apache/PHP/Drupal settings:
#

# Protect files and directories from prying eyes.
<FilesMatch "(\.(engine|inc|install|module|sh|.*sql|theme|tpl(\.php)?|xtmpl)|code-style\.pl|Entries.*|Repository|Root)$">
  Order deny,allow
  Deny from all
</FilesMatch>

# Set some options.
##Options -Indexes
##Options +FollowSymLinks

# Customized error messages.
ErrorDocument 404 /index.php

# Set the default handler.
DirectoryIndex index.php

# Override PHP settings. More in sites/default/settings.php
# but the following cannot be changed at runtime.

# PHP 4, Apache 1
##<IfModule mod_php4.c>
##  php_value magic_quotes_gpc                0
##  php_value register_globals                0
##  php_value session.auto_start              0
##</IfModule>


# Reduce the time dynamically generated pages are cache-able.
<IfModule mod_expires.c>
  ExpiresByType text/html A1
</IfModule>

# Various rewrite rules.
<IfModule mod_rewrite.c>
  RewriteEngine on

  # If your site can be accessed both with and without the prefix www.
  # you can use one of the following settings to force user to use only one option:
  #
  # If you want the site to be accessed WITH the www. only, adapt and uncomment the following:
  # RewriteCond %{HTTP_HOST} !^www\.example\.com$ [NC]
  # RewriteRule .* http://www.example.com/ [L,R=301]
  #
  # If you want the site to be accessed only WITHOUT the www. , adapt and uncomment the following:
  # RewriteCond %{HTTP_HOST} !^example\.com$ [NC]
  # RewriteRule .* http://example.com/ [L,R=301]


  # Modify the RewriteBase if you are using Drupal in a subdirectory and
  # the rewrite rules are not working properly.
  #RewriteBase /drupal

  # Rewrite old-style URLs of the form 'node.php?id=x'.
  #RewriteCond %{REQUEST_FILENAME} !-f
  #RewriteCond %{REQUEST_FILENAME} !-d
  #RewriteCond %{QUERY_STRING} ^id=([^&]+)$
  #RewriteRule node.php index.php?q=node/view/%1 [L]

  # Rewrite old-style URLs of the form 'module.php?mod=x'.
  #RewriteCond %{REQUEST_FILENAME} !-f
  #RewriteCond %{REQUEST_FILENAME} !-d
  #RewriteCond %{QUERY_STRING} ^mod=([^&]+)$
  #RewriteRule module.php index.php?q=%1 [L]

  # Rewrite current-style URLs of the form 'index.php?q=x'.
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
</IfModule>

# $Id: .htaccess,v 1.73 2006/04/14 09:08:26 killes Exp $

I had the same problem when first installing Drupal and my ISP explained that "Options +FollowSymLinks" and "Options -Indexes" are applied already by default for security reasons.

I also tested each .htaccess variable setting by commenting/uncommenting them individually from the default Drupal version and found that only "Options +FollowSymLinks" and "Options -Indexes" and the following:

# PHP 4, Apache 1
<IfModule mod_php4.c>
  php_value magic_quotes_gpc                0
  php_value register_globals                0
  php_value session.auto_start              0
</IfModule>

caused the error outlined in the original post.

These settings I commented out and left everything else as it was and it worked fine including "DirectoryIndex index.php". It is better to only remove settings that are actually causing errors.

I had the same problem before I could do the installation.

Had to comment out the following:

# Don't show directory listings for URLs which map to a directory.
####Options -Indexes

# Follow symbolic links in this directory.
####Options +FollowSymLinks

# Customized error messages.
ErrorDocument 404 /index.php

# Set the default handler.
####DirectoryIndex index.php

Drupal 5.1
GD library bundled (2.0.28 compatible)
MySQL database 4.1.15
PHP 5.2.1-0.dotdeb.1
Unicode library PHP Mbstring Extension
Web server Apache2.0.54 (Debian GNULinux) mod_ssl2.0.54 OpenSSL0.9.7e

Bert.

I removed my htaccess file to see if the site would break for testing, then put the file back but get these symbols..

‹

How do I resolve this problem?

AntSEO

I've found a way to make Drupal work with XAMMP for OSX. (10.5)
edit the httpd.conf. in xampp/etc/ explained in the link below. Don't forget to restart Xampp!

thanks to this post:

http://drupal.org/node/10133#comment-917298

http://drupal.org/node/31725#comment-79506

Brought down my site editing the .htaccess file even restored the backup and still couldn't get site up, went on a bunch of different forums for .htaccess problems, tried commenting out, commenting in lines in .htaccess nothing worked. So this is what I did.

Actually just did a mock reinstall of drupal 6.0 and it worked. (Backup your site first and the SQL database files!)

went into the www/sites folder and added a folder called mysite.com (just use the same name as your site) and placed a new settings.php file in there gave write permission and then you put open install.php in a browser or mysite.com/install.php

Go to settings.php and edit your file and place your host info into line 92 or
$db_url = 'mysql://username:password@localhost/databasename';

and then go to mysite.com/install.php and enter in all data to install username pass, localhost etc...

Click to install and it will come up and say site is already installed see existing site and this worked for my site came right up.

First tried by editing .htaccess file to remove comment from RewriteBase /. But its not worked for me.

Then setting memory limit double to the existing one given success.

Same problem.
My configuration is Suse Linux Enterprise Server 12 SP2, Apache/2.4.23.
I've modified .htaccess in order to solve the issue, replacing
Order allow,deny with Require all granted at line 7 of original .htaccess.
I think this problem is because newer version of apache has a new directive: Require.

At https://httpd.apache.org/docs/2.4/upgrading.html is reported:

Mixing old and new directives

Mixing old directives like Order, Allow or Deny with new ones like Require is technically possible but discouraged. mod_access_compat was created to support configurations containing only old directives to facilitate the 2.4 upgrade. Please check the examples below to get a better idea about issues that might arise.