Support

I can also see a timeout error. This is usually caused by accidentally using the wrong kind of PHP binary, which seems to be the case in your site:

INFO |101129 00:00:08|PHP Interface :cgi-fcgi

You are using the PHP CGI binary which is designed to serve web pages, not run command-line PHP scripts (like Akeeba Backup's backup.php). It has a preconfigured time limit of 30 seconds, which makes the script time out. As per the documentation, you have to use the path to the PHP CLI (CLI = Command Lie Interface) binary in your CRON job's command-line. If you are unsure about this path, ask your host. If they reply with the same path you're using, escalate your support request until you get to talk with a support technician who can actually spell PHP and who can help you with that.

If that doesn't work with your host, please edit the backup.php file and place the following line right after the

I forgot to mention it, I apologize. The one you edited is indeed the correct one.

@biopgoo Yes, the ZIPArchiver engine tries to use PHP's ZIP class to handle the file compression. Since we have no control with the specifics of the compression we consider it only suitable for very small sites running on quite beefy servers. If you try to compress a large file with it, it will result to a 0 byte file. Using the regular ZIP engine or the JPA engine is the recommended method of backup.

@breathwork It is quite apparent that your host won't allow you to go over that maximum execution time limit they have set in their PHP CGI binary. The only technically possible workaround is to ask them which is the path to the PHP CLI (Command Line Interface) binary on their server, then use it in the CRON command line as per the instructions in our documentation. This is a limitation of how PHP works so there's only that much we can do about it.