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:
Hello, I have been working with Rackspace Cloud Files for my backups with not problems at all, but I have one site I can not send backup files to Rackspace; I have tried everything with no success.
The warning: Access denied.

Thanks for your help.
Enrique

Rackspace recently published a new version of the API that we use to access the service. The old version is no longer available. We have found that the new API is just unreliable and randomly returns "not authorized" results even though everything is sent correctly. Later, the same setup will work. "Later" could be 5 minutes or 5 days. We think it has to do with the new central authorization, it gets too busy and fails to authorize valid users.

At the current time, we do not recommend Rackspace as a cloud provider. The reasons are the authorization problems and that other cloud services are much faster.

OK, thanks for your fast reply. I will contact Rackspace to see what they have to say.
Have a great day!

Here's what Nicholas actually said when I asked him about it:

Regarding the API issues with RackSpace, I've not written an announcement.

The fact remains that their new authentication API sometimes responds and sometimes it doesn't. We have no control over it.

FYI, this issue also happens with third party client software such as CyberDuck.

I've verified that our implementation is correct (even though RackSpace's API documentation has errors...) and I've verified that the "known good" implementation of CyberDuck experiences the same issues as us.

The difference in the new API is that they have implemented a centralized authentication service.

It seems that sometimes it's overloaded and responds incorrectly that the user can't be authenticated.

There's also another issue regarding hosts with missing system-wide Certificate Authority caches.

I've written a workaround which will be implemented in 4.1.0 stable, but this only accounts for the rare SSL errors, not the 400 Not Authorized replies from RackSpace.

The 400 errors are due to the problems in RackSpace's authentication API.