Inconsistent Support for the DYNAMIC_PORT Variable

A fix for this issue has been implemented in version 2026.3.16.0

Inconsistent Support for the DYNAMIC_PORT Variable

avatar

Hello,

I am using Remote Desktop Manager version 2026.3.13.0, and I would like to report an inconsistency in the support for the DYNAMIC_PORT variable across different session types.

This variable is used to retrieve the dynamically allocated local port of an SSH tunnel established by a VPN connection. It is particularly useful when the local port is assigned randomly, as it allows other applications to connect to the correct port without requiring a fixed port configuration.

However, DYNAMIC_PORT appears to be supported by some session types, such as Command line application, but not by others. Specifically, I am unable to use this variable with the official DBeaver plugin.

I found an older discussion on your forum, dating back approximately eight years, where this functionality was already addressed for DBeaver: $DYNAMIC_PORT$ is always 0

At the time, support for this use case appears to have been added when DBeaver was used through a different session configuration. However, with the introduction of the official DBeaver plugin, this functionality seems to have been overlooked or is no longer available.

Could you please clarify why DYNAMIC_PORT is not supported by the DBeaver plugin, while it works with other session types such as Command line ?

More importantly, could you consider adding support for DYNAMIC_PORT to the official DBeaver plugin, so that it can dynamically connect to SSH tunnels using randomly assigned local ports?

Ideally, this variable should be consistently available across all relevant session types and plugins, wherever the underlying connection mechanism supports it.

Thank you for your time and consideration. I look forward to your feedback.

All Comments (3)

avatar

Hello,

Thank you for the detailed report, and for pointing out the difference between session types.

We tested this in our lab with RDM 2026.3.13.0, the same version you are using, and we were able to reproduce what you describe: the Command line entry receives the dynamic port of the SSH tunnel, while the DBeaver entry does not and is launched with the port configured in the entry.

We have opened an investigation with our development team to look into this. I cannot give you a timeline at this point, but I will update you here as soon as I have news.

Thank you for your patience and for reporting it.

Best regards,

Alexis Geller Peiro

avatar

Hello,

This will be fixed in the next minor update, RDM 2026.3.16.0

Regards,

David Hervieux

avatar

Hello,

Following up on this case: RDM 2026.3.16.0 is now available, and its release notes include a fix for the issue you reported. The DBeaver add-on, along with several other add-ons, no longer ignores the dynamic port of a VPN tunnel, so a DBeaver entry linked to a tunnel using a random local port should now connect to that port instead of the one configured in the entry.

You can download the new version from our website:

https://devolutions.net/remote-desktop-manager/download/

Once you have installed it, could you please test it with your DBeaver entry and confirm that it now works as expected? If it still opens DBeaver with the original port, please reply with a few details (how the tunnel is linked to the entry and whether "Use dynamic port" is enabled), and we will look into it further.

Thank you for your patience and for reporting this.

Best regards,

Alexis Geller Peiro

A fix for this issue has been implemented in version 2026.3.16.0