Support

Akeeba Solo

#25172 Solo reports incorrect Curl version of PHP 5.5 as funcional

Posted in ‘Akeeba Solo (standalone)’
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

PHP version
n/a
Akeeba Solo version
n/a

biopgoo
There seems to be an issue with PHP 5.5 and a defective CURL build that makes SOLO report that the backup works correctly, while it fails. This could be an issue with SOLO mistakenly indicating that that combination of PHP version and CURL build is a valid PHP version for backing up. I have been shocked to find out that two months of Backups have vanished even when SOLO said it was correct. It should be simple to check that combination of PHP version and CURL build. A nice big red warning of incorrect PHP version would be really helpful

BTW a feature I would like in additional configuration would be a drop down that allows me to choose what language I would like SOLO to be shown in. It seems to be related to the Web browser.

Totally unrelated it seems that the filename
Akeeba Solo Debug Log (4).zip
is rejected by the ticket system

Thank u

biopgoo
PHP 5.5 with defective CURL seems like it is default PHP on my hosting provider. I have opened ticket stating that backup will not work on any of our sites so it would be great that they set default PHP to be 5.6.

Akeeba Solo 1.8.1 does WSOD on installation on the index.php?view=wizard&task=applySiteSettings step

nicholas
Akeeba Staff
Manager
This issue has occurred in a grand total of two servers making it extremely isolated. Therefore building an automatic detection doesn't make sense (automation only makes sense when talking about economies of scale).

Furthermore, from where Solo is sitting it cannot possibly detect this issue. It sends a PUT request and Dropbox is supposed to reply with an HTTP 200 OK message with an empty body. The broken cURL version replies back with success (200 OK) and an empty body even though it didn't bother sending any data to the server. Moreover, since chunked upload to Dropbox may take a while to assemble the file (the call to upload finalization returns before Dropbox performs the assembly) we cannot check whether the file is uploaded immediately after its creation. The only reliable way to know that it failed is having a human check the uploads a few minutes to a couple of hours later.

So, you and another guy who are affected by the broken cURL build had to contact us and we were ultimately able to tell you to use a different PHP version. That's all we can do, I'm afraid.

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!

biopgoo
Phpinfo() reports Curl information 7.48.0 and if that is enough to know that curl is broken it would be nice to have. I have blacklisted PHP 5.5

nicholas
Akeeba Staff
Manager
No, this is incorrect. cURL 7.48.0 is perfectly functional. The problem is that yours and the other guy's host have applied some patch which is not part of the official distribution that breaks the build. If it was something as easy as checking a version number, as I said above, we would have already done that.

Let me put this in the most clear terms: your host screwed up the compilation. You have an extremely rare problem that affects a grand total of 2 people out of several hundred thousand users of our software. This issue is not worth any further investigation. Just make sure that you avoid the broken build on your broken host.

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!

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.