We traced the error to be caused by clock drift on the core AS in ISD 20.
The problem is now solved with the core AS 20-ffaa:0:1401 producing again valid Beacons.
The fix was tested with a separate AS connected to the same parent AS you are.
You AS is not reachable from the attachment point.
Can you confirm that the VPN client is running on your side? (`systemctl status openvpn@client`)
And that you can ping the VPN server through the tunnel?
`ping 10.0.8.1`
Best regards