Support

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:

I use Akeeba Backup and have it set so Webcron.org does the backup. It has worked well for many months, but then, after I upgraded to 3.11.3 earlier this week, my cron jobs are not working right.

Prior to the upgrade, the first lines of the log said:
HTTP/1.1 303 See other
Server: Apache
Set-Cookie: 4ac78176077866c5d903b5be295f5e84=da315a8837ea145065c3a1f883121690; path=/
Location: http://silverpen.org/index.php?option=com_akeeba&view=backup&task=step&key=[secret]&profile=1
Cache-Control: max-age=3600

After the upgrade the first lines say:
HTTP/1.1 302 Found
Server: Apache
X-Logged-In: False
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Cache-Control: no-cache, max-age=3600
Pragma: no-cache
Set-Cookie: 4ac78176077866c5d903b5be295f5e84=acafa055e6d0676670f664a474c0b2a8; path=/
Location: http://silverpen.org/index.php?option=com_akeeba&view=backup&task=step&key=[secret]&profile=1

Prior to upgrade, the cron job took about 260 sec, afterwards it takes 25 sec and still returns an "OK" - but Akeeba's log says "failed".

I've attached the Akeeba log, and the message I get at Webcron.org

Thanks, Davide. This took care of the problem (YAY!). My site is not multilingual, but it does use some specialized components (specifically jreviews). I don't know if that was what was causing the difficulties or not.