Winbox - opens and runs, attached in rdm tab. Pressing close (x) just remove window but status is kept running (green play icon). So do not opens again while not closed manually (right mouse click - Close). Anyway, its keeping open status in any condition after was launched. And after closing and reopening RDM its present in recent opened window list.
HTML - (Proxmox CP in example). Worked in ealier versions (about 4-5 back). After pressing button/link that opens in new window in current tab - RDM flips/flaps as trying open new window and no new window displayed, current tab stop responding while other tabs continue to work.
Hello,
Thank you for contacting us on this matter!
In order to help us attempt to replicate the behaviors internally, I would like to ask you a few questions.
Best regards,
Gabriel Degrandpré
3.2. HTML
In addition, memory garbage/leak after closing html tabs (Microsoft Edge WebView2 processes) didnt closing.
Hello,
Thank you for your reply! In order to investigate the first issue with the Microtik Winbox entry, I will have to look into obtaining an environment to test this internally.
Regarding the second issue, I would like to verify if temporarily changing the embedded browser to Edge instead of Chrome changes the behavior, or if it remains the same. The goal would be to verify if the issue affects all web sessions, or only those using the Chrome embedded browser.
Best regards,
Gabriel Degrandpré
Hello,
Same problem with winbox for me, it appears since 2022.2.12.0 version if im not mistaken
Changing embedded browser to Edge fix the second issue.
Hello,
Thank you for your responses!
I'm still working on getting a working Winbox test entry, I'll update the forum thread as soon as I am able to test it and see if I could replicate the problem.
Best regards,
Gabriel Degrandpré
Hello,
First of all I would like to thank you for your patience while we were waiting for the Winbox environment to be set up. It's finally here and functional.
I believe I was able to replicate the issue, and I will report it to our engineering team shortly. In the meantime, it would seem that using the Close button from the Dashboard tab after having closed the Winbox session will allow you to manually remove its "'Running" state, so this could be a workaround for now.
I will update the thread as soon as I have new information to share!
Best regards,
Gabriel Degrandpré
Hello,
The closing of Winbox sessions is now fixed internally, and will be in version 2022.2.27.0.
Regards
Jonathan Del Signore
Version 2022.2.29.0.
Winbox sessions closing issue still present
Hello,
Thank you for your response.
May I ask you, if you have the time, to try our current RDM beta for version 2022.3.12.0? I would like to confirm if you also experience the issue on this version, since on my side I confirmed that the issue is resolved in both this beta and in RDM 2022.2.29.0.
Here are the steps to create a portable instance of the RDM beta :
1. Download the RDM zip folder from the link below :
https://devolutions.net/remote-desktop-manager/home/thankyou/rdmbinbeta
2. Extract this zip in an empty folder of your choice
3. Launch RemoteDesktopManager64.exe from this folder
4. Register your license
Note that if you use a team data source, we do not recommend trying to access it from the RDM beta, since the version mismatch could cause issues.
Best regards,
Gabriel Degrandpré
Beta has another behavior. After start it use local datasource (i'm using local) and account is seen. After setup path to winbox, it opens but no login info provided to Winbox. Changed settings (maybe new structure mismatch&) and provided account info from datasource. Unsuccessfull - no account info provided to Winbox. Changed account settings to arbitrary and provide user and password. Success. Closing session works.
Hello,
Thank you for your response!
Could you please elaborate on what you mean by "Changed account settings to arbitrary"? I'm not certain I understand what you did exactly, and want to be sure I properly understand what you did to cause the connection to work
Best regards,
Gabriel Degrandpré
Sorry from Google Translate :)
That means, i provide account/password right in settings fields on the General tab, not choosing from datasource.
Hello,
Thank you for your response! I'll see if I am able to replicate this new issue. I will get back to you shortly with the results!
Best regards,
Gabriel Degrandpré
Hello,
I did some tests but can't seem to replicate the issue you describe unfortunately. I tried the Custom, Inherited and Linked (Vault) credential modes, and they all worked as expected and allowed my Winbox entry to be logged in properly.
Could you please reconfigure your Winbox entry with the settings that do not work, when right-click the entry and select "Copy Username and Password"? I would like to verify if the correct credentials are pasted when this is done.
Best regards,
Gabriel Degrandpré