Error 500 on /wp-admin URLs with plugin enabled

  • Resolved marger

    (@marger)


    9 years, 6 months ago

    Hi,

    For the past months, I experience this problem on two websites, both hosted on the same server (debian jessie based, php 5.6.24). With BackupWordpress enabled (3.6.2 and I think at least one previous version), I get HTTP error 500 on every /wp-admin backend URL. As soon as I disable this plugin, I can reach the backend again. I run version 3.6.2 on several other sites hosted on other servers without problems.

    I tried:

    • Reinstalling WordPress 4.6.1
    • Reinstalling BackupWordpress 3.6.2
    • Changing to Twenty Sixteen Theme
    • increasing PHP memory to 256MB
    • disabling my .htaccess

    None of this has any effect.

    I reverted to version 3.4.3 and that runs fine on exactly the same sites, where the only difference is this version change.

    I would love to keep using the plugin on these two sites since it otherwise meets my needs perfectly. Is this a bug in the plugin, or can I change something in my web server configuration to solve this issue?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor Katrina “Kat” Moody

    (@katmoody)

    9 years, 5 months ago

    I think this is a bug related to the file size handling. The developers are working on a fix for this, though improvements made in 3.6.2 should have also actually helped 🙁

    What’s happening is that the plugin is running more in the background than it needs to, and on some sites that have additional stuff running in the background (file scanning, security plugins, etc) it can lead to this 500 error which I think is an indication of hitting the memory limit. I think.

    In any case, let’s see if the next update helps improve this situation for you or not and if it does not we might need to take a deeper look so we can troubleshoot it more effectively for you, okay?

    Kat

    Thread Starter marger

    (@marger)

    9 years, 5 months ago

    Thanks for your reply, Kat. I’ll keep you posted after the next plugin update. I should note that I also tested with all other plugins disabled and only this one enabled, so there wasn’t a lot of fancy stuff running in the background.

    Plugin Contributor Katrina “Kat” Moody

    (@katmoody)

    9 years, 5 months ago

    I can also verify that the 3.5 version seems to work for another user with this exact issue after we went through some troubleshooting yesterday. We are still working on this one though!
    Kat

    Thread Starter marger

    (@marger)

    9 years, 5 months ago

    That sounds promising, thank you for the update.

    Plugin Contributor Katrina “Kat” Moody

    (@katmoody)

    9 years, 5 months ago

    I just wanted to include an update for you (and anyone else who might be following this issue) – we are about two weeks out from this first update we are hoping will correct this issue for users. In the meantime, please feel free to report back here with any updates if you are having this issue and are using the earlier version of the plugin with success.

    Thanks so much for your patience as we’ve worked to figure out this issue.

    Kat

    Thread Starter marger

    (@marger)

    9 years, 5 months ago

    Thanks, will keep an eye out for the update!

    Plugin Contributor Katrina “Kat” Moody

    (@katmoody)

    9 years, 4 months ago

    We’re currently looking at a release for early next week – just an update before we head into the Thanksgiving holiday here in the US.

    Kat

    Plugin Contributor Katrina “Kat” Moody

    (@katmoody)

    9 years, 4 months ago

    Well, the beta release didn’t show that it helped this issue, though it did solve another bug we had. So while we’re heading for that release it won’t solve the issue for you guys. I don’t want you to think we’ve forgotten about you, though. This is one of two issues we’re focusing on until we can hopefully solve it completely or at least improve the situation for those who are experiencing it.

    Thanks for sticking with us and for your patience!
    Kat

    Plugin Contributor Katrina “Kat” Moody

    (@katmoody)

    9 years, 2 months ago

    As this post is older and there have been further updates to the plugin. Can I please have any additional related updates or users having similar issues start a new thread so I can help you more quickly?

    Thanks so much! I’m closing this post as resolved, because this is affecting a small number of users at this point and there hasn’t been further updates in a while.

    If you’re still having issues please link back to this post (if you were one of the posters on this thread) so I can follow up on the history of your issue.

    Thanks again,
    Kat

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Error 500 on /wp-admin URLs with plugin enabled’ is closed to new replies.