wp-admin HTTP Error 500 (Internal Server Error)

  • Ted Rouse

    (@tedrouse)


    11 years, 10 months ago

    Hi there. I’m copying down a remote WP set-up to my local MAMP host for testing, development, etc.

    Pretty much everything went smoothly from exporting/importing the SQL and re-jigging the wp-config.php perspective and I’m able to view the site locally with no problems. But when navigating to http://(local site address)/wp-admin, I’m constantly presented with an Internal Server Error 500, so I can’t login to make the necessary permalinks adjustments and whatnot.

    I’ve mucked with the .htaccess, tweaked the php.ini, and even borked around with the permissions, all to no avail. I’m sure I’m missing something, but I don’t know what it is. Any guidance would be greatly appreciated.

    (Note: When I do a FRESH local WP install, everything is fine – it only seems to be an issue after connecting to the imported database. Maybe the problem’s in there?)

    Thanks much…

    -Ted.

Viewing 3 replies - 1 through 3 (of 3 total)
  • esmi

    (@esmi)

    11 years, 10 months ago

    Check your error logs.

    Thread Starter Ted Rouse

    (@tedrouse)

    11 years, 10 months ago

    The Apache logs? They don’t seem to contain any clues (that I can decipher, anyway).

    [Thu May 31 13:08:41 2012] [notice] Digest: generating secret for digest authentication ...
[Thu May 31 13:08:41 2012] [notice] Digest: done
[Thu May 31 13:08:41 2012] [notice] Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/0.9.8r DAV/2 PHP/5.3.6 configured -- resuming normal operations
[Thu May 31 13:08:55 2012] [error] [client 127.0.0.1] File does not exist: /Users/tedrouse/Sites/favicon.ico
[Thu May 31 13:22:48 2012] [error] [client ::1] client denied by server configuration: /Users/tedrouse/Sites/.DS_Store
[Thu May 31 14:10:18 2012] [error] [client 192.168.1.101] client denied by server configuration: /Users/tedrouse/Sites/.DS_Store
[Thu May 31 14:10:18 2012] [error] [client 192.168.1.101] File does not exist: /Users/tedrouse/Sites/favicon.ico

    I disabled all of the plugins via phpAdmin, and it did the trick. When re-activating them one by one, it seems that Jetpack was causing some trouble.

    esmi

    (@esmi)

    11 years, 10 months ago

    Not the Apache logs. The actual error logs. They may be generated in the folder where the error is occurring. If you are using Virtual hosts, they may be generated in logs/error.log. Check your httpd.conf file for details.

    You can also turn debug on and enable error logging in WordPress – which is handy when working locally.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘wp-admin HTTP Error 500 (Internal Server Error)’ is closed to new replies.