[SOLVED] SSH jump host: cannot enter credentials, cannot connect, and RDM hangs

Hello,

Thank you for the report, I'll check to see what's wrong.

Regards,

Next version of RDM Free will correctly allow you to specify credentials for the gateway. For the issue with RDM hanging, we're currently investigating.

Regards,

Thanks! Let me know if I can provide some logs...

Hello,

We've identified the underlying problem and a fix has been made internally. With it, we can't reproduce the issue you reported. There are still a few kinks to iron out but it should be more stable in the next release of RDM Free+Enterprise.

Regards,

Hello,

Thanks, I'm eager to test that. I'll make sure to report any other bug I encounter. :)

I had the same hang problem on 12.6.0.0, just updated to 12.6.1.0 and the problem persists.

Hello Gustavo,

Are you encountering the hang only when the terminal prompts for a username, or does it occur any time you try to close it?

Regards,

I use saved credentials so I never get prompted for anything. I get the black terminal and I am able to close the tab, but can't do anything afterwards, and the sidebar still shows up as connected.

I confirm this is the same on v3.6.1.0 (Free): I saved the credentials in my connection, I only get a black terminal. As soon as I close the tab, RDM hangs.

I'm unable to reproduce the issue with the gateway not connecting (giving a black screen).
If you are using host names to connect, could you try using the IP directly? It might improve the connection speed.


Just to be sure, does this gateway setup work with the Rebex SSH Shell entry type?

Regards,

I'm already using IP addresses.

I'm not sure how to test with Rebex, I don't see the connection type in my free edition:

In the bottom left there is the option button (the dots), you need to check the "Show deprecated entries" + "Show subtypes" button:

Thanks. Just tested, jump host works flawlessly with Rebex Shell.

Same for me, was already using IP addresses and the jump host works fine with Rebex (which is what I've been using).

We've made a fix for the hang when closing the tab, but for now we're unable to reproduce the black screen issue. The change will be available in 12.6.2.0, I'd like if you could try out the gateway again when that version is out.

Regards,

I just tested with version 3.6.2.0: closing the tab doesn't make RDM hangs anymore, but still no SSH connection is opened.

Could you enable verbose as well as the logs (event mode) in the SSH shell settings:



And then send the log file to me through private message.

This might help us figure out the underlying issue.

Regards,

Hi Hubert,

I've found the issue by looking at those logs! Here are my logs:

[02/08/2017 18:07:04] Looking up host "172.16.19.41" (IPv4)
[02/08/2017 18:07:04] Connecting to 172.16.19.41 port 0
[02/08/2017 18:07:04] Failed to connect to 172.16.19.41: Network error: Cannot assign requested address

The issue is that the default port for the jump host is 0, not 22:



Changing the port to use 22 allows me to connect correctly.

I guess you could make a change in RDM to set the default port to 22 (like it is for the SSH main connection). In the meantime, we just have to remember to set the port, and all is good. Thanks a lot for your help!

Great catch :) We'll fix this for next version.

Regards,

Confirmed it works for me as well after changing the default port to 22. Thanks!