SFTP failure to connect

[wnjohnson3]

I’ve been using cyberduck for years but recently (new mac m1 sonoma) I can not use cyberduck to sftp connect to anything. So I purchased 9.0.2 from the Apple Store and still having the same problem.

Most recent testing is connection to 2nd account on my mac.

command line sftp test@192.168.146.200 works just fine,

but doing the same with cyberduck gets Connection Failed: Broken pipe. The connection attempt was rejected. The server may be down, or your network may not be properly configured.

Steps to reproduce the behavior:

1. Open Cyberduck browser
2. Click on test connection
3. Connection immediately fails and countdown 10 sec to retry
4. See Connection failed dialog box

Expected behavior
successful login to remote, and remote browser to to display directory

Screenshots
configuration

Desktop (please complete the following information):

• OS: Mac OS Sonoma (M1 processor)
• Version 14.7

Log Files
Please include the [log file]
cyberduck.log

Additional context
Add any other context about the problem here.

[vincentluciani]

Hello,
Is it related to the issue I raised (#16366)?
Looking at your screenshot, I see the url (value in blue with hyperlink: sftp://192.168.146.200) does not contain the user name (should be sftp://test@192.168.146.200 ?). That would explain why the connection functioned properly with the command line (sftp test@192.168.146.200) versus the connection with Cyberduck (sftp 192.168.146.200).
I am also a Mac user

[wnjohnson3]

Yes, exactly. I did not notice that. In past versions the username was automatically added to the url. Now I can’t figure out how to make that happen.

…

On Sep 23, 2024, at 9:07 AM, Vincent Luciani ***@***.***> wrote: Hello, Is it related to the issue I raised (#16366 <#16366>)? Looking at your screenshot, I see the url (value in blue with hyperlink: sftp://192.168.146.200) does not contain the user name (should be ***@***.*** ?). That would explain why the connection functioned properly with the command line (sftp ***@***.***) versus the connection with Cyberduck (sftp 192.168.146.200) — Reply to this email directly, view it on GitHub <#16368 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALRSX6X7SMPKT32PEFHVCSDZYAHCFAVCNFSM6AAAAABOUVVHVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRYGE3TGNBRG4>. You are receiving this because you authored the thread.

[tatze96]

Now I can’t figure out how to make that happen.

You can't get Cyberduck to display the username within the URL, as it doesn't get displayed within the URL of the bookmark window on macOS, although it is included during the connection. see #16369

[vincentluciani]

Is it a coincidence that since then sftp does not function on Mac anymore but still functions on Windows?

[dkocher]

The log indicates a broken pipe error connecting to 192.168.146.200. Please share the verbose output for a successful connection with ssh -v from Terminal.app

[wnjohnson3]

different ip address (different location) but same computer/problem

cli_ssh.log
cyberduck_240923.log

[wnjohnson3]

I include the command line ssh log and the attempted sftp connection via cyberduck. Note the IP address has changed but the configuration and testing is the same.

cli_ssh.log

cyberduck_240923.log

[wnjohnson3]

I have two Macs.
My home Mac has this problem. It is M2 processor running Sonoma 14.7 and Cyberduck 9.0.2.
My work Mac executes the same tests without problems. It is Intel processor running Sonoma 14.6.1 and Cyberduck 9.0.2.

Is this a M2 code bug???

[vincentluciani]

I have the same problem of connection. I have an M2 processor running no Sequoia 15.0, Cyberduck 9.0.2

[wnjohnson3]

I upgraded from Sonoma to Sequoia 15.0.1 today and my M2 MAC is now working. My guess is the upgrade cleared up some trash that prevented cyberduck from working with Sonoma.