Support

We had the same issue with another user on GoDaddy, the crappiest host on the galaxy who recently made some "changes" to their servers (most definitely to the worse). I guess it's now official:

We will no longer support the use of our software on GoDaddy. This host is broken beyond repair.

It's not my fault either that GoDaddy made changes which broke their servers beyond repair. The backups are taken perfectly, but due to GoDaddy being a lousy host you get an error message at the end. This problem does not happen on any other host, does not come from our code and we can't fix it. Please report it to GoDaddy. If they refuse to fix it you can just move to a decent host. I do not see why we should offer you a refund for an issue that's beyond our control. As we have written in our refund policy, which you explicitly accepted when subscribing, there are absolutely no refunds given when the problem is due to a hosting issue beyond our control. Moreover there was no way I could have predicted that GoDaddy would do such changes. I am a developer, not a psychic!

I spent most of yesterday thinking of a solution. I don't know if it was torturing my brain for 12 hours or the two beers I had at night when I decided to call it a day, but I dreamed up a solution. Literally. This one came to me as I was sleeping. I just tested it on another client's site (not on GoDaddy, but with a very tight mod_security rule set) and it did work. So, I will go into a stretch and guess that GoDaddy did a similar change to their servers. So let's put my psychic abilities to the test.

Please go to Akeeba Backup, Configuration and scroll all the way down. Check the following boxes:

- Disable step break before large files
- Disable step break after large files
- Disable proactive step breaking
- Disable step break in finalization
- Set an infinite PHP time limit

These are all dangerous settings, in the sense that they could make a backup crash unless you use very conservative timing settings. So, right above them, set the following:
- Minimum execution time: 1 second
- Maximum execution time: 14 seconds
- Runtime bias: 75%

This SHOULD work around the unrealistic limitations set by GoDaddy on the number of consecutive requests you can perform on a similar URL. However it may cause the backup to fail out cold as you will be using more CPU time. If this happens, try the ultraconservative timing settings:

- Minimum execution time: 1 second
- Maximum execution time: 14 seconds
- Runtime bias: 75%

In all honesty, I need someone to test that solution for me. If that really works you were right, there was a way to help you which I failed to see at the time, in which case I will do exactly as I say in our refund policy and give you a full refund. I will also up the ante and turn your subscription into a 2-year Deluxe one as a way to apologise and thank you for testing this for me.

That's great news to hear! I'm very happy that my solution did work.

As promised I refunded your subscription (you should see it in your bank statement within a few days) and gave you a free 2-year Deluxe one. You will have to log out and log back in to see the new downloads.