Have I read the related troubleshooter articles above before posting (which pages?)? No
Have I searched the tickets before posting? No
Have I read the documentation before posting (which pages?)? No
Joomla! version: 2.5.7
PHP version: See attatched logfile
MySQL version: See attatched logfile
Host: (optional, but it helps us help you)
Akeeba Backup version: 3.6.6 Pro
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:
Hello Nicholas,
I noticed a ticket from another user about a similar issue. I use Front-end backup (with Webcron.org) on several websites. I just upgraded 1 site (Akeeba backup pro 3.5.6 -> 3.6.6). Since this upgrade, the Front-end backup doesn't work anymore. The created file is about 2MB (instead of 260MB !) and gets the extension .j01 instead of .jpa.
I checked the settings on the website of Webcron.org : everything is ok. Webcron.org still sends me an email telling me that the job was done succesfully (200OK) although it isn't. The Akeeba backup component didn't send any confirmation mail (which triggered me to take a closer look).
When manually making a backup in the backend, it works perfect. I tried to (re)configure the component using the wizard, but the result is the same : front-end backup with Webcron.org doesn't work properly.
On all the other sites (using Akeeba backup pro v3.6.5) the Front-end backup with Webcron.org works like a charm.
I suppose the bug is somewhere in the new version 3.6.6 of Akeeba backup. I added the logfile of the last backup attempt (Front-end with Webcron.org).
Chris K.
Redpider Webdesign