Support

Hi there,

we are using Akeeba Backup on Update in combination with Panopticon. 
Yesterday there were errors after the update and we tried to restore the backup. But it didn't work. (It still was Akeeba Backup 9.9.11)

Now I updated Akeeba Backup on one site and made all extension updates. Then I made the Joomla update which took the backup automatically.
But I wasn't able to restore this backup. The error is:

Extraction of the backup archive has failed.
The last error message was:

Invalid header in archive file, part 0, offset 163. Please make sure to download and upload backup archive files using SFTP, or FTP in Binary transfer mode and do check that their file size matches the sizes reported in the Manage Backups page of Akeeba Backup / Akeeba Solo.

We use a custom profile for the backup which transfers the backup automatically to another FTP server using FTPS.
When I create a backup with the default profile which does not transfer the backup then the restoration works as expected. 

I changed the settings in our profile to no delete the backup after transfer. Both files have exactly the same size. I tried to restore the backup that was not transferred and that was in the same directory as the one I created with the default backup (it also has the same file size). 

But I get the same error message whe restoring the local backup, so I think the problem is not the transfer via FTPS but somewhere else in the profile settings.

Please find the log attached. 

Can you think of a setting that would create this error? What can I do about this?

If you need any further information, please feel free to contacting me. 

Kind regards, 

Tanja Vogt

Hi Davide,

when I use the Kickstart.php the restoration works. Please find debug attached. 

I also testet with one of the backups that were transferred via FTPS yesterday and with the kickstart this also works. 

Only when I use our custom profile and want to restore via manage backups the restoration fails. So I seems there is everything ok with the backup itself. 

Kind regards,

Tanja Vogt

Yes, that is correct.

Hello Davide,

I installed Akeeba Backup twice again.
Same error. 

But I think I found the problem: When I start the restoration via backend then the encrytion key is automatically filled by our pw manager.
When I enter the correct pw it works as expected.

So everything working now. 

If the error message had included something with incorrect pw, I would have been able to solve the problem on my own. Maybe you can have a look at the error message.

Thank you very much for your help!

Kind regards, Tanja

Yes, that makes also sense to me. But I suggest to change the error message, if you can see that the pw is wrong so that maybe other users with the same problem are able to find a solution themselves.