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
Describe the bug
Unable to connect to ssh target through an egress worker. Getting the error message "Connection closed by 127.0.0.1 port 52471"
The SSH target is a managed application. We are able to connect to other ssh targets such as ubuntu VM's through the same egress worker.
Error message when connection with the client
ssh 127.0.0.1 -p 52471 -o NoHostAuthenticationForLocalhost=yes
debug1: Local version string SSH-2.0-OpenSSH_9.6
kex_exchange_identification: Connection closed by remote host
Connection closed by 127.0.0.1 port 52471
When we connect from the egress worker directly to the target its working
ssh admin@10.10.1.1
debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.6
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.11
debug1: compat_banner: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.11 pat OpenSSH* compat 0x04000000
To Reproduce
Steps to reproduce the behavior:
Start Boundary Client
Connect the target
Error is there
MacBook-Pro-2 ~ % ssh 127.0.0.1 -p 52471 -o NoHostAuthenticationForLocalhost=yes
Connection closed by 127.0.0.1 port 52471
Expected behavior
A succesfull connection directly from a boundary client
Additional context
Similar issue was dropped (#765) but was closed due to no response
The text was updated successfully, but these errors were encountered:
Thanks for the quick response @richardleeps. Do you mind sharing over your worker logs so we can dig into this further? Feel free to email me at adam.bouhmad@hashicorp.com.
Describe the bug
Unable to connect to ssh target through an egress worker. Getting the error message "Connection closed by 127.0.0.1 port 52471"
The SSH target is a managed application. We are able to connect to other ssh targets such as ubuntu VM's through the same egress worker.
Error message when connection with the client
When we connect from the egress worker directly to the target its working
To Reproduce
Steps to reproduce the behavior:
MacBook-Pro-2 ~ % ssh 127.0.0.1 -p 52471 -o NoHostAuthenticationForLocalhost=yes
Connection closed by 127.0.0.1 port 52471
Expected behavior
A succesfull connection directly from a boundary client
Additional context
Similar issue was dropped (#765) but was closed due to no response
The text was updated successfully, but these errors were encountered: