UCARP-based failover Bad Interface Name

Business solution to host your own OpenVPN server with web management interface and bundled clients.
Post Reply
hopa
OpenVpn Newbie
Posts: 3
Joined: Wed Mar 16, 2022 11:11 am

UCARP-based failover Bad Interface Name

Post by hopa » Wed Mar 16, 2022 11:44 am

Hi,

I try to evaluate the for future use before switching from fixed to subscriptions, so i followed this instructions https://openvpn.net/vpn-server-resource ... over-mode/
First Node runs as KVM, second node on a Bare-metal server.

On Testing Failover I got the following error on the secondary node:
Server Agent is inactive due to the following errors: {'errors': {'cs.https.ip_address': [('error', "LOCAL_ADDR enp1s0 : bad local address name or interface is not up; must be 'all', 'localhost', a local IP address, or an interface name: r: [Error: service failed to start due to unresolved dependencies: {'user'}.]....."}, 'last_restarted''}

The baremetal hasn't any interface enp1s0, it's interface name is enp3s4f0. On first node interface name is enp1s0.

Thanks in advance,
Pat

User avatar
openvpn_inc
OpenVPN Inc.
Posts: 1332
Joined: Tue Feb 16, 2021 10:41 am

Re: UCARP-based failover Bad Interface Name

Post by openvpn_inc » Wed Mar 16, 2022 11:57 am

Hello hopa,

I'd suggest changing it to 'whateveryourinterfacenameis' and see if that helps.
cd /usr/local/openvpn_as/scripts/
./sacli --key "cs.https.ip_address" --value "whateveryourinterfacenameis" configput
./sacli start

Kind regards,
Johan
Image OpenVPN Inc.
Answers provided by OpenVPN Inc. staff members here are provided on a voluntary best-effort basis, and no rights can be claimed on the basis of answers posted in this public forum. If you wish to get official support from OpenVPN Inc. please use the official support ticket system: https://openvpn.net/support

Post Reply