Comment 10 for bug 1677198

I understand this is an upstream bug. I'll just write this here anyway, will post bug upstream later if nobody beats me to it.

Affects me too. The imported config said aes-256-cbc. That was read in as BF-something-or-other. Blowfish, not AES. After setting that to AES-256-CBC, the thing connects.

After some time, the following happens:

nm-openvpn[3577]: [integrity] Inactivity timeout (--ping-restart), restarting
nm-openvpn[3577]: SIGUSR1[soft,ping-restart] received, process restarting
nm-openvpn[3577]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
nm-openvpn[3577]: TCP/UDP: Preserving recently used remote address: [AF_INET]<ip address>:<port>
nm-openvpn[3577]: UDP link local: (not bound)
nm-openvpn[3577]: UDP link remote: [AF_INET]<ip address>:<port>
nm-openvpn[3577]: [integrity] Peer Connection Initiated with [AF_INET]<ip address>:<port>
nm-openvpn[3577]: Preserving previous TUN/TAP instance: tun0
nm-openvpn[3577]: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 0 3573 --bus-name org.freedesktop.NetworkManager.openvpn.Connection_8 --tun -- tun0 1500 1558 <ip address> <mask> restart
nm-openvpn[3577]: WARNING: Failed running command (--up/--down): could not execute external program
nm-openvpn[3577]: Exiting due to fatal error
NetworkManager[667]: <error> [1496682880.1314] platform-linux: do-add-ip4-route[8: 0.0.0.0/0 50]: failure 101 (Nätverket kan inte nås)

It seems that nm-openvpn fails. Ideas on what to do?