500 Internal Server Error. '.htaccess' file within a subdirectory

  • guarriman

    (@guarriman)


    11 years, 6 months ago

    Hi.

    Using WordPress 4.0 on FreeBSD, I get a 500 Error (Internal Server Error) message when accessing
    http://www.mysite.com/blog_dir/

    Under parent directory (http://www.mysite.com/) I created an ‘.htaccess’ file with lots of Rewrites which work propertly
    http://www.mysite.com/item/foo/
    http://www.mysite.com/news/whatever/
    …

    Under the subdirectory (http://www.mysite.com/blog_dir/) I created an ‘.htaccess’ with the default WordPress stuff:
    —————-

    # BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog_dir/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog_dir/index.php [L]
</IfModule>
# END WordPress

    ——————-

    What am I doing wrong? The same configuration works ok in an Ubuntu WordPress 4.0 machine.

    I read that this issue may be due to a corrupt ‘.htaccess’, but I uploaded it twice (another way to check it?).

    Thank you very much in advance.

Viewing 1 replies (of 1 total)
  • Moderator James Huff

    (@macmanx)

    11 years, 6 months ago

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the Twenty Fourteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

Viewing 1 replies (of 1 total)

The topic ‘500 Internal Server Error. '.htaccess' file within a subdirectory’ is closed to new replies.

Tags