Jetscocat/SOCKS proxy stops when closing extra tab that is connected over DVLS gateway
Every since upgrading from RDM 2026.2 to 2026.3 we are encountering the issue that RDM stops the socks connection when you open a extra web session tab, and close this tab, the other session is also closed.
It's 100% reproducable by using a DVLS gateway connection for a web session, opening info in a new tab, and closing that tab instantly. The other tabs stops responding, and when you refresh it states the socks socket is closed.
Every since upgrading from RDM 2026.2 to 2026.3 we are encountering the issue that RDM stops the socks connection when you open a extra web session tab, and close this tab, the other session is also closed.
It's 100% reproducable by using a DVLS gateway connection for a web session, opening info in a new tab, and closing that tab instantly. The other tabs stops responding, and when you refresh it states the socks socket is closed.
Hello Patrick,
Thank you for the clear description and the reproduction steps.
We were able to match this behavior to a known regression introduced in Remote Desktop Manager 2026.3.
When a Website entry goes through Devolutions Gateway, all the tabs of that session share the same local tunnel.
In 2026.3, closing any extra tab stops that tunnel, so the remaining tabs lose their connection.
Our development team has completed a fix, and it is now in testing.
It is planned for an upcoming 2026.3 maintenance release.
Until then, here is how to limit the impact.
Keep the extra tab open while you still need the main tab, then close the whole entry when you are done.
If a tab already stopped responding, close the entry and open it again to start a new tunnel.
If this blocks your daily work, you can go back to Remote Desktop Manager 2026.2.19, where this issue does not occur. DVLS will also need to be rolled back to 2026.2.
We will let you know as soon as the version with the fix is available.
Best regards,
Alexis Beauparlant
Hello,
Thank you for your patience while our team looked into the issue you reported.
I'm happy to let you know that the latest version of Remote Desktop Manager (2026.3.16.0) includes a fix for this problem. You can download it from our website here:
https://devolutions.net/remote-desktop-manager/download/
Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists or if you notice anything unusual related to the same original problem, just reply to this message with a few details, and we will be glad to look into it further.
Thank you for your collaboration.
Best regards,
Maxim Robert