Support

Short version: This problem is caused by the malfunction of our CDN. I'll release an update today or tomorrow which will fix this.

Long version: Since a few releases ago, we serve the update provisioning information (the short piece of data which tells which is the latest version and where to get it) from a CDN. Unfortunately, the CDN was caching the update provisioning files for too long, making updates impossible for 1-3 days after each release. Today morning (GMT+3 time) I tried switching the cdn.akeebabackup.com to a non-CDN version source. Anyway, both the CDN and the solution were broken, causing Live Update to believe that there is no update available.

What I'm doing right now is to scrap the whole CDN-for-updates idea and resetting everything to contact directly akeebabackup.com. I will then release an update which you will have to install manually.

Sorry about that. Updates is the only thing I can not test reliably until after a release is made.

I beat the damn thing to submission. Pending a DNS update, here's what you can do after three hours from now to solve this issue:

1. Go to your site's back-end, Components, Akeeba Backup and click on the live update button (now reading "Live Update not supported"). Click on Refresh update information. After a few seconds it should come up with a page which tells you that you are either up-to-date or out-of-date. If it returns a "not supported" page again, retry in a few hours (DNS is a tricky beast and can take up to three days to propagate, depending many things).

2. If you have enabled Akeeba Backup's automatic update notification emails, don't do anything. Just wait up to 24 hours and it will solve itself.

And the best thing is that I don't need to issue an update on the code. Phew! It just took me a day to work around :D

You're welcome! I'd appreciate it if you could test this solution and tell me if it works. It works on my Rochen-hosted sites, as the DNS propagates in virtually zero time. I want to see how it works on non-Rochen hosted sites as well :)

Awesome! Thank you for the confirmation!

This report is very ambiguous and I can't make much of it.

"This" can mean: upgrading using the update notification email, upgrading using the Live Update, upgrading by installing it through the Joomla! installer, installing for the first time, taking a backup or restoring a backup.

"Wiped out" can mean: my files are gone, my database contents are gone, nothing is really gone but I can't login to my site.

These are 18 different things you might be asking support for. I'll take a wild guess: upgrading Akeeba Backup (usually through the update notification email) results in you being unable to login to your site. This issue is very well documented in our Troubleshooting Wizard and has nothing to do with Akeeba Backup.

Some further thoughts on that troubleshooting article and why it exists. Needless to say, the Joomla! session bug was squashed by yours truly, the patch is accepted and Joomla! 1.7.1 onwards won't suffer from it. The other Joomla! installation bugs are worked around as of Akeeba Backup 3.3.4. The remaining issue (user doing something funky with the Joomla! view levels and forgetting it until he logs out from his site) is obviously not something I can work around because it has no correlation with what I do in Akeeba Backup; that's a user issue and I'm documenting the workaround because people always think that Akeeba Backup is to blame. That's understandable. The last thing you remember installing is always to blame, right? More so when you perform an update through the one click action email which starts a new user session and makes the problem evident. But it's not caused by Akeeba Backup.

If I made the wrong wild guess, please start a new thread, explain what "this" and "wiped out" means and I can help you fix it without losing your work. There's no code in the installation or backup procedure which can delete anything on your site, so it's easy to work around it. If the problem happened during restoration, then you'll already have a backup and we can easily work around this issue. I just need to know which of the 18 possible problems you might be reporting is going on so that I can properly assist you.