• Where can I find more information about
    “Not expected HTTP response body: 429 Too many requests body { padding-top: 60px; /* 60px to make the container go all the way to the bottom of the topbar */ } Error 429 Too many requests”

    I just installed BackWPUp on a site using the Avada theme, which I would not recommend to anyone. The backup is throwing that error.

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

Viewing 15 replies - 1 through 15 (of 19 total)
  • That means that ther too many request to the server from the blog. There will be done some request to detect if the job starts. Did you know if ther limitations ?

    I have the same problem – same message when tried to back up the site using BackWPup plugin. Can you advise on a solution for WP beginner level of technical understanding?

    Nora, have you solved it yet?

    Thank You!

    Hello Jana, the problem on explain it is that there cames many techniques at once.

    The 429 is a standrd http respoce status code. See https://en.wikipedia.org/wiki/List_of_HTTP_status_codes.

    But without many deteails of Hoster, Plugins, WordPress, PHP, Webserver and more Information i can’t say where it cames from.

    THe first step you can do is deactivating of other plugins to find out is it a problem betwen plugins. Than the thame with the Theme.

    Thread Starter Nora McDougall

    (@nora-mcdougall)

    Sorry for the late response. I have not solved the problem yet, but that is because I have been working on other projects.

    I think that the advice Daniel gave is pretty spot on. When I started working on the site, there were 34 plugins, about half are either unneeded or insecure. I have been working on removing them.

    But, my question is, what is it about BackWPUp that would cause that error, when other plugins don’t have the problem? There is some function in BackWPUp that is more sensitive to server requests than in the other plugins.

    Jana, just for your enlightenment, quite a lot of the requests from WordPress to the server are requests to the database for information. The main WordPress functions make their own requests, but most plugins also request information from the server. It’s like of like the “woman who lived in a shoe who had so many children she didn’t know what to do…”

    Yes, BackWPUp has more sensitive to server requests than in the other plugins. Other plugins don’t need that reequests normely.

    Has anyone figured out if this is a plain problem? I didn’t see a definitive answer…

    Thread Starter Nora McDougall

    (@nora-mcdougall)

    This is an interesting problem, jazkobo!

    1. There is no number attached to each plugin that tells how many server requests it makes.

    2. There is no number given by the web host that tells how many server requests your site can take.

    3. That means that each plugin writer can claim that the problem is other plugins making too many server requests!

    Thank You Nora for your previous response, I was too busy fixing the page itself – I re-installed the Theme that ran into some other issue and decided to use different plugin for backing up the site, which didn’t give me any alerts…

    What host is everyone using?
    I’m using Godaddy and it’s the only time I’ve ever had this error. I’m using the WordPress Managed hosting by Godaddy. I have a feeling they’re preventing the backups because they do their own backups as well. (I don’t fully trust them so I was hoping to do my own as well…)

    Thread Starter Nora McDougall

    (@nora-mcdougall)

    Hmmmm, that’s interesting @son0fhobs. The one client I have with the problem is also using the WordPress Managed hosting on GoDaddy. Looks like you hit on the real problem!

    In my case, the database backups are working fine. It’s the file backups that are the problem.

    No, its not GoDaddy, as much as I hear negative things about them. I used BackWPup with one client’s WordPress who is hosted by GoDaddy and it worked fine, yet with a second client I get the “Not expected HTTP response …”

    I did deactivate all other plugins and that did not make any difference, the error continued to occur.

    Since it worked with one client and not another, being that the second was done at 7 AM PST, that could be a bad time with GoDaddy, so I will leave it and return later and try again.

    OK, I think I should post an update.

    I will stand corrected, it is GoDaddy that creates the issue with this BackWPup plugin.

    I have 2 clients, 3 WordPress sites that use GoDaddy as their website host. One client does “not” use the managed wordpress system offered by GoDaddy, and the other client with 2 WordPress sites uses the “Managed WordPress system in GoDaddy.

    The major difference between these two clients and their websites is the “Managed WordPress”.

    According to GoDaddy, what we both figure is that BackWPup plugin attempts to access some core files that the Managed WordPress secures or limits access. Where a different backup plugin does not, and as a result works fine under the Managed WordPress system.

    So, I hope the developer of this plugin reads this and works to overcome this problem because even a premium version of their plugin will be useless under these conditions.

    If you have a Managed WordPress package with GoDaddy, this plugin will likely not work, as of this date.

    Thread Starter Nora McDougall

    (@nora-mcdougall)

    Thanks for the update! Incompatibilities are always an interesting debugging problem. Clients often don’t understand why you can’t know everything about every system and software. These forums are super when someone like you provides very specific information!

    But, whether the plugin author is responsible to make a free plugin compatible with GoDaddy’s system, I’m not so sure about that idea. Of course, the plugin author could choose to do that work, but we sure do expect a lot from our free plugin authors!

    Thanks Mark for your thorough info.

    BackWPUp is redundant on Managed WordPress Hosting, so personally, I don’t think it’s worth worrying about.

    The point of Managed WordPress Hosting is built in backups and security. Given BackWPUp becomes redundant to Godaddy’s service, it shouldn’t be an issue that it doesnt work.

    Personally though, I never completely trust anything and would rather have backups in more than one place. So if I’m eventually motivated, I’ll probably try to find an alternative backup, just because.

    Anyway, props everyone on figuring this issue out in detail. Go team!

    Thanks for the reply.

    Maybe, as it was past, I would accept the backups created by systems as Managed WordPress, but, with a recent experience with a hacker, I now tend to feel the same as you. I prefer to maintain my own backups as my method involves my own personal spare external drive that is not connected to the internet and DropBox types as a secondary backup in the event I loose my spare drive.

    What happened recently was a hacker got into the website account, installed 8000 malware HTML’s and corrupted the backups made by the website host making them useless. Since the web host is never 100% secure, I won’t risk the loss and cost of it.

    I have used another backup plugin in those two Managed WordPress sites. For sites that do not use Managed WordPress, I use BackWPup.

    I prefer to use such plugins because it does the job is short order and manually backing up all those folders and files is really time consuming, especially when backing up is part of my business.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Error 429’ is closed to new replies.