Page 1 of 1
Version 3.4.1 (4522) did not work / M1 chip Ventura
Posted: Tue Dec 20, 2022 1:59 am
by M.Edremit
Hello,
Version 3.4.1 (4522) did not work. There is an error message [Transport error:socked_protect error]. I can connect with my iOS iphone device. Not working on my MACOS Ventura M1 Pro.
I will wait for your support and guidance for the solution.
Thanks.
Re: Version 3.4.1 (4522) did not work / M1 chip Ventura
Posted: Tue Dec 20, 2022 12:58 pm
by openvpn_inc
Hello M.Edremit,
I would suggest uninstalling OpenVPN Connect, rebooting the mac device, then downloading and install OpenVPN Connect, and trying again. If it still fails, reboot, and then try again. If that still fails, we'll likely have to gather some logs to figure out what's blocking things in your particular setup. We have tested OpenVPN Connect 3.4.1 4522 on macOS with Ventura and M1 chip and found it to be working. But there may be something in your configuration or setup that blocks it somehow.
Kind regards,
Johan
Re: Version 3.4.1 (4522) did not work / M1 chip Ventura
Posted: Wed Jan 04, 2023 2:52 am
by M.Edremit
Hi again Johan,
Error Log Information
Transport Error: socket_protect error (UDP)
what should I do?
Re: Version 3.4.1 (4522) did not work / M1 chip Ventura
Posted: Wed Jan 04, 2023 3:40 am
by M.Edremit
sudo /Library/Frameworks/OpenVPNConnect.framework/Versions/Current/usr/sbin/ovpnagent
I solved it with this command. Maybe it will help you for permanent solution.
Re: Version 3.4.1 (4522) did not work / M1 chip Ventura
Posted: Thu Jan 12, 2023 3:39 pm
by openvpn_inc
Hello M.Edremit,
Upon startup that process should be started. Did you restart?
Kind regards,
Johan
Re: Version 3.4.1 (4522) did not work / M1 chip Ventura
Posted: Mon May 29, 2023 9:15 pm
by rubavz
M.Edremit wrote: ↑Wed Jan 04, 2023 3:40 am
sudo /Library/Frameworks/OpenVPNConnect.framework/Versions/Current/usr/sbin/ovpnagent
I solved it with this command. Maybe it will help you for permanent solution.
Indeed this solution works perfect, the question is why ... it works the first time but not after reboot do I need to keep my laptop suspended always to avoid this issue?