The MU forums have moved to WordPress.org

404 error after install (12 posts)

  1. savagemike
    Member
    Posted 13 years ago #

    Well I followed the instructions to install Wordpress MU, but when I click on the "log in" button I get a 404 error. My .htaccess file reads as follows:

    RewriteEngine On
    RewriteBase /wordpressmu/

    #uploaded files
    RewriteRule ^(.*/)?files/$ index.php [L]
    RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
    RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]

    # add a trailing slash to /wp-admin
    RewriteCond %{REQUEST_URI} ^.*/wp-admin$
    RewriteRule ^(.+)$ $1/ [R=301,L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule . - [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]

    <IfModule mod_security.c>
    <Files async-upload.php>
    SecFilterEngine Off
    SecFilterScanPOST Off
    </Files>
    </IfModule>

    I have it currently installed on a subdomain, http://mu.asavagebydesign.com
    I cannot for the life of me figure out why it is doing this, as when I initially went there it seemed to work fine. It was only after giving it my DB information and attempting to log in that this is happening. The actual error reads:
    The requested URL /wordpressmu/wordpressmu/wp-signup.php was not found on this server.

    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

  2. savagemike
    Member
    Posted 13 years ago #

    OK update here... Now the 404 error is gone. But the pages all load up without CSS, and when I attempt to log in, it simply reloads the log in page. I am flabbergasted.

  3. tdjcbe
    Member
    Posted 13 years ago #

    I have it currently installed on a subdomain, http://mu.asavagebydesign.com

    Actually you don't. You have your site in an iframe and the files are installed in mu.asavagebydesign.com/wordpressmu/ As noted in the readme file, please install the files within root of where you;re going to run your site from, in this case mu.asavagebydesign.com.

  4. savagemike
    Member
    Posted 13 years ago #

    Well that is exactly where I put them. If there is indeed an iframe it was not of my doing. Is there anyway to fix this?

  5. savagemike
    Member
    Posted 13 years ago #

    I look at at my directory structure with Filezilla and double check my subdomain setup and everything looks correct. The subdomain points to http://asavagebydesign.com/wordpressmu and the wordpress mu files are all in there. There is no directory called http://mu.asavagebydesign.com/wordpressmu, so I am confused as to why this is occuring.

  6. savagemike
    Member
    Posted 13 years ago #

    OK I am on the phone now with GoDaddy. I have this subdomain and the directory structure set up exactly the same as the way I have my normal wordpress set up at http://blog.asavagebydesign.com so I am assuming the issue is on their end.

  7. savagemike
    Member
    Posted 13 years ago #

    Well that was productive. They don't know why this is happening either. I am trying a re-install. If the same error keeps occurring (iframe and all) does anyone know why this may be?

  8. savagemike
    Member
    Posted 13 years ago #

    OK I give up. There must be something about the way my .htaccess or php.ini or apache or something is set up because all I do is upload the directory containing all of the files and rename the directory so my subdomain points at it. I open it in my browser, fill out the DB information, then click "log in". And every single time it's broken.

  9. savagemike
    Member
    Posted 13 years ago #

    OK I fixed it. :-)

  10. VentureMaker
    Member
    Posted 13 years ago #

    So, what was that? :)

  11. Pegasus-18
    Member
    Posted 13 years ago #

    Would be good to know. GoDaddy, htaccess or db issue? ;-)

  12. blogz
    Member
    Posted 13 years ago #

    Seems like there is still some problem in it. Its giving me 403 error.

About this Topic

  • Started 13 years ago by savagemike
  • Latest reply from blogz