Hello,
Same problem here since the last update. Is there a setting to change ?
Thank you very much.
Best regards

We need more context. Can you please provide a debug log showing the issue?

Hello,
Here is my log : cyberduck.log
Thank you very much.

Hello - Same issue on Mac OS 13.4.1, Ever since latest CyberDuck update (Version 8.6.2 (40032)). Broken Pipe errors every few minutes, even when idle with no transfers - then cannot initiate any new transfers, create folders, etc. after errors begin - must close connection and re-connect to server, then all is OK for a few minutes again (FTP running on unraid - no recent changes to server or network environment). If broken pipe errors begin appearing during active transfers, the active transfers are not impacted and still complete successfully.

Thanks for the log files. Is there any chance to get a test account to be able to reproduce the issue as I don't see any reason in the logs? Feel free to send it to support@cyberduck.io for privacy reasons.

same here. Mountain Duck has the same issue. Is there a way to downgrade?
My log from CyberDuck:
mprove-cyberduck.log

CyberDuck 8.6.2 / macOS 13.5
Mountain Duck 4.14.2

PS: Mountain Duck is extremely useful (as it worked a week ago). I am a happy user and donator.

Thanks for providing details and logs. In the meantime I'm able to reproduce the issue and we are working on a fix.

Regression from 05a029b.

Version 8.6.3 with a fix has now been released.

I often had this broken pipe issues, also before this version. But a change of user behavior fixed it for me:

1. Open Cyberduck (SFTP connection on custom SSH port)
2. Edit file with TextEditorOfChoice (creates dir structure + file under /tmp/*)
3. Mac goes to sleep. Mac wakes some time later.
4. First go to Cyberduck and perform a refresh action. May take 20secs or so.
   • In doubt create a blank file, refresh dir (to be sure it is not memory representation only), file still there, delete file. Then you certainly now the pipe is upright.
5. Only then resume in your TextEditorOfChoice.

If your first action after Mac wake is to go to the TextEditor perform some changes and save, then CyberDuck often got stuck. Sometimes managed to continue after 2-3min, but often I had to force quit it, then copy text file contents, then reconnect Cyberduck, reopen file and paste clipboard, or else my changes were gone!

Since I changed my operation order after the wake event I had no crashes ever again!

Version 8.6.3 with a fix has now been released.

Thank you! Much better!