Akeeba Backup for WordPress

#28352 – Internal upgrade to 2.3.3 failure

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Friday, 01 September 2017 14:27 CDT
We are consistently running into failure notices on every attempt (multiple sites) to do an internal upgrade for Akeeba WP 2.3.2 to 2.3.3. Consistent failure on every site on which we have attempted this upgrade.

Screenshot of JSON Parse error notification attached.

Switching over to a manual upgrade (deactivate, delete, re-upload, reinstall, reactivate) severs the connection to previous backups made to the home server (we backup both to the host server so that our clients have access to backup files, and then, alternatively, to our own server in the cloud for emergency restores if the server fails.

Thank you.

Custom Fields

WordPress version (in x.y.z format) 4.8.1
PHP version (in x.y.z format) 5.6
Akeeba Backup version (x.y.z format) 2.3.2
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!