Hi Using Debian 13 myself.
Editing the NMconnection file and adding "data-ciphers=AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305:AES-128-CBC" does solve the connection issue however....
The real bug seems to relate to the fact NetworkManager must be restarted before trying the connection, preferably stopped then restarted after modifying the file.
In some cases the connection vanishes from NM however it still appears in the systemconnections directory. Go figure?
The import option is a bit of a mess, it misses the whole section for TLS and adds the port to the file name which then seems to corrupt the import. My solution is to create a basic OpenVPN connnection, Stop NM, edit the file, start NM and pray!
A template for import would be useful as I can't fathom the file structure or fields required.
Example of one of my working configs. [connection] id=us-la2-smart.serverlocation.co uuid=bd3e845a-f09e-4a31-b94e-108d72dc6d39 type=vpn [vpn] auth=SHA256 ca=/VPN/serverlocation.crt cipher=AES-256-CBC data-ciphers=AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305:AES-256-CBC connection-type=password dev-type=tun float=no mssfix=no ns-cert-type=server password-flags=1 port=1194 proto-tcp=yes remote=us-la2-smart.serverlocation.co remote-random=no ta=/VPN/tls.crt ta-dir=1 tun-ipv6=no tunnel-mtu=1500 username=harryharry service-type=org.freedesktop.NetworkManager.openvpn [ipv4] method=auto [ipv6]
