Hello, First for the sake of clarity, let me detail the setup: I have a Windows 10 machine where Cryptomator is installed, using Dokany. On this Windows machine, a network share called “Vault” is mounted as “P:” The share is setup on a Debian server, and accessible from 10.10.20.11. Only a spec…

Welcome to the Cryptomator Community :slightly_smiling_face: , Cryptomator relies for filesystem permissions on the JDK, the standard toolkit of Java. It checks if the parent directory of the vault is writable, because in there it needs to create a directory. You can test the reported filesystem a…

Hello, Thanks for checking. What I realized is that even if I don’t mount the directory as a “network drive” and just map the directory as “network location” (which basically the same, but does not assign a letter and does not retrieve storage info), it does not work either. Note that the user in…

You tested it with the wrong path :wink: When you are using jshell, you are actually writing Java code. To use the backslash in a string, it must be escaped with another backslash. Hence, to use two backslashes you must write four: var p = Path.of("\\\\10.10.20.11\\Vault");

Hi, Thanks for the tip, my bad. I understood that a single backslash was to escape, but for some reason my brain skipped that there were two actual backslashes for a network path :sweat_smile: jshell> var p = Path.of("\\\\10.10.20.11\\Vault"); Files.isWritable(p); p ==> \\10.10.20.11\Vault\ $3 ==> …

I’m experiencing a very similar problem but with a Synology NAS drive. I have a vault there already which I can unlock and re-lock fine. But when I try to create a new vault on the NAS I get that same ‘no write permission’ message. I haven’t tried creating it on my hard drive and then moving it to t…

[image] Fitfit: Only a specific user can access the share/directory It sounds like that the local login user differs from “access allowed” user. Is this the case? If yes, if you run the the terminal with jshell/Cryptomator as this specific user, does it then work? On my setup, where I only …

In the middle of the night it came to me: I’d recently updated from 1.5.14 to 1.5.16. So I’ve rolled back to 1.5.14 and it is working again now. I hope a member of the Cryptomator team picks this up. Now: back to trying to work out why I can no longer access my vaults from my Android phone.

I’m not sure of how Windows handles stored credentials and such. The only thing I know is that it does not matter if I map a drive letter, a domain name with host redirection, or a path with the IP. In all cases there is that same “permission” error. As the user in question only exists on the remo…

Same issue here, with Koofr drive. I was able to create Cryptomator vaults through Cyberduck. Now I was not able to delete or write files there (me too, after updating to 1.5.16) so… I came here. :smirk: Same false results from JShell. I’ve even tried to delete Windows credentials associated to C…

I can confirm that moving back to 1.5.14 the creation of vault is working.

Cryptomator Community

Unable to create new Cryptomator vault on a network share mounted in Windows

Help Desktop App