OpenVPN Connect doesn't fail over to second remote entry, but OpenVPN Community does
-
Hi all,
Our company recently added a second ISP (fiber) for Internet redundancy, so I've been working on implementing client-side failover for our OpenVPN VPN service hosted on pfSense.
Two ISPs (WAN1 – cable and WAN2 - fiber)
I created a pair of new OpenVPN servers - one listening on WAN1 and the other on WAN2. Both servers work perfectly when tested independently.
The exported client profile contains two remote entries, one for each WAN:
remote WAN2-IP 1194 udp4
remote WAN1-IP 1194 udp4
The issue
When I disable the WAN2 interface on pfSense, OpenVPN Connect 3.8.0 continuously retries the first remote entry. It times out, restarts, and immediately retries WAN2 again. It never attempts the second remote entry.
However, if I import the exact same profile into OpenVPN Community Edition (GUI) 2.7.5, it behaves exactly as I expected - it times out on WAN2 and then automatically switches to WAN1 and connects successfully.
I'm sure I'm overlooking something.
Any suggestions would be greatly appreciated. Thanks!pfsense: 25.07.1
OpenVPN: 2.6.14 -
Never mind. It was a bad software installation. Once the 3.8.0 being removed and the 3.9.0 being installed, the problem was gone. 3.8.0 on another station is working fine too. Thanks.
Privacy Policy · Cookie Policy