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
Problem creating directory in encrypted vault over FTP #9950
Comments
I cannot reproduce the error here neither manually nor is our integration test failing for creating directories in a vault. Can you attach the full transcript from the log drawer? |
I can post a screenshot when I get home (~8 hours). In the meantime, may I guess that your test FTP server can create nested directories with one single command (MKDIR /x/y/z) whereas mine can only create one level at a time? |
Hmm... I am unable to immediately reproduce the bug. In my simple tests Cyberduck is correctly issuing separate MKDIR commands. I will try to recall what activities I was doing before I hit the problem yesterday and see if I can recreate the problem. If not, I'll post back here in 24 hours and resolve as invalid or wfm. |
While trying to reproduce the original directory creation failure, I kept running into some upload failure problem. Maybe they are related? I think maybe there is some kind of caching problem or something. Here is what I did:
|
Forgot to add at the end: no errors seen in cyberduck.log and none seen in the log drawer. Last log drawer entries are listing the directory contents and then nothing related to the upload attempts. Also, closing and reopening Cyberduck does not clear out the inability to upload problem. |
I am connecting to an encrypted vault over FTP. I try to create a directory and the operation fails with:
I see at the bottom of the error popup:
In the preceding directory listing, I see there is no "W7" directory. I think Cyberduck is trying to create a nested directory "W7/[UID]" in one command which returns a 550 error. I think Cyberduck needs to issue two separate commands:
Attachments
uploadbug.jpg
(174.2 KiB)The text was updated successfully, but these errors were encountered: