Openning SSH Sessions - Index was out of range

A fix for this issue has been implemented in version 2025.3.29.0
Resolved Implemented

Openning SSH Sessions - Index was out of range

avatar

Hi,

I've been using RDM for a while and have several ssh connections saved. All of a sudden, when I try to open one I receive this error: "Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index"

Latest version, no updates available.

This is on all ssh connections.

Appreciate any help.

Thanks!

All Comments (27)

avatar

Hello,

Thank you for reaching out to us regarding this,

Could you please specify the version of RDM you are currently using?

I'm also wondering if this issue is occurring with multiple entries or only a specific SSH session?

Best regards,

Samuel Dery

avatar

Sure, build is: 2025.3.22.0 64-bit (PreJIT)

This is happening with pretty much all SSH entries. RDP sessions are working.

Thanks

avatar

Hello,

Thank you!

Could you please try creating a brand-new SSH entry and let us know if the issue persists? This will help us determine whether the problem originates from the global SSH settings or from existing entries.

If the issue reoccurs, please try resetting RDM to its default settings and see if the problem continues:

https://docs.devolutions.net/rdm/kb/how-to-articles/reset-rdm-to-default-settings/

Let me know the results.

Best regards,

Carl Marien

avatar

Hi,

I'm having exactly the same problem with this error. It started appearing after updating to version 2025.3.22.

avatar

Hello,

I would like to review the issue personally and schedule a session with you.

I’ll be sending you an email with a link where you can request a session at your convenience.

Best regards,

Carl Marien

avatar

Happy to jump on a call.

I did some more testing; New connection seems to work. Copying an existing connection has the same error.

An existing connection might randomly work, but no more than one. If opening another connection, it will always fail.

A fix for this issue has been implemented in version 2025.3.29.0