New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not unlock vault #238

Closed
konus1 opened this Issue Apr 19, 2016 · 10 comments

Comments

Projects
None yet
3 participants
@konus1
Copy link

konus1 commented Apr 19, 2016

Basic Info

  • I'm running Cryptomator on: Windows 8.1 64bit
  • I'm using Cryptomator in version: 1.0.3

Description

I created a vault with windows 7-64bit pro using Cryptomator version 1.0.3
On a different client, I then tried to open the vault. After entering the password, the red colored button turns green and Windows opens a new window. After a short waiting period I get the (german) error message
netzwerkfehler
However I can access the linked webdav site directly and see the encrypted files.

Additionally, the virtual vault-drives are still visible after closing cryptomator and they still have drive letters in the system
connection

Log File

2016-04-19 11:11:19,711 INFO  [SingleInstanceManager:299] no running instance found
2016-04-19 11:11:20,891 DEBUG [SingleInstanceManager:325] InstanceManager bound to port 54596
2016-04-19 11:11:21,231 DEBUG [WelcomeController:151] Current version: 1.0.3, lastest version: 1.0.3
2016-04-19 11:11:45,300 INFO  [WebDavMounterProvider:39] Using WindowsWebDavMounter
2016-04-19 11:11:45,308 INFO  [log:186] Logging initialized @26026ms
2016-04-19 11:11:45,373 INFO  [Server:345] jetty-9.3.3.v20150827
2016-04-19 11:11:45,398 INFO  [ContextHandler:775] Started o.e.j.s.ServletContextHandler@37dc8f42{/,null,AVAILABLE}
2016-04-19 11:11:45,409 INFO  [ServerConnector:270] Started ServerConnector@4186b18{HTTP/1.1,[http/1.1]}{0.0.0.0:54623}
2016-04-19 11:11:45,409 INFO  [Server:397] Started @26129ms
2016-04-19 11:11:45,410 INFO  [WebDavServer:79] Cryptomator is running on port 54623
2016-04-19 11:11:46,448 INFO  [WebDavServer:117] Servlet available under http://localhost:54623/scan
2016-04-19 11:11:46,452 INFO  [AbstractWebdavServlet:169] authenticate-header = Basic realm="Jackrabbit Webdav Server"
2016-04-19 11:11:46,453 INFO  [AbstractWebdavServlet:174] csrf-protection = null
2016-04-19 11:11:46,453 INFO  [AbstractWebdavServlet:181] createAbsoluteURI = true
2016-04-19 11:11:46,453 INFO  [ContextHandler:775] Started o.e.j.s.ServletContextHandler@97938cf{/scan,null,AVAILABLE}
2016-04-19 11:11:46,481 DEBUG [CommandResult:85] Command execution finished. Exit code: 0
Output: Der Vorgang wurde erfolgreich beendet.
...

2016-04-19 11:12:01,047 DEBUG [CommandResult:85] Command execution finished. Exit code: 0
Output: Laufwerk X: ist jetzt mit \\localhost@54623\DavWWWRoot\scan verbunden.
...

2016-04-19 11:19:26,099 DEBUG [CommandResult:85] Command execution finished. Exit code: 0
Output: X: wurde erfolgreich gel”scht.


2016-04-19 11:19:26,101 INFO  [ContextHandler:885] Stopped o.e.j.s.ServletContextHandler@97938cf{/scan,null,UNAVAILABLE}
2016-04-19 11:19:29,857 DEBUG [Server:416] doStop org.eclipse.jetty.server.Server@2bf76575
2016-04-19 11:19:29,858 DEBUG [Server:438] Graceful shutdown org.eclipse.jetty.server.Server@2bf76575 by 
2016-04-19 11:19:29,860 INFO  [ServerConnector:310] Stopped ServerConnector@4186b18{HTTP/1.1,[http/1.1]}{0.0.0.0:0}
2016-04-19 11:19:29,861 INFO  [ContextHandler:885] Stopped o.e.j.s.ServletContextHandler@37dc8f42{/,null,UNAVAILABLE}
@markuskreusch

This comment has been minimized.

