If changing the themes folder name doesn't resolve your issue, the next step would be to rename the /wp-content/plugins folder and then try /wp-admin again.If this fixes your issue, you'll have change your plugins folder name back to plugins, then update and re-enable each plugin.Another potential fix is to temporarily rename your /wp-content/themes folder (to something like themes.bak) and try to navigate directly to /wp-admin -- there is a chance that a customization to the theme is causing an incomplete upgrade / blocking a database upgrade.If this resolves your issue, change the directory name back to themes and see if the problem persists.If that doesn't work, you should remove the .htaccess file from the site, and see if you can get access back to the admin. Godaddy is on my short list of hosts that I won't work with on Wordpress sites, but it does generally work with very basic site setups.I've seen this happen before -- Jake makes one good suggestion and I've had to do just that to resolve the issue in several cases.I'm a Word Press novice trying to help a friend (who is even more of a Word Press novice) with his Word Press blog hosted on Go Daddy.It was working fine until he apparently (he doesn't fully remember) was prompted to upgrade the software.
Happened to me on sites hosted at godaddy and Bluehost.
@Flashing Cursor -- definitely will come back and let you guys know. Problem persists even when I rename the theme directory. Will try re-uploading Word Press files as Jake suggests asap.
It is important that you do NOT copy over the wp-content folder or the files. This will allow you to make sure the upgrade is complete.
If you are getting the yoursite.com/wp-admin/upgrade.php? _wp_http_referer=%2Fwp-admin%2F error, this worked for me: I ran a patch in Go Daddy found in the WP application section of my Go Daddy hosting manager.
Now the blog still works for end-users (you can see it here) but whenever you log into the Word Press admin, you get a Page Not Found / "This is somewhat embarrassing, isn’t it? The URL that the browser has been redirected to is: It seems like the upgrade attempt was messed up somehow.
Given I don't know what precisely caused this, what steps should I take to start investigating the problem and ideally rolling back the upgrade (or completing it) so that the blog is usable again?