Support

Akeeba Backup for Joomla!

#31107 cronjob problem with ftp

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by on Wednesday, 17 April 2019 17:17 CDT

onefoot
Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

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 get this when i try to make the backup with a cronjob:

Akeeba Backup CLI 6.4.2 (2019-03-14)
Copyright (c) 2006-2019 Akeeba Ltd / Nicholas K. Dionysopoulos
-------------------------------------------------------------------------------
Akeeba Backup is Free Software, distributed under the terms of the GNU General
Public License version 3 or, at your option, any later version.
This program comes with ABSOLUTELY NO WARRANTY as per sections 15 & 16 of the
license. See http://www.gnu.org/licenses/gpl-3.0.html for details.
-------------------------------------------------------------------------------

You are using Joomla! 3.9.4 on PHP 7.3.2 (cli)

Starting a new backup with the following parameters:
Profile ID 3
Description "Command-line backup"

Configuration variables overriden in the command line:
engine.postproc.ftp.user, engine.postproc.ftp.pass

Current memory usage: 3.59 MB

Unsetting time limit restrictions.

Site paths determined by this script:
JPATH_BASE : /home/satrekk/www/onefoot.ch/joomla
JPATH_ADMINISTRATOR : /home/satrekk/www/onefoot.ch/joomla/administrator

An error has occurred:
Could not decrypt settings for profile #3

The settings for backup profile #3 are stored encrypted in your database.
However, PHP 7.3.2 (cli) on your server -which you use to run this backup
script- does not support encrypted settings. Since the settings cannot be read
the backup has failed.

The detected errors are:

The encryption key has changed

Since your encryption key has changed you have permanently lost all your
encrypted settings. Please reconfigure the backup profile and retry taking a
backup. There is nothing else you can do.

dlb
There's a bug in 6.4.2, a new release will be available on Monday.

In the mean time, you can turn off encryption in the component options, then open your profile options and save. That saves them unencrypted and should let CLI work.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

onefoot
Hi,
The problem occures also with the encryprtion turned off.

I hope with the update the problem will be gone...

dlb
Evidently this work around has changed since Nicholas posted it on Friday. He posted in another ticket today that there would be a new release soon.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!