SSH Port Forward seems to be broken in version 2025.2.16.0

Hello,

Thank you for reaching out!

To better understand the issue you're experiencing could you please share a few more details about your configuration and workflow?

The easiest way to share your session settings is to right-click the entry, select Clipboard, and choose Copy Entry. Please remember to any sensitive information before sharing.

Also, could you let us know which data source you're using?

We’ll be happy to look into this further with the additional details.

Best regards,

Stephan

Hi @k526816

For the missing local port forwarding, I have found a possible cause for this bug and a fix has been made that will be available in the next release.

On the other hand, I've been unable to reproduce your problems, so I will need more details to fix the dynamic forwarding. What I understand is that no connection is successful going through the dynamic port forwarding, am I correct? If so, what is connecting to it? (another entry from RDM, an external application?) and what proxy protocol is it setup to use? (SOCKS4, SOCKS4a or SOCKS5?)

Regards

Hi,

>> For the missing local port forwarding, I have found a possible cause for this bug and a fix has been made that will be available in the next release.

For the record, the Local Port Forwarding, the is IPv6 that I am dealing with and it seems to not parse the IPv6 correctly.

>> What I understand is that no connection is successful going through the dynamic port forwarding, am I correct?

There are logs indicating connection open and closed but the page is not loading.

The xxx.yyy.local is a masked domain and it will be resolved to ipv6 address.

I have even try to use IP directly instead of hostname, still no luck.

Listening on: 127.0.0.1:50001D

Received global request: hostkeys-00@openssh.com, no need to reply

New connection on: 127.0.0.1:50001

Sending forward channel open request: 0|- xxx.yyy.local:443

Received channel open confirmation: 0~0 WS 200000|2097152 MPS 32000|32768

Successfully established connection 127.0.0.1:50001 -> xxx.yyy.local:443

New connection on: 127.0.0.1:50001

Sending forward channel open request: 1|- unitedstates.smartscreen.microsoft.com:443

Sending channel close request: 0|0

Received channel close request: 0|0

Closed tunnel: 127.0.0.1:50001|:0

Received channel open confirmation: 1~1 WS 200000|2097152 MPS 32000|32768

Successfully established connection 127.0.0.1:50001 -> unitedstates.smartscreen.microsoft.com:443

New connection on: 127.0.0.1:50001

Sending forward channel open request: 0|- config.edge.skype.com:443

>> If so, what is connecting to it? (another entry from RDM, an external application?)

Yes, another entry from RDM (edge browser entry) with --proxy-server="socks5://127.0.0.1:50001" settings

>> and what proxy protocol is it setup to use? (SOCKS4, SOCKS4a or SOCKS5?)

SOCKS5 only

Hey @k526816,

In addition to Denis’s questions, could you please confirm whether there are any special characters used in the Host of your Port Forward entry?

Also, if possible, an export of your session (without including your credentials) would be very helpful for further troubleshooting.

Thanks in advance!