[Resolved] openvpn-gui does not open anymore in vpn chain after update from 2020.2.16.0

Implemented

[Resolved] openvpn-gui does not open anymore in vpn chain after update from 2020.2.16.0

avatar

Hello all.

First i'll describe the connection.
I need to make RDPconnections through a SSH tunnel after connecting with OpenVPN to my office.
Each customer has 1 SSH connection from my office with a couple of tunnels for rdp.
The SSH connection can only be used from my office. And i have to use an OpenVPN connection from me to the office (i work from home)

1.First i made a VPN type "VPN - OpenVPN GUI" to the office.

2.For each customer i made 1 "SSH portforward" session type (with several portforwards), in the VPN properties of this session i have a VPN connection (type VPN link) to the VPN i made in the step before this.
I also tried to use the make a session "SSH tunnel" but this does not remedy the problem

3.For each customer i have several RDP sessions. In the VPN properties of each RDP session I have a VPN connection (type session) to the SSH port forward, made in the step above this. and the RDP sessions for each customer is in a VPN group.

in each step i have a delay in the VPN properties of 6 seconds to stabilize the connection first.

In version 2020.2.16.0 i could double click on the RDP session and first OpenVPN would start and when connected, the SSH tunnel with port forwards would be processed and the the RDP connection would be made.

But after updating to 2020.3.14.0 or 2020.3.18.0 the SSH tunnel with portforwards will be processed directly (and fail) without starting OpenVPN and thus RDP connection will fail.
Now i can only make the RDP connections when i first double click on the OpenVPN connection (step 1) and the on the RDP session.

Do any of you have tips? did i make the chain of connections wrong?

thanks for replying!



All Comments (7)

avatar

Hello,

We will do some testing on our side to figure out what's happening. In the mean time, is it possible for you to downgrade back to 2020.2.16.0 to verify if you can connect properly again?

Regards,

Hubert Mireault

avatar

i don't have version 2020.2.16.0 anymore so i downloaded 2020.2.20.0
i can't downgrade through the installer. it complains that a newer version is installed.
so i tried on different laptop where i didn't upgrade yet (still on 2020.2.16.0), and imported an export from 2020.3.18.0. and on that version is no problem.
so i imported back to the laptop with 2020.3.18.0 and problem is still there.

i also tried some logging, but i can't find any fault in logs

avatar

Hello,

Thank you for your detailed information, I was able to reproduce the issue and I've opened a ticket. We'll update this thread once we have a fix.

Regards,

Hubert Mireault

avatar

Hello,

After discussion, we decided that chaining VPNs shouldn't be the default behavior. So what we've done is we added an option in the Vault Settings called "allow VPN chaining with SSH entries". You will need to enable this option to have the behavior you had in the past. This will be available in RDM 2020.3.19.0.

Take note that if you're using Devolutions Server, you will need to wait for an update to release on that end as well.

Regards,

Hubert Mireault

avatar

hi!

Thank you for the quick fix!

I agree with you that VPN chaining does not win beauty contests but in my case i didn't see a work around.

i'll await the release!

avatar

after update to 2020.3.19.0 VPN chaining in combination with SSH entries works again,
thanks!

avatar

Glad to hear it works for you!

Regards,

Hubert Mireault