Support

Hi,
I was having problems with backups timing out, most likely due to their size. The finder tables are >4GB in size, and I'm uploading to S3 over only a 10mbit link. For this reason, backups are performed by cron using the akeeba-backup.php command-line script.

I read a previous thread about enabling JPS encryption for the archives. It appears now backups are failing with "Could not decrypt settings for profile #1". I have created a key to use for backups and stored it in the configuration, but the error message says the command-line backup can't support encrypted backups. I've even tried disabling the JPS encryption, and it still reports the same error message.

This is on fedora29 with mcrypt installed.

# rpm -qva|grep mcrypt
mcrypt-2.6.8-19.fc27.x86_64
libmcrypt-2.5.8-22.fc28.x86_64
php-pecl-mcrypt-1.0.1-3.fc28.x86_64

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.8.6 on PHP 7.2.15 (cli)

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

Current memory usage: 3.4 MB

Unsetting time limit restrictions.

Site paths determined by this script:
JPATH_BASE : /var/www/www.mysite.com-443/html
JPATH_ADMINISTRATOR : /var/www/www.mysite.com-443/html/administrator

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

The settings for backup profile #1 are stored encrypted in your database.
However, PHP 7.2.15 (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.

Please upgrade to Akeeba Backup 6.4.2, released yesterday. The bug is fixed there. Thank you for your patience.

I am using 6.4.2. I've also restarted the webserver (httpd-2.4.34-3.fc28.x86_64) and the problem continues.

Please go to the Configuration screen for Profile #1 and click on the Save button. Now retry your CLI backup. Does that solve the problem?

The issue is not about encrypting your backup archive, it is about decrypting the configuration data.

An error has occurred:

Could not decrypt settings for profile #1

This also did not work. If I disable "Use Encryption" on the Security tab and Save the configuration, it works. Enabling it again causes the error message.

There also doesn't appear to be a log file created with any debugging info to assist.

No, there's no log file, the backup never started. This is the problem that was fixed in 6.4.2, you're the first one to report a problem with the fix. I'm waiting to hear back from Davide and Nicholas now.

Thank you for your report, you found a bug. Nicholas was able to track it down and he expects to release a new version on Monday. In the mean time, turning off encryption is the only work around.

Thanks for your help.

You're welcome! Have a good weekend.

Is it possible that backups would not work at all now? I've disabled encryption on both profiles, and have tried both, and now neither work at all when attempting to backup from the command line. They fail with the same error message as previous.

Backups from the console appear to work.

Perhaps I should go back to the previous release?

The information from the Configuration settings is encrypted. The CLI interface can't read that encryption, so the backup fails. If you turn off encryption, and then save each profile so they are stored without encryption, the CLI backup should work. That's my understanding of the issue. Nicholas didn't give me many details, he just said he knew what was wrong and would release a fix on Monday. He's traveling this weekend.

Just a note to follow up and report that 6.4.2.1 fixed the encrypted backup key problem.