Closed ghost closed 4 years ago
This may be realted to the outdated web-dav version. The dependencies recieved an update now, so this needs to be retested.
Thank you for responding.
If your retest comment is not directed to me please just ignore the following.
Before I entertain retesting...
By retest do you mean build a new cli jar from branch develop and try again with that or something else? Will it matter if the vault in question is format 6 or 7?
Just released 0.4.0 which is compatible with vaultf format 7 (;
But if this issue is obsolete anyway, you don't have to.
Thank you for this. In certain circumstances I prefer the cli tool over the UI version.
I did have a backup of the vault that showed this issue and it was converted to version 7.
I was able to open and use this vault with cryptomator-cli-0.4.0.jar.
I'll close this. A new issue can be opened if it later turns out the casual test I did is insufficient to show that this issue is fixed.
After:
java -jar ~/utils/cryptomator-cli-0.3.1.jar --vault ~/Documents/media --passwordfile /tmp/pwd.yivJH4 --bind 127.0.0.1 --port 8080 &
I see
When I try:
sudo mount -t davfs http://localhost:8080/media ~/media
I get
and there is nothing in ~/media.
Note that using the AppImage version 1.4.15, I can mount and see files in this directory.
Also, I have two other vaults both of which I can mount and see files via the cli and appimage variants...
This seems to be related to just the "media" vault.
Any hints about how to fix this?
I've also tried
gio mount dav://127.0.0.1:8080/media
but this also fails with:(gio mount works well for the other two vaults)