Akeeba Backup for Joomla!

Thursday, 22 April 2021 14:15 CDT

tomarriola

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:

We can't operate akeeba backup without it shutting down my entire server with a 502 bad gateway ngnix error. I host on digital ocean and manage the server with plesk.

Today I opened akeeba backup, edited a backup config and saved. That caused a serverwide crash. Its not the 1st time and it only happens with akeeba backup.

We are considering upgrading here to Plesk Obsidian and php /7.4 but thats a guess as to a fix for this.

Any ideas? There is no long file to send. I only saved a configuration.

Tom

Thursday, 22 April 2021 22:38 CDT

nicholas

Saving the configuration page is a very straightforward process. It just writes a single row to a single table using the Joomla database API. If that causes your server to crash something's wrong with your server. You need to have your server administrator look into it.

All I can tell you is that PHP 7.4 is fully supported. Not it's one of the two PHP versions we are currently developing against (the other is 8.0), it's also what we use on all of our live sites as well. While we do not have any Plesk-based servers, it's just a management console. The underlying servers are the same no matter if you are using Plesk, cPanel or a self-managed setup like we do in our development and testing servers.

If I were you I'd be looking into the NginX, PHP-FPM and the PHP error logs. When NginX throws a 502 it means that it can't talk to PHP-FPM or PHP timed out or it crashed. In all cases NginX sees that it can't receive a reply from the PHP-FPM server within its configured time limit, hence the error. This narrows down the problem to the NginX setup (do you have an adequate timeout limit for PHP-FPM?), PHP-FPM (does it have enough threads in the pool?) and PHP itself (did it core dump?). Your server administrator will know how to address any of these issues.

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!

Sunday, 23 May 2021 20:17 CDT

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