SFTP failure to connect #16374
Replies: 6 comments 8 replies
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
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.
|
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
|
Is it a coincidence that since then sftp does not function on Mac anymore but still functions on Windows? |
Beta Was this translation helpful? Give feedback.
-
|
The log indicates a broken pipe error connecting to |
Beta Was this translation helpful? Give feedback.
-
|
different ip address (different location) but same computer/problem |
Beta Was this translation helpful? Give feedback.
-
|
For some reason the server blocks the connection for Cyberduck. Check the server log for any related output. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I have two Macs. Is this a M2 code bug??? |
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem of connection. I have an M2 processor running no Sequoia 15.0, Cyberduck 9.0.2 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I'm facing the same issue. Worked for years. |
Beta Was this translation helpful? Give feedback.
-
|
Share a log file and the error message. |
Beta Was this translation helpful? Give feedback.
-
|
Ha! The culprit is the privacy protection setting for "local network" that obviously gets reset with (more or less) every macOS update. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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 [email protected] 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:
Expected behavior
successful login to remote, and remote browser to to display directory
Screenshots
configuration
Desktop (please complete the following information):
Log Files
Please include the [log file]
cyberduck.log
Additional context
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions