Akeeba Backup for Joomla!

Wednesday, 18 April 2012 06:34 CDT

alastair

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 1.5.23
PHP version: 5.2.10
MySQL version: (unknown)
Host: Easyspace virtual server
Akeeba Backup version: Professional 3.4.3

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: Command line backup - problem with upload to Dropbox. The backup is triggered by a CRON script. The backup is executing correctly but the upload to Dropbox is failing: "Post-processing interrupted -- no more files will be transferred". This previously functioned correctly. All Dropbox settings have been re-entered to ensure they are correctly configured. Please note, Akeeba configuration for part size for archive splitting not currently set per your documentation's recommendation - but I have tested with the recommended configuration and it also did not work.

Wednesday, 18 April 2012 07:43 CDT

nicholas

It looks like Akeeba Backup is not able to connect to Dropbox. I would recommend going to Akeeba Backup's Configuration page and re-connect Akeeba Backup to Dropbox. Please follow both connection steps (mandatory). This change was required if you upgraded from an Akeeba Backup version up to and including 3.4.1 to version 3.4.2 or later. The reason is that the old, hack-ish Dropbox connection library stopped working and we had to use Dropbox' official API. The downside of the official API is that it requires you to connect your Dropbox account to your Akeeba Backup profile using OAuth authentication. If the authentication fails of, for any reason, the authorisation token expires / becomes invalid you will not be able to upload to Dropbox. I know, that sucks, but it's their official API and as a third party developer I have no choice but to use 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!

Wednesday, 18 April 2012 08:14 CDT

alastair

Thanks for your quick response. I apologise, I should have mentioned that I have already connected my Dropbox account via Akeeba Backup's configuration panel. I just tried to do so again and the Dropbox popup that opened stated that the account was already authorised for Akeeba. It shows as "ok" for step 2 of the Dropbox config. I also tested a backend backup and received the same error as before.

Wednesday, 18 April 2012 08:43 CDT

nicholas

The only thing which could explain that is a failed update to the new version of Akeeba Backup. Can you please try re-downloading and installing Akeeba Backup Professional on your site, without uninstalling your existing Akeeba Backup version, twice? I know this sounds odd, but some times Joomla! "forgets" to copy all files during an update, especially when you are using Joomla! 1.5.

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!

Wednesday, 18 April 2012 09:43 CDT

alastair

Hello again. I just reinstalled twice (via the Joomla! module installer) and am afraid the same failure is still occurring...

Wednesday, 18 April 2012 10:46 CDT

nicholas

There is only one thing left: a server-side firewall. I was afraid it would come down to this :( It's not so easy to workaround. Another user with the same problem had his hosting company add all 152 possible subnets of AWS (which Dropbox is using to power its services) into the firewall's whitelist and that, finally, worked. Unfortunately, since this is a hosting limitation, I can't do anything about 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!

Thursday, 19 April 2012 05:07 CDT

alastair

I don't think that this is a firewall issue; I (briefly) turned the server firewall off altogether to test and the same thing is happening still. And my host says there is no additional firewall on their system beyond the one I have control over. Is there any way to get more detailed debugging information about the problem connecting to Dropbox? The log shows this (below) which is quite light on detail. :)

[120419 11:00:27] Failed to process file /administrator/components/com_akeeba/backup/site-www.[....].zip
[120419 11:00:27] Error received from the post-processing engine:
[120419 11:00:27]

Thursday, 19 April 2012 05:29 CDT

nicholas

There is abother reason for an error message not being returned: a null response from cURL. This means that cURL on your server is not able to communicate with HTTPS servers. This is usually attributed to either lack of SSL support when building PHP, cURL or the PHP cURL extension or the lack of an up-to-date system-wide SSL root (CA) certificates file. This is something your host will have to check. The closest thing I could find to help you is this page on installing CA certificates.

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!

Thursday, 19 April 2012 05:44 CDT

alastair

Thanks for your reply. This sounds like it could be a possible cause (my SSL certificates are unsigned); I will investigate.

Thursday, 19 April 2012 05:57 CDT

nicholas

Please remember that I am talking about the server's cache of root certificates (like Verisign's root certificates), not your web site's SSL certificates. I'm trying to make sure you won;t be looking at the wrong place :)

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