Support

Akeeba Backup for Joomla!

#33143 Frontend backup failed

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by on Thursday, 02 July 2020 17:17 CDT

arc3c
Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

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:

Dear,

The backend backup is succeeding well but since one week, the frontend backup is always failing with this error:

* OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054
* Closing connection 518
curl: (56) OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054

Do you know where this error is coming from and how to resolve it.

Kind regards

Cedric

nicholas
Akeeba Staff
Manager
Error 10054 means that the TLS (HTTPS) connection was reset by the remote server. You need to ask your host about it.

However, if your problem only started on Saturday you need to check your TLS (HTTPS) certificate. Is it signed by Sectigo Ltd? If that's the case you will need to either upgrade the software you use to run the remote backup or use a different SSL provider (Let's Encrypt is free of charge and works fine). Here's some background. Some TSL libraries like GnuTLS (all versions) and OpenSSL before 1.1.0 could not understand that even if the topmost root CA (AddTrust) certificate has expired the certificate is still good if another CA in the signature chain (USERtrust) is marked as a root CA itself. This made all Sectigo certificates become untrusted overnight by a large proportion of remote clients which were using these outdated TLS libraries. Unfortunately, Sectigo certificates are among the cheapest paid certificates AND all older versions of PHP and cURL could only be compiled against the problematic TLS libraries. This combination broke a lot of things since Saturday. Both us and the Joomla project were working over the weekend to update our TLS certificates so that our clients don't experience service interruption (some was inevitable on Saturday morning). Again, this really only applies to you if you observed this issue starting Saturday and you have a Sectigo signed TLS certificate.

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!

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.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

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!