Copy link
Contributor

markuskreusch commented Apr 19, 2016

According to the log output the location has been successfully mounted (we did not get an error code from the mount command). The error message is displayed by Windows Explorer which sometimes has problems accessing webdav or other network shares.

You may try to:

  • temporarily disable your antivirus / firewall solution to check if it interferes with Cryptomator, if so you may reconfigure it to allow all connections from/to the virtual drives
  • go to the Cryptomator settings and check the IPv6 checkbox. This will use IPv6 for mounting which works better on some systems

Because the connection to the drives does not work well Windows may leave them connected when closing Cryptomator eventhough we try to remove them. You will have to manually remove them. You can do this by right-clicking "Computer" in Windows Explorer and selecting "Netzlaufwerk trennen...".

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Apr 19, 2016

If you google "0x80070035", there are various forum posts suggesting firewall software is blocking the connection. In our case we make loopback connections from localhost to localhost, which can safely be whitelisted. Please contact your AV/firewall supplier if you need help with managing firewall rules.

@konus1

This comment has been minimized.

Copy link

konus1 commented Apr 19, 2016

Temporarily disable my antivirus / firewall solution did not help. IPv6 is not possible here since my gateway does not forward it. (tested it anyway)
I created a new vault on the same webdav-drive and was able to access it. The problems with the existing vault still persists.

Removing network shares seems to be a windows problem. I can not disconnect them on gui or on console. They disaperar only after a new boot.

@konus1

This comment has been minimized.

Copy link

konus1 commented Apr 20, 2016

Tonight I tested again on my first computer and found out, that I am not even able to access the vault on the computer I created it with.
So it seems like it is not a configuration/ firewall / virusscanner -problem, but a problem with the vault itself. It is possible that a vault could get corrupted? Maybe by an unreliable network connection?
Is there any way to recover a broken vault or a way I can check integrity?
I can not find any error information on the log, but attached it anyway.

BTW: no Problems with disconnecting drives again.

2016-04-20 11:53:58,959 INFO  [SingleInstanceManager:299] no running instance found
2016-04-20 11:54:00,141 DEBUG [SingleInstanceManager:325] InstanceManager bound to port 59871
2016-04-20 11:54:00,540 DEBUG [WelcomeController:151] Current version: 1.0.3, lastest version: 1.0.3
2016-04-20 11:54:21,753 INFO  [WebDavMounterProvider:39] Using WindowsWebDavMounter
2016-04-20 11:54:21,763 INFO  [log:186] Logging initialized @23216ms
2016-04-20 11:54:21,812 INFO  [Server:345] jetty-9.3.3.v20150827
2016-04-20 11:54:21,833 INFO  [ContextHandler:775] Started o.e.j.s.ServletContextHandler@6ae27d2a{/,null,AVAILABLE}
2016-04-20 11:54:21,840 INFO  [ServerConnector:270] Started ServerConnector@2e5ba42b{HTTP/1.1,[http/1.1]}{0.0.0.0:59876}
2016-04-20 11:54:21,841 INFO  [Server:397] Started @23295ms
2016-04-20 11:54:21,841 INFO  [WebDavServer:79] Cryptomator is running on port 59876
2016-04-20 11:54:30,976 INFO  [WebDavServer:117] Servlet available under http://localhost:59876/scan
2016-04-20 11:54:30,980 INFO  [AbstractWebdavServlet:169] authenticate-header = Basic realm="Jackrabbit Webdav Server"
2016-04-20 11:54:30,981 INFO  [AbstractWebdavServlet:174] csrf-protection = null
2016-04-20 11:54:30,981 INFO  [AbstractWebdavServlet:181] createAbsoluteURI = true
2016-04-20 11:54:30,982 INFO  [ContextHandler:775] Started o.e.j.s.ServletContextHandler@7f31406e{/scan,null,AVAILABLE}
2016-04-20 11:54:31,008 DEBUG [CommandResult:85] Command execution finished. Exit code: 0
Output: Der Vorgang wurde erfolgreich beendet.


2016-04-20 11:54:31,134 DEBUG [Server:506] REQUEST on HttpChannelOverHttp@3bc7bb2f{r=1,c=false,a=DISPATCHED,uri=/scan}
OPTIONS //localhost:59876/scan
Connection: keep-alive
User-Agent: Microsoft-WebDAV-MiniRedir/6.3.9600
translate: f
Host: localhost:59876


2016-04-20 11:54:31,138 DEBUG [Server:520] RESPONSE for /scan h=true
302 null
Date: Wed, 20 Apr 2016 09:54:31 GMT
Location: http://localhost:59876/scan/


2016-04-20 11:54:31,140 DEBUG [Server:506] REQUEST on HttpChannelOverHttp@3bc7bb2f{r=2,c=false,a=DISPATCHED,uri=/scan/}
OPTIONS //localhost:59876/scan/
Connection: keep-alive
User-Agent: Microsoft-WebDAV-MiniRedir/6.3.9600
translate: f
Host: localhost:59876


2016-04-20 11:54:31,166 DEBUG [Server:520] RESPONSE for /scan/ h=true
200 null
Date: Wed, 20 Apr 2016 09:54:31 GMT
DAV: 1, 2
Allow: OPTIONS, GET, HEAD, POST, TRACE, PROPFIND, PROPPATCH, MKCOL, COPY, PUT, DELETE, MOVE, LOCK, UNLOCK
MS-Author-Via: DAV


2016-04-20 11:54:31,194 DEBUG [Server:506] REQUEST on HttpChannelOverHttp@5f5e83f5{r=1,c=false,a=DISPATCHED,uri=/scan}
PROPFIND //localhost:59876/scan
Connection: keep-alive
User-Agent: Microsoft-WebDAV-MiniRedir/6.3.9600
Depth: 0
translate: f
Content-Length: 0
Host: localhost:59876


2016-04-20 11:54:31,195 DEBUG [Server:520] RESPONSE for /scan h=true
302 null
Date: Wed, 20 Apr 2016 09:54:31 GMT
Location: http://localhost:59876/scan/


2016-04-20 11:54:31,196 DEBUG [Server:506] REQUEST on HttpChannelOverHttp@5f5e83f5{r=2,c=false,a=DISPATCHED,uri=/scan/}
PROPFIND //localhost:59876/scan/
Connection: keep-alive
User-Agent: Microsoft-WebDAV-MiniRedir/6.3.9600
Depth: 0
translate: f
Content-Length: 0
Host: localhost:59876
@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Apr 20, 2016

File integrity is checked using HMAC-SHA256 and damages will be reported to you. This is a just a connection problem. To make sure: Use any alternate WebDAV client of your choice, such at Cyberduck and connect anonymously to localhost:59876/scan (or whatever port is used in your next launch)

@konus1

This comment has been minimized.

Copy link

konus1 commented Apr 20, 2016

I copied the vault directory to my local drive and was able to open it flawlessly within seconds. So you are right, it is not a corruption but probably a connection problem.

How can I open a remote webdav-Server within Cryptomator? Do I need the commercial sibling MountainDuck or is there a way to use CyberDuck?
With MountainDuck, connection problems ar still existent.

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Apr 22, 2016

As long as the remote drive is made available to the system as a "normal" (network mapped) drive, Cryptomator should be able to interact with it. It gets the file path from the operating system and can't distinguish local from network drives. If you use MountainDuck oder just Windows Explorer shouldn't make a difference (except for performance maybe).

@markuskreusch markuskreusch modified the milestone: 1.1 Apr 28, 2016

@overheadhunter overheadhunter modified the milestones: 1.1, 1.x May 10, 2016

@overheadhunter overheadhunter modified the milestones: 1.x, 1.4.0 Jun 20, 2018

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Jun 20, 2018

WebDAV related problems might be solved after implementing #207.

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Jul 12, 2018

Good news, everyone! We've released version 1.4.0-beta2, which introduces Dokany support. You now have the choice between Dokany and WebDAV based virtual hard drives.

Please retest this issue with Dokany enabled.

@no-response

This comment has been minimized.

Copy link

no-response bot commented Jul 26, 2018

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment