AWS APN Linux client 3.4.0 complains about a port clash when the problem is an incorrect verify-x509-name line

Hey. I am using the AWS VPN Client, found here https://docs.aws.amazon.com/vpn/latest/clientvpn-user/client-vpn-connect-linux.html. When I upgraded from 3.1.0 to 3.4.0 and downloaded an OpenVPN profile that has the verify-x509-name entry in it (which the version 3.4.0 added support of), the client failed to connect with a GUI message "The VPN process failed to start the port is already in use by another process". The logs also had an entry about ports (logs below). The new line was verify-x509-name VPN Server Name which is incorrect.

After removing the verify-x509-name entry from the OpenVPN file, this error disappeared. It seems something is broken in the client which makes the error misleading. Is there an official bug tracker for the client, I can submit this there.

Logs

2023-06-20 13:23:45.680 +03:00 [DBG] /sbin/sysctl stderr: 
2023-06-20 13:23:45.680 +03:00 [DBG] /sbin/sysctl exit code: 0
2023-06-20 13:23:45.680 +03:00 [DBG] [TI=11] IP forwarding disabled successfully
2023-06-20 13:23:45.680 +03:00 [DBG] [TI=11] Starting OpenVPN process with command: "/opt/awsvpnclient/Service/Resources/openvpn/acvc-openvpn" --config "/opt/awsvpnclient/Resources/eqhli2ms.r0d" --management 127.0.0.1 8096 "/opt/awsvpnclient/Resources/wjl5gj3r.p2x" --management-query-passwords --script-security 2 --up /opt/awsvpnclient/Service/Resources/openvpn/configure-dns --down /opt/awsvpnclient/Service/Resources/openvpn/configure-dns --up-restart --down-pre --push-peer-info --setenv UV_AWS_CLIENT_APP_VER 3.4.0
2023-06-20 13:23:45.681 +03:00 [DBG] [TI=5] Listening for OpenVPN output from [13037]
2023-06-20 13:23:45.685 +03:00 [DBG] [TI=5] [PID: 13037] Options error: Unrecognized option or missing or extra parameter(s) in /opt/awsvpnclient/Resources/eqhli2ms.r0d:18: verify-x509-name (2.4.5)
2023-06-20 13:23:45.685 +03:00 [DBG] [TI=5] [PID: 13037] Use --help for more information.
2023-06-20 13:23:45.762 +03:00 [DBG] /usr/bin/lsof stdout: 
2023-06-20 13:23:45.762 +03:00 [DBG] /usr/bin/lsof stderr: 
2023-06-20 13:23:45.762 +03:00 [DBG] /usr/bin/lsof exit code: 1
2023-06-20 13:23:45.762 +03:00 [DBG] [TI=11] Management port 8096 has been taken by another process
2023-06-20 13:23:46.779 +03:00 [DBG] /bin/ps exit code: 1
2023-06-20 13:23:46.779 +03:00 [ERR] [TI=11] Failed to get process owner of PID: -7. Stdout: , stderr: error: process ID out of range
Usage:
ps [options]
Try 'ps --help <simple|list|output|threads|misc|all>'
or 'ps --help <s|l|o|t|m|a>'
for additional help text.
For more details see ps(1).

2023-06-20 13:23:46.790 +03:00 [WRN] [TI=11] Exception occured checking process alive: System.Exception: Failed to get process owner of PID: -7
   at ACVC.GTK.Service.DBus.OvpnGtkService.GetProcessOwner(Int32 pid) in /home/ubuntu/Jenkins/workspace/GtkBuild/SecureConnectClient/ACVC.GTK.Service/DBus/OvpnGtkService.cs:line 319
   at ACVC.GTK.Service.DBus.OvpnGtkService.IsAliveAsync(Int32 pid) in /home/ubuntu/Jenkins/workspace/GtkBuild/SecureConnectClient/ACVC.GTK.Service/DBus/OvpnGtkService.cs:line 228
2023-06-20 13:23:46.791 +03:00 [DBG] [TI=31] Wait for OpenVPN processes to finish graceful shutdown
2023-06-20 13:23:46.797 +03:00 [DBG] [TI=31] All OpenVPN processes exited properly
2023-06-20 13:23:46.797 +03:00 [DBG] [TI=31] Finished waiting OpenVPN graceful shutdown. Proceed with killing any orphaned OpenVPN processes
2023-06-20 13:23:46.901 +03:00 [DBG] Orphaned process are alive: False
2023-06-20 13:23:46.901 +03:00 [DBG] [TI=31] Attempting to restore /etc/resolv.conf if /etc/resolv.conf.ovpnsave exists
2023-06-20 13:23:46.901 +03:00 [DBG] [TI=31] /etc/resolv.conf.ovpnsave not found