500 internal server error after jet pack authorization

  • JimHardinberg

    (@jimhardinberg)


    10 years ago

    Hi all. OK, I’ve got a doozy here…

    I’m getting the 500 Internal Server Error only when I try to log in to the admin page and access the dashboard. The site itself is up and running. This happened after I hit the button to “authorize” (I think that is what it said on the jetpack page of the dashboard). Jetpack was installed and running fine, but then I hit the button on the big green splash screen that shows up in the dashboard.

    So, here is what I have done so far to fix it…

    1. Logged in via FTP and renamed the plugin folder. Didn’t work.
    2. Added a php.ini file to increase php memory. Didn’t work.
    3. Changed the wp-options table, active-plugins to a:0:{} – Didn’t work.

    I am at a loss how to fix it. Any help would be appreciated!

    https://www.ads-software.com/plugins/jetpack/

Viewing 10 replies - 16 through 25 (of 25 total)
  • Thread Starter JimHardinberg

    (@jimhardinberg)

    Hi Ryan. Thanks for the response. Unfortunately, it is still not working. I am unable to login to the admin section of the site at all.

    Jim, what if you try going directly to the login page, /wp-login.php

    I just tried that I can pull your login page.

    Thread Starter JimHardinberg

    (@jimhardinberg)

    I am able to get to the login page, however when I enter the name and password I get the dreaded 500 error.

    Well damn! I am out of options, outside of reinstalling portions and working your way to a total reinstall.

    Thread Starter JimHardinberg

    (@jimhardinberg)

    I guess I’m just going to have to do a re-install. This sucks! I cannot for the life of me figure out what the hell is causing this. If you have any more ideas, please let me know otherwise I’m going to have to rebuild it.

    Plugin Contributor Ryan C.

    (@ryancowles)

    Can you try to login to your site via FTP once again? Then, navigate to your /wp-content/plugins/ directory and delete the existing jetpack folder. After doing so, are you able to login to your Dashboard?

    Thread Starter JimHardinberg

    (@jimhardinberg)

    Hi again Ryan. I deleted the entire jetpack directory via FileZilla, then attempted to log-in via both Chrome and IE. Neither worked.

    When I enabled the jetpack extension, it must have corrupted something in the database itself. Even changing the active-plugins table to 0 didn’t help this problem. Something else went crazy in there.

    Plugin Contributor Ryan C.

    (@ryancowles)

    Thanks again for the update, Jim. Could you check the error logs on your server, and see if they contain any additional information about the 500 error? If you don’t know where to find this information, your host should be able to help you track it down.

    I ran into similar symptoms today. I updated Jetpack yesterday. I turned on the new Protect. I checked it this morning and it reported it had blocked 60+ malicious login attempts.

    Today I updated the “CAPTCHA” plug-in, Version 4.1.0 By BestWebSoft. After I updated CAPTCHA by BestWebSoft I immediately started to see the “Prove Your Humanity” math problem from Protect on the login screen in addition to the math problem from CAPTCHA by BestWebSoft. When I hit the login button my browser would throw out the 500 error. I could not access wp-admin.php.

    I tried signing in from a different I.P. and was able to login. I disabled Protect and the issue disappeared. I can now login and hit wp-admin.php just fine.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    I tried signing in from a different I.P. and was able to login. I disabled Protect and the issue disappeared. I can now login and hit wp-admin.php just fine.

    You could enable Protect and whitelist your own IP as explained here, but since you already use another Captcha plugin you probably don’t need 2. Leaving Protect off is probably your best bet!

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘500 internal server error after jet pack authorization’ is closed to new replies.