• Resolved giraffeweb

    (@giraffeweb)


    I have deactivated all plugins and if I try to activate NextGen, I get:
    This page isn’t working
    domainname.com is currently unable to handle this request.
    HTTP ERROR 500

    If NextGen is already activated, I cannot log into the wp-admin and get the same error above. All I can do is ftp in and drag the NextGen plugin out of the folder. This is happening on every website I am hosting on my VPS, so I think it is a server issue. I tested it on GoDaddy and Dreamhost and it works fine. Can anyone point me in the right direction so I can see what to look at on my webhost? It is not necessarily a plugin conflict as on some sites, even if I deactivate all plugins and try to active NextGen, it gives this error. Is it a memory issue???

    It is also doing this with the version of WP previous to 4.7.3. I have PHP 5.4.32 with the intent to upgrade to 7 soon. Thanks! Judy

    Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • I’m having the same issue over the past few days. Almost all my sites that run NextGen return a 500 server error even with the latest version. Removing the plugin is the only fix. I hope someone finds a fix for this ASAP

    Plugin Contributor photocrati

    (@photocrati)

    @giraffeweb – Perhaps there is something relevant in the server/site error logs that might point to what may be causing this issue? Unfortunately there may not be a lot we can offer if this is an environment configuration issue although perhaps the support services of your web host might be able to look into this for you.

    Thanks!

    – Cais.

    Thread Starter giraffeweb

    (@giraffeweb)

    I was trying to reply to you brandibush77 but I cannot see your question here, yet I got an e-mail with the below – the only way you can get back in is to ftp into the website, navigate to wp-content/plugins and drag the nextgen-gallery plugin up to the top so it goes in the directory above (if you want to keep it) or just delete it:
    brandibush77 wrote:

    Please help! I am an admin on a website that does not belong to me…it belongs to my boss. I installed the NextGen plugin to do some photo galleries for her and was immediately locked out with the HTTP 500 error. Since I can’t get past that error page to log into my admin account, I can’t uninstall NextGen, which I’m seeing is the only way to fix this. How can I bypass the error page and get back into my account so I can uninstall this and keep working? I am on hold til I figure this out and my boss is not happy. TIA

    Thread Starter giraffeweb

    (@giraffeweb)

    Below is one of the errors I get in my error log. I am not sure of the entire error as the line is truncated because it is too long I guess.
    So, based on the below, anyone have an idea what I can ask my webhost could be the problem? I will check a few other my clients who are on GoDaddy and Dreamhost who are not having this problem and see if there is anything i there error logs.

    [06-Mar-2017 11:05:47 UTC] WordPress database error Deadlock found when trying to get lock; try restarting transaction for query UPDATE wp_options SET option_value = ‘1488800147’ WHERE option_name = ‘_transient_timeout_2__974818834’ made by A_MVC_Router->cache_lookups, C_Photocrati_Transient_Manager::update, C_Photocrati_Transient_Manager->set, set_transient, update_option

    Plugin Contributor photocrati

    (@photocrati)

    @giraffeweb – Although that error can occur from time to time it is intermittent and would not be causing anything in the immediate sense.

    – Cais.

    Thread Starter giraffeweb

    (@giraffeweb)

    So, I turned on wp_debug and figured out I am have a memory error. I logged into whm and Tweak Settings->PHP and increased “cPanel PHP max POST size”. I rebooted the server and now I can login at wp-admin. I still would like to know why NextGen is now eating up all the memory on my sites now when it didn’t used to.

    Plugin Contributor photocrati

    (@photocrati)

    @giraffeweb – There is no way to tell from front facing view what might be happening on your site. There could also be something else that has changed which is triggering this problem.

    Thanks!

    – Cais.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘HTTP ERROR 500’ is closed to new replies.