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

Upgraded to build 4166, now can not use Cyberduck! #2484

Closed
cyberduck opened this issue Aug 21, 2008 · 2 comments
Closed

Upgraded to build 4166, now can not use Cyberduck! #2484

cyberduck opened this issue Aug 21, 2008 · 2 comments
Assignees
Labels
bug fixed ftp FTP Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

6d4fd52 created the issue

I upgraded to the 4166 build and immediately had problems connected to FTP sites. Our corporate site contains the directory structure '/files/Tools' but after connecting to the site using the new build I can navigate into '/files' but when I try to navigate into the tools subfolder it fails telling me the directory does not exist. Log snip below. Looks like it is putting the "files" name in the string twice - is it using it instead of the server name? Very strange.

Note I tried same transfer using a different tool (net2ftp) and it works file. Also, the build previous to 4166 I was using worked fine.

Any help appreciated.

200 NOOP command successful.
STAT //files/files/Tools
211-status of //files/files/Tools:
550 //files/files/Tools: No such file or directory.
211 End of Status
CWD //files/files/Tools
550 //files/files/Tools: No such file or directory.


@cyberduck
Copy link
Collaborator Author

anonymous commented

Further info - I can connect to any directory (in my example, /files/Tools) if I set it as the "initial directory" during the connection. But once in a directory I can not use Cyberduck to navigate / drill-down into sub folders.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Fixed in 5e2fefc. Please try the latest nightly build from (http://update.cyberduck.ch/nightly).

@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
bug fixed ftp FTP Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants