Show SSH error messages sent by server
1
Hello.
In RDM, SSH error messages are not displayed.
This makes it complicated to troubleshoot connectivity issues.
Sometimes we get this:
And from our jump host (linux VM) we get this error message.
I'm not saying it's the same, but it probably is.
SSH error messages sent by the SSH server are usually detailed and helpful.
It would be nice to get the error messages sent by the SSH server.
Best regards.
Marcel
Devolutions Server, RDM and GW admin.
6ea4ae38-4ac1-4a2f-859b-e48d4e4c148c.png
69004c66-55e9-4f0b-8c75-b2e65a6d2361.png
Recommended Answer
Hello Marcel,
From what I see of our internal ticket linked to this forum thread, we have improved the error handling in version 2026.1. Can you confirm on what version you're currently on, and if the error messages have improved?
Regards,
Hubert Mireault
All Comments (9)
Hello Marcel,
If your goal is to see these kinds of logs, you can configure the log tab of your SSH entry to either log these events to a file, or to log them directly in the terminal, which might make it easier to debug these kinds of issues in your case. I would also recommend setting verbose to 2, as I believe this kind of information won't show if it`s set to 0.
You can also pair it with the disconnect action setting so you can keep the terminal opened even if it disconnects, so you can have time to see these logs.
Let me know if this helps you.
Regards,
Hubert Mireault
5b910709-a82d-412a-847e-0159ad6e5928.png
71ca7ce5-ba25-4a19-9cd2-f0f2ff57ad86.png
Hello.
Thanks for the hint, but:
- That conflict with our global logging option configured on all sessions.
- Why not display a meaningful error instead of just a generic error ?
Cheers.
Marcel
Devolutions Server, RDM and GW admin.
I understand the limitation in this case.
I've discussed this with our terminal expert, and good news, it should definitely be possible to improve the handling of possible errors when first establishing the connection. We've opened a ticket to improve this. It will require a rework of how we handle these errors, but he has an idea of how to achieve this which is a good first step.
As a note, when the terminal disconnects after the initial authentication process, it's much more difficult to have appropriate error messages as there's no clear identifier from the server as to why the client was disconnected. So, on that aspect, we won't be changing the behavior for now.
Regards,
Hubert Mireault
Hello.
Great news thank you!
Marcel
Devolutions Server, RDM and GW admin.
Hello.
Do you have any news about this request ?
Thank you and best regards.
Marcel
Devolutions Server, RDM and GW admin.
Hello Marcel,
From what I see of our internal ticket linked to this forum thread, we have improved the error handling in version 2026.1. Can you confirm on what version you're currently on, and if the error messages have improved?
Regards,
Hubert Mireault
Hello @Hubert Mireault
We are currently running 2025.3 in PROD and testing 2026.2 in LAB.
I will check it out in the LAB.
Best regards.
Marcel
Devolutions Server, RDM and GW admin.
Perfect, thank you !
Devolutions Server, RDM and GW admin.
e15744bf-994d-4e25-b321-664422796757.png
That's great, I'm glad to hear this is now more usable for you.
Regards,
Hubert Mireault
