Akeeba Backup for Joomla!

Wednesday, 01 October 2025 14:19 CDT

davidascher

I have searched for something like this already having been reported but I seem to have the opposite problem from what people have reported in the past. In their cases, the scheduled cronjobs to perform backups were not succeeding but manual backups were succeeding; in my case scheduled cronjobs to perform backups DO succeed but manual backups do nothing. I just get the initial screen and no sign of activity and no logs of any kind. The automatic back prior to an update (to Joomla 5.3.4) also does nothing in the same way as a manual backup. (My backup archives are sent to BackBlaze B2 - which is a great service that you suggested. Thank you for that, although the transfer of the backup archive to BackBlaze fails occasionally without explanation, that happens rarely enough that it is tolerable and has nothing to do with this issue. )

I have 3 other sites running on the same VPS and none of them have this issue.

Without a log file to look at, I don't know how to troubleshoot this. I don't know when the problem started as I don't generally do manual backups, I rely upon the scheduled backups. I first noticed it when I tried to update this site to Joomla 5.3.4 and the automatic backup prior to update just did nothing. I then tried a manual backup and that did nothing. I then tried running the backup cron job manually and it succeeded.

I'd be happy to supply additional information, but I'm at a loss to know what information I can supply about the failure when I cannot find any kind of error indication in any log file I've examined.

Wednesday, 01 October 2025 17:14 CDT

davidascher

I have attempted to do manual backups on this site using my Android tablet. I seem to have no problem backing up the site manually using my Windows 10 laptop.

I cleared my (Chrome) browser's cache - clearing out everything from forever (which I will probably regret doing at some point in the future) and manual backups still did 'nothing'. No sign of activity and no log activity that I could find.

I then tried manual backups using Firefox, Opera, Samsung's browser - all worked just fine.

I uninstalled and reinstalled Chrome and that made no difference at all. Manual backups still do nothing at all.

I'd think that if the manual backups work on three other browsers they should work on Chrome after clearing out all the saved data in Chrome and uninstallling and re-installing Chrome. I look forward to any suggestions for what might be wrong and how to fix it.

Thursday, 02 October 2025 00:37 CDT

nicholas

although the transfer of the backup archive to BackBlaze fails occasionally without explanation, that happens rarely enough that it is tolerable and has nothing to do with this issue.

It has to do with their architecture. Most services have a frontend API router which receives the upload and routes it to the actual storage server – the machine that's choke-full of disk drives. BackBlaze B2 has us initially communicate with a very lightweight API router which gives us an upload endpoint URL. That upload endpoint URL essentially has us connect directly to the specific storage server your data will be stored into. The problem is that if the storage server is busy, or otherwise won't receive the request… the upload fails. The benefit of this approach, though, is that that it's a much simpler architecture for them, which is why they can sell it dirt cheap. If you can live with the occasional failure, that's good; their price is hard to beat :)

in my case scheduled cronjobs to perform backups DO succeed but manual backups do nothing.

You are in luck, because not two weeks ago I got an OnePlus Pad 3 to replace my decrepit, six-year-old iPad Pro. I know from first-hand experience that Google Chrome on Android does work with Joomla 4.4 and 5.3 (and 5.4, and 6.0, and 3.10 if you are curious!) and Akeeba Backup. Just before I started replying to support requests this morning I did take a backup of a testing site using my tablet.

The other data point we have is that everything works fine on your laptop, therefore it's not a matter of having a third party extension or a CDN which might be screwing up JavaScript delivery or execution. This is important, as it rules out an entire branch of devilishly complicated troubleshooting we could've followed.

You used other browser (I presume on your tablet) which rules out DNS configuration, system TLS certificate cache, and any device-level and connection-level issue. That's also good, because it killed off yet another branch of troubleshooting dead in its tracks.

You also said cleared the Chrome cache and even reinstalled it. So, it's not a matter of a caching issue.

So, we have an issue that only happens with Chrome on your tablet. It's not an issue with Chrome on Android in general, and it's not an issue with your tablet. This leaves us with Chrome extensions and ad blockers. Can you try disabling all of that, even if they sound unrelated to the problem, and retry the backup?

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!

Thursday, 02 October 2025 06:45 CDT

