500 error when accessing wp-login.php after 4.0 upgrade

  • Resolved Ebbmar

    (@ebbmar)


    10 years, 2 months ago

    Hi,

    I have read all(?) the posts regarding issues with accessing the admin page after upgrading to 4.0, but so far nothing I have done have helped.
    Upgraded from 3.9.2 to 4.0, during the last part of the automatic upgrade I got a few lines of text that I did not have time to read before it redirected me to wp-login.php page, which was blank.
    I am running
    * FreeBSD 9.2
    * PHP 5.4.32
    * MySQL 5.1.73
    * Apache/2.2.29

    I have:
    * Done a manual reinstall per https://codex.www.ads-software.com/Upgrading_WordPress_Extended
    * Verified that all files are owned by www, which is the user the httpd process is running under.
    * Verified .htaccess file, even removed it.
    * Renamed theme and plugin directories in order to deactivate them
    * Downloaded the wp-settings.php file from github per https://www.ads-software.com/support/topic/cant-login-after-400-update?replies=19

    The main page works ok, but when I go to wp.login.php, and enter my credentials, I get the white page.

    The log I get from the web server when trying to access /wp-admin is:
    192.168.0.11 – – [06/Sep/2014:23:05:18 +0200] “POST /wp-login.php HTTP/1.1” 500 – “https://www.ebbmar.com/wp-login.php” “Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.103 Safari/537.36”

    Any more ideas or suggestions are really appreciated!

Viewing 9 replies - 1 through 9 (of 9 total)
  • Moderator t-p

    (@t-p)

    Error 500 ISE is very generic and can be caused by various problems including server errors. Here are some thing you can try to solve it:
    – Your first step should be checking your site’s error logs for a more specific error message. If you need help locating them, ask your hosting provider to help you with that.
    – check with your host if the domain name is configured properly to point to public_html folder
    – It may indicate .htaccess issue. Regenerate .htaccess, and be sure the encoding in your text editor is Unicode No BOM
    – It may also indicate a problem with the configuration on the server. Usually your hosting company tech support can help.
    – it could be problem with the plugins, try resetting the plugins folder by FTP or phpMyAdmin.
    – it could be a problem with the theme. Momentarily, try switching to the default WordPress theme via FTP or whatever file management application your host provides by renaming your current theme to rule out any theme specific issue.
    – If the above troubleshooting steps fail to resolve the issue, try manually re-uploading all files and folders EXCEPT the wp-config.php file and the /wp-content/ directory from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones. Read the Manual Update directions first!

    Ebbmar, good luck. I’m having exactly the same issue as you are.

    I’m also running FreeBSD 9.x with very similar versions of everything.
    I’ve tried everything including deactivating all plugins, switching to the 2014 theme, updating files manually, and removing .htaccess. All to no avail.

    To Tara, the issue isn’t the domain. The Apache config in my case has worked now for 3+ years. There is an error in the logs regarding sessions.
    BTW, in my case, I’m doing the hosting myself.

    The thread for my issue is here: https://www.ads-software.com/support/topic/dashboard-area-broken-after-upgrade-to-40?replies=19

    Thread Starter Ebbmar

    (@ebbmar)

    Hi,

    Just like Derwood (and yes, I read your thread :)), I am hosting it myself and it have been running smoothly for many years. And the admin page was working fine before I did the upgrade.
    I’ve tried all steps Tara mentioned, though I will give the last item another shot and delete all files except the wp-config.php and /wp-content/ and re-upload all the files.

    Thread Starter Ebbmar

    (@ebbmar)

    Finally managed to get a real error by setting error_reporting(1) in the end of wp-config.php:
    Fatal error: Call to undefined function hash() in /usr/local/www/apache22/data/wp-includes/session.php on line 64

    Now I have to see if I can find out why the hash() function isn’t working..

    Thread Starter Ebbmar

    (@ebbmar)

    Found it.. I had not the php5-hash port installed.
    After installing it, it the admin page worked ok!

    Yeah, that fixed it for me too. php5-hash needs to be added to depeendencies for the WordPress 4 port.
    Good work, Ebbmar! Thank you very much!

    Moderator t-p

    (@t-p)

    @derwood, @ebbmar glad you got it sorted ??

    Would you mind pointing me towards the exact steps needed to “php5-hash needs to be added to depeendencies for the WordPress 4 port”?

    Nevermind – I believe this was platform related as it didn’t affect my live server upgrade, only my local test one.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘500 error when accessing wp-login.php after 4.0 upgrade’ is closed to new replies.