You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System(s) are you seeing this problem on?
Windows
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
20240203-110809-5046fc22
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
I've tested I can use ssh node01 without error, but wezterm ssh failed.
Host proxy_server
HostName xxx
User ubuntu
Host node01
HostName xxx
User root
ProxyCommand ssh proxy_server-W %h:%p
output:
14:21:50.213 INFO mux::ssh > Using ssh config: {
"hostname": "10.3.3.117",
"identityfile": "C:\\Users\\xxx/.ssh/id_dsa C:\\Users\\xxx/.ssh/id_ecdsa C:\\Users\\xxx/.ssh/id_ed25519 C:\\Users\\xxx/.ssh/id_rsa",
"port": "22",
"proxycommand": "ssh proxy_server -W xxx:22",
"stricthostkeychecking": "no",
"user": "root",
"userknownhostsfile": "C:\\Users\\xxx/.ssh/known_hosts C:\\Users\\xxx/.ssh/known_hosts2",
"wezterm_ssh_backend": "libssh",
"wezterm_ssh_verbose": "true",
}
14:21:50.216 INFO libssh::ssh_config_parse_file > Reading configuration data from C:\Users\xxx/.ssh/config
14:21:50.226 INFO libssh::ssh_config_parse_line > Unsupported option: ForwardAgent, line: 9
14:21:50.227 INFO libssh::ssh_config_parse_line > Unsupported option: ForwardAgent, line: 14
14:21:50.227 INFO libssh::ssh_config_parse_line > Unsupported option: ForwardAgent, line: 19
14:21:50.228 INFO libssh::ssh_config_parse_line > Unsupported option: ForwardAgent, line: 24
14:21:50.229 INFO libssh::ssh_config_parse_line > Unsupported option: ForwardAgent, line: 29
14:21:50.230 INFO libssh::ssh_config_parse_line > Unsupported option: ForwardAgent, line: 35
14:21:50.230 INFO libssh::ssh_config_parse_line > Unsupported option: UpdateHostKeys, line: 68
14:21:50.243 INFO libssh::ssh_connect > libssh 0.8.90 (c) 2003-2023 Aris Adamantiadis, Andreas Schneider and libssh contributors. Distributed under the LGPL, please refer to COPYING file for information about your rights, using threading threads_winlock
14:21:50.244 INFO libssh::ssh_connect > Socket connecting, now waiting for the callbacks to work
14:21:50.246 INFO libssh::ssh_connect > Actual timeout : 10000
14:21:50.247 INFO libssh::ssh_socket_pollcallback > Received POLLOUT in connecting state
14:21:50.247 INFO libssh::socket_callback_connected > Socket connection callback: 1 (0)
14:21:50.248 INFO libssh::ssh_client_connection_callback > session_state=2
14:21:50.248 INFO libssh::ssh_socket_unbuffered_write > Enabling POLLOUT for socket
channel 0: open failed: connect failed: Temporary failure in name resolution
stdio forwarding failed
14:21:50.693 INFO libssh::ssh_socket_exception_callback > Socket exception callback: 2 (10054)
14:21:50.694 INFO libssh::ssh_socket_exception_callback > Socket error: Unknown error
14:21:50.695 INFO libssh::ssh_client_connection_callback > session_state=9
14:21:50.695 INFO libssh::ssh_connect > current state : 9
To Reproduce
No response
Configuration
no relevant wezterm lua file
Expected Behavior
No response
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
What Operating System(s) are you seeing this problem on?
Windows
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
20240203-110809-5046fc22
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
I've tested I can use
ssh node01
without error, but wezterm ssh failed.output:
To Reproduce
No response
Configuration
no relevant wezterm lua file
Expected Behavior
No response
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: