Scenario #1 which is working:
> in server 1 I have host setup with username and ssh key + SSH gateway through jump server with username and ssh key.
This connection auto connects through the gateway jump server into server1 properly as it always has and still does.
Scenario #2 which is NOT working:
I then have servers 2,3,4,5 setup to connect to their respective servers using username and ssh key.
In all 4 of these setups I have 2 ssh gateways configured:
This setup has been working for a couple years now but after this latest update (2025.2.17.0 64-bit (JIT)) #2 above (server1) pops up interactive authentication prompting for username. manually entering same username that is already in the ssh gateway config works. Yes the jump server does not prompt. This happens in all 4 servers.
I have 7 other sets of servers setup the same way and all are affected. Its as if the 2nd SSH Gateway is not honouring the configured username and forcing a prompt.
Interactive authentication in terminal global setting is set to NO
all the server connections are set to Default but I tested manually setting to NO, with no difference.
Hello Patrick,
Thank you for reaching our to the Devolutions support team.
On which version this set-up was working?
Are you using the agent for those hops?
Which type of data source you are using?
What is the version of this data source?
Can you also share the Gateway logs and the Profiler level 1?
https://docs.devolutions.net/rdm/commands/help/profiler/
https://docs.devolutions.net/dgw/kb/troubleshooting-articles/gateway-troubleshooting/#devolutions-gateway-logs-and-diagnostics
Use this link to share your logs:
FOR-50422 PatrickPower
Best regards,
Patrick Ouimet
> On which version this set-up was working?
>>>>> ALL previous version. been using this setup for years. I check for updates every Friday morning. I didnt check my previous version but i would guess it was the last version Version 2025.2.16.0
> Are you using the agent for those hops?
>>>>> Yes I use Pageant agent, speaking of which, that seems to no longer get stopped when closing RDM anymore with this new version. I disconnect all my session then close RDM. Next time I launch RDM and I now get error that it cant start because one is already running. restarting laptop is only way I have found to solve it as I do not see anything in tray or task manager. And because my only open current session failed to start, i can not stop it within RDM.
> Which type of data source you are using?
>>>>> Local data source (SQLite)
> What is the version of this data source?
>>>>> I do not know how to check that
> Can you also share the Gateway logs and the Profiler level 1?
>>>> Profiler was sent using the send to support button within profiler.
>>>> For Gateway logs when I click admin > Devolutions Gateway it redirects me to https://devolutions.net/solutions/starter-pack/ not where the steps in your article send me
Hello Patrick,
Thank you for this feedback.
This is a known issue with multiple hops.
It should be fixed on version 2025.2.18.0.
Best regards,
Patrick Ouimet