SSH sessions fail via Devolutions Gateway, error 10054

SSH sessions fail via Devolutions Gateway, error 10054

avatar

Hello,

I’m encountering an issue with all SSH connections through Devolutions Gateway.
RDP, HTTPS and other sessions work perfectly, but SSH sessions fail with the following error in the Gateway logs:

INFO tcp{client=x.x.x.x:15917}:generic_client{session_id="6b6bf8cc-660e-4210-aa2a-edeafef5edde" protocol="Ssh"
target="tcp://x.x.x.x:22"}: devolutions_gateway::proxy: Forwarding ended abruptly reason="Une connexion existante a dû être fermée par l’hôte distant. (os error 10054)"

Details:

  • Gateway version: 2025.3.0 and 2025.3.2 (Windows Server)
  • RDM version: 2025.3.16
  • Target host: VMware ESXi host (SSH enabled and reachable)
  • From the Gateway itself, SSH to the ESXi works fine using PowerShell or PuTTY
  • Only SSH via RDM + Gateway fails immediately

Already tested:

  • Restarted Devolutions Gateway service (no change)
  • Update Devolutions Gateway (no change)


Thanks for your help,

Tiago

All Comments (3)

avatar

Hello Tiago,

Thank you for reaching out to our forum.

1- Could this issue be related to an update of the Gateway version? Was it working before with the same SSH host?
2- I would also like to ask if launching the same SSH entry through the Devolutions Server web interface makes any difference.
3- Additionally, are you able to connect via SSH to another machine, such as an Ubuntu host?

Best regards,

Michel Audi

avatar
Hello Tiago,

Thank you for reaching out to our forum.

1- Could this issue be related to an update of the Gateway version? Was it working before with the same SSH host?
2- I would also like to ask if launching the same SSH entry through the Devolutions Server web interface makes any difference.
3- Additionally, are you able to connect via SSH to another machine, such as an Ubuntu host?

Best regards,


@Michel Audi
Hello,

1- No, this is not related to a Gateway update.
2- It seems to work fine when launched from the Devolutions Server web interface so the issue only occurs from the RDM client.
3- I cannot connect via SSH to other machines, including an Ubuntu host.

Best regards,

avatar

Hello,

Thank you for the clarification. Could you please share with us the properties of that SSH entry in your RDM?


Best regards,

Michel Audi