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

Using Cyberduck with an encrypted vault on Google Drive (university account) I get "File Not Found" errors and greyed out files. #11099

Closed
cyberduck opened this issue Jul 6, 2020 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jul 6, 2020

aa241fb created the issue

While navigating the encrypted vault in Cyberduck I receive many "retrying" messages for opening folders and random errors while transferring files. When something goes wrong, the files get greyed out and trying to do anything with them (such as deleting them) results in an error such as:

File not found  /My Drive/Cryptomator_Cyberduck/privateStorage/d/ZK/N5PFJSUNKHQ5W3LANKTQFCNSVMQFUH. Please contact your web hosting service provider for assistance.

I checked and the corresponding file does not indeed exist on google drive, but it shows in cyberduck regardless of the number of times I refresh.

The issue persists both on the latest version of cyberduck for Mac and windows 10.

Can you please help me out? This makes cyberduck completely useless for my use case. I've been successfully using boxcryptor but I really want to migrate to cyberduck, and I most certainly will if we can work out the cause and the solution for this.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 26, 2021

@dkocher commented

Duplicate for #10654.

Loading

@cyberduck cyberduck closed this Jan 26, 2021
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants