Moderator
James Huff
(@macmanx)
Volunteer Moderator
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. 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 Default theme (WordPress 1.5 – 2.9.2) or the Twenty Ten theme (WordPress 3.0 and higher) 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 (WordPress 1.5 – 2.9.2) or the Twenty Ten theme (WordPress 3.0 and higher) 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.
hi, what do you mean by renaming the .htaccess?
create a new file and upload again?
and will it be the problem of permission?
——————————–
in my .htaccess
——————————–
RewriteEngine On
RewriteBase /home/
#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>
——————————–
thanks a lo
Moderator
James Huff
(@macmanx)
Volunteer Moderator
hi, what do you mean by renaming the .htaccess?
Basically, just change the name to something like htaccess (remove the dot), but since you have a multisite installation, that would be very problematic.
Instead, proceed to the server error log.
my site: http://blog.do-did-done.com/
i juz notices that only the main page and admin page can be accessed.
‘about’ page occurs the internal problem also.
all plugins are inactivated and twenty-ten theme is used.
thanks
i’ve changed the .htaccess
old: RewriteBase /home/
new: RewriteBase /
now the subsite can be accessed, however the main site is keep loading.
main: http://blog.do-did-done.com/
sub: http://blog.do-did-done.com/lameian/
lameian – when you changed the .htaccess did you also move the site?
Of note, you CANNOT have WordPress installed in a subfolder and ‘act’ as if it’s in Root with MultiSite. If WordPress is in the HOME folder, then there it must stay and that must remain in your URL. Period.
