Cannot sync using hashes when using rcloud webdav as backend

What is the problem you are having with rclone?

I try to sync between 2 different rclones (got webdav to be working on both machines) - I want to upload a static website and sync source and destination easily.

Run the command 'rclone version' and share the full output of the command.

Client:
rclone v1.70.1

  • os/version: Microsoft Windows 11 Pro 24H2 24H2 (64 bit)
  • os/kernel: 10.0.26100.4351 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.24.4
  • go/linking: static
  • go/tags: cmount

Which cloud storage system are you using? (eg Google Drive)

Webdav using rclone

rclone v1.70.1

  • os/version: ubuntu 24.04 (64 bit)
  • os/kernel: 6.8.0-62-generic (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.24.4
  • go/linking: static
  • go/tags: none

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone sync E:\folder\dist remote:httpdocs --transfers=64 --track-renames

Server command to start

rclone serve webdav PATH --addr XXX --etag-hash=md5 --user XXX --pass  XXX

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

[pcloud]
type = pcloud
hostname = eapi.pcloud.com
token = XXX

[remote]
type = webdav
url = XXX
vendor = rclone
user = XXX
pass = XXX

A log from the command that you were trying to run with the -vv flag

2025/06/23 21:30:24 ERROR : webdav root 'httpdocs': Ignoring --track-renames as the source and destination do not have a common hash

NOTE: Really only output, using --progress I see 166 of 5292 files are being uploaded every time i executed the command.

welcome to the forum,

need to choose correct value for --track-renames-strategy or remove --etag-hash=md5

or maybe run rclone serve webdav on the source and dest, then rclone sync src: dst: --track-renames
in that case, md5 could work.