I noticed the same behaviour after the recent RoyalTS update. I use the same Document with Connections on another machine, also Windows - where this behaviour wasn't occuring.
I noticed that I didn't get the "known hosts" warning for this connection. I cleared the content of "Computer\HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys" with Regedit, where the known_hosts for Putty are stored. When this was cleared, after accepting the warning permanently, I got the Putty window embedded in RoyalTS. But after that, it loaded outside again in a separate Putty window.
The Connection has a Credential Name set, which points to a Credential "ssh key" in another Document with Credentials. This Credential "ssh key" has username set and path to a private ssh key in .ppk format.
It seems that which such hosts as soon as the connection is accepted and is stored in Registry Key above as a known host, the Putty window is launched externally. While if I select "Allow once" at the Putty Security warning, Putty is embedded in RoyalTS.
Hi Jason,
sorry you are experiencing issues with PuTTY. I looked at the tickets and couldn't find other issues in this area as you described so I assume it has something to do with your system. Maybe resetting the configuration may help. Please try the following:
1) Stop your running Royal TS instances.
2) Navigate to "%appdata%\code4ward” (C:\Users\<user>\AppData\Roaming\code4ward\).
3) In this folder you should see a configuration file named "code4ward.RoyalTS.UserPreferences.config". Please rename this file to any other temporary name so you can undo the changes if they don't help.
4) Try launching Royal TS again.
5) Check if the issue still exists.
Please note: After doing this, Royal TS will lose its configuration. You will have to reopen your documents and redo any changes made to the configuration.
If this doesn't resolve your issue, please open a support ticket to dig deeper.
Regards,
Stefan
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