Support

Akeeba Backup for Joomla!

#42718 Timeout issue with remote backup execution on new server

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
6.0.4
PHP version
8.4
Akeeba Backup version
10.2.2

Latest post by sandvelder on Friday, 13 February 2026 12:27 CST

sandvelder

Dear Nicolas & the Akeeba Team,

I currently manage 30 Joomla websites, all of which successfully run monthly backups via CRON jobs. These sites are hosted on a single server and run without issue.

I have recently added a 31st site, hosted on a different server provided by a colleague. While I have matched the environment to my primary server as closely as possible, I am encountering a timeout issue.

When I attempt to test the backup via the front-end backup URL in Chrome to verify the configuration before setting up the CRON job, the browser returns: "This site can’t be reached – [site name] took too long to respond."

Environment Details:

  • Joomla: 6.0.4

  • Akeeba Backup: 10.2.2

  • PHP: 8.4

  • Memory Limit: 1G

  • Max Execution Time: 300

  • Max Input Time: 600

Troubleshooting performed:

  1. Verified PHP settings (as noted above).

  2. Cleared all browser data, cookies, and cache in Chrome.

  3. Confirmed the site is otherwise accessible; the error only occurs when triggering the backup URL.

Given that this is a different server environment, do you have any recommendations on specific PHP extensions or server-side firewall settings (such as mod_security) that might be interfering with the remote execution of the backup script?

I look forward to hearing from you.

Kind regards,

Francois

J. Francois Barnard

logo_2022_250.png

 

nicholas
Akeeba Staff
Manager

When I attempt to test the backup via the front-end backup URL in Chrome 

This will never work, nor should it ever work as per the documentation:

  • It is not designed to be run from a normal web browser, but from an unattended cron script, utilizing wget or cron as a means of accessing the function.

  • Normal web browsers tend to be "impatient". If a web page returns a bunch of redirection headers, the web browser thinks that the web server has had some sort of malfunction and stop loading the page. It will also show some kind of "destination unreachable" message. Remember, these browsers are meant to be used on web pages which are supposed to show some content to a human. This behaviour is normal. Most browsers will quit after they encounter the twentieth page redirect response, which is bound to happen. Do not report a "bug" stating that Firefox, Internet Explorer, Chrome, Safari, Opera or another browser doesn't work with the front-end backup feature. It was NOT meant to work by design and you've been sufficiently warned.

If this is what you mean by "timeout", then there is no timeout. It's just the nature of the front-end backup. Use it in a CRON job with wget and it will work.

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!

sandvelder

Dear Nicolas

Thank you so much for your prompt response!

I usually test the command on the browser and they usually work. I found the "ID-10-T" problem on my side, and rectified it. :-) My 31st Joomla site will now backup once a month on the first day at 00:45. Perfect!

Have a good weekend.

Francois Barnard

J. Francois Barnard

logo_2022_250.png

 

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!