Support

 Updating problem with Akeeba Admin Tools and Akeeba Backup:

Error connecting to the server:
Oh, dear, we have a 403
ACCESS FORBIDDEN
Please try one of the following pages:
Home Page

Package download failed: https://www.akeebabackup.com/component/ars/?view=download&id=2629&dlid=&dummy=my.zip

The 403 error indicates that your site can not communicate with our update servers. This may be caused by your host's firewall.

Please ask your host to open communications over TCP port 80 to cdn.akeebabackup.com (note to host: this is a CDN, the hostname resolves to different sets of IPs based on geolocation) and TCP port 443 to www.akeebabackup.com.

Dale,

Thanks for the reply. My issue with your reponse is that we have 'never' encountered this particular error message on any of our clients Joomla websites (over 100) with 8-20 installed addon's over the past 8 years! If Akeeba is requiring something 'very' unique to your own updating system versus everyone else, then Akeeba needs to rethink it's update procedures. If Akeeba is using the same update ports that everyone else is using, then the issue is not on our hosting service but on your end.

Things change. Until very recently Joomla!'s Extension Updater could not update a paid extension. Now they can, both in the 2.5 series and in the 3.2/3.3 series. But they use two different techniques to do it.

Let me ask Nicholas to take a look at this to make sure I'm on the right track.

There have been several similar update errors this afternoon. One of them has been solved, it was a bad Download ID. Please double check your Download ID to make sure it is correct. You can find your proper ID under the My menu item above.

Thanks Dale. That was the issue. I was unaware that the download ID's were generated via a hash of your users email addresses and passwords. I believe I recently change the passwords on many site due to the Heartbleed virus as a precaution. If I get this error message on other sites, I'll get the new download ID's that have been generated.

I wasn't thinking about Heartbleed. We're going to get a whole new round of bad Download IDs. :-(

You can prevent the ID from changing by using Add-On Download IDs instead of the main one. The Add-Ons are not based on email and hashed password.

Dale,

OK, all of my clients use the Download ID's that are generated when I set them up. So now I was wondering why it might have changed? Is this something that has been done internally by Akeeba for some ID's?

We didn't do it this time! The December 25 change was us. When we updated to Joomla! 3.2 and used the new password hash, that changed all of the Download IDs. It was big fun for a while there.

If they changed their password on our site, that would change the primary Download ID. If they are using Add-On IDs, they are not supposed to change.