Hi there! I'm running the OpenVPN Appliance 2.5 on Hyper-V (pre-installed *.vhd) and i want to setup a failover pair. The single server works perfectly, but i can't get the failover configuration to work. I did the following steps: [list]Setup first node 10.x.x.28, testing VPN functionality => all fine[/list] [list]Setup second node 10.x.x.29 following this guide https://docs.openvpn.net/configuration/setting-up-high-availability-failover-mode . The only difference is, that i have allowed root user for SSH[/list] [list]Go back to the admin gui on 1st node "Configuration => Failover and enter ip-addr. of the two nodes and the cluster ip 10.x.x.30 [/list] [list]Hit the "Validate" button, all test shows "GOOD"[/list] [list]GUI shows the success message "Access Server is restarting"[/list] After this, nothing happens and the primary server doesn't restart. After later manual restart of the primary node, the admin GUI isn't accessible any longer (neither on the .28 nor on the cluster ip). It seems that the config hast not been applied properly. Any ideas? Many thanks liceo

Setup failover mode doesn't work after hit "Commit & Restart"

liceo

Hi there!

I'm running the OpenVPN Appliance 2.5 on Hyper-V (pre-installed *.vhd) and i want to setup a failover pair. The single server works perfectly, but i can't get the failover configuration to work.

I did the following steps:

Setup first node 10.x.x.28, testing VPN functionality => all fine

Setup second node 10.x.x.29 following this guide https://docs.openvpn.net/configuration/setting-up-high-availability-failover-mode . The only difference is, that i have allowed root user for SSH

Go back to the admin gui on 1st node "Configuration => Failover and enter ip-addr. of the two nodes and the cluster ip 10.x.x.30

Hit the "Validate" button, all test shows "GOOD"

GUI shows the success message "Access Server is restarting"

After this, nothing happens and the primary server doesn't restart. After later manual restart of the primary node, the admin GUI isn't accessible any longer (neither on the .28 nor on the cluster ip). It seems that the config hast not been applied properly.

Any ideas?

Many thanks

liceo

The Johan

Please upgrade to 2.5.2.

liceo

Yep cool, 2.5.2 seems to work!

Many thanks!

The Johan

No problem, have a nice day.