You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cyberduck prompts an error "File not found, /bucket/sourcefolder. Please contact your web hosting service provider for assistance." when moving a "folder" from within the bucket in-to an encrypted vault within the same bucket.
The object appears to be copied (visible on refresh) but the original is not removed from it's original location.
Moving a folder containing a file (for example a movie) from outside the vault (in the bucket), to inside a vault appears to behave as expected.
Moving a empty folder from within a vault, into the bucket containing the vault produces the same error, but without copying the folder.
Moving a folder containing a file (like a movie) from within a vault, into the bucket containing the vault also produces the same error without copying the requested folder or file.
I have only tested this against actions within the same bucket so far.
The text was updated successfully, but these errors were encountered:
Cyberduck prompts an error "File not found, /bucket/sourcefolder. Please contact your web hosting service provider for assistance." when moving a "folder" from within the bucket in-to an encrypted vault within the same bucket.
The object appears to be copied (visible on refresh) but the original is not removed from it's original location.
Moving a folder containing a file (for example a movie) from outside the vault (in the bucket), to inside a vault appears to behave as expected.
Moving a empty folder from within a vault, into the bucket containing the vault produces the same error, but without copying the folder.
Moving a folder containing a file (like a movie) from within a vault, into the bucket containing the vault also produces the same error without copying the requested folder or file.
I have only tested this against actions within the same bucket so far.
The text was updated successfully, but these errors were encountered: