WebDav problems like "Failed to copy: 403 Forbidden"


tested with: v1.56.0-beta.5505.f593558dc
OS: windows Server 2016 Server
Cloud storage system: webdav, windows server IIS

rclone config:

type = webdav
url = http://xxx.aaa.com
vendor = other
user = dompie
pass = XXXXXXX

I connect to a webdav server.

rclone mount Webbi: n:
This mount works just fine. I can copy files and create directories.

What does not work is this.

rclone copy c:\Users\soul\Documents\Jasmin Webbi:test

Or this
rclone copy c:\Users\soul\Documents\Jasmin Webbi:

Any ideas ?

That looks like a webdav incompatibility

What provider is the webdav?


Can do your test with -vv --dump bodies --retries 1 --low-level-retries 1 --log-file rclone.log and post the log generated?

I'll be able to see exactly what is failing then.

I am not allowed to upload attachments :slight_smile: And posting links is also forbidden. But there is a workaround :slight_smile: So here is what you asked for :slight_smile:

Not working

Working(with mount)


In the first log this happens

2021/05/17 15:01:36 DEBUG : PROPFIND /test HTTP/1.1


2021/05/17 15:01:36 DEBUG : HTTP/1.1 404 Not Found

so rclone tries again with a / on the end

2021/05/17 15:01:36 DEBUG : PROPFIND /test/ HTTP/1.1


2021/05/17 15:01:36 DEBUG : HTTP/1.1 404 Not Found

So then rclone tries to create the directory

2021/05/17 15:01:36 DEBUG : MKCOL /test/ HTTP/1.1

and we get

2021/05/17 15:01:36 DEBUG : HTTP/1.1 403 Forbidden

  <h3>You do not have permission to view this directory or page using the credentials that you supplied.</h3>

So it really looks like that user doesn't have permission to make directories on the server.

The difference with the mount trace is this

2021/05/17 15:06:41 DEBUG : PROPFIND /dompie/testdir/ HTTP/1.1


2021/05/17 15:06:41 DEBUG : HTTP/1.1 207 Multi Status


So that directory does exist.

I repeated the process without using any directories for the remote target. See video :slight_smile: I do not even know why I've included them. :slight_smile:


Can you look in the IIS logs to see what caused the 403 error when you tried it with rclone copy?

Probably the thing to do next would be to the same operations with mount and with copy with -vv --dump bodies and try to compare the HTTP transactions to see what the difference is.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.