cyberduck
cyberduck copied to clipboard
Issues downloading an .iso file from SFTP
It's not just me, some of the guys at Native Instruments have had the same issue. When downloading an .iso with Cyberduck, the process doesn't stop when it reaches the end of the file. In other words, the download keeps on going and I never have a complete file. Yesterday for instance, the download reached some 40 GB of a 12 GB file before I cancelled it.
Hopefully you already know about this and a fix is on the way, because I love Cyberduck otherwise.
This is version 8.4.2 on an M1 Mac 12.4
cheers, Dan [email protected]
Hi Dan,
I can't reproduce the described download behavior within the latest Snapshot version in combination with the SFTP servers available to me.
Please tell us which server software you are using on the server.
Additionally, please enable debug logging, reproduce the download behavior, and send us the log file afterward. If you don't like to see sensitive data shared publicly, please send the log file with the ticket reference GH-13634 to [email protected]. Otherwise, attach it here.
Sidenote: If you want to share the log file here, make sure to attach it through the GitHub web interface, as it wouldn't be visible to us otherwise.
– Laura
Hi
I'm having a similar issue (version 8.4.3 on M2 MacOS). Download seem to continue forever and past 100%...
I checked the enable-debug-logging box only after stopping the download, but there seems to be some info in there nonetheless: cyberduck.log
After turning off the "Segmented downloads with multiple connections per file" option, I could download the file. Although once it had finished I think Cyberduck tried to restart the download, asking me if I wanted to overwrite the downloaded file, so I selected "cancel" and the file seems to be okay.
Yes, I've had to turn off the same "segmented downloads" option. Cyberduck works properly with that option off.
@polypx @bertcoerver Please let us know what SSH server you are connecting to. The SFTP server does possibly not implement reads with a file offset properly.
Hello,
just a headup. Same issue happening with Google Drive:
Duplicate for #13374.