Support

The "403" error comes from the front-end backup code and it really means "you haven't supplied to correct password". Here is something very vital: your front-end backup key should consist of only alphanumeric (letters & digits: 0-9, a-z, A-Z) or it should be URL-escaped. Since this may be a bit tough, I have found an on-line URL encoder. You just paste your secret word in the big text area and press "Convert source data". Copy the string from the utf-8 box to your front-end backup string and you're set.

For example, if you are backing up www.example.com and your secret word is l@l$3#, you should end up with a CRON command line like this:

curl -b /tmp/cookies.txt -c /tmp/cookies.txt -L --max-redirs 1000 -v ""http://www.example.com/index2.php?option=com_akeeba&view=backup&key=l%40l%243%23&format=raw"

Also note that due to Joomla! filtering out input data, if you use certain combinations of special characters, e.g. lower than and greater than symbol, your secret word may be chopped or altered without even notifying you. This is a known limitation/feature of the Joomla! CMS. That's why the documentation suggests that you use a plain alphanumeric secret key, which eliminates such potential problems.

The front-end backup secret key IS NOT your Amazon key and IS NOT your Joomla! password. Please, please, read the documentation first.

Go to Akeeba Backup's Control Panel. On the upper right there is a "Parameters" icon. Click on it. A modal configuration dialog appears. Please find the "Enable front-end and remote backup" and set it to "Yes". Right below it, here it is: "Secret word". This is the one you have to put in the URL. Let's make an experiment. Change it to "notverysecret" (without the quotes) and click on Save.

Use the following CRON command line:

curl -b /tmp/cookies.txt -c /tmp/cookies.txt -L --max-redirs 1000 -v "http://www.mydomain.com.au/index2.php?option=com_akeeba&view=backup&key=notverysecret&format=raw"

Does it work for you now?

Furthermore, there is yet another automated backup option for Pro subscribers: http://www.akeebabackup.com/akeeba-backup-documentation/native-cron-script.html. This should work on most servers, as long as they don't impose an execution time / max server load limit on command-line scripts.

PS: Upgrading to Enhanced support is currently not possible. However, if you buy the Enhanced Support package and contact me I can either refund you the difference or extend your subscription for 6 months. Also note that I will be off-line this week Tuesday to Saturday, so there's no point rushing into buying the support package. Tip: look for the "Support Unavailability" calendar on the right hand of all support-related pages, including this one. It shows when I'm mostly or completely off-line.

OK, we posted at the same time :) I am glad you figured it out.

You are right. All those "secrets" and "passwords" are completely intimidating. I've tried to have only one "secret key" in Akeeba Backup itself. However, each third party service (FTP, Amazon S3, DropBox, you-name-it) requires its own set of authentication parameters, calling them something fancy to further the confusion.