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

Auto-retry does not resume for failure "Interoperability failure - SSL peer shut down incorrectly" #10731

cyberduck opened this issue Jun 8, 2019 · 1 comment


Copy link

@cyberduck cyberduck commented Jun 8, 2019

c36a63f created the issue

I'm trying to download a multi-terabyte file from Backblaze B2 using Cyberduck 7.0 installed from Microsoft Store. Here's what I did to make sure the transfer automatically resumed even if a temporary network error occurs:

  • Disabled 'Transfers -> Downloads -> Segmented downloads with multiple connections per file'
  • Chose 'Resume' for 'Transfers -> Downloads -> Existing Files'
  • Enabled 'Connection -> Repeat failed networking tasks'

During transfer, I sometimes get 'Interoperability failure - SSL peer shut down incorrectly', which seems to mean the connection has been closed unexpectedly. When this happens, Cyberduck does not resume where the last byte was transferred but starts the transfer from the beginning, practically making it impossible to finish the transfer in my case.

To work around this issue, I have to disable 'Connection -> Repeat failed networking tasks' and press the 'Resume' button in the 'Transfers' window manually whenever an error occurs, but it'd be really nice if I can just enable automatic retry without worrying about this issue.

Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 13, 2019

@ylangisc commented

In fdfd9af.


@cyberduck cyberduck closed this Jun 13, 2019
@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.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants