Support

After updating to 1.7.1 Akeeba Solo I am not able to restore jps backups from my Akeeba Solo installation.

When I run Akeeba Extract Wizard on the jps file I get the error:

Can't read file header information; your archive is corrupt

When I run Akeeba Kickstart on the jps file I get an error similar to:

')' expected

I remember a similar issue with Akeeba Backup for Joomla! (jps corrupted files although the error message was about missing part files) that was solved manually reinstalling the component. So I have tried uploading Solo files and overwriting the ones on my server but it has not fixed my issue.

jpa backups work fine.

The site is a Prestashop 1.6.1.3 site.

Please let me know what info do you need to check into this issue.

PS: Yes I have tested that password is correct several times (even copying and pasting from jps configuration!!)

The format of the jps files was upgraded to improve security a few months ago. Akeeba eXtract is end of life and will not be upgraded to handle the new encryption format. You need to use kickstart.php (available on our downloads page) to extract your encrypted archive directly on your site. Kickstart will call the installer when it has finished extracting the archive.

Hi Dale,
thank you very much for your reply. Nevertheless as I also mention on my post, Kickstart does not work either. Trying to restore a jps file created with 1.6 version of Akeeba Solo works correctly but trying to restore a jps file created with 1.7 version gives error.

What version of Kickstart are you using?

It is a long shot, but let's replace the kickstart.php file that you are using with a fresh copy. The error almost looks like the file is damaged.

Hi Dale,
that did it!!

Thank you very much for your help!! Using a fresh copy of Kickstart just downloaded fixed the issue.

I can now breath again!!

Thanks!!

You are welcome! I am glad it is working now.

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.