Cyberduck Mountain Duck CLI

#11574 closed enhancement (worksforme)

how to debug ssh failed connection

Reported by: todd.fischer Owned by:
Priority: normal Milestone:
Component: sftp Version: 7.8.2
Severity: normal Keywords: ssh
Cc: Architecture: Intel
Platform: macOS 10.15

Description

Question: when an ssh connection fails, where do I find the log so I can see at which step the failure occurred?

I have used cyberduck for years to move files up to my hostgator account. I recently upgraded to a cloud based account. For some reason cyberduck gives me a "Listing directory / failed" error message. I have cut the user name, IP address, and port number out of the cyberduck bookmark and pasted it into a shell terminal session ssh command line parameters and everything works fine from the command line (shown below).

I am at a loss as to how to debug what I am doing wrong with CyberDuck.

Thanks for a great product. I used CyberDuck nearly every day.

Todd

bongo-osx:~ toddfischer$ ssh -v -p 2222 efcv4qc9@50.116.88.12

OpenSSH_8.1p1, LibreSSL 2.7.3
debug1: Reading configuration data /Users/toddfischer/.ssh/config
debug1: /Users/toddfischer/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 47: Applying options for *
debug1: /etc/ssh/ssh_config line 51: Applying options for *
debug1: Connecting to 50.116.88.12 [50.116.88.12] port 2222.
debug1: Connection established.
debug1: identity file /Users/toddfischer/.ssh/id_rsa type 0
debug1: identity file /Users/toddfischer/.ssh/id_rsa-cert type -1
debug1: identity file /Users/toddfischer/.ssh/id_dsa type -1
debug1: identity file /Users/toddfischer/.ssh/id_dsa-cert type -1
debug1: identity file /Users/toddfischer/.ssh/id_ecdsa type -1
debug1: identity file /Users/toddfischer/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/toddfischer/.ssh/id_ed25519 type -1
debug1: identity file /Users/toddfischer/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/toddfischer/.ssh/id_xmss type -1
debug1: identity file /Users/toddfischer/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c000002
debug1: Authenticating to 50.116.88.12:2222 as 'efcv4qc9'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: diffie-hellman-group-exchange-sha256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(2048<8192<8192) sent
debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: got SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: ssh-rsa SHA256:O4CwSiIUGPvZLmNaN8p3KF51yu7p2WtpF9OsN2z7NU8
debug1: Host '[50.116.88.12]:2222' is known and matches the RSA host key.
debug1: Found key in /Users/toddfischer/.ssh/known_hosts:76
debug1: rekey out after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 4294967296 blocks
debug1: Will attempt key: /Users/toddfischer/.ssh/id_rsa RSA SHA256:0cvOwYFhMu8oLWnC1CS9gpqftg1ByrafIQ5NJO18dUQ
debug1: Will attempt key: /Users/toddfischer/.ssh/id_dsa 
debug1: Will attempt key: /Users/toddfischer/.ssh/id_ecdsa 
debug1: Will attempt key: /Users/toddfischer/.ssh/id_ed25519 
debug1: Will attempt key: /Users/toddfischer/.ssh/id_xmss 
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: /Users/toddfischer/.ssh/id_rsa RSA SHA256:0cvOwYFhMu8oLWnC1CS9gpqftg1ByrafIQ5NJO18dUQ
debug1: Server accepts key: /Users/toddfischer/.ssh/id_rsa RSA SHA256:0cvOwYFhMu8oLWnC1CS9gpqftg1ByrafIQ5NJO18dUQ
debug1: Authentication succeeded (publickey).
Authenticated to 50.116.88.12 ([50.116.88.12]:2222).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: exec
debug1: Requesting X11 forwarding with authentication spoofing.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
X11 forwarding request failed on channel 0
Last login: Mon Feb  1 09:43:43 2021 from 63.227.129.129
efcv4qc9@fastcam.com [~]# 

Change History (1)

comment:1 Changed on Feb 5, 2021 at 6:35:04 PM by dkocher

  • Component changed from core to sftp
  • Resolution set to worksforme
  • Status changed from new to closed

Try if sftp -v -p 2222 efcv4qc9@50.116.88.12 works on the command line. Try to provide log output from Cyberduck.

Note: See TracTickets for help on using tickets.