Issue with OpenVPN for IOS 3.4.0

[Beno44]

Afternoon,

Since upgrading to OpenVPN 3.4.0 the below config keeps failing (No issue with the previous version).

dev tun
proto udp
cipher AES-128-CBC
comp-lzo
client
remote xxxx.xxxx.xxxx.xxxx 1194
persist-key
status-version 3
verb 3
resolv-retry infinite
ns-cert-type server
nobind

<ca>

Error message is:

Connection Failed

There was an error attempting to connect to the selected server.

Error Message: option_error: sorry, unsupported options present in the configuration: UNKNOWN/UNSUPPORTED OPTIONS.


Logs are as follow:

⏎[Oct 20, 2023, 14:12:30] Performance stats on disconnect:
CPU usage (microseconds): 4088121
Network bytes per CPU second: 0
Tunnel bytes per CPU second: 0
⏎[Oct 20, 2023, 14:12:44] OpenVPN core 3.8.1 mac x86_64 64-bit built on Aug 23 2023 04:17:34
⏎[Oct 20, 2023, 14:12:44] Frame=512/2112/512 mssfix-ctrl=1250
⏎[Oct 20, 2023, 14:12:44] NOTE: This configuration contains options that were not used:
⏎[Oct 20, 2023, 14:12:44] Unsupported option (ignored)
⏎[Oct 20, 2023, 14:12:44] 6 [persist-key]
⏎[Oct 20, 2023, 14:12:44] 9 [resolv-retry] [infinite]
⏎[Oct 20, 2023, 14:12:44] UNKNOWN/UNSUPPORTED OPTIONS
⏎[Oct 20, 2023, 14:12:44] 7 [status-version] [3]
⏎[Oct 20, 2023, 14:12:47] Raw stats on disconnect:


Any suggestions would be amazing ;o)

[Beno44]

Should add that this config works with TunnelBlick.

[Beno44]

Is there any other IOS app where you can upload your own ovpn file (similar to OpenVPN I guess)?

[openvpn_inc]

Hello Beno44,

The issue you have encountered is caused by using a server directive on a client. That is not valid. You can use another client, and maybe you'll get lucky. But the issue is that the directive used is simply not valid for a client. So the best solution is to fix that.

From the reference manual:

--status-version n
Set the status file format version number to n.
This only affects the status file on servers with multi-client capability enabled.

Since a server directive is totally invalid in a client configuration, please remove that line from your client configuration profile. It should then work.

Kind regards,
Johan