Akeeba Backup for Joomla!

Sunday, 27 March 2016 12:38 CDT

palazzi

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:

Running update from manage, I clear cache, find updates and get this warning:

Warning
Update: Could not open update site #12 "FOF Updates (official releases)", URL: http://cdn.akeebabackup.com/updates/fof.xml

Loading your XML, I see there is an API key error:

<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>updates/fof.xml</Key><RequestId>AFE2297C0B6D8ED9</RequestId><HostId>2tdffR45IebH7zGCLhPBN6Qtavhe9D1bCd42ztm9E0l6ElPGSz6Wi8vFGieFZX2JC829Ce0/6Ag=</HostId></Error>

My guess is you have a typo in the CDN key so updates cannot load. Please let me know when this is fixed. Second weekend in a row I'm running into weird issues updating akeeba.

Sunday, 27 March 2016 16:25 CDT

nicholas

FOF 2 is deprecated and the updates have been removed from the CDN last week. Moreover, it's NOT necessary to update it manually. The latest version is installed when you install Akeeba Backup or Admin Tools.

The FOF updates were only there for third parties. All third parties have been informed since last year to switch to FOF 3 and pretty much nobody is using FOF 2 still. FYI, in the near future we will also switch all of our software to FOF 3. The only reason we hadn't done that already is that FOF 3 doesn't support Joomla! 1.x, 2.5 and 3.0 to 3.2 but Akeeba Backup and Admin Tools had to because of the two zero day exploits found in old Joomla! versions between October and December 2015. We had to make sure users of these old versions were able to back up and protect their sites before upgrading them.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Sunday, 27 March 2016 16:35 CDT

palazzi

Thanks for the quick reply - this only happens on 2 sites for me for some weird reason. With everything updated (except J! still on 3.4.8) if I clear update cache, and check for updates I still get that error on two of my sites. Since it's no longer in use, how do I clear it up? Ironically, this is not happening on my oldest sites, but ones mid-age.. in other words, a 4 year old site that has been upgraded over the years, no error. But on these, which are 3 and 2 year old sites, I get that error. Out of 15 sites updated, only 2 have shown the issue. If you would, please share how to fix the error from appearing. Thanks.

Sunday, 27 March 2016 16:51 CDT

nicholas

When Joomla! detects that an update site is no longer available it disables the update site. When you clear the updates Joomla! re-enables all update sites. Since they didn't let me add a Delete option in the update site manager the only way to get rid of obsolete update sites is to edit the database. You need to remove the row from the #__update_sites table that has the URL http://cdn.akeebabackup.com/updates/fof.xml

I am actually wondering why you ended up with an update site (update XML source) for FOF, though. It was add in the FOF installation package on March 13th, 2013 and removed on September 6th, 2013. There were very few versions of Akeeba Backup and Admin Tools which included this update site. Logically, it should be the oldest site that displays this error, not the newer ones. Unless you skipped some updates on the old site and had installed one of the few releases that added FOF 2's update site to Joomla!.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Sunday, 27 March 2016 16:54 CDT

palazzi

Thanks for this Nicholas, again great support. I'll go edit those two sites' entries out. No idea how they got there. It may be because I develop using a free version of akeeba, sometimes reuse the template code for next site and things carry over. When I launch I use the pay version and then load the latest and greatest. Just a weird workflow I suspect more than anything else. Again, appreciate it.

Monday, 28 March 2016 01:19 CDT

nicholas

Yes, that seems to be it. At one point your master site had one of these old versions installed and there you had your update site issue now that we removed the XML stream from our CDN :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Wednesday, 27 April 2016 17:20 CDT

System Task

system

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.

Edited by on 2016-04-27 17:20 CDT

Support