Royal Apps

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.

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. 

I went through the recent issues and this got my attention: 

https://support.royalapps.com/support/discussions/topics/17000024949

I noticed that something has changed regarding renaming the Putty Tabs with the recent RoyalTS version. I tried disabling this functionality on a SSH Connection:

Properties - Advanced - Features - "Disable Remote-Controlled Window Title Change"

Now when I accept the connection to known hosts at first connection, the Putty window is embedded to RoyalTS every time. 

Some time = 10 minutes :)

I know about the Bulk edit, I just have 425 Connections spread out through many folders, so Dashboard view doesn't group the all at once in the view, so I went folder per folder per "Connection Type". No big deal, just glad the behaviour is back.  

"Show all connections from all subfolders" - oh nice, didn't know about this feature before. Thank you, I'll keep this in mind for future bulk edits.

Can confirm I'm having the same issue on some of my connections too. 

Error that I'm getting is "Cannot read executable filename for process with id 9016: "Access is denied.""

Also ""StartAsync" failed starting ""C:\Users\<username>\AppData\Local\Temp\Royal TS V7\Plugins\107df0a3-eab8-40ee-87f2-cc8a310f9269\RoyalTS_PuTTY.exe"" popped up at least once.

In both cases Putty window is starting up in separate window, but RoyalTS thinks that connection has failed.

I believe I've never encountered this error before the last update i've installed (7.3.50602)

Same problem here since version 7.3.50602 with putty (0.83) based ssh connections (rebex works fine)

Properties - Advanced - Features - "Disable Remote-Controlled Window Title Change" --> Helps ... but please fix the behavior to the last state before the update.

I was just about to test it again, then it worked for me. Then I had a colleague check it, some of the servers that didn't work yesterday worked for him. Then I tried again, most of the servers worked, but then it suddenly started again and the putty sessions only opened in the background. Even those that were still working 1 minute ago. But some of them still working. 

One thing I noticed: One of the working embedded putty window in Royal shows now the "Computer name" instead of the "Display name" like before?

So we can't recreate it consistently either. But we only have the phenomenon since the latest update.

Even while I'm writing this post, the behavior change from minute to minute. Connection that not be embedded 2 minutes before now working, others do not work now. Maybe a timing issue?