Support

Dear support team,



I want to use a current akeeba backup file to build up a test environment.

The extract works fine, also the database restore, but at the last step an internal server error occured 500.

it seems that the following script caused the error, because its url is used:

http://xavian.de/installation/index.php?view=finalise



So what can be the reason for that error. I did it often without any error.

Can it be a conflict using admin tools?



Best regards



Markus

Markus,

Was this backup done with the current version of Akeeba Backup? There was an old error during the finalization step, but it should not affect a 5.6.0 backup.

It is doing a few things in that phase of the backup:

• Deleting the /installation folder
• Deleting the backup archive
• Deleting the kickstart files
• Renaming the .htaccess file (it is "hidden" during the restore to keep it from blocking the restore)

Let's rename the /installation folder - we're not ready to delete it yet - and see if your site comes up. If it doesn't look right, you can rename htaccess.txt to .htaccess. If it looks OK, we can do the remaining steps manually.

Dear Dale,

I prepared a new backup with 5.6.0 and a restore with kickstart 5.4.0.
The result is the same, the last step caused a 500 error.

I renamed the installation folder to _installation and the side comes up with the htaccess.txt but not with the .htaccess.
But every called url caused a 404 because I am using sh404sef and that uses url rewriting and needs a .htaccess file.

I would think there is something wrong, because I did this backup restore procedure several times without an error
and I don't understand why it doesn't work anymore.
The only difference I remember is that I am using akeeba admin tools now.

Best regards

Markus

Admin Tools would not block the restore process unless you had an enhanced .htaccess file in a folder above the on you are installing into. Then it would inherit the directives from that one. During the extraction, Kickstart will rename the .htaccess file for the current site. The file for the current site should be in the root and named htaccess.bak. You can rename that to .htaccess manually. You would also need to rename the /installation folder.

Dear Dale,

the problem is solved.
In the last restore step just before the url
http://xavian.de/installation/index.php?view=finalise
will cause the 500 error I have to deactivate the option that the .htaccess will be replaced with the Jooma default htaccess file.

I am quite sure that I never deactivated this checkbox to restore the backup and that the Akeeba Admin Tools are the reason for that.

Best regards

Markus

Markus,

It is possible that the 500 error is caused by the enhanced .htaccess file created by Admin Tools. But Admin Tools is not running at that point in the restore, that's what I meant that it wasn't caused by Admin Tools.

Once you get the site up with the new default .htaccess file, you can create a new enhanced .htaccess file. It may work, because some of those options have to be formatted for the specific version of Apache that your server is running. If you have trouble, start by changing the Track and Trace option to "---", not yes, not no, the "nothing selected" option. That one is the most common option that servers don't like.

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.