Support

> I remembered I left the ANGIE Password blank at the Configuration but I was wondering why it was asking for password.

This is a browser issue (and I was able to reproduce it with Chrome, Safari and Firefox). Browsers auto-fill the ANGIE password in two places:
- In the Configuration page (even though it's not a visible field!)
- In the Backup Now page
They use whatever password is stored for that site, usually the Super User's password. The next version of Akeeba Backup will have an ill-documented attribute in this password field which instructs the browser to never fill it in automatically.

> I deleted the file of akeebabackup from the CPanel, still it was locked out so I decided to delete the entire files of my site and made a fresh Joomla start as I can no longer wait for the advice of Nicholas.

Rebuilding the site is not necessary. Dale gave you the correct solution. Deleting that file after you extract the backup archive and BEFORE you click on the "Run the restoration" button in Kickstart will remove the password protection from ANGIE.

> I just wasted my time building the site. Perhaps, you should warn subscribers to put password on ANGIE to avoid wasting their time. If my suggestion makes sense, I read from Nicholas that if Akeebabackup subscribers can introduce some sensible suggestions to improve his products, he gives subscribers some breaks.

Rebuilding the site IS NOT NECESSARY. Even if the restoration script is dead, out, kaput you can still restore your site manually, using the emergency restoration: https://www.akeebabackup.com/documentation/akeeba-backup-documentation/unorthodox-emergency-restoration.html

Even this is not necessary. As Dale explained, deleting the password.php file removes the password protection from ANGIE.

Finally, even though the issue is caused by the browser auto-filling fields and our users not paying attention to that, I did find a way to prevent that and I'll apply that to the next release.

> Can you help me with the “Kickstart.php 404 error: Article Not Found” when I tried access kickstart.php for my site address.?

404 is a "Not Found" error. The only reason to get it is when you upload Kickstart to the wrong directory. What usually happens is that when you connect to your site by FTP or SFTP you are looking at the account root directory, not the web root. The web root is usually a directory called public_html, httpdocs, htdocs, www or something similar. This is where kickstart.php must be uploaded in order to be accessible from a browser. For further questions regarding this issue please contact your host.

> By the way, does the “kickstart” restoration perform the same purpose of restoring and site transfer with “Site Transfer Wizard”? I just want to know this because if I cannot get the “kickstart” to work for me, I will try the “Site Transfer Wizard.”

No, they are doing quite the opposite thing from each other:
- Kickstart will extract a JPA, JPS or ZIP backup archive.
- Site Transfer Wizard will not create a backup archive, it will transfer individual files.
In both cases, after Kickstart or STW is finished you will be launching the restoration script (ANGIE). This is what does the actual restoration.

PITFALL WARNING: Site Transfer Wizard does not work well across different hosts if you have large files (over 5Mb) or when your remove server limits the number of FTP connections per hour. In these cases it's far better using regular backup archives and Kickstart.