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

Problem with synchronize when using tunneled sftp #2381

Closed
cyberduck opened this issue Aug 7, 2008 · 3 comments
Closed

Problem with synchronize when using tunneled sftp #2381

cyberduck opened this issue Aug 7, 2008 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Aug 7, 2008

anonymous created the issue

As I can access the host not directly I have created an port redirection from port 10001 of my local machine to port 22 of the targetcomp hopping over an, from outside reachable, server via:
ssh -L 10001:targetcomp:22 user@server

Now I connect cyberduck (sftp transfer) to localhost at port 10001. This works fine and I can do manual down/up-loads.

The problem arrises If I use synchronize to an larger nested directory structure. With the latest release (build 3999) cyberduck stops working at some subdirectory (no progress in action, no data transfer).
With the latest nightly build (4155) I have not this problem, but at the end cyberduck reports an error due incomplete download. Only different sizes are reported but no files specified. But I have the impression, that everything is loaded.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 9, 2008

anonymous commented

The problem (as with 4155) persists with 3.02. The directory is a very full /Library/Mail folder.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 13, 2009

@dkocher commented

Milestone 3.2 deleted

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 9, 2009

@dkocher commented

I cannot replicate this in the latest snapshot build available at http://update.cyberduck.ch/nightly. Please reopen if this is still an issue for you.

@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.
Projects
None yet
Development

No branches or pull requests

2 participants