Mounted drive is empty (Windows), NoSuchFileException in the log

Help Desktop App
1

Hi all,
I’ve been using Cryptomator for some time now and I really like it. But now I have a big problem (on one device at least): I can, on a Windows 7 PC, unlock the vault and mount the unlocked vault. But the mounted drive is just empty. I’ve enabled debug mode and it shows me a NoSuchFileException in the debug log. I guess this has to do with my problem:

09:19:36.871 [pool-5-thread-18] DEBUG org.eclipse.jetty.server.HttpChannel - HttpChannelOverHttp@307015cf{r=6,c=false,a=IDLE,uri=//127.0.0.1:42427/3vjR6bQuQ6I-/t/} onContentComplete
09:19:36.871 [pool-5-thread-18] DEBUG org.eclipse.jetty.server.HttpChannel - HttpChannelOverHttp@307015cf{r=6,c=false,a=IDLE,uri=//127.0.0.1:42427/3vjR6bQuQ6I-/t/} onRequestComplete
09:19:36.872 [pool-5-thread-18] DEBUG org.eclipse.jetty.server.HttpChannel - HttpChannelOverHttp@307015cf{r=6,c=false,a=IDLE,uri=//127.0.0.1:42427/3vjR6bQuQ6I-/t/} handle //127.0.0.1:42427/3vjR6bQuQ6I-/t/ 
09:19:36.872 [pool-5-thread-18] DEBUG org.eclipse.jetty.server.HttpChannel - HttpChannelOverHttp@307015cf{r=6,c=false,a=DISPATCHED,uri=//127.0.0.1:42427/3vjR6bQuQ6I-/t/} action DISPATCH
09:19:36.872 [pool-5-thread-18] TRACE o.c.f.webdav.servlet.LoggingFilter - REQUEST 8:
PROPFIND /3vjR6bQuQ6I-/t/ HTTP/1.1
Connection: keep-alive
User-Agent: Microsoft-WebDAV-MiniRedir/6.1.7601
Host: 127.0.0.1:42427
Content-Length: 0
Depth: 1
translate: f

09:19:36.873 [pool-5-thread-18] TRACE o.c.cryptofs.CryptoDirectoryStream - OPEN 
09:19:36.878 [pool-5-thread-18] TRACE o.c.cryptofs.CryptoDirectoryStream - CLOSE 
09:19:36.878 [pool-5-thread-18] WARN  org.eclipse.jetty.server.HttpChannel - /3vjR6bQuQ6I-/t/
java.io.UncheckedIOException: java.nio.file.NoSuchFileException: F:\nextcloud\t\d\2A\6AIUPWUWEGDQTNCRDZHA4UUNUZFQFK\RCXAMUGX2FGFWDU5XVB2TG3IXAP2PUVTH72PJI45NZ3WNEJKXYRBX5RLSJH4FCWLZEWZRPO7XGKMVCXYJAD4FZMMYLX7X6RBONIO32CHAEDTDA4WGMIWG4ZM4KULK23R
	at org.cryptomator.frontend.webdav.servlet.DavFolder.getMembers(DavFolder.java:114)
	at org.apache.jackrabbit.webdav.MultiStatus.addResourceProperties(MultiStatus.java:63)
	at org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.doPropFind(AbstractWebdavServlet.java:561)
...
Caused by: java.nio.file.NoSuchFileException: F:\nextcloud\t\d\2A\6AIUPWUWEGDQTNCRDZHA4UUNUZFQFK\RCXAMUGX2FGFWDU5XVB2TG3IXAP2PUVTH72PJI45NZ3WNEJKXYRBX5RLSJH4FCWLZEWZRPO7XGKMVCXYJAD4FZMMYLX7X6RBONIO32CHAEDTDA4WGMIWG4ZM4KULK23R
	at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)

This error message repeats a few times in the log.

The vault is stored in a folder that is synced with Nextcloud to a server. The Nextcloud client says sync was successful, so I think this is not the problem.
Edit: I’ve started a new sync in a new local folder now, just to be sure it’s not a Nextcloud problem. I will update this thread when the sync run has finished.

On another device luckily things still seem to be working, so I made a local copy of all the decrypted files now (just in case). However, I don’t want to remove all the files and add them again to my vault again. Instead I would like to fix the real issue (or bug) here.

2

So, after the complete resync of the Nextcloud folder the problem still persists. On the other device the file Cryptomator complains about also does not exist. But there I can unlock the vault (without any error in the log), on my PC I can’t.

3

I’ve noticed something strange: I have an application that directly opens a sub folder of the unlocked vault drive (for example when saving a file). And this is working. So what’s not working is opening the top folder (so the mounted network drive) in the Windows Explorer. But some files seem to be missing there. Again, on the other device everything seems to be fine.

4

The problem seems to be resolved now :slight_smile: I upgraded from 1.3.1 to 1.3.3 on my Win 7 box. Then I first had another strange error (it could not mount the network drive). After that I rebooted and suddenly things were working again!