Akeeba Backup for Joomla!

Monday, 06 April 2026 01:31 CDT

crimleit

Hi Nicholas

9 out of my 110 websites are producing an error after finalizing the weekly backup. The backup process itself works (the jpa file is saved here: public_html/administrator/components/com_akeebabackup/backup) but the step «Post-processing engine = Upload using WebDAV» has been failing for weeks. I use Phil's mysites.guru remote maintenance tool.

All these 9 websites are hosted by the same webhoster 1ahosting.ch.
The WEBDAV target is kDrive by Infomanikak.

31 other websites hosted by the same webhoster are backing up without issues.
The WEBDAV target is also kDrive by Infomanikak.

This makes it difficult for me to understand where the cause for these errors might be. The majority of the websites hosted by this webhoster are transferring the jpa files using WEBDAV to kDrive without any issue. But the 9 websites mentioned above do.

The webhoster's support answers:

«We do not block outgoing connections. The backup itself runs smoothly (steps 1–29, file size approx. 186 MB, duration approx. 45 seconds). The problem occurs from step 30 onwards, when the WebDAV transfer to Infomaniak kDrive begins. The log shows the following pattern: The backup engine initiates a check of the destination directory ‘akeeba-backups/’ on the kDrive server. After that, there is no further response – neither a confirmation nor an error message. Every 12 seconds, the engine restarts the process. This repeats four times without the actual file upload ever taking place. There are no blocks or changes on our end. The PHP limits are generously configured (max_execution_time: 300s, memory_limit: 2048 MB) and are not a factor here.»

I attached an «All information and debug» log file. Where do you think is the cause for these errors: webhoster or kDrive?
Gratefully waiting for advices :-)

Thank you very much and kind regards
Chris

Monday, 06 April 2026 02:10 CDT

nicholas

Your host did an excellent job at telling you what the problem is. I would've further told you that this means the problem comes from either the host blocking the connection at this point, or the remote end. Your host did have that in mind when they told you that they do not block outgoing connections. Therefore, what they are politely saying, is "This is a kDrive problem; go bother them".

I would like to also remind you of your December 2025 ticket. If you recall, there was no change in our code, no change in your configuration, but the upload to kDrive failed because they had cocked something up on their end. I also see this ticket of your from November 28th, 2025. Again, you had a problem with kDrive on some hosts. Back in August you had a problem with WebDAV again because of 2FA (I guess you had to create an app-specific password instead of using your regular account password).

I see a consistent history of issues with you trying to use kDrive. Not only you are wasting a lot of time to their problems, you also do not have a reliable storage for your backups which is a major risk factor.

I would strongly recommend using your Synology NAS instead. Having Akeeba Backup Pro upload to a Synology NAS hosted at your home / in your office is a very popular combination in the D-A-CH area in particular – I presume because it's great for privacy, and fairly easy to set up, plus you guys have had good ADSL2 and fibre Internet for ages. My personal experience is that Synology NAS is very reliable for backup storage.

If you want to keep things strictly off-premises, I can also wholeheartedly recommend Scaleway from first-hand experience. They're a French company offering similar services to Amazon AWS with data centres in Paris, Milan, Amsterdam, and Warsow. Their storage service is S3 compatible and works perfectly with Akeeba Backup.

Of course, what you choose to do is up to you. I feel obliged to give you not just support, but also my objective analysis and recommendations. You can choose to keep trying with kDrive, but be warned you will be contacting them every few months to fix problems they create as it seems.

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!

Monday, 06 April 2026 08:23 CDT

crimleit

Thank you Nicholas. Yes, I do remember my December 2025 issue with kDrive. My current backup strategy is as follows:

For as many websites as possible, I use my Synology NAS.

My 110 websites are hosted at different webhosters:

40 are hosted by 1ahosting.ch
→ none of them works with my Synology NAS
→ all of them worked with kDrive before long
→ for a couple of weeks, 9 of them do not work with kDrive any more
→ 31 still work fine with kDrive

30 are hosted by myself which is a reseller hosting in partnership with kreativmedia.ch
→ all of them work fine with my Synology NAS

24 of my customers have their own hosting trusting kreativmedia.ch as well
→ some of them work fine with my Synology NAS
→ some of them do NOT work with my Synology NAS, but they do work with kDrive

16 customers who have their own hosting such as hoststar.ch, metanet.ch, novatrend.ch, netzone.ch and many more
→ some of them work fine with my Synology NAS
→ some of them do NOT work with my Synology NAS, but they do work with kDrive

I am sure you will understand, that this situation is more than unsatisfactory, it's awkward: my backups are stored at two different places. That’s simply out of sheer necessity. Now, the 9 websites mentioned above are resisting any variant of post processing target: kDrives keeps failing and my Synology NAS keeps failing as well. From week to week, I download these jpa files manually using FTP. Which of course is cumbersome.

I am trying now to find out the reason for my Synology NAS failing in some cases.

Thank you very much and kind regards
Chris

Monday, 06 April 2026 16:21 CDT

nicholas

Uh, 110 sites trying to all send backups to a single prosumer-grade NAS may be too much for it. For starters, even if you're on fibre Internet, you are limited in bandwidth to the point that if more than around 20 sites are trying to send files at the same time your connection will be saturated, the upload become slow, and the whole process will time out. And that's if –a very big if– the NAS can manage all these connections.

Prosumer-grade storage is great if you have one site, maybe a small handful that you can offset backups for so that they don't spam the storage all at once. With over a hundred sites you need a professional-grade storage solution. My suggestion is to look into Scaleway, or something similar. I have hands-on experience with Scaleway and Amazon S3; neither has ever let me down.

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!

Tuesday, 07 April 2026 04:26 CDT

crimleit

Thank you Nicholas.

I will take your advice on board and consider Scaleway.

I can reassure you that not all 110 websites perform their backups at the same time. The backup schedules I have set up on mysites.guru follow a well-thought-out plan and are spread out not just over several hours, but even over several days.

Thank you very much and kind regards
Chris

Support