Support

Their server returned an HTTP 401. It says it doesn't like the username and password you provided. That's all I can tell you. I have no way of knowing why they return this status code. Maybe retry entering the username and password, after testing that this comination works with a different WebDAV client on your computer?

I am trying to determine something. Are you hosted on Infomaniak? The reason I am asking is this ticket. If you are both on the same host, I have an idea about what is going on.

Here are my observations. 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 also tested our WebDAV integration anyway against 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.

No code change. Code works fine. Suddenly, two clients using the same provider (Infomaniak) have the same problem at the same time. This says there is an issue with this service. Does it block our client? Has it stopped supporting basic authentication? Something else? I do not know. It's on their end. All I know is that we get an HTTP 401 back. They need to find out why their servers do that if we are sending them the correct username and password.

I knew it! :D

I will venture a guess as what it could've been. WebDAV is basically a set of extensions to HTTP to make it possible to write to files. The authentication part is still very much standard HTTP.

I suspect that they made a mistake configuring the HTTP authentication on their servers, only allowing Digest Authentication instead of also allowing the far more common HTTP Basic Authentication. Windows defaults to Digest Authentication. Many third party WebDAV clients support both authentication methods; if one fails, they fall back to the other. This is why they probably didn't notice what happened. Akeeba Backup, however, only supports HTTP Basic Authentication. Probably the patch is re-enabling HTTP Basic Authentication.

As to why we only support HTTP Basic Authentication, the reason is very much practical. Digest Authentication is a slow; you have to get a nonce, you have to know which hash methods the server supports, and then compile the authentication header. Yes, all this can be detected, but it takes several precious seconds. Each time you upload a file. If this doesn't limit the time you have to upload a file to the point that the file upload fails, it definitely makes everything go glacially slow. That's why we decided to not support it. It was technically possible, but completely impractical :/