Support

The Joomla version is irrelevant. The backup engine is used in Akeeba Backup for Joomla, Akeeba Backup for WordPress and of course our standalone backup application Akeeba Solo. It does not rely on Joomla. Do note that I have been developing on Joomla 6 since its Alpha 1 version many, many months ago. My main dev site is Joomla 6 on PHP 8.4 and I also test on a combination of Joomla 4.4, 5.4, and 6.0 on PHP versions 7.4, 8.2, 8.4, and 8.5. That is to say, it's not your Joomla or PHP version; it's what I am using as my main dev target and I would've caught any issues months ago.

Moreover, there has been no update in Akeeba Backup in the last couple of months. Most importantly, the last time we updated the code for WebDAV was May 2023, over two and a half years ago. So, it's not a change in the code that has anything to do with it.

I tested it anyway on a Joomla 6.0.1 site running Akeeba Backup 10.1.0 on PHP 8.4.15 which is pretty much the configuration you are using. My target is a WebDAV server created on a cPanel-based site hosted by Rochen using cPanel's "Web Disk" feature. No problem at all. My 200 MiB backup (20 files of 10 MiB each) uploaded just fine.

The message you get means that your WebDAV provider replied with an HTTP 401 response. This comes from them, not us. They did not like the username and password you sent them. If you are sure your username and password is correct (Test it! Do NOT assume it's correct just because it used to work!) then the problem is either with your host, or your WebDAV provider. I can't help you with this. It's not under my control.

I am wondering if your host may be the problem. I have seen hosts which use very aggressive server-side caching, including caching non-GET requests and beyond the response's expiration time (both of which violate RFC 9111). If you are both on the same host, it would mean that something suddenly changed there, maybe they are doing something like that. I could also be chasing windmills and this being a much simpler problem with the WebDAV provider, so take what I said with a grain of salt.

No, Akeeba Backup is not the problem. As I told you:

Moreover, there has been no update in Akeeba Backup in the last couple of months. Most importantly, the last time we updated the code for WebDAV was May 2023, over two and a half years ago. So, it's not a change in the code that has anything to do with it.

I tested it anyway on a Joomla 6.0.1 site running Akeeba Backup 10.1.0 on PHP 8.4.15 which is pretty much the configuration you are using. My target is a WebDAV server created on a cPanel-based site hosted by Rochen using cPanel's "Web Disk" feature. No problem at all. My 200 MiB backup (20 files of 10 MiB each) uploaded just fine.

As I already told you:

I am wondering if your host may be the problem. I have seen hosts which use very aggressive server-side caching, including caching non-GET requests and beyond the response's expiration time (both of which violate RFC 9111)

Try using a different WebDAV server with your host. If that also doesn't work then the problem lies with your host.

IMPORTANT: Your host is the company which hosts your web site. This is standard terminology.

If accessing a different WebDAV server works, then the problem is with kDrive.

I don't know why you started by contacting kDrive before making sure that your host works, and why you are trying to involve me for something that is between your host and whichever WebDAV provider you are trying to use. I am not God Almighty. I cannot make third party companies outside my control do anything. I can only make a WebDAV client which works with any standard WebDAV server supporting HTTP Basic Authentication.