SSH Session isn't restarting after being closed

Hello,

Thank you for contacting the Devolutions service desk!

Allow me to ask you a few questions to help me attempt to replicate this behavior internally.

• What version of RDM do you currently use?
• What type of data source do you use with RDM?
• Are there any other non-default options in your SSH Shell entry's properties other than "Close on disconnect or error" ?

Best regards,

Hi Gabriel,

Version of RDM: 2022.2.12.0
Data source: Local Data Source
The following are changed from defaults:
Max scrollback lines: 20,000
Unticked "Close on disconnect or error"
That is really it...
Some of the connections are setup with jump host (SSH Gateway), some aren't. Some have TCP keepalives enabled, others don't... But "Reconnect" isn't working with any questions.

In fact, Reconnect is working when SSH session is live - when doing Reconnect on such session it closes session and reconnects in the same window. If I close session (ie with "exit" command in SSH) and then trying to click "Reconnect" then nothing happens.

root@test-host-01:~$ exit
logout
[30/09/2022 16:51:07] Bytes sent: 2528, Bytes received: 3871
[30/09/2022 16:51:07] Packets sent: 19, Packets received: 23
[30/09/2022 16:51:07] Kex completed: 1

Hello,

Thank you for your response!

I will see if I can replicate the issue, and I'll get back to you as soon as I have news to share.

Best regards,

Hello,

Thank you for your response! I would like to verify if it would be possible for you to update to the latest version of RDM, 2022.2.24.0, and see if the issue persists.

On my side, with this version, I have no issues reconnecting a session that has been disconnected with the Exit command.

Best regards,

Hi Gabriel,

Sorry I prob had to mention that at the beginning - I am using Mac version of RDM. And I checked on your website the latest available version of RDM for Mac is 2022.2.12.0. For Windows 2022.2.24.0 is latest. But I don't have Windows where I could test it.
And perhaps the issue isn't "version related", maybe it is OS related problem. Do you have resources to test that scenario on MacOS instead? Or let me know if you want me to contribute more to that troubleshooting and provide some lower level debugging details.

Thanks.

Hello,

Thank you for your response! I'm sorry I assumed you were on Windows, I should have asked to avoid confusion.

In that case, since you are using RDM for Mac, I will test again with that version instead and see if I can replicate. I should be able to give you another update soon!
Best regards,

Hello,

I can confirm that I was able to replicate the issue on RDM Mac! I'm going to open a ticket shortly so our engineering team can look into this.

We will keep you posted as progress is made on the case!

Best regards,

Update : In case it could come up, the ticket number for this case is RDMM-3545

Hello,

Our engineering team has solved the issue you reported. The fix is available in the new version of RDM Mac that just released today, RDM 2022.3.4.0.

Best regards,

Thanks Gabriel. I can confirm it is resolved now with new release.