openvpn legacy migration issues (gw down)

[tessus]

In light of the deprecation notice in 25.7 (running OPNsense 25.7.3_7-amd64), I've been trying to migrate away from the legacy OpenVPN setup.

My current setup looks like this: WAN_OpenVPN (opt13), legacy OpenVPN client connection (ovpnc1), Interface assignment: opt13 -> ovpnc1
The WAN_OpenVPN GW is up and clients (several VMs) can access the Internet via this GW.

I have now created a new client instance (ovpnc2) in the new interface and deactivated the legacy connection. According to the VPN -> Connection Status and VPN -> Log File, the new connection is up and running. So far so good. After assigning this new connection to the WAN_OpenVPN interface: opt13 -> ovpnc2 the GW shows that it is down. In the dashboard it shows Loss: 100%.

Of course the clients can no longer access the Internet via the GW.

If I switch back ro the legacy connection (and change the interface assignment again), everything works again.

I checked the log files, but couldn't find any issues, so I am a bit stuck. I don't understand why the GW is complaining, even though the new VPN connection is up.

Can someone help me debug this further or maybe someone has experienced a similar issue and knows the solution. I am currently at my wits' end, since this situation makes no sense to me.

[tessus]

Due to this issue  I stopped using OpenVPN altogether and switched to Wireguard (luckily my VPN provider also supports wg, even though no official documentation exists).

This topic can be deleted.