Connecting drive failed (53 error) in 1.3.4 version

Hello!

I have Connecting drive failed (53 error) in 1.3.4 version

Windows 7 x64 with last updates, Eset internet security with disabled firewall, Cryptomator on 80 port, Windows Registry checked.


This topic do not help me. Do not know how to find what is wrong to use Troubleshooting the WebDAV Redirector.

log

15:59:38.116 [main] INFO org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.3.4 on Windows 7 6.1 (amd64)
15:59:38.703 [JavaFX Application Thread] INFO o.c.launcher.MainApplication - JavaFX application started.
15:59:38.808 [JavaFX Application Thread] INFO o.c.common.settings.SettingsProvider - Settings loaded from C:\Users\Александр\AppData\Roaming\Cryptomator\settings.json
15:59:39.320 [JavaFX Application Thread] INFO org.cryptomator.jni.JniModule - loaded WinFunctions.dll
15:59:39.414 [JavaFX Application Thread] INFO org.eclipse.jetty.util.log - Logging initialized @-1ms to org.eclipse.jetty.util.log.Slf4jLog
15:59:39.458 [JavaFX Application Thread] INFO o.c.frontend.webdav.WebDavServer - Binding server socket to 127.0.0.1:80
15:59:39.478 [JavaFX Application Thread] INFO o.e.jetty.server.AbstractConnector - Started ServerConnector@1a974d3{HTTP/1.1,[http/1.1]}{127.0.0.1:80}
15:59:40.357 [pool-4-thread-1] INFO org.eclipse.jetty.server.Server - jetty-9.4.8.v20171121, build timestamp: 2017-11-22T01:27:37+04:00, git hash: 82b8fb23f757335bb3329d540ce37a2a2615f0a8
15:59:40.401 [pool-4-thread-1] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@562b65d7{/,null,AVAILABLE}
15:59:40.401 [pool-4-thread-1] INFO org.eclipse.jetty.server.Server - Started @-1ms
15:59:40.401 [pool-4-thread-1] INFO o.c.frontend.webdav.WebDavServer - WebDavServer started.
15:59:40.468 [pool-4-thread-1] INFO org.eclipse.jetty.server.session - DefaultSessionIdManager workerName=node0
15:59:40.468 [pool-4-thread-1] INFO org.eclipse.jetty.server.session - No SessionScavenger set, using defaults
15:59:40.469 [pool-4-thread-1] INFO org.eclipse.jetty.server.session - Scavenging every 600000ms
15:59:40.478 [pool-4-thread-1] INFO o.a.j.w.server.AbstractWebdavServlet - authenticate-header = Basic realm="Jackrabbit Webdav Server"
15:59:40.479 [pool-4-thread-1] INFO o.a.j.w.server.AbstractWebdavServlet - csrf-protection = null
15:59:40.479 [pool-4-thread-1] INFO o.a.j.w.server.AbstractWebdavServlet - createAbsoluteURI = true
15:59:40.480 [pool-4-thread-1] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@2837b817{/PZJWBX9GSKXF/backup,null,AVAILABLE}
15:59:40.480 [pool-4-thread-1] INFO o.c.f.w.s.WebDavServletController - WebDavServlet started: /PZJWBX9GSKXF/backup
15:59:40.483 [pool-4-thread-1] INFO o.c.f.w.s.WebDavServletController - Mounting http://cryptomator-vault:80/PZJWBX9GSKXF/backup using org.cryptomator.frontend.webdav.mount.WindowsMounter
15:59:41.005 [pool-4-thread-2] INFO o.c.ui.controllers.WelcomeController - Current version: 1.3.4, lastest version: 1.3.4
15:59:55.770 [pool-4-thread-1] ERROR o.cryptomator.ui.model.AutoUnlocker - Auto unlock succeded, but mounting the drive failed.
org.cryptomator.frontend.webdav.mount.Mounter$CommandFailedException: Command failed with exit code 2. Expected 0. Stderr: ??? ??? 53.

?? ??? ??? ???.

at org.cryptomator.frontend.webdav.mount.ProcessUtil.assertExitValue(ProcessUtil.java:28)
at org.cryptomator.frontend.webdav.mount.WindowsMounter.mount(WindowsMounter.java:43)
at org.cryptomator.frontend.webdav.servlet.WebDavServletController.mount(WebDavServletController.java:102)
at org.cryptomator.ui.model.Vault.mount(Vault.java:140)
at org.cryptomator.ui.model.AutoUnlocker.mountSilently(AutoUnlocker.java:90)
at org.cryptomator.ui.model.AutoUnlocker.unlockSilently(AutoUnlocker.java:77)
at org.cryptomator.ui.model.AutoUnlocker.unlockAll(AutoUnlocker.java:58)
at org.cryptomator.ui.model.AutoUnlocker.lambda$unlockAllSilently$0(AutoUnlocker.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

16:10:03.445 [pool-4-thread-4] INFO o.c.ui.controllers.WelcomeController - Current version: 1.3.4, lastest version: 1.3.4
16:10:03.809 [pool-4-thread-5] INFO o.c.ui.controllers.WelcomeController - Current version: 1.3.4, lastest version: 1.3.4
16:10:05.018 [pool-4-thread-5] INFO o.c.ui.controllers.WelcomeController - Current version: 1.3.4, lastest version: 1.3.4

Have you checked the registry entry that is also mentioned in the topic you’ve linked? Have you tried a different port than 80? Well, even though it works (at least in my quick test), we recommend setting a port between 1024 and 65535.