Skip to content

Failure uploading nested folders to vault #15489

Description

Describe the bug
I Created an ARCHIVE bucket in Google Cloud, enabled Cryptomator inside It with a password. When I upload a folder with nested folders, during the creation of the nested folders I receive an arror saying "File not found", but If I see the encrypyted folders on the bucket using the browser I understand that the folder with the first sub-folder is created. From this moment, I cannot access anymore with Cyberduck and I have to delete these folders manually on the bucket using the browser

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
I expect that If I upload folders with sub-folders they are correctly created and populated

Screenshots
Screenshot attached
1
2

Desktop (please complete the following information):

  • OS: Windows 11
  • Version 23H2

Log Files
Log file attached
cyberduck.zip

Additional context
It seems a problem about Cryptomator, infact the same operation without It works fine

Metadata

Metadata

Labels

azureAzure Protocol Implementationb2Backblaze B2 Protocol ImplementationcryptomatorCryptomator VaultgooglestorageGoogle Cloud Storage Protocol ImplementationopenstackOpenStack Swift Protocol Implementation

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions