Skip to content
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

Vaults are not detected #10566

Closed
cyberduck opened this issue Jan 4, 2019 · 14 comments
Closed

Vaults are not detected #10566

cyberduck opened this issue Jan 4, 2019 · 14 comments
Assignees
Labels
Milestone

Comments

@cyberduck
Copy link
Collaborator

3c57a9b created the issue

Steps to reproduce:

  1. Create a new Cryptomator vault
  2. Open the newly created vault.
  3. Vault folder opens and displays encrypted files. No password prompt, even when refreshing.

Similar to #10422, but the “Auto detect and open vault in browser” preference is checked.
Similar to #10352, but on the GUI, not the CLI, and the vault is never detected, not randomly.


I already had this issue in October and waited for a couple releases before trying again.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I cannot reproduce with version 6.9.0 testing using OpenStack OVH Storage.

@cyberduck
Copy link
Collaborator Author

3c57a9b commented

I just updated to 6.9.0 (29768) and I get the exact same behaviour with an OVH-provided storage (set up to “Swift (OpenStack Object Storage)”).
I can give access to the faulty server if that can help.

-(I'm not sure of the expected process here so I reopened, sorry if that's not how you prefer to work, please let me know how you expect to deal with such unresolved issues :) )*

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 MattiSG]:

I just updated to 6.9.0 (29768) and I get the exact same behaviour with an OVH-provided storage (set up to “Swift (OpenStack Object Storage)”).
I can give access to the faulty server if that can help.

(I'm not sure of the expected process here so I reopened, sorry if that's not how you prefer to work, please let me know how you expect to deal with such unresolved issues :) )
Thanks for letting us know – we will continue to look into this and trying to reproduce.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Ticket retargeted after milestone closed

1 similar comment
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#10352 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#10723 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

3c57a9b commented

Tested with version 7.1.0 (31365), still the same :(

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I cannot reproduce with version 7.3.1 testing using OpenStack OVH Storage.

@cyberduck
Copy link
Collaborator Author

3c57a9b commented

Tested with version 7.4.0 (32960), still the same :(

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Try the new manual unlock feature.

@cyberduck
Copy link
Collaborator Author

3c57a9b commented

I unfortunately cannot test because of #11088.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants