Thanks again for the feedback regarding the PuTTY fix of the latest build. @Branko and others, I've just updated the KB regarding the Linux version as well. We can share that we are actively working on Linux but except for that we can't really share anything else right now.
jason w
For a while now, I've had recurring problems with the PuTTY integration. When it works, PuTTY is launched and RoyalTS encapsulates it in a tab as it should. When it fails, I get a separate PuTTY window, and RoyalTS thinks the connection has failed, but the PuTTY window works fine (logs into the server and works as normal) - just not inside RoyalTS.
This problem started gradually over multiple RoyalTS versions. Now, it happens almost every time I launch an SSH session - from a connection in the document, or duplicating a tab.
This happens on multiple Linux servers - RHEL7, RHEL8, and Debian 12. Oddly, it rarely (if at all) happens on my Opnsense box (FreeBSD). (One difference I can see beyond the remote OS is that my Opnsense box is a "static" connection, where all of my other servers are in a dynamic folder.)
I am on latest RoyalTS on Windows 11. My PuTTY plugin settings are the default, except for the embed method (set to Window - I have tried Client Area with no change, and the PuTTY cursor not being focused when using Client Area is a distraction for me).
I am using the PuTTY shipped with RoyalTS. In my PuTTY session, I do not have a custom window title.
Happy to share more info or any required logs. Appreciate any insight into what is going on.
1 person has this problem