Support

Akeeba Backup for Joomla!

#42664 Akeeba Causes Check for Updates to fail with 504 Gateway Timeout

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
5.4.2
PHP version
8.2.30
Akeeba Backup version
10.2.2

Latest post by nicholas on Sunday, 25 January 2026 15:20 CST

Friday, 23 January 2026 15:25 CST

sforsgren

When I go to /administrator, intermittently the tile that tells you how many updates are available will error out.  If I click the tile to go to Check for Updates, sometimes it will work but commonly, it will hang and then timeout with 504 Gateway timeout.

These messages also appear on the backend:

Update: Could not open update site #641 "FOF 4.x", URL: http://cdn.akeeba.com/updates/fof4_file.xml
Update: Could not open update site #654 "Admin Tools Core for Joomla", URL: https://cdn.akeeba.com/updates/pkgadmintoolscore.xml
Update: Could not open update site #658 "Akeeba Backup Core for Joomla!", URL: https://cdn.akeeba.com/updates/pkgakeebabackupcore.xml

I see these in the logs:

2026-01-23T17:01:43+00:00 INFO 75.70.226.11 updater Loading information from update site #658 with name "Akeeba Backup Core for Joomla!" and URL https://cdn.akeeba.com/updates/pkgakeebabackupcore.xml took 20.00 seconds
2026-01-23T17:01:43+00:00 WARNING 75.70.226.11 updater Error opening url: https://cdn.akeeba.com/updates/pkgakeebabackupcore.xml for update site: Akeeba

Also:

2026-01-23 17:01:31 UTC [apache][:warn] [pid 10603:tid 10603] [client 75.70.226.11:12148] Timeout waiting for output from CGI script /<removed>/public_html/administrator/index.php, referer: https://www.betterhealthguy.com/administrator/index.php

I sent this information to Siteground and they responded:

I then attempted to make a cURL request to https://cdn.akeeba.com/updates/pkgakeebabackupcore.xml and the second request timed out. The reason is that the connection to one of the Akeeba CDN IPs fails:

baseos | betterhealthguy.com | <removed>:~$ telnet 143.244.60.193 443
Trying 143.244.60.193...
telnet: connect to address 143.244.60.193: Connection timed out

Thus I would suggest to contact Akeeba and ask them to double check if your server's IP 104.154.211.192 is blocked and if yes, then to remove the limit so updates can be successful.

Thank you in advance!

Edited by sforsgren on 2026-01-23 15:26 CST

Sunday, 25 January 2026 11:28 CST

nicholas

This is on a CDN hosted by BunnyCDN. I couldn't tell you the IP address as it is specific to where you are from.

I can access the URL just fine from all the geographic locations I have access to. In each one of them, the domain resolves to a different IP, none of which is the one you mentioned. Unfortunately, I do not have any server in Chicago (that's where your hosts' servers are based on the IP they are mentioning), so I can't check directly.

I also note that the A record is very short-lived, its TTL is just 35 seconds. Is it possible that their resolver or upstream DNS server has cached the DNS record way past its TTL, meaning it's no longer valid?

They –or you, from an SSH session– could check that by doing dig cdn.akeeba.com @1.1.1.1 to get the DNS resolution directly from CloudFlare CDN, or dig cdn.akeeba.com @8.8.8.8 to get the DNS resolution directly from Google CDN. In both cases the local resolver and the upstream DNS server it's configured to use are completely bypassed. However, since 1.1.1.1 and 8.8.8.8 are always served from servers close to you (to oversimplify: it's the DNS equivalent of a CDN), you will see the same IP as your local DNS resolver should be seeing.

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, 25 January 2026 12:56 CST

sforsgren

Siteground responded as follows:

-----

I've noticed that the hostname cdn.akeeba.com is associated with multiple IP addresses within the network 143.244.60.192/27. This particular network was previously blocked on our end due to concerns over malicious activity. However, we have now lifted this block, and you should find that access to the hostname cdn.akeeba.com is restored and functioning as expected:

-----

Thus, I will continue to monitor for any ongoing issues and appreciate your support very much!  Thanks for the excellent tools you make available for Joomla!

Sunday, 25 January 2026 15:20 CST

nicholas

Well, that would explain it :D Those IPs are from one of the big datacenter and server providers which handle a very large proportion of the traffic on the Internet. Think about Akamai, but not a household name to get an idea of what I am talking about. BunnyCDN is using several of these providers for their edge servers. I think the SiteGround agent must've escalated internally to someone who immediately saw the problem and fixed the problem on their end. Well, it happens. I can't and won't be mad about things that are only obvious in retrospect :)

Have a great rest of your weekend and thank you very much for your kind words!

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: 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!