Support

Hello,

We have removed integration with the Dropbox v1 API because Dropbox itself announced it is deprecated and will be turned off by June 28th, 2017. We chose to remove support for the deprecated API now to make sure that all of our clients will be ready for Dropbox' deprecation next year. If you think that's an overkill please keep in mind that we added Dropbox v2 support in November 2015 with the documentation note that it's the recommended version and that the v1 API may stop working at any point.

Unfortunately, Dropbox' v1 and v2 APIs are very different and there is no way to have an automatic migration from v1 to v2. The access tokens used in the two API versions are and work different. This means that by upgrading to a new version of Akeeba Backup / Akeeba Solo your backup profiles which were using the deprecated Dropbox v1 API integration are no longer linked to a post-processing engine and produce errors.

Luckily there's a very simple process you have to follow once on every site and backup profile you want to (re)link to Dropbox.

THIS PROCESS ONLY NEEDS TO TAKE PLACE ONCE PER BACKUP PROFILE AND SITE.

• Go to your Akeeba Backup / Akeeba Solo main page.
• Select the backup profile you want to relink.
• Click on Configuration.
• In the Post-processing Engine dropdown select "Upload to Dropbox (v2 API)"
• Click on Configure next to it.
• Click on the "Authentication – Step 1" button.
• You may have to log in to Dropbox if you are not already logged in. Also, if you had not authorized another Akeeba Backup or Akeeba Solo installation to use Dropbox you may see a confirmation about it. If you are already logged in and have authorized our software to use Dropbox you will not see any of that.
• You then see a page with the big title "Dropbox Authentication is almost complete". Click on the blue "Complete Dropbox authentication" button below it.
• Now you're back to Akeeba Backup / Akeeba Solo. Click on Save & Close to complete the setup.

Unlike the Dropbox v1 API you must not copy the token from one profile / site to another. Instead, repeat the process above. Dropbox API v2 produces a new token every time you link a new backup profile or site to Dropbox without revoking the previous one.

Again, we apologize for having to go through this process but this is due to changes made on Dropbox' side. On the upside, the Dropbox API v2 is much more stable, allows for bigger uploads and lets us perform "chunk uploads", a technique which allows us to transfer very large backup archives without you having to set up small part sizes. You can now safely use a Part Size for Split Archives up to 2047 Mb without any upload worries.

I can see that the backup is not finishing at all, so fixing the Dropbox connection won't help at this point.

In the backup log file I observe that the backup got stuck and restarted twice before it got stuck for a third time, causing it to fail. This means that your server is blocking it from completing. Let's try doing something about it.

Go to Akeeba Backup's Configuration page. Scroll all the way down to the fine tuning settings and set:
- Minimum execution time: 5 seconds
- Maximum execution time: 3 seconds (yes, the maximum is less than the minimum, it's not a typo)
- Execution time bias: 50%

Try running another backup. If this still doesn't work please ZIP and attach the new log file. Thank you!

You're welcome! I'm glad I could help you :)