• I’m something of a newbie to wordpress (though I used to have a b2 blog), and I’m attempting to do step 5. of the readme: namely, “Launch /wp-admin/install.php in your browser.” The difficulty I am having has to do with permissions on my server, I think. Whenever I attempt this command I get the error message: Forbidden
    You don’t have permission to access /blog/wp-admin/install.php on this server.
    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.”
    Additionally, I ran into this same problem on step 4: “Point your browser to wp-admin/install-config.php” and had to create a manual wp-config.php file from the sample file provided. Because I got the same results from running an installer in step 4, I’m resonably certain this is the same error. However, I’m at a loss to understand what that error is, exactly.
    My server is running PHP version 4.3.3 and MySQL version 4.0.15-standard. Additionally, I am using IE version 6.0.28. I hope this is enough information to recognize my problem. Thank you for your time.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The permissions may be wrong ?
    Try setting the permissions to 755 or 766 ?
    If you aren’t sure how to do that with your ftp client, post back here ??

    Thread Starter senbei

    (@senbei)

    Well, I tried CHMODing the files and I still got the error: “Forbidden
    You don’t have permission to access /blog/wp-admin/install.php on this server.
    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request”
    I’m at my wits end. This part of my site has been down for quite some time and it’s really starting to make me feel incompetent. xP

    Senbei,
    Have you entered in the necessary database information in the WP-CONFIG.PHP file? You can check out some instructions here which may help. Look specifically at item number five.
    HTH.
    Craig.

    I just had and fixed an identical problem with Fedora FC4. If your server is running selinux, and you moved the files into the apache directory, you may have hit a bug with how selinux tracks file permissions. See:
    https://www.issociate.de/board/post/182411/Sub_directories_forbidden.html

    What made me suspicious was I could not access /blog/readme.html, but the same file with the same permissions worked from /

    My fix was simple: I disabled selinux. Reboot

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Forbidden = Failure’ is closed to new replies.