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
I want to xxh into a host that is configured to use 2 jumphosts. It is not resolvable from my local machine. ssh apparently uses the jumphosts to resolve the final host. laptop --- (VPN) ---> maestro ---> remote-gateway ---> dmz-app02 ~/.ssh/config
Host dmz-app02.customers-localdomain.intranet
User root
ProxyJump maestro,remote-gateway
Host remote-gateway
User fphtl
HostName gateway.customerdomain.de
ProxyJump maestro
Host maestro
User root
HostName maestro.localdomain.intranet
Now ssh dmz-app02.customers-localdomain.intranet
works fine
but xxh dmz-app02.customers-localdomain.intranet
Probably the connection takes more time than expected.
Try to increase the timeout by adding "++pexpect-timeout 10" argument.
Answer from host is empty. Try again with +v or +vv or try ssh before xxh.
If I add the IP address manually to the ssh config, it works fine. But that is a lot of hosts which change quite frequently. Is this inherent to the way xxh uses ssh or ist there a way to configure this?
The text was updated successfully, but these errors were encountered:
First, we have a lack of this kind of feedback before and this is the case that hard to test. It would be very cool if we had a docker-composed testing stand for this in xxh-dev. In this case we will be in the same environment while we testing xxh.
Second, the final xxh command is ssh host -t "/path/to/shell/entrypoint.sh" in fact. The connection between local host and the remote host are on the ssh shoulders. The first you can try to test is this command is working i.e. ssh host -t "/bin/bash". If it works then xxh should work. You can try to build xxh local on the remote host and repeat the command i.e. ssh host -t "/home/user/.xxh_local/.xxh/shells/..../entrypoint.sh". Don't forget about verbose mode -v in ssh and +v/+vv in xxh.
Third, on the off-chance, try what you see in the notification - increase timeout - ++pexpect-timeout 90.
Finally try to disable pexpect by adding ++pexpect-disable.
Thanks for diving into it! Resolving this issue is very desirable and appreciated!
I want to xxh into a host that is configured to use 2 jumphosts. It is not resolvable from my local machine. ssh apparently uses the jumphosts to resolve the final host.
laptop --- (VPN) ---> maestro ---> remote-gateway ---> dmz-app02
~/.ssh/config
Now
ssh dmz-app02.customers-localdomain.intranet
works fine
but
xxh dmz-app02.customers-localdomain.intranet
If I add the IP address manually to the ssh config, it works fine. But that is a lot of hosts which change quite frequently. Is this inherent to the way xxh uses ssh or ist there a way to configure this?
The text was updated successfully, but these errors were encountered: