<p>More information about this error may be available
in the server error log.</p>
ok, so whats in the error log?
whats in any of your .htaccess files?
I restored the .htaccess file to the original content so I am now able to get to my admin login screen.
Now I just need to fix my RSS feeds. Here is the error log.
38.108.180.152 - - [25/Apr/2009:01:15:55 -0700] "GET /pedalheadblog.com/robots.txt HTTP/1.1" 404 231 "-" "Mozilla/5.0 (compatible; ScoutJet; +http://www.scoutjet.com/)"
38.108.180.152 - - [25/Apr/2009:01:15:56 -0700] "GET /pedalheadblog.com/ HTTP/1.1" 200 4676 "-" "Mozilla/5.0 (compatible; ScoutJet; +http://www.scoutjet.com/)"
38.108.180.152 - - [25/Apr/2009:01:15:58 -0700] "GET /pedalheadblog.com/wp-content/themes/ships-ahoy/favicon.ico HTTP/1.1" 200 12342 "-" "Mozilla/5.0 (compatible; ScoutJet; +http://www.scoutjet.com/)"
72.47.228.155 - - [25/Apr/2009:01:35:53 -0700] "HEAD /pedalheadblog.com/wp-cron.php?check=8c537884c13465b89d86b7634819c308 HTTP/1.0" 200 - "-" "WordPress/2.7.1"
66.249.73.153 - - [25/Apr/2009:01:35:53 -0700] "GET /pedalheadblog.com/?feed=rss2 HTTP/1.1" 500 389 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
66.249.73.153 - - [25/Apr/2009:01:36:55 -0700] "GET /pedalheadblog.com/?feed=rss2 HTTP/1.1" 500 389 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
66.249.73.153 - - [25/Apr/2009:01:37:57 -0700] "GET /pedalheadblog.com/?feed=rss2 HTTP/1.1" 500 389 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
66.249.73.153 - - [25/Apr/2009:01:38:58 -0700] "GET /pedalheadblog.com/?feed=rss2 HTTP/1.1" 500 389 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
Here is the contents of my .htaccess file:
AddHandler php5-script .php
I have been having this problem. I believe (or is it hope) that I have now solved it.
Since upgrading to 2.8 yesterday evening, I have had Error 500 Internal Error messages as I move around in the wp-admin areas. Today I have deactivated and renamed all of the plugins in my wp-content/plugins/ folder (including index.php and hello.php), changing them all to .old
I then renamed each of them one-by-one and activated them in the plugins area of wp-admin until I found one in particular immediately recreated the problem. I then deactivated this plugin and checked the others, none of them caused the problem other than wp security scan 2.6.
I have now deleted this plugin (remorsefully) from my install until it has been updated for 2.8. If you are using this plugin, this may be the cause of the error.
Regards
Glenn
http://www.blog.redcentaur.com/2009/upgrading-to-wordpress-2-8/