davidascher

Chrome on Android doesn't support extensions. I have no ad blocker on my Android tablet.

It's Chrome 140.0.7339.207 running on Android 15; SM-X210 Build/AP3A.240905.015.A2.

I can't see how the Chrome version or Android version could be relevant in this case, but I thought I would let you know that info anyway.

I will do some more testing - I have an Android 12 phone that I will test on to see if it also has this issue. I will also create a test copy of the site and see if this problem occurs on it as well - I would hope it does. I will let you know the results of that testing when I have it. I have an appointment this morning so it won't be until later today.

If you have access to an Android device and would find it useful to try this yourself, I can set up a Super User account for you to work with. Let me know if you think that would be useful. If you can't reproduce the problem because you don't have an Android device to test from, then that would likely be a waste of time.

I have turned on system debugging and took a look at what it reports ... It appears that the process gets as far as

infoakeeba.runpluginstrait - Event "onComAkeebabackupDispatcherBeforeDispatch" resolved to class Joomla\Event\Event -- called from Akeeba\Component\AkeebaBackup\Administrator\Dispatcher\Dispatcher->triggerPluginEvent at [ROOT]/administrator/components/com_akeebabackup/src/Mixin/TriggerEventTrait.php line 75
infoakeeba.runpluginstrait - Event "onComAkeebabackupBackupControllerBeforeExecute" resolved to class Joomla\Event\Event -- called from Akeeba\Component\AkeebaBackup\Administrator\Controller\BackupController->triggerPluginEvent at [ROOT]/administrator/components/com_akeebabackup/src/Mixin/TriggerEventTrait.php line 75
infoakeeba.runpluginstrait - Event "onComAkeebabackupBackupControllerBeforeMain" resolved to class Jooml...
infoakeeba.runpluginstrait - Event "onComAdministratorHtmlViewBeforeMain" resolved to class Joomla\Event...
infoakeeba.runpluginstrait - Event "onComAdministratorHtmlViewAfterMain" resolved to class Joomla\Event\Event -- called from Akeeba\Component\AkeebaBackup\Administrator\View\Backup\HtmlView->triggerPluginEvent at [ROOT]/administrator/components/com_akeebabackup/src/Mixin/TriggerEventTrait.php line 75
infoakeeba.runpluginstrait - Event "onComAkeebabackupBackupControllerAfterMain" resolved to class Joomla\Event\Event -- called from Akeeba\Component\AkeebaBackup\Administrator\Controller\BackupController->triggerPluginEvent at [ROOT]/administrator/components/com_akeebabackup/src/Mixin/TriggerEventTrait.php line 75
infoakeeba.runpluginstrait - Event "onComAkeebabackupBackupControllerAfterExecute" resolved to class Joomla\Event\Event -- called from Akeeba\Component\AkeebaBackup\Administrator\Controller\BackupController->triggerPluginEvent at [ROOT]/administrator/components/com_akeebabackup/src/Mixin/TriggerEventTrait.php line 75
infoakeeba.runpluginstrait - Event "onComAkeebabackupDispatcherAfterDispatch" resolved to class Joomla\Event\Event -- called from Akeeba\Component\AkeebaBackup\Administrator\Dispatcher\Dispatcher->triggerPluginEvent at [ROOT]/administrator/components/com_akeebabackup/src/Mixin/TriggerEventTrait.php line 75

It doesn't appear that there is any helpful info there. Is there any other tracing mechanism that can be enabled?

Thanks

Thursday, 02 October 2025 07:15 CDT

nicholas

Beyond the tablet, I also have a Samsung Galaxy S24 phone. Since it's the same manufacturer, Android version, and Chrome version I tried taking a backup of my site with it. It works perfectly fine.

I really can't think about what could be the problem here. Anything I can think of would either affect the entire device, or the entire site. Having something which doesn't work on a specific browser on a specific device for only a specific site sounds like a browser extension issue. I am not sure if it's possible for apps to install extensions or services used by Chrome on Android, to be honest. I know that auto-fill does allow that, e.g. how things like 1Password integrate to the browser. They literally run their own code on the page. Does Chrome allow anything else beyond auto-fill? I have no idea.

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