a few things I have found. This is totally from people saying they had the same problem..
one guy said " I was experiencing this same problem...but when I changed the path for the $serveDir variable while defining the configuration parameters to be the FULL pathname starting at root the problem was fixed."
(even I dont know what that means)
Another guy said that it was fixed when he uploaded a new index file to the main dir.
the last and most common reason for it was what this guy is talking about...
"The first thing to check is if you have a file called ".htaccess" in the directory you're trying to read. If this file contains instructions which the web server doesn't know how The first thing to check is if you have a file called ".htaccess"
in the directory you're trying to read. If this file contains
instructions which the web server doesn't know how to parse, then it will generate this error message, and the simplest way to fix the problem is to remove the file or replace it with an existing file from somewhere else.
Remember to make a copy of this file before you remove it! to parse, then it will generate this error message, and the simplest way to fix the problem is to remove the file or replace it with an existing file from somewhere else.
Remember to make a copy of this file before you remove it!
