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.

Embed method: Window

The new build does not change anything. Still the most of the putty windows are not recognized and open in the background and are not embedded. 

I send you a demo with a not working example from one of our gitlab server via support ticket and give you a reference to this forum post. The only thing is: We use a credential as reference. That works. Then I change it from credential to embedded user/password. The error still exists. Then I changed our password to a wrong dummy password: The putty window starts embedded am give me the error message wrong password and the terminal window is embedded in the background :-) But maybe you can change it to a server IP you have access and it still fails?

Hi Stefan. I tried to do a quick screen recording but have not the right tooling to do it now. There are NO additional messages on screen nor from putty.  The putty windows stays minimized, but the connection is open.

I would like to share the behavior via a teams/teamviewer whatever session ... but it seems its not allowed on your side.

I uploaded a screenshot to the ticket.

No, it ends with  a ~ 

see screenshot in ticket ... 

Prompt is in the ticket. I search more prompt examples ... maybe you will find something simmilar ...

But sometimes it works, sometimes not. And I changed nothing to the prompt. But anyway ... It worked before the update ... why not change back the behaviour of RoyalTS to the old, working one?

most of the prompts are default debian ... most of the connection on our side use rebex ...some of the connections work better with putty ... 

Hi Stefan. Thanks for the new Release. We tested it on two separate installations, and it seems to work now. The putty windows are embedded as expected.

Offtopic and also: https://support.royalapps.com/support/solutions/articles/17000027785-is-there-a-linux-version-of-royal-ts-x- 

Unfortunately, my wink smile was not posted.

And I know this 8 years old statement ... but the world continues to move ... Windows 11 is not the future ... and embed putty in a Windows app will also be not the way for the future. Rebex works great most of the time. RoyalTS on macOS works also fine. MS Visio and RoyalTS are the last pieces of software that I currently need Windows for in a VM.

Anyway .. I deleted my post because it's off-topic, you're right. 

Hello, can confirm, version 50617 solved the issue, windows are embedded now.