Error calling protect method on socket [Mac M1]

[alexsmartens]

This issue is related to https://github.com/OpenVPN/openvpn3/issues/139 which was unfortunately closed without anyone attempting to solve it.

I'm seeing this problem on an M1 Mac. OpenVPN Connect 3.3.6 (4368): Error calling protect () method on socket. Here's my log:

[Sep 15, 2022, 07:17:13] EVENT: RESOLVE
[Sep 15, 2022, 07:17:13] Contacting
XXX.XXX.XXX.XXX:1194 via UDP
[Sep 15, 2022, 07:17:13] EVENT: WAIT
[Sep 15, 2022, 07:17:13] UnixCommandAgent:
transmitting bypass route to
/var/run/agent_ovpnconnect.sock
"host": "XXX.XXX.XXX.XXX"
"ipv6": false,
"pid": 11202
[Sep 15, 2022, 07:17:13] Transport Error:
socket_protect error (UDP)
[Sep 15, 2022, 07:17:13] Client terminated
restarting in 2000 ms...

[alexsmartens]

The OpenVPN community would really appreciate if someone could take care of fixing the above problem.

For now, @antonb-taod suggested a good temporary fix that worked for me:

I don't know what issue other have, but I was able to solve mine today.

I was getting an error calling protected() method and same logs as mentiones above. I figured out that the file /var/run/agent_ovpnconnect.sock didn't exist and apparently the problem was that for any reason the ovpn agent wasn't running. To solve this I had to start /Library/Frameworks/OpenVPNConnect.framework/Versions/Current/usr/sbin/ovpnagent manually (I'm using macOS M1 12.2.1).

Hope it will help someone.

[ordex]

This bug tracker is about the OpenVPN3 library. For problems with OpenVPN Connect (that is a commercial product), please go to https://openvpn.net/support

[strayon]

I resolved this issue by revisiting OpenVPN's startup settings in "Settings > General > Login Items" and re-enabling it. Previously, I had unchecked it in the startup section.

[georganix]

Thank you @strayon that helped. Also, when entering the username in the VPN some servers require a prefix DOMAIN\userhandler. I also removed the DOMAIN\ portion and connected immediately.

[diereysaa]

In my case (MacOS Sonoma 14.1.2 on M2) the solution proposed by @antonb-taod and posted by @alexsmartens worked like a charm. Just needed to add sudo to it and the ampersand for leaving the daemon running in the background:

sudo /Library/Frameworks/OpenVPNConnect.framework/Versions/Current/usr/sbin/ovpnagent &

[hemanthshopflo]

In my case (MacOS Sonoma 14.1.2 on M2) the solution proposed by @antonb-taod and posted by @alexsmartens worked like a charm. Just needed to add sudo to it and the ampersand for leaving the daemon running in the background:

sudo /Library/Frameworks/OpenVPNConnect.framework/Versions/Current/usr/sbin/ovpnagent &

@diereysaa i tried in mac M2 its not working, can u suggest a better way.

[diereysaa]

@diereysaa i tried in mac M2 its not working, can u suggest a better way

Hmmm, I guess I forgot to mention that my own proposed solution didn't work for me to leave working in the background. I'm using Zsh and have an alias like this:

alias openvpn='sudo /Library/Frameworks/OpenVPNConnect.framework/Versions/Current/usr/sbin/ovpnagent'

Without the ampersand at the end, and leaving the console window running the background:

However, some times it gets stuck somehow, so it's a matter of cancelling (Ctrl+C) the background process and restarting it.

Hope you get it fixed and running soon :)

[free521521521]

I resolved this issue by revisiting OpenVPN's startup settings in "Settings > General > Login Items" and re-enabling it. Previously, I had unchecked it in the startup section.

It works for me. Actually I realise the login item right after the app installation, I closed all of them immediately. That make the app not work.

[vd-eerkul]

In my case (MacOS Sonoma 14.1.2 on M2) the solution proposed by @antonb-taod and posted by @alexsmartens worked like a charm. Just needed to add sudo to it and the ampersand for leaving the daemon running in the background:

sudo /Library/Frameworks/OpenVPNConnect.framework/Versions/Current/usr/sbin/ovpnagent &

sudo /Library/Frameworks/OpenVPNConnect.framework/Versions/Current/usr/sbin/ovpnagent

worked without &, terminal need still while connecting it.

[fabiodepaula7]

In my case (MacOS Sonoma 14.1.2 on M2) the solution proposed by @antonb-taod and posted by @alexsmartens worked like a charm. Just needed to add sudo to it and the ampersand for leaving the daemon running in the background: sudo /Library/Frameworks/OpenVPNConnect.framework/Versions/Current/usr/sbin/ovpnagent &

sudo /Library/Frameworks/OpenVPNConnect.framework/Versions/Current/usr/sbin/ovpnagent

worked without &, terminal need still while connecting it.

You can do this enabling Settings->General->Login Itens->Allow in Background->OpenVPN Client.

[RamdlanFaqih]

I resolved this issue by revisiting OpenVPN's startup settings in "Settings > General > Login Items" and re-enabling it. Previously, I had unchecked it in the startup section.

it works !

[JackPala]

I resolved this as well by re-adding as a login item and giving it background access.

That being said, having an app that is required to be a startup item in order to function is a bug.

[schwabe]

@JackPala please reports the bug at support.openvpn.net. The connect team unfortunately completely ignores github issues.