New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure connecting through jump server with alias in configuration for target host #11227
Comments
Please make sure to run the current snapshot build of [milestone:7.7 7.7] as version 7.6.2 does not yet have this feature. The bookmark configuration refers to the target host in the internal network. We should find a |
|
Hi! Thanks for your reply. I got version 7.7.0 (33716) running but the bastion connection still isn’t working for me. I think I may be misunderstanding part of the terminology. Allow me to explain my setup: .ssh/config:
When I use ssh, I can just Cyberduck fails without errors—which is what I’d expect from an app trying to connect to RedCapNew directly, without a bastion… In Cyberduck, I’ve entered redcap.address.com in the Thanks again for your help, —Marco |
Hello. I'm also using version 7.7.0. ~/.ssh/config
/var/log/secure on bastion
Cyberduck is trying to connect to "targetserver", it should connect to 192.YYY.Y.YYY. I added "192.YYY.Y.YYY targetserver" to /etc/hosts in bastion and it worked. Thank you. |
Replying to [comment:3 mbaciarello]:
You should enter |
Replying to [comment:4 ApplePedlar]:
Thanks for reporting this. We will try to reproduce. |
I can reproduce this error, which is actually reported by Cyberduck in my case. After entering the
I'd say it looks as though Cyberduck entered the |
Hi, The feature is still not working for me. I am running Version 7.7.1 (33788) on macOS 11.0.1. I have set ~/.ssh/config as follows:
If I do ssh ServerB from Terminal, everything is working fine. In Cyberduck, I add a new bookmark using SFTP protocol and set the field "Server:" to "ServerB". It automatically autocompletes the field "Username:" correctly. Then, when I try to connect, it gives me an error Connection failed saying the following: -DNS lookup for ServerB.address failed. DNS is the network service that translates a server name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing access to the network.* Thank you for your help. -EDIT:* Could it just be related to the fact that the user in the bastion host is different from the user in the target host? It is not a problem in the config file, since it is working from command line. It also works in Cyberduck when trying to connect to a different remote machine where the user has the same name as that of the bastion host. |
Version 7.7.2 is working fine for me. Not sure if it's in the official release or beta update channel, so in case you want to try it: Preferences → Update → … check for updates in → Snapshot Builds I'd close the ticket but trac doesn't show version 7.7.2 in the popup menu, yet… |
Thank you, version 7.7.2 is also working for me. I did not notice it because it is not in the official channel yet. However, the password of the jumphost server is not saved (even if Add to keychain is checked). I tried both password and public key authentications. I also tried by adding another bookmark with the jumphost only. In that case the password is correctly saved for the access to the jumphost, but when I connect to the target server via the jumphost, it is asked again every time. Is that expected? |
Confirmed, in my case it's mandatory pub key auth, and Cyberduck fails to store the passphrase in Keychain even though the checkbox is ticked and UseKeychain is 'yes' in the bastion host's config. As a workaround, I had to set the passphrase to my private key to null (ssh-keygen -p), but I can't recommend this because it's relatively insecure. |
The latest snapshot builds with version 7.7.2.x do not have any additional changes regarding SSH jump host support. The DNS error if we cannot resolve the target host ( |
Replying to [comment:13 ioemilio]:
I can confirm this is not currently working as expected and credentials for jump hosts are not saved. As a workaround, set a private key to be used for authenticating with the jump host in the OpenSSH configuration using |
Can you please try if still see this issue with the current snapshot build |
It looks like it is working now (with build 33825), and also the password field is already correctly filled in. Thank you! |
Confirmed working… Thanks for the outstanding support. |
Hi,
I've read that Cyberduck can use configuration data from ~/.ssh/config in order to connect to SFTP servers. Specifically, I need this because I need to connect via a bastion server (Proxyjump option).
From the wiki page, I really can't understand how to configure a new connection which will use the config info. Should I use the Host value from the config file as the server's nickname in Cyberduck? Or as the server's nickname?
Thank you in advance for your help…
The text was updated successfully, but these errors were encountered: