Supports Joomla 1.5 and later (Akeeba Backup 3.4 and later). We extended our support for remote sites using an Akeeba Backup JSON API as old as the one supported by Akeeba Backup 3.3.0 which was released in mid-2011, supporting Joomla 1.5 and PHP 5.3. The maximum supported version is what we have released in March 2023. Of course this includes all versions of Akeeba Backup for WordPress and Akeeba Solo (released between mid-2013 and March 2023). In short, if you have a site using any version of our backup software released the past thirteen (13) years you can use Akeeba Remote CLI with it. Neat!
Please note that not all features are available in all versions of our backup software. Exporting and importing profiles require API level 320 which was introduced in Akeeba Backup for Joomla! 3.6.0, released in mid-2012.
Works with sites on recalcitrant servers with way too verbose PHP error output. In the past, our software could get stopped by servers outputting PHP deprecated notices, notices, and warnings in the output. While having servers outputting these PHP non-error messages in the output is a bad idea for various reasons (including the security of your site) we understand that in many cases the server configuration may not be under your control, e.g. when you want to take a backup of a site being handed over by the old site integrator.
Convey wrong secret key errors instead of reporting there is no way to connect to the site. Akeeba Remote CLI 2 would always report “there's no way to connect to your site” regardless of the actual reason of the error. This version will tell you if the problem is the wrong Secret Key, so you can troubleshoot a more narrow error condition without nearly as much frustration.
Now reports when a record does not exist instead of returning a more generic error about the failed operation. You previously got a generic error such as cannot download or cannot delete. Now you are told that the reason is the record does not exist. If you get the old error message it means that there was a server error instead.
Remove --verbose option, it's implied when you use --debug. We saw that some people, especially those who should know better, would constantly forget to add the --verbose option to get detailed information about why the Akeeba Backup JSON API did not work, thus misleading them into misdiagnosing the problem. Using the --debug flag will now turn on verbose output as well and override the --quiet flag as well.
Using --debug also generates the log file remotecli_log.txt. If you are trying to troubleshoot a backup issue, using the --debug flag (previously along with the --verbose flag) can generate a lot of output which overflows your terminal's scroll buffer, making it hard to get a cohesive view of what is going on. Using the --debug flag will now create the file remotecli_log.txt in the current working directory, mirroring the debug output you see on the screen. If you get lost, open this file, and you can see exactly what has been going on.
Bug fixes and minor improvements. Please check out the CHANGELOG below.