Rclone doesn't read from unencrypted Cryptomator vault (WebDAV)

Help and Support
1

What is the problem you are having with rclone?

rclone is not reading unencrypted Cryptomator webdav container

"V:" is an unencrypted Cryptomator vault, mounted with "WebDAV (Windows Explorer)"

Cryptomator at v1.8.0 (latest)

dir V: => shows everything unencrypted

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

rclone v1.62.2

  • os/version: Microsoft Windows 11 Home 22H2 (64 bit)
  • os/kernel: 10.0.22621.1555 Build 22621.1555.1555 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.20.2
  • go/linking: static
  • go/tags: cmount

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

none, only local sync

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

rclone.exe -vv sync V:\ZEUS D:\Temp\test

The rclone config contents with secrets removed.

no rclone.conf is used

A log from the command with the -vv flag

2023/05/01 16:24:07 DEBUG : Creating backend with remote "V:\\ZEUS"
2023/05/01 16:24:07 DEBUG : Using config file from "D:\\autostart\\tools\\rclone\\rclone.conf"
2023/05/01 16:24:07 DEBUG : fs cache: renaming cache item "V:\\ZEUS" to be canonical "//?/V:/ZEUS"
2023/05/01 16:24:07 DEBUG : Creating backend with remote "D:\\Temp\\test"
2023/05/01 16:24:07 DEBUG : fs cache: renaming cache item "D:\\Temp\\test" to be canonical "//?/D:/Temp/test"
2023/05/01 16:25:07 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       1m0.0s

2023/05/01 16:26:07 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       2m0.0s

2023/05/01 16:27:07 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       3m0.0s

2023/05/01 16:28:07 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       4m0.0s

2023/05/01 16:29:07 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       5m0.0s

2023/05/01 16:30:07 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       6m0.0s

and so on ...

2

tho you are not using a mount, some of these caveats might still apply.
https://rclone.org/commands/rclone_mount/#windows-caveats

as a test, i would open two command prompts.
onc prompt with admin privileges, one prompt without admin privileges.
and run rclone ls v:\ -vv

might create a webdav remote and have rclone use that?

3

as "normal user": same behaviour as above
as "admin": drive "V:" not found
(as expected, Cryptomator runs under "normal user")

My goal is a little bit more complex than described.
I broke it down to a simple example to show the problem.
So i can't/won't create a remote webdav.

Thanks

4

might post full output of rclone lsd v:\ -vv

5 
D:\autostart\tools\rclone>rclone lsd v:\ -vv
2023/05/01 20:54:55 DEBUG : rclone: Version "v1.62.2" starting with parameters ["rclone" "lsd" "v:\\" "-vv"]
2023/05/01 20:54:55 DEBUG : Creating backend with remote "v:\\"
2023/05/01 20:54:55 DEBUG : Using config file from "D:\\autostart\\tools\\rclone\\rclone.conf"
2023/05/01 20:54:55 DEBUG : fs cache: renaming cache item "v:\\" to be canonical "//?/v:/"

Nothing more.
There is no destination named "v" or "V" in my rclone.conf.

6

worked for me, tho without webdav

rclone cat d:\files\cryptomator\WELCOME.rtf -vv
2023/05/01 15:29:50 DEBUG : rclone: Version "v1.62.2" starting with parameters ["rclone" "cat" "d:\\files\\cryptomator\\WELCOME.rtf" "-vv"]
2023/05/01 15:29:50 DEBUG : Creating backend with remote "d:\\files\\cryptomator\\WELCOME.rtf"
2023/05/01 15:29:50 DEBUG : Using config file from "c:\\data\\rclone\\rclone.conf"
2023/05/01 15:29:50 DEBUG : fs cache: adding new entry for parent of "d:\\files\\cryptomator\\WELCOME.rtf", "//?/d:/files/cryptomator"
{\rtf1\fbidis\ansi\uc0\fs32
{\sa80 \fs40\qc \u55357\u56592\u65039  ENCRYPTED VOLUME  \u55357\u56592\u65039}\par
{\sa80 This is your vault's access location.}\par
{\sa80 }\par
{\sa80 Any files added to this volume will be encrypted by Cryptomator. You can work on it like on any other drive/folder. This is only a decrypted view of its content, your files stay encrypted on your hard drive all the time.}\par
{\sa80 }\par
{\sa80 Feel free to remove this file.}\par
7

My "V:" ist the unencrypted drive, not the vault himself. (see my first post)
You looked at the cryptomator vault.
No problem with that,

8

if you create a new vault, it auto-creates WELCOME.rtf
and that is the file i used with rclone cat

and here is ms-word:

image
image1036×578 33.4 KB

i always try to avoid drive letters but if that is required.

rclone cat v:\WELCOME.rtf -vv
2023/05/01 15:44:08 DEBUG : rclone: Version "v1.62.2" starting with parameters ["rclone" "cat" "v:\\WELCOME.rtf" "-vv"]
2023/05/01 15:44:08 DEBUG : Creating backend with remote "v:\\WELCOME.rtf"
2023/05/01 15:44:08 DEBUG : Using config file from "C:\\data\\rclone\\rclone.conf"
2023/05/01 15:44:08 DEBUG : fs cache: adding new entry for parent of "v:\\WELCOME.rtf", "//?/v:/"
{\rtf1\fbidis\ansi\uc0\fs32
{\sa80 \fs40\qc \u55357\u56592\u65039  ENCRYPTED VOLUME  \u55357\u56592\u65039}\par
{\sa80 This is your vault's access location.}\par
{\sa80 }\par
{\sa80 Any files added to this volume will be encrypted by Cryptomator. You can work on it like on any other drive/folder. This is only a decrypted view of its content, your files stay encrypted on your hard drive all the time.}\par
{\sa80 }\par
{\sa80 Feel free to remove this file.}\par

image
image881×257 12.6 KB

9

Sorry, you're right.

Which Cryptomator version?

Btw.: with fuse everything's fine.
I can't use fuse. (Reason: under WSL all directories have the same inode => file system loop)

What's with WebDAV?

10

just curious, as i am working in my wsl skills, why is that a problem?

rclone works fine with webdav, on windows and on wsl.
is that not an option?

11 
just curious, as i am working in my wsl skills, why is that a problem?

look here: WSL - WinFsp (Local Drive) -> possible filesystem loop · Issue #2872 · cryptomator/cryptomator · GitHub

12

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