Support

Akeeba Backup for Joomla!

#18288 Post Processing to Dropbox (for round 20 Websites) failed since update 3.9.1

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Thursday, 28 November 2013 05:42 CST

Hotkeyharry
EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue: Post Processing to dropbox gives error - I have to download all processed backups manually...
Yes - I've tried different minimum an maximum execution timeouts and bias settings in the post-processing and configuration window like recommended from ANGIE...

Error comes in both cases:manually started backup AND automated Webcron Backup!

nicholas
Akeeba Staff
Manager
The Dropbox post-processing engine hasn't been touched throughout the 3.8.x and 3.9.x releases. It's the same code. What I see in our logs is that it takes a very, very long time to send the file to Dropbox. The most likely cause for this issue is an overloaded server or a server with a very limited amount of bandwidth. 1&1 is known to have servers that fall in both categories at the same time. You can try setting the part size for split archives to a very low value (around 1Mb or even less) and see how long it takes to transfer each backup part size. This will give you a good estimate of the available bandwidth between your host and Dropbox.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Hotkeyharry
I've did a Amazon S3 Backup and it was working proper - so Dropbox seems to be the problem...I#m checking - thanx for help

nicholas
Akeeba Staff
Manager
That's strange. Dropbox is using Amazon EC2 and S3 for its service. Can you try re-authenticating Akeeba Backup to Dropbox?

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Hotkeyharry
great idea!! but not the resolution.
I've done new authentication to Dropbox, but same error occurs:

Sicherung fehlgeschlagen
Der Sicherungsvorgang wurde angehalten, da ein Fehler entdeckt wurde.
Die letzte Fehlermeldung lautet:
AJAX Loading Error
HTTP Status: 500 (Internal Server Error)
Internal status: error
XHR ReadyState: 4
Raw server response:
Please click the 'Analyse Log' button below have Akeeba Backup analyse its log file for further information.

I will check another homepage with new authentication, but that's an odd thing, that the errors occurs on same time, on all pages, that I safe to Dropbox since two (or longer) years

Hotkeyharry
Second test on second site: new authentication to Dropbox but no success,
Loading Backup Profile 2 (Amazon S3 Bucket): trouble-free backup with success

very strange ...

nicholas
Akeeba Staff
Manager
I tested again, on several sites running 3.9.1 and using Dropbox. Sorry, I can't reproduce this issue. Transfer to Dropbox works perfectly. This means that the problem comes from your host, not our code.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

nicholas
Akeeba Staff
Manager
There is another option in our Dropbox integration called Enable chunk upload. CAn you try disabling it?

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Hotkeyharry
incredible, oh man, yes that's it:
until now tested:
3x different domains on 3 different Hosts (1und1) backuped, all running and done!
I will disable this function on all other sites... ;-))
But what was the "chunk upload" for??
greetz

nicholas
Akeeba Staff
Manager
Hmmmmm..... What is the size of your backup archive?

The chunked upload is a workaround to Dropbox' limitation of 150Mb per backup archive. It tries to upload each backup archive in small chunks to Dropbox. It, however, uses a different URL to connect to Dropbox than the regular upload. I want to check two things:
1. If it's only triggered for large backup archives, as it's supposed to
2. If some hosts seem to be blocking it

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Hotkeyharry
21 MB, 37MB and 38MB

nicholas
Akeeba Staff
Manager
Thank you very much for the feedback! I now know what I have to do to debug this issue.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Hotkeyharry
In standard the chunk button is not active, or? Should I disabled it on all sites?? Am I the only german Akeeba Backup user with hosting on 1und1 and using Dropbox?? strange ;-))

nicholas
Akeeba Staff
Manager
It is enabled by default. You will have to do the same on all of your sites.

I am sure you are not the only German Akeeba Backup user using 1&1 and Dropbox, but you are the only one to have filed a ticket so far :) I have another user with the same issue, but he's not from Europe. I will have to dig deeper and find out if the problem is server-related or something on our site. In the former case it makes sense that only some servers of a particular host are affected. Each server may have a slightly different configuration than the others.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!