[Cyberduck-trac] [Cyberduck] #10731: Backblaze B2: Auto-retry does not resume with 'Interoperability failure - SSL peer shut down incorrectly'

Cyberduck trac at cyberduck.io
Sat Jun 8 21:23:24 UTC 2019


#10731: Backblaze B2: Auto-retry does not resume with 'Interoperability failure -
SSL peer shut down incorrectly'
------------------------+----------------------
 Reporter:  trustin     |         Owner:
     Type:  defect      |        Status:  new
 Priority:  normal      |     Milestone:
Component:  core        |       Version:  7.0
 Severity:  normal      |    Resolution:
 Keywords:              |  Architecture:  Intel
 Platform:  Windows 10  |
------------------------+----------------------
Description changed by trustin:

Old description:

> 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 sometime 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.

New description:

 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.

--

--
Ticket URL: <https://trac.cyberduck.io/ticket/10731#comment:1>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows


More information about the Cyberduck-trac mailing list