Support

I am looking at support tickets and documentation but I am not seeing a quick clear answer. I tried to restore my backup and got this message. Now the site is down and I cannot access the front or back end.

This process of restoring created a new folder. Clicking on run site restoration script opens windows with these errors. /installation/index.php


Error 403 - Forbidden



You don't have permission to access the requested resource. Please contact the web site owner for further assistance.

I am assuming Admin Tools is causing this but now cannot get in to add a directory if that is the fix?

Perhaps some documentation under Restore Latest Backup on using both tools together in the documentation would be helpful.

Thank you

There should be an exemption in .htaccess Maker that allows access to that file during an internal restore. It is there by default, it is possible that it was accidentally deleted.

Since the site is down, we don't have to worry about that right now, we can't do an internal restore. You need to put the backup archive in the root of your site, along with kickstart.php. Next, rename your .htaccess file so you can execute kickstart.php. Then visit kickstart.php, in the address bar of your browser go to www.mysite.com/kickstart.php. All the same things happen as with an internal restore, you just get a better view.

When you get everything working again, the two lines that need to be in "Allow direct access to these files" in .htaccess Maker are:

administrator/components/com_akeeba/restore.php
administrator/components/com_joomlaupdate/restore.php

Hello, I understand the .htacess file should have an exception in it. I am confused why this is not in a RED warning in the documentation. This must be a very common issue.

I added this to my .htacess after deleting the Installation directory and it went through.

Allow access including PHP files:
installation

Just strange I could not find this straight away.

I think it is not emphasized because the exemption is a default, it is shipped with Admin Tools.

The two you mentioned are in there when you install and add the custom .htacess. The one killing my site was not.

If you do not add "installation" to the exceptions trying to restore the site fails, both backend and frontend are blocked. At least that was my experience. The files needed to restore the site are in this directory and when I click on the restore it's cannot finish.

That was my experience. When I deleted the "installation" folder the site was back and accessible. I added "installation" to the exceptions and the restore went through.

Does this sound accurate?

Hi Nicholas, I figured it was a glitch on my site. I found it hard to believe you were so thorough would overlook something like this. I am not sure what my scenario was exactly. I have never used it before and this was a test site I was restoring to default.

I'll explore this more.

Thanks for your help and for clearing this up.

Just to be clear, I just ran the restore from the backup extension and followed the screens. I did not do anything manually.

So you are saying it should have taken care of renaming the .htaccess for me?

I will try it again and see what happens looking via FTP.

Yes, it should be taken care of automatically. The restore.php program renames .htaccess, which eliminates the need for further exceptions.

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.