After changing the active node of the cluster, the VPN connection is not established

vyos v1.2.3

There is a cluster configuration and VPN pptp and l2tp
Configuration works clients are connected.
If the active node of the cluster changes as planned, or when the active node reboots, the clients stop connecting.
If i delete the configuration for pptp and l2tp and commit, then add the deleted sections and make commit again then clients will be able to connect.

In version 1.1.8, in the cluster section, i can add
service ipsec
service pptpd
service xl2tpd
And it worked

There are no pptpd and xl2tpd services in the current version, but the addition service accel-ppp but it does not worked.

Please help solve the problem.

An example of my configuration:
cluster {
dead-interval 20000
group cluster {
auto-failback false
primary rt01
secondary rt02
service 10.x.x.12/23/eth1
service 212.x.x.19/28/eth0
service ipsec
service accel-ppp
}
interface eth1
keepalive-interval 5000
monitor-dead-interval 20000
pre-shared-secret PreSharedSecret
}

vpn {
ipsec {
ipsec-interfaces {
interface eth0
}
nat-networks {
allowed-network 0.0.0.0/0 {
}
}
nat-traversal enable
}
l2tp {
remote-access {
authentication {
mode radius
radius {
server 10.x.x.3 {
key RadiusPresharedKey
}
server 10.x.x.2 {
key RadiusPresharedKey
}
}
}
client-ip-pool {
start 10.x.y.50
stop 10.x.y.149
}
dns-servers {
server-1 10.x.x.2
server-2 10.x.x.3
}
idle 1800
ipsec-settings {
authentication {
mode pre-shared-secret
pre-shared-secret PreSharedSecret
}
ike-lifetime 3600
lifetime 3600
}
outside-address 212.x.x.19
outside-nexthop 10.x.y.1
}
}
pptp {
remote-access {
authentication {
mode radius
radius {
server 10.x.x.3 {
key RadiusPresharedKey
}
server 10.x.x.2 {
key RadiusPresharedKey
}
}
}
client-ip-pool {
start 10.x.y.150
stop 10.x.y.249
}
dns-servers {
server-1 10.x.x.2
server-2 10.x.x.3
}
gateway-address 10.x.y.1
outside-address 212.x.x.19
}
}
}

Hello @rodikov, did you build 1.2.3 for yourself? Accel-ppp not used in 1.2.3 for pptp and l2tp. Can you provide output of command show version

Hello @Dmitry.
Yes, I built 1.2.3 myself according to the instructions with git.
Version: VyOS 1.2.3
Built by: rodikov
Built on: Wed 09 Oct 2019 11:38 UTC
Build UUID: 26d6e0ce-9794-46e6-9a6d-0485d8e892d6
Build Commit ID: 46f9b2ab60e4fa

Architecture: x86_64
Boot via: installed image
System type: Microsoft Hyper-V guest

Hardware vendor: Microsoft Corporation
Hardware model: Virtual Machine
Hardware S/N: 1321-2473-2213-0729-8385-4783-79
Hardware UUID: 403e1e1a-a237-f143-899b-44aff8fd5afd

Copyright: VyOS maintainers and contributors

This is not 1.2.3, you was build image from current branch, also called as rolling releases. Date of this commit 6 Oct 2019. I want reproduce your schema in our LAB. I will tell you when I have result.

Thanks, @Dmitry. I build I collected the image using the command:
./configure --build-type release --architecture amd64 --version 1.2.3 --build-by “rodikov”.
Maybe I need to rebuild the image differently and check?

You need use crux branch if you want build stable release.

Well, I will try and report the result later.

I tried in 1.2.3, all works as expected. Also I will create task on phabricator for recovery this feature for 1.3 rolling.

I used crux branch for build stable release. The pptpd and xl2tpd services are in place. Now everything works as expected. Thanks for the